Hi,
Could you paste the output of 'xmms2 info 7069' ? (According to the
playlist entry, 7069 should be the id of the file you added)
The id3ed output seems to indicate that the file also has an id3v1
header. XMMS2 extracts both the id3v1 and id3v2 metadata and stores
them in the medialib. The xmm
Package: aptitude
Version: 0.6.1.3-3
Severity: normal
When using the curses interface, pressing + on a section still marks all
packages for update, even those that are held.
-- Package-specific info:
aptitude 0.6.1.3 compiled at Nov 20 2009 15:39:26
Compiler: g++ 4.3.4
Compiled against:
apt ver
Package: aptitude
Version: 0.6.1.3-3
Severity: normal
When using the curses interface, pressing + on a section still marks all
packages for update, even those that are held.
-- Package-specific info:
aptitude 0.6.1.3 compiled at Nov 20 2009 15:39:26
Compiler: g++ 4.3.4
Compiled against:
apt ver
Package: aptitude
Version: 0.6.1.3-3
Severity: normal
When using the curses interface, pressing + on a section still marks all
packages for update, even those that are held.
-- Package-specific info:
aptitude 0.6.1.3 compiled at Nov 20 2009 15:39:26
Compiler: g++ 4.3.4
Compiled against:
apt ver
I think that's a bug in the libxmmsclient++-dev package. The
dependency on boost comes from the xmms2 c++ bindings, so
xmms2-client-cpp.pc should contain the corresponding -l statement.
Current upstream xmms2 dropped the runtime dependency on boost. So
this bug will be fixed by the next xmms2 vers
On Fri, Nov 6, 2009 at 12:03 AM, Florian Reck wrote:
> You said that the current version of promoe was compiled using an older
> version of libboost-singals, so I removed the libboost-signals package
> and installed the older version 1.39, but it won't work:
I might have been a bit unclear. The p
The problem has to do with boost.
The current libboost-signals-dev package in debian is 1.40, while
libxmmsclient++3 was build against 1.39.
When promoe is stated, the dynamical linker uses the boost 1.39 shared
library, which doesn't work correctly in this case.
The best way to fix this in my op
Hi,
To get visualization working you need to add the visualization plugin
to the effect order. This is done through the config system of xmms2.
On my system 'xmms2 config_list | grep effect' returns
effect.order.0 = visualization
effect.order.1 = equalizer
effect.order.2 =
The visualization can
versions of libxmms2clientN and the other
way round
regards,
Thomas Frauendorfer
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
xmms2 has no esound output plugin, as nobody wrote one yet.
But you could try to use the libao output plugin and configure ao to
output to esd.
(According to the libao2 description that should be possible)
Or you could try to use pulse
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists
Hi,
now I managed to crash irssi with the following sequence:
/load otr
/load xmpp
/xmppconnect -ssl @jabber.ccc.de
/unload otr
Backtrace:
#0 0xb7a8d556 in raise () from /lib/libc.so.6
#1 0xb7a8ed78 in abort () from /lib/libc.so.6
#2 0xb7ac7a6d in __libc_message () from /lib/lib
Hi,
I compiled some of the libs with -O0 -g
Using
/load xmpp
/xmppconnect -ssl @jabber.ccc.de
/load otr
/unload xmpp
I get this backtrace:
#0 0xb7ae2556 in *__GI_raise (sig=6)
at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#1 0xb7ae3d78 in *__GI_abort () at abort.c:88
#2 0xb7b1ca6d in __l
The above link didn't work for me.
A working link to the psi forum is:
http://psi-im.org/forum/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
The Bug is easy to fix. Either one off the two patches fixes it.
handle_message_without_type.diff only fixes the problem I reported,
while handle_all_unknown_types_as_normal.diff fixes the code, so that
it complies with the rfc section I mentioned before
Index: src/core/xmpp-protocol.c
==
Package: irssi-plugin-xmpp
Version: 0.13+cvs20080121-1
Severity: normal
irssi-plugin-xmpp ignores messages, if they don't contain a 'type'
attribute.
rfc3921 states in 2.1.1. 'Types of Message':
"if an application receives a message with no 'type' attribute or the
application does not understand
Hi,
After another look at the Bug I sent, I found out, that the real Problem lies
in QAbstractScrollArea.
If the QAbstractScrollArea is hidden while the custom QScrollButton is
inserted, the show() method of the QScrollButton must be called to make it
visible.
The attachment demonstrates the
Package: libqt4-gui
Version: 4.3.1-2
Severity: normal
When loading a custom scrollbar to a QAbstractItemView via
setVerticalScrollBar or setHorizontalScrollBar, the scrollbar will no
longer be displayed correctly, as soon as a new model is loaded through
setModel.
The attached file demomstrates t
Package: dirmngr
Version: 0.9.2-1
Severity: normal
On updating dirmngr I got the following error:
dirmngr[6427]: Fatal: libksba is too old (need 0.9.11, have 0.9.8)
Updating libksba8 to version 0.9.11-1 solved the problem, so dirmngr
should declare a versioned dependendy on libksba8 (>= 0.9.11-1)
Shouldn't a simple recompile be sufficient?
pgpLi4zTbksYf.pgp
Description: PGP signature
19 matches
Mail list logo
