Version: (using KDE KDE 3.5.2) Installed from: Ubuntu Packages OS: Linux I've seen quite a lot of random Kicker crashes lately, with my Ubuntu Dapper Drake development desktop. This has even happened at night, when the desktop hasn't been in use at all and there are no external logins. However, I have noticed that the machine has lost connection to the net, and I have a ksysguard in the panel that listens to a ksysguardd on a remote machine. I therefore speculate that the crash happens as a result of the machine loosing connection to the 'net. The backtrace is useless but it happens quite often so it should be reasonably reproduceable...
> The backtrace is useless but it happens quite often so it should be > reasonably reproduceable... given that you offered almost no explanation or supporting information, it's probably not easy to reproduce. some suggestions to help make this bug report more useful: - install the kde -dbg packages so the backtrace is more meaningful - attach your ksysguard applet configuration
Created attachment 16351 [details] My ksysguard applet config
Unfortunately, it is a box I cannot really experiment with a lot... :-( I got the kdelibs-dbg installed now, but I couldn't find a corresponding kdebase-dbg-package in Ubuntu. Is there such a package in Ubuntu? Any other -dbg packages I could install? I've attached the config, hope that helps.
I'm seeing 100% reproducable crashes now. I put in a new box with the same name as before, DNS and the key has changed, and SSH reports those "OMG!, DNS SPOOFING, MAN-IN-THE-MIDDLE" errors before it closes the connection (yeah, I should have thought about that). If I comment out that host and its display in the config I attached last time, the crash doesn't happen, so it has to be something there. Now I have the backtraces of two crashes. They don't seem very useful, but I hope they can help a bit. Also, I have recorded what the console says. There are four blocks here, the first is the console output, then the backtrace, and another attempt, with also console output and another backtrace: QWidget::setMinimumSize: The smallest allowed size is (0,0) QWidget::setMinimumSize: The smallest allowed size is (0,0) QWidget::setMinimumSize: The smallest allowed size is (0,0) kicker: crashHandler called KCrash: Application 'kicker' crashing... ScimInputContextPlugin() QWidget::setMinimumSize: The smallest allowed size is (0,0) QWidget::setMinimumSize: The smallest allowed size is (0,0) QWidget::setMinimumSize: The smallest allowed size is (0,0) (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (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) [Thread debugging using libthread_db enabled] [New Thread -1234209088 (LWP 5769)] [KCrash handler] #6 0x00200064 in ?? () #7 0xb7023dc6 in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3 #8 0xb7023fc2 in QApplication::notify () from /usr/lib/libqt-mt.so.3 #9 0xb77a8d7d in KApplication::notify (this=0x80569c0, receiver=0x8264cd0, event=0x826c6d0) at kapplication.cpp:550 #10 0xb6fb50ef in QApplication::sendEvent () from /usr/lib/libqt-mt.so.3 #11 0xb7025417 in QApplication::sendPostedEvents () from /usr/lib/libqt-mt.so.3 #12 0xb702551e in QApplication::sendPostedEvents () from /usr/lib/libqt-mt.so.3 #13 0xb6fc83c3 in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3 #14 0xb703c8b7 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3 #15 0xb703c7da in QEventLoop::exec () from /usr/lib/libqt-mt.so.3 #16 0xb70228d5 in QApplication::exec () from /usr/lib/libqt-mt.so.3 #17 0xb7eb8362 in kdemain () from /usr/lib/libkdeinit_kicker.so #18 0xb7c2aea2 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6 #19 0x080483b1 in ?? () kjetilk@rabbit:~> ScimInputContextPlugin() QWidget::setMinimumSize: The smallest allowed size is (0,0) QWidget::setMinimumSize: The smallest allowed size is (0,0) QWidget::setMinimumSize: The smallest allowed size is (0,0) kicker: crashHandler called KCrash: Application 'kicker' crashing... ScimInputContextPlugin() QWidget::setMinimumSize: The smallest allowed size is (0,0) QWidget::setMinimumSize: The smallest allowed size is (0,0) QWidget::setMinimumSize: The smallest allowed size is (0,0) *** glibc detected *** free(): invalid next size (fast): 0x0825b428 *** (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (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) [Thread debugging using libthread_db enabled] [New Thread -1233574208 (LWP 5798)] [KCrash handler] #6 0xa095b1c8 in ?? () #7 0xb7ddd3f5 in __malloc_initialize_hook () from /lib/tls/i686/cmov/libc.so.6 #8 0xb70bedc6 in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3 #9 0xb70befc2 in QApplication::notify () from /usr/lib/libqt-mt.so.3 #10 0xb7843d7d in KApplication::notify (this=0x80569c0, receiver=0x82647a0, event=0x826c6e8) at kapplication.cpp:550 #11 0xb70500ef in QApplication::sendEvent () from /usr/lib/libqt-mt.so.3 #12 0xb70c0417 in QApplication::sendPostedEvents () from /usr/lib/libqt-mt.so.3 #13 0xb70c051e in QApplication::sendPostedEvents () from /usr/lib/libqt-mt.so.3 #14 0xb70633c3 in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3 #15 0xb70d7a4f in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3 #16 0xb70bd87e in QApplication::processEvents () from /usr/lib/libqt-mt.so.3 #17 0xb70bd8a9 in QApplication::processEvents () from /usr/lib/libqt-mt.so.3 #18 0xb7f61dfa in ExtensionManager::initialize () from /usr/lib/libkdeinit_kicker.so #19 0xb7f62647 in ExtensionManager::qt_invoke () from /usr/lib/libkdeinit_kicker.so #20 0xb7128e29 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #21 0xb74bbe1a in QSignal::signal () from /usr/lib/libqt-mt.so.3 #22 0xb71465a0 in QSignal::activate () from /usr/lib/libqt-mt.so.3 #23 0xb714e090 in QSingleShotTimer::event () from /usr/lib/libqt-mt.so.3 #24 0xb70bedc6 in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3 #25 0xb70befc2 in QApplication::notify () from /usr/lib/libqt-mt.so.3 #26 0xb7843d7d in KApplication::notify (this=0x80569c0, receiver=0x80da250, event=0xbf9e1e68) at kapplication.cpp:550 #27 0xb70500ef in QApplication::sendEvent () from /usr/lib/libqt-mt.so.3 #28 0xb70b07b3 in QEventLoop::activateTimers () from /usr/lib/libqt-mt.so.3 #29 0xb7063eff in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3 #30 0xb70d78b7 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3 #31 0xb70d77da in QEventLoop::exec () from /usr/lib/libqt-mt.so.3 #32 0xb70bd8d5 in QApplication::exec () from /usr/lib/libqt-mt.so.3 #33 0xb7f53362 in kdemain () from /usr/lib/libkdeinit_kicker.so #34 0xb7cc5ea2 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6 #35 0x080483b1 in ?? ()
I've got this 100% reproducable on two independent boxes now, both running Ubuntu Dapper. But I guess it is an old version anyway, I'll hump over to Ubuntu and report it there, and possibly upgrade my ubuntu too... :-)
I don't think I've seen this since 3.5.4 or something, I'm pretty sure it can be closed.