Application that crashed: plasma-desktop Version of the application: 0.3 KDE Version: 4.3.2 (KDE 4.3.2) Qt Version: 4.5.2 Operating System: Linux 2.6.31-17-386 i686 Distribution: Ubuntu 9.10 -- Backtrace: Application: Plasma Workspace (kdeinit4), signal: Segmentation fault [KCrash Handler] #6 0x00137d57 in XVisualIDFromVisual () from /usr/lib/libX11.so.6 #7 0x013ce70e in qt_x11_getX11InfoForWindow (xinfo=0x9bca6e4, a=...) at kernel/qwidget_x11.cpp:400 #8 0x013d5b4e in QWidgetPrivate::create_sys (this=0x9bca5f0, window=27276995, initializeWindow=true, destroyOldWindow=true) at kernel/qwidget_x11.cpp:545 #9 0x01396b1c in QWidget::create (this=0x95e93b8, window=27276995, initializeWindow=true, destroyOldWindow=<value optimized out>) at kernel/qwidget.cpp:1253 #10 0x05bb0c1e in ?? () from /usr/lib/kde4/plasma_applet_systemtray.so #11 0x05bac3f0 in ?? () from /usr/lib/kde4/plasma_applet_systemtray.so #12 0x05bac4cb in ?? () from /usr/lib/kde4/plasma_applet_systemtray.so #13 0x0061e263 in QMetaObject::activate (sender=0x9c52f28, from_signal_index=4, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3113 #14 0x0061eec2 in QMetaObject::activate (sender=0x9c52f28, m=0x6f8908, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3187 #15 0x00623387 in QSingleShotTimer::timeout (this=0x9c52f28) at .moc/release-shared/qtimer.moc:76 #16 0x0062349c in QSingleShotTimer::timerEvent (this=0x9c52f28) at kernel/qtimer.cpp:298 #17 0x006183bf in QObject::event (this=0x9c52f28, e=0xbf928e00) at kernel/qobject.cpp:1075 #18 0x0133ff54 in QApplicationPrivate::notify_helper (this=0x91b24a0, receiver=0x9c52f28, e=0xbf928e00) at kernel/qapplication.cpp:4056 #19 0x0134767c in QApplication::notify (this=0x918b628, receiver=0x9c52f28, e=0xbf928e00) at kernel/qapplication.cpp:3603 #20 0x0105fbfa in KApplication::notify (this=0x918b628, receiver=0x9c52f28, event=0xbf928e00) at ../../kdeui/kernel/kapplication.cpp:302 #21 0x006086cb in QCoreApplication::notifyInternal (this=0x918b628, receiver=0x9c52f28, event=0xbf928e00) at kernel/qcoreapplication.cpp:610 #22 0x006357ce in QCoreApplication::sendEvent (this=0x91b4e44) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213 #23 QTimerInfoList::activateTimers (this=0x91b4e44) at kernel/qeventdispatcher_unix.cpp:572 #24 0x006330e0 in timerSourceDispatch (source=0x91b4e10) at kernel/qeventdispatcher_glib.cpp:165 #25 0x00296e88 in g_main_context_dispatch () from /lib/libglib-2.0.so.0 #26 0x0029a730 in ?? () from /lib/libglib-2.0.so.0 #27 0x0029a863 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #28 0x0063302c in QEventDispatcherGlib::processEvents (this=0x91b2260, flags=...) at kernel/qeventdispatcher_glib.cpp:327 #29 0x013e0be5 in QGuiEventDispatcherGlib::processEvents (this=0x91b2260, flags=...) at kernel/qguieventdispatcher_glib.cpp:202 #30 0x00606c79 in QEventLoop::processEvents (this=0xbf9290c4, flags=) at kernel/qeventloop.cpp:149 #31 0x006070ca in QEventLoop::exec (this=0xbf9290c4, flags=...) at kernel/qeventloop.cpp:201 #32 0x0060953f in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888 #33 0x0133fdd7 in QApplication::exec () at kernel/qapplication.cpp:3525 #34 0x0570d80d in kdemain () from /usr/lib/libkdeinit4_plasma-desktop.so #35 0x0804dde1 in launch (argc=<value optimized out>, _name=<value optimized out>, args=<value optimized out>, cwd=0x0, envc=0, envs=0x9153708 "", reset_env=false, tty=0x0, avoid_loops=false, startup_id_str=0x80511a5 "0") at ../../kinit/kinit.cpp:677 #36 0x0804ea35 in handle_launcher_request (sock=<value optimized out>, who=<value optimized out>) at ../../kinit/kinit.cpp:1169 #37 0x0804eeac in handle_requests (waitForPid=<value optimized out>) at ../../kinit/kinit.cpp:1362 #38 0x0804fbaf in main (argc=2, argv=0xbf929924, envp=0xbf929930) at ../../kinit/kinit.cpp:1793 This bug may be a duplicate of or related to bug 216519 Reported using DrKonqi
Fixed in KDE SC 4.4. Regards *** This bug has been marked as a duplicate of bug 198294 ***
Seeing this (or something very similar) on 4.4.1 on Kubuntu 9.10 64bit
@Damon: may be the backtrace is different (and therefor the crash is different) Please open a new bug report for your crash. Regards