Version: 1.3.3 (using KDE KDE 3.1.1) Installed from: Gentoo Packages Compiler: gcc (GCC) 3.2.2 20030322 (Gentoo Linux 1.4 3.2.2-r2) CHOST="i686-pc-linux-gnu" CFLAGS="-march=pentium2 -O3 -pipe" OS: Linux Crash Handler gave me this: --QUOTE-- (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...[New Thread 16384 (LWP 7687)] (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... 0x41048339 in waitpid () from /lib/libpthread.so.0 #0 0x41048339 in waitpid () from /lib/libpthread.so.0 #1 0x406b8d1d in KCrash::defaultCrashHandler(int) () from /usr/kde/3.1/lib/libkdecore.so.4 #2 0x4104715c in __pthread_sighandler () from /lib/libpthread.so.0 #3 <signal handler called> #4 0x40ce1318 in QSocket::sn_read(bool) () from /usr/qt/3/lib/libqt-mt.so.3 #5 0x40e1dd43 in QSocket::qt_invoke(int, QUObject*) () from /usr/qt/3/lib/libqt-mt.so.3 #6 0x40b0f209 in QObject::activate_signal(QConnectionList*, QUObject*) () from /usr/qt/3/lib/libqt-mt.so.3 #7 0x40b0f2e5 in QObject::activate_signal(int, int) () from /usr/qt/3/lib/libqt-mt.so.3 #8 0x40df0912 in QSocketNotifier::activated(int) () from /usr/qt/3/lib/libqt-mt.so.3 #9 0x40b2b850 in QSocketNotifier::event(QEvent*) () from /usr/qt/3/lib/libqt-mt.so.3 #10 0x40ab3014 in QApplication::internalNotify(QObject*, QEvent*) () from /usr/qt/3/lib/libqt-mt.so.3 #11 0x40ab258b in QApplication::notify(QObject*, QEvent*) () from /usr/qt/3/lib/libqt-mt.so.3 #12 0x4062a6f9 in KApplication::notify(QObject*, QEvent*) () from /usr/kde/3.1/lib/libkdecore.so.4 #13 0x40a8dd0a in QEventLoop::activateSocketNotifiers() () from /usr/qt/3/lib/libqt-mt.so.3 #14 0x40a6b377 in QEventLoop::processEvents(unsigned) () from /usr/qt/3/lib/libqt-mt.so.3 #15 0x40ac5176 in QEventLoop::enterLoop() () from /usr/qt/3/lib/libqt-mt.so.3 #16 0x40ac5018 in QEventLoop::exec() () from /usr/qt/3/lib/libqt-mt.so.3 #17 0x40ab3241 in QApplication::exec() () from /usr/qt/3/lib/libqt-mt.so.3 #18 0x0806718d in QFrame::paintEvent(QPaintEvent*) () #19 0x410d6b47 in __libc_start_main () from /lib/libc.so.6 --ENDQUOTE--
strace output here: http://www.gangwarily.ca/strace.out
if you turn off online cddb looks up does this help? (in your $KDEHOME/share/config/kscdrc set CDDBRemoteEnabled=true to CDDBRemoteEnabled=false) if not, does moving your $KDEHOME/share/config/kscdrc out of the way completely help? if so, please send it to me if you don't mind... if that doesn't help anything, try downgrading Qt to 3.1.1 since i've seen a few issues now that all have a recent upgrade to 3.1.2 in common?
Setting CDDBRemoteEnabled=false worked. My bad. I saw that in another bug and should have tried it before submitting mine but I allowed myself to think "that's not related". Removing kscdrc altogether also works. Thanks Aaron. md.
Subject: Re: kscd crashes on startup On Saturday 05 April 2003 12:44, you wrote: > ------- You are receiving this mail because: ------- > You are the assignee for the bug, or are watching the assignee. > > http://bugs.kde.org/show_bug.cgi?id=56881 > > > > > ------- Additional Comments From markd@gangwarily.ca 2003-04-05 21:44 > ------- Setting CDDBRemoteEnabled=false worked. My bad. I saw that in > another bug and should have tried it before submitting mine but I allowed > myself to think "that's not related". > > Removing kscdrc altogether also works. > > Thanks Aaron. well, the bug still exists, so don't thank me yet... libkcddb just got moved from kdenonbeta into kdemultimedia, so i'll be porting kscd to use that (stable) implementation for 3.2 and then this and other cddb-related bugs *knock on wood* will go away =) thanks for the bug report, though!
*** This bug has been marked as a duplicate of 55976 ***