Version: unknown (using KDE 3.3.0, Gentoo) Compiler: gcc version 3.4.1 20040803 (Gentoo Linux 3.4.1-r2, ssp-3.4-2, pie-8.7.6.5) OS: Linux (i686) release 2.6.8-gentoo-r4 Sometimes the "splash" comes up (where it attempts to scan for mp3's) but then a SIGABRT window appears The following gdb output appears Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 1104460656 (LWP 13913)] 0xffffe410 in ?? () #0 0xffffe410 in ?? () #1 0x0827f6c8 in ?? () #2 0x00000000 in ?? () #3 0x00000000 in ?? () #4 0x41a01fa3 in __waitpid_nocancel () from /lib/libpthread.so.0 #5 0x40eace00 in KCrash::defaultCrashHandler () from /usr/kde/3.3/lib/libkdecore.so.4 #6 0x00000000 in ?? () #7 0x00000000 in ?? () #8 0xbffff1f0 in ?? () #9 0x0828e808 in ?? () #10 0xbfffee88 in ?? () #11 0x4131617f in QWidget::event () from /usr/qt/3/lib/libqt-mt.so.3 I tried deleting "app" settings and "config" (jukrc) and associated files from the ".kde3.3" directory to see if this might have been caused by a borked config file but this has not made any difference. Nick...
Could you try building JuK with debugging symbols? Unfortunately there's not really anything useful in this backtrace.
I've the same problem on my notebook [asus M3000N] juk 2.1 kde 3.3.0 linux vanilla 2.6.9 gcc version 3.4.2 (Gentoo Linux 3.4.2-r2, ssp-3.4.1-1, pie-8.7.6.5) output if launched from a shell: bash-2.05b$ juk XRender juk: ERROR: Communication problem with juk, it probably crashed. bash-2.05b$ ozzo
Yes ... I get the same error from the shell prompt too .... glad that im not the only one with this problem Nick... On Monday 25 October 2004 16:31, Alberto Viale wrote: > ------- You are receiving this mail because: ------- > You reported the bug, or are watching the reporter. > > http://bugs.kde.org/show_bug.cgi?id=90411 > > > > > ------- Additional Comments From ozzozzo libero it 2004-10-25 18:31 > ------- I've the same problem on my notebook [asus M3000N] > > juk 2.1 > kde 3.3.0 > linux vanilla 2.6.9 > gcc version 3.4.2 (Gentoo Linux 3.4.2-r2, ssp-3.4.1-1, pie-8.7.6.5) > > output if launched from a shell: > bash-2.05b$ juk > XRender > juk: ERROR: Communication problem with juk, it probably crashed. > bash-2.05b$ > > ozzo
Actually that's just a generic KDE error message that happens any time that an application crashes on startup, basically. There's still not anything that I can do with this at the moment without a valid backtrace.
I've got exactly the same problem after I updated to KDE 3.3.1 last week. Completely deleting the configuration files did not help. gcc-Version 3.4.2 (Gentoo Linux 3.4.2-r2, ssp-3.4.1-1, pie-8.7.6.5) After recompiling kdemultimedia with debugging symbols turned on I get the following backtrace: ----------- Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 16384 (LWP 1165)] 0x41a423f8 in waitpid () from /lib/libpthread.so.0 #0 0x41a423f8 in waitpid () from /lib/libpthread.so.0 #1 0x40face78 in ?? () from /usr/kde/3.3/lib/libkdecore.so.4 #2 0x40ec4eb6 in KCrash::defaultCrashHandler () from /usr/kde/3.3/lib/libkdecore.so.4 #3 0x40fbae04 in kde_malloc_is_used () from /usr/kde/3.3/lib/libkdecore.so.4 #4 0x00000010 in ?? () #5 0x40fbae20 in kde_malloc_is_used () from /usr/kde/3.3/lib/libkdecore.so.4 #6 0x40face78 in ?? () from /usr/kde/3.3/lib/libkdecore.so.4 #7 0x40fbae04 in kde_malloc_is_used () from /usr/kde/3.3/lib/libkdecore.so.4 #8 0x00000001 in ?? () #9 0x00000000 in ?? () #10 0x40f60651 in malloc () from /usr/kde/3.3/lib/libkdecore.so.4 #11 0x0000048e in ?? () #12 0x00000400 in ?? () #13 0x00000400 in ?? () #14 0x0821d488 in ?? () #15 0x4175b154 in ?? () from /usr/qt/3/lib/libqt-mt.so.3 #16 0x40f605f0 in malloc () from /usr/kde/3.3/lib/libkdecore.so.4 #17 0x00000008 in ?? () #18 0x0000044e in ?? () #19 0xbfffe818 in ?? () #20 0x41b4f2df in operator new () from /usr/lib/gcc/i686-pc-linux-gnu/3.4.2/libstdc++.so.6 ----------- Kostja
I'm wondering if this is a Gentoo specific thing since all of the reports so far seem to come from Gentoo. Unfortunately it doesn't seem like you did manage to get debugging symbols -- otherwise all of the "??" lines wouldn't be in there. Unfortunately there's still not anything mentioning JuK showing up at all in them. Just out of curiosity -- you didn't happen to upgrade GCC recently did you?
I've started to recompile kdelibs and kdebase with debugging symbols...maybe that will help... You're right with the GCC update, I've updated from gcc 3.3 to 3.4 one month ago. As gcc 3.3 is still installed my next step will be to rebuild kdemultimedia with the "old" gcc.
Ok, this is probably a duplicate of 85889 which is just brokenness in the Gentoo dependancy system as relates to GCC / C++ application packaging. There's a test script in there that should help check on stuff like this.
You were completely right. This is indeed a duplicate of bug 85889. Simply running the command # emerge tunepimp musicbrainz taglib fam solved the problem and JuK comes up as usual. The perl test script told me the libraries which were still linked to libstdc++.so.5. So after all this bug is not JuK specific and can be closed. Thanks for your fast help, Scott!
*** This bug has been marked as a duplicate of 85889 ***