Application: plasma-desktop (0.4) KDE Platform Version: 4.5.90 (4.6 RC1) Qt Version: 4.7.1 Operating System: Linux 2.6.34.7-0.5-default i686 Distribution: "openSUSE 11.3 (i586)" -- Information about the crash: - What I was doing when the application crashed:Start Computer and after Log In everything worked, but no plasma desktop. Then DrKonqi came up The crash can be reproduced every time. -- Backtrace: Application: Plasma-Desktop-Umgebung (plasma-desktop), signal: Segmentation fault [Current thread is 1 (Thread 0xb251d710 (LWP 7224))] Thread 2 (Thread 0xa9f26b70 (LWP 7227)): #0 0xb6313ffa in pthread_mutex_lock () from /lib/libpthread.so.0 #1 0xb7644464 in pthread_mutex_lock () from /lib/libc.so.6 #2 0xb31f60ef in g_main_context_prepare () from /usr/lib/libglib-2.0.so.0 #3 0xb31f6f22 in ?? () from /usr/lib/libglib-2.0.so.0 #4 0xb31f760e in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #5 0xb64b7787 in QEventDispatcherGlib::processEvents (this=0x88ee948, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #6 0xb648829d in QEventLoop::processEvents (this=0xa9f262b0, flags=...) at kernel/qeventloop.cpp:149 #7 0xb64884c9 in QEventLoop::exec (this=0xa9f262b0, flags=...) at kernel/qeventloop.cpp:201 #8 0xb63897b9 in QThread::exec (this=0x887a060) at thread/qthread.cpp:490 #9 0xb646822d in QInotifyFileSystemWatcherEngine::run (this=0x887a060) at io/qfilesystemwatcher_inotify.cpp:248 #10 0xb638c3aa in QThreadPrivate::start (arg=0x887a060) at thread/qthread_unix.cpp:285 #11 0xb6311b25 in start_thread () from /lib/libpthread.so.0 #12 0xb763646e in clone () from /lib/libc.so.6 Thread 1 (Thread 0xb251d710 (LWP 7224)): [KCrash Handler] #7 0xb73477af in Plasma::Containment::setScreen (this=0x0, newScreen=0, newDesktop=0) at /usr/src/debug/kdelibs-4.5.90/plasma/containment.cpp:959 #8 0xb76ee087 in Activity::containmentForScreen (this=0x8b0f9c0, screen=0, desktop=0) at /usr/src/debug/kdebase-workspace-4.5.90/plasma/desktop/shell/activity.cpp:183 #9 0xb76ee2c6 in Activity::activateContainment (this=0x8b0f9c0, screen=0, desktop=0) at /usr/src/debug/kdebase-workspace-4.5.90/plasma/desktop/shell/activity.cpp:203 #10 0xb76ee367 in Activity::checkScreens (this=0x8b0f9c0) at /usr/src/debug/kdebase-workspace-4.5.90/plasma/desktop/shell/activity.cpp:230 #11 0xb76ee730 in Activity::opened (this=0x8b0f9c0) at /usr/src/debug/kdebase-workspace-4.5.90/plasma/desktop/shell/activity.cpp:402 #12 0xb76ee82a in Activity::ensureActive (this=0x8b0f9c0) at /usr/src/debug/kdebase-workspace-4.5.90/plasma/desktop/shell/activity.cpp:215 #13 0xb76fa684 in DesktopCorona::activityAdded (this=0x8185080, id=...) at /usr/src/debug/kdebase-workspace-4.5.90/plasma/desktop/shell/desktopcorona.cpp:687 #14 0xb76faf79 in DesktopCorona::checkActivities (this=0x8185080) at /usr/src/debug/kdebase-workspace-4.5.90/plasma/desktop/shell/desktopcorona.cpp:578 #15 0xb771e62a in PlasmaApp::corona (this=0x808f510) at /usr/src/debug/kdebase-workspace-4.5.90/plasma/desktop/shell/plasmaapp.cpp:796 #16 0xb771e93b in PlasmaApp::setupDesktop (this=0x808f510) at /usr/src/debug/kdebase-workspace-4.5.90/plasma/desktop/shell/plasmaapp.cpp:299 #17 0xb77203b0 in PlasmaApp::qt_metacall (this=0x808f510, _c=QMetaObject::InvokeMetaMethod, _id=18, _a=0x8160590) at /usr/src/debug/kdebase-workspace-4.5.90/build/plasma/desktop/shell/plasmaapp.moc:156 #18 0xb648f8ad in QMetaObject::metacall (object=0x808f510, cl=QMetaObject::InvokeMetaMethod, idx=45, argv=0x8160590) at kernel/qmetaobject.cpp:237 #19 0xb649a375 in QMetaCallEvent::placeMetaCall (this=0x8140818, object=0x808f510) at kernel/qobject.cpp:534 #20 0xb649e57f in QObject::event (this=0x808f510, e=0x8140818) at kernel/qobject.cpp:1211 #21 0xb64895aa in QCoreApplication::event (this=0x808f510, e=0x8140818) at kernel/qcoreapplication.cpp:1561 #22 0xb5997bed in QApplication::event (this=0x808f510, e=0x8140818) at kernel/qapplication.cpp:2486 #23 0xb5995434 in QApplicationPrivate::notify_helper (this=0x80b1f10, receiver=0x808f510, e=0x8140818) at kernel/qapplication.cpp:4445 #24 0xb599e0d7 in QApplication::notify (this=0x808f510, receiver=0x808f510, e=0x8140818) at kernel/qapplication.cpp:3845 #25 0xb6a37541 in KApplication::notify (this=0x808f510, receiver=0x808f510, event=0x8140818) at /usr/src/debug/kdelibs-4.5.90/kdeui/kernel/kapplication.cpp:311 #26 0xb6488fbe in QCoreApplication::notifyInternal (this=0x808f510, receiver=0x808f510, event=0x8140818) at kernel/qcoreapplication.cpp:732 #27 0xb648cd4c in sendEvent (receiver=0x0, event_type=0, data=0x8050b20) at kernel/qcoreapplication.h:215 #28 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x8050b20) at kernel/qcoreapplication.cpp:1373 #29 0xb648ce9c in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1266 #30 0xb64b75b4 in sendPostedEvents (s=0x80b4300) at kernel/qcoreapplication.h:220 #31 postEventSourceDispatch (s=0x80b4300) at kernel/qeventdispatcher_glib.cpp:277 #32 0xb31f6b49 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #33 0xb31f7350 in ?? () from /usr/lib/libglib-2.0.so.0 #34 0xb31f760e in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #35 0xb64b773b in QEventDispatcherGlib::processEvents (this=0x8087288, flags=...) at kernel/qeventdispatcher_glib.cpp:422 #36 0xb5a4b53a in QGuiEventDispatcherGlib::processEvents (this=0x8087288, flags=...) at kernel/qguieventdispatcher_glib.cpp:204 #37 0xb648829d in QEventLoop::processEvents (this=0xbff55474, flags=...) at kernel/qeventloop.cpp:149 #38 0xb64884c9 in QEventLoop::exec (this=0xbff55474, flags=...) at kernel/qeventloop.cpp:201 #39 0xb648cf70 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1009 #40 0xb5993124 in QApplication::exec () at kernel/qapplication.cpp:3719 #41 0xb770380a in kdemain (argc=1, argv=0xbff55684) at /usr/src/debug/kdebase-workspace-4.5.90/plasma/desktop/shell/main.cpp:118 #42 0x0804861b in main (argc=1, argv=0xbff55684) at /usr/src/debug/kdebase-workspace-4.5.90/build/plasma/desktop/shell/plasma-desktop_dummy.cpp:3 Possible duplicates by query: bug 261154. Reported using DrKonqi
[Comment from a bug triager] This issue could be related to bug 261154, bug 261157, or bug 257213. Regards
*** This bug has been marked as a duplicate of bug 261157 ***