Since my last "emerge -u world", which included xmms-1.2.10-r13, I have been unable to start xmms without a segfault. (It was already running at the time of the upgrade, and could play things, but it has refused to start up since I closeed it.) I have tried moving ~/.xmms to ~/.xmms.bak to see if it was anything in my config files, to no avail. I tried using the "debug" USE flag and running it through gdb, but apparently the debug USE flag doesn't add "-g" to the CFLAGS (which is the subject for another bug, not this one), so I copied the ebuild directory to my overlay and got it to inherit "debug", then tried again. This worked, and the output will be attached as a separate file to this bug. I can't figure out from the output where exactly the problem lies, so I'm submitting it here. My /usr/lib/xmms/ directory listing is also attached to this bug. Should I rename the plugins to add ".bak" on the end, then try renaming them back one-by-one until it fails to load? Note that I haven't tried this yet so it may not even be the cause of the problem. Also, xmms loads fine as the root user, or indeed, any other non-priviliged user - it's just when loaded as my normal user that it segfaults. Please bear in mind that I have already renamed my ~/.xmms directory, so it wouldn't seem to by my personal configuration. Also, using mplayer to access XMMS plugins works fine. Thanks! Reproducible: Always Steps to Reproduce: 1. For me, it's just one step: Launch xmms as my normal user. I don't know enough about the problem to say if it happens on other computers. Actual Results: xmms segfaults with the error shown above. Expected Results: xmms should have loaded normally. Portage 2.0.51.19 (default-linux/x86/2005.0, gcc-3.3.5-20050130, glibc-2.3.4.20041102-r1, 2.6.9-gentoo-r9 i686) ================================================================= System uname: 2.6.9-gentoo-r9 i686 Intel(R) Pentium(R) 4 CPU 1400MHz Gentoo Base System version 1.4.16 Python: dev-lang/python-2.3.4-r1 [2.3.4 (#1, Feb 8 2005, 02:51:43)] distcc 2.16 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [disabled] ccache version 2.3 [enabled] dev-lang/python: 2.3.4-r1 sys-devel/autoconf: 2.59-r6, 2.13 sys-devel/automake: 1.7.9-r1, 1.8.5-r3, 1.5, 1.4_p6, 1.6.3, 1.9.4 sys-devel/binutils: 2.15.92.0.2-r7 sys-devel/libtool: 1.5.14 virtual/os-headers: 2.6.8.1-r2 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-O2 -mcpu=i686 -pipe" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.3/env /usr/kde/3.3/share/config /usr/kde/3.3/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/share/config /var/bind /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig ccache distlocks sandbox sfperms strict" GENTOO_MIRRORS="http://www.mirrorservice.org/sites/www.ibiblio.org/gentoo/ http://ftp.belnet.be/mirror/rsync.gentoo.org/gentoo/ http://distfiles.gentoo.org/" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/home/ciaran/portage/overlay" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="x86 X acpi alsa apm avi berkdb bitmap-fonts cdr crypt cups curl dga divx4linux dvd emboss encode esd fam flac foomaticdb fortran gd gdbm gif gmail gnome gphoto2 gpm gstreamer gtk gtk2 imagemagick imlib ipv6 jack java jbig joystick jpeg kde kdeenablefinalladspa libg++ libwww mad mikmod mmx motif mp3 mpeg multitarget mysql ncurses nls nodrm nptl ogg oggvorbis opengl oss pam pdflib perl pic png povray ppds python qt quicktime readline real samba sdl slang sse ssl svga tcpd tiff truetype truetype-fonts type1-fonts v4l vorbis xml2 xmms xv zlib" Unset: ASFLAGS, CBUILD, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS
Created attachment 56921 [details] Output of gdb running xmms (with debugging symbols) This contains the output of the "bt full" command as well.
Created attachment 56922 [details] File listing of /usr/lib/xmms/ (ls -lR)
Quick update - it appears that logging out and logging back in fixes this. I'm not altogether sure why but it's probably something I should have done in the first place. I'm not sure whether this still classifies it as a "bug" or just "temporary problem". I'll leave it open in case you want any more information about my setup, but it appears that the problem itself is fixed.
I had forgotten this bug was still open. This should probably be closed, as it's more or less dead. I'm now on xmms-1.2.10-r15 and I haven't had this problem occur again, so at worst it's a very intermittent problem, and at best it was a temporary problem with my system. I consider this bug closed, but I'll let the devs decide if it is or not.
Ok i'm closing this bug. If you continue to have the same problem reopen. Thanks for the feedback
