whenever I load xmms, i get a repeating GLib error which repeats itself continuously for maybe 5secs then xmms loads seemingly correctly. i tried remerging glib then xmms, but this made no difference. Reproducible: Always Steps to Reproduce: 1. type xmms on the command line 2. 3. Actual Results: The following message is repeatedly sent to standard out for about 5secs "GLib-CRITICAL **: file gtree.c: line 209 (g_tree_lookup): assertion `tree != NULL' failed." Expected Results: just opened without hanging for 5secs while giving me error messages Portage 2.0.50-r6 (default-x86-1.4, gcc-3.3.2, glibc-2.3.2-r9, 2.4.24) ================================================================= System uname: 2.4.24 i686 Mobile Intel(R) Pentium(R) 4 - M CPU 2.00GHz Gentoo Base System version 1.4.8 distcc 2.13 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [disabled] ccache version 2.3 [enabled] Autoconf: sys-devel/autoconf-2.58-r1 Automake: sys-devel/automake-1.8.3 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-march=pentium3 -O3 -pipe" CHOST="i686-pc-linux-gnu" COMPILER="gcc3" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3.2/share/config /usr/kde/3/share/config /usr/lib/mozilla/defaults/pref /usr/share/config /usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/ /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O2 -mcpu=i686 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs ccache sandbox" GENTOO_MIRRORS="http://mirror.aarnet.edu.au/pub/gentoo http://gentoo.oregonstate.edu http://www.ibiblio.org/pub/Linux/distributions/gentoo" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="" SYNC="rsync://localhost/gentoo-portage" USE="X aalib acpi alsa apache2 arts avi berkdb bonobo cdr crypt cups dvd encode esd ethereal foomaticdb gdbm gif gnome gpm gtk gtk2 gtkhtml guile imlib java jpeg kde libg++ libwww mad mikmod motif mozilla mpeg mysql ncurses nls oggvorbis opengl oss pam pcmcia pdflib perl plotutils png pnp python qt quicktime readline samba slang spell sse ssl svga tcpd tetex truetype usb video_cards_radeon x86 xml2 xmms xv zlib"
I would like to add that these errors will not occur if xmms is run as root.
what xmms plugins do you have installed? You can do: qpkg -I -v -f /usr/lib/xmms Try removing some of the plugins (just move them to a temp dir for testing) to figure out which one is causing the problem.
[root@david /usr/lib/xmms] #qpkg -I -v -f /usr/lib/xmms media-libs/flac-1.1.0 * media-plugins/alsa-xmms-0.9.12 * media-plugins/xmms-arts-0.7.1-r1 * media-sound/xmms-1.2.10-r1 * [root@david /usr/lib/xmms] # I tried moving the Input/libxmms-flac.*, then Output/libALSA.* and Ouput/libarts.* to my home dir and then reloading xmms like u suggested and the error still occurs every time. I'm assuming that the error is the xmms code itself or with one of the default plugins. it works properly as root just like the last poster mentioned - maybe its a permissions thing
odd... I get no messages at all, and I have a ton of plugins installed: (20:57:04 Mon Apr 19 2004 jeremy@eradicator) ~ $ xmms (20:57:12 Mon Apr 19 2004 jeremy@eradicator) ~ $ you can remove alsa-xmms, btw. It's been removed from portatge since it was included in xmms-1.2.8 and later. The only thing drastically different on my system is that I use '-O2' instead of '-O3'. Since it "seems to load correctly," I'm going to close this bug, but if you figure out what is causing it, please reopen.
Same error here... Perhaps the following link might be interesting: http://bugs.xmms.org/long_list.cgi?buglist=1738 There it says that this error comes from one of the gentoo-patches (but they do not say which one)
Shardik, you're experiencing a differnet problem. This bug report was for warning messages because of glib-2.4. You are segfaulting with glib 2.2. Please open a new bug report, and try commenting out all the patches in the ebuild to see if it is indeed becasue of a gentoo patch.
