Bug 254699

Summary: Plasma crashed when I clicked on a working update-prog tray icon [QCoreApplication::postEvent, StatusNotifierItemJob::contextMenuReady]
Product: [Plasma] plasma4 Reporter: Stojmo <nigromontanus>
Component: generalAssignee: Plasma Bugs List <plasma-bugs>
Status: RESOLVED FIXED    
Severity: crash CC: andresbajotierra, dplater, efaston, holmesmich, info, journeyman1126, muad.dib8, zekkerj
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In: 4.5.5 and 4.6.0
Attachments: New crash information added by DrKonqi
New crash information added by DrKonqi

Description Stojmo 2010-10-19 22:47:24 UTC 
Application: plasma-desktop (0.3)
KDE Platform Version: 4.5.1 (KDE 4.5.1)
Qt Version: 4.7.0
Operating System: Linux 2.6.35-22-generic x86_64
Distribution: Ubuntu 10.10

-- Information about the crash:
- What I was doing when the application crashed:

Plasma crasched when I clicked on a working update-prog symbol
Immediate plasma relaunch

-- Backtrace:
Application: Plasma arbetsyta (plasma-desktop), signal: Segmentation fault
[Current thread is 1 (Thread 0x7fa6b63d17a0 (LWP 1714))]

Thread 2 (Thread 0x7fa68e12d710 (LWP 1716)):
#0  0x00007fa6b5cd91d3 in __poll (fds=<value optimized out>, nfds=<value optimized out>, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:87
#1  0x00007fa6aa8c3009 in ?? () from /lib/libglib-2.0.so.0
#2  0x00007fa6aa8c345c in g_main_context_iteration () from /lib/libglib-2.0.so.0
#3  0x00007fa6b338e1e6 in QEventDispatcherGlib::processEvents (this=0x167a8c0, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:417
#4  0x00007fa6b3360a02 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#5  0x00007fa6b3360dec in QEventLoop::exec (this=0x7fa68e12ccb0, flags=) at kernel/qeventloop.cpp:201
#6  0x00007fa6b326b2fd in QThread::exec (this=<value optimized out>) at thread/qthread.cpp:490
#7  0x00007fa6b33405f8 in QInotifyFileSystemWatcherEngine::run (this=0x170ec90) at io/qfilesystemwatcher_inotify.cpp:248
#8  0x00007fa6b326e27e in QThreadPrivate::start (arg=0x170ec90) at thread/qthread_unix.cpp:266
#9  0x00007fa6adf20953 in ?? () from /usr/lib/nvidia-current/libGL.so.1
#10 0x00007fa6b2fe3971 in start_thread (arg=<value optimized out>) at pthread_create.c:304
#11 0x00007fa6b5ce591d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#12 0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7fa6b63d17a0 (LWP 1714)):
[KCrash Handler]
#6  0x00007fa6b3268eb6 in fetchAndAddOrdered (this=0x7fa6b2fa5150) at ../../include/QtCore/../../src/corelib/arch/qatomic_x86_64.h:164
#7  fetchAndAddAcquire (this=0x7fa6b2fa5150) at ../../include/QtCore/../../src/corelib/arch/qatomic_x86_64.h:297
#8  QMutex::lock (this=0x7fa6b2fa5150) at thread/qmutex.cpp:159
#9  0x00007fa6b3364642 in QCoreApplication::postEvent (receiver=0x2e5e990, event=0x2de4c00, priority=0) at kernel/qcoreapplication.cpp:1141
#10 0x00007fa6959e4c73 in StatusNotifierItemJob::contextMenuReady (this=0x2e5e990, menu=0x2d53640) at ../../../../../plasma/generic/dataengines/statusnotifieritem/statusnotifieritemjob.cpp:53
#11 0x00007fa6959e4ce0 in StatusNotifierItemJob::qt_metacall (this=0x2e5e990, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fffcb1af3f0) at ./statusnotifieritemjob.moc:75
#12 0x00007fa6b3379b27 in QMetaObject::activate (sender=0x2dad7d0, m=<value optimized out>, local_signal_index=<value optimized out>, argv=0x0) at kernel/qobject.cpp:3280
#13 0x00007fa6959dec7f in StatusNotifierItemSource::contextMenuReady (this=0x1, _t1=0x2d53640) at ./statusnotifieritemsource.moc:109
#14 0x00007fa6959e3be4 in StatusNotifierItemSource::qt_metacall (this=0x2dad7d0, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fffcb1af4e0) at ./statusnotifieritemsource.moc:90
#15 0x00007fa6b3379b27 in QMetaObject::activate (sender=0x2d772b0, m=<value optimized out>, local_signal_index=<value optimized out>, argv=0x0) at kernel/qobject.cpp:3280
#16 0x00007fa6abbe889c in DBusMenuImporter::slotMenuAboutToShow() () from /usr/lib/libdbusmenu-qt.so.2
#17 0x00007fa6abbe9a5c in DBusMenuImporter::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libdbusmenu-qt.so.2
#18 0x00007fa6b3379b27 in QMetaObject::activate (sender=0x2d53640, m=<value optimized out>, local_signal_index=<value optimized out>, argv=0x0) at kernel/qobject.cpp:3280
#19 0x00007fa6b2911f40 in QMenu::qt_metacall (this=0x2d53640, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fffcb1af960) at .moc/release-shared/moc_qmenu.cpp:97
#20 0x00007fa6b336abf9 in QMetaMethod::invoke (this=0x7fffcb1afc10, object=0x2d53640, connectionType=<value optimized out>, returnValue=..., val0=..., val1=..., val2=..., val3=..., val4=..., val5=..., val6=..., val7=..., val8=..., val9=...) at kernel/qmetaobject.cpp:1575
#21 0x00007fa6b336c306 in QMetaObject::invokeMethod (obj=0x2d53640, member=<value optimized out>, type=<value optimized out>, ret=..., val0=..., val1=..., val2=..., val3=..., val4=..., val5=..., val6=..., val7=..., val8=..., val9=...) at kernel/qmetaobject.cpp:1148
#22 0x00007fa6abbe37c1 in DBusMenuImporter::updateMenu() () from /usr/lib/libdbusmenu-qt.so.2
#23 0x00007fa6959e01bb in StatusNotifierItemSource::contextMenu (this=0x2dad7d0, x=977, y=1006) at ../../../../../plasma/generic/dataengines/statusnotifieritem/statusnotifieritemsource.cpp:474
#24 0x00007fa6959e62d8 in StatusNotifierItemJob::start (this=0x2e5e990) at ../../../../../plasma/generic/dataengines/statusnotifieritem/statusnotifieritemjob.cpp:43
#25 0x00007fa6b58b2b21 in Plasma::ServiceJob::qt_metacall (this=0x2e5e990, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=<value optimized out>) at ./servicejob.moc:72
#26 0x00007fa6959e4cc0 in StatusNotifierItemJob::qt_metacall (this=0x1, _c=48122880, _id=1, _a=0x0) at ./statusnotifieritemjob.moc:70
#27 0x00007fa6b3373bde in QObject::event (this=0x2e5e990, e=0x1) at kernel/qobject.cpp:1219
#28 0x00007fa6b24abfdc in QApplicationPrivate::notify_helper (this=0xcbb3c0, receiver=0x2e5e990, e=0x2e12ed0) at kernel/qapplication.cpp:4396
#29 0x00007fa6b24b1aed in QApplication::notify (this=0xca9f90, receiver=0x2e5e990, e=0x2e12ed0) at kernel/qapplication.cpp:4277
#30 0x00007fa6b3ffd156 in KApplication::notify (this=0xca9f90, receiver=0x2e5e990, event=0x2e12ed0) at ../../kdeui/kernel/kapplication.cpp:310
#31 0x00007fa6b3361cdc in QCoreApplication::notifyInternal (this=0xca9f90, receiver=0x2e5e990, event=0x2e12ed0) at kernel/qcoreapplication.cpp:732
#32 0x00007fa6b3364c22 in sendEvent (receiver=0x0, event_type=<value optimized out>, data=0xc53560) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#33 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=<value optimized out>, data=0xc53560) at kernel/qcoreapplication.cpp:1373
#34 0x00007fa6b338e653 in sendPostedEvents (s=0xcbeb40) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:220
#35 postEventSourceDispatch (s=0xcbeb40) at kernel/qeventdispatcher_glib.cpp:277
#36 0x00007fa6aa8bf342 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#37 0x00007fa6aa8c32a8 in ?? () from /lib/libglib-2.0.so.0
#38 0x00007fa6aa8c345c in g_main_context_iteration () from /lib/libglib-2.0.so.0
#39 0x00007fa6b338e193 in QEventDispatcherGlib::processEvents (this=0xc53070, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:415
#40 0x00007fa6b255ea4e in QGuiEventDispatcherGlib::processEvents (this=0x1, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:204
#41 0x00007fa6b3360a02 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#42 0x00007fa6b3360dec in QEventLoop::exec (this=0x7fffcb1b0ea0, flags=) at kernel/qeventloop.cpp:201
#43 0x00007fa6b3364ebb in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1009
#44 0x00007fa6b5fbca56 in kdemain (argc=<value optimized out>, argv=<value optimized out>) at ../../../../plasma/desktop/shell/main.cpp:118
#45 0x00007fa6b5c1dd8e in __libc_start_main (main=<value optimized out>, argc=<value optimized out>, ubp_av=<value optimized out>, init=<value optimized out>, fini=<value optimized out>, rtld_fini=<value optimized out>, stack_end=0x7fffcb1b1268) at libc-start.c:226
#46 0x0000000000400669 in _start ()

Possible duplicates by query: bug 252098, bug 247792, bug 247467, bug 235790.

Reported using DrKonqi
Comment 1 Raphael 2010-10-21 23:59:06 UTC 
Created attachment 52731 [details]
New crash information added by DrKonqi

plasma-desktop (0.3) on KDE Platform 4.5.1 (KDE 4.5.1) using Qt 4.7.0

Same bug same definition, I clicked the icon update and kpackagekit crashed

-- Backtrace (Reduced):
#6  QMutex::lock (this=0x1d40) at thread/qmutex.cpp:151
#7  0x00007fbf4bf67642 in QCoreApplication::postEvent (receiver=0x2cd6780, event=0x24de0b0, priority=0) at kernel/qcoreapplication.cpp:1141
#8  0x00007fbf2f638c73 in StatusNotifierItemJob::contextMenuReady (this=0x2cd6780, menu=0x2820bb0) at ../../../../../plasma/generic/dataengines/statusnotifieritem/statusnotifieritemjob.cpp:53
#9  0x00007fbf2f638ce0 in StatusNotifierItemJob::qt_metacall (this=0x2cd6780, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fffe274ee00) at ./statusnotifieritemjob.moc:75
[...]
#11 0x00007fbf2f632c7f in StatusNotifierItemSource::contextMenuReady (this=0x1d40, _t1=0x2820bb0) at ./statusnotifieritemsource.moc:109
Comment 2 Beat Wolf 2010-10-24 10:35:41 UTC 
*** Bug 255057 has been marked as a duplicate of this bug. ***
Comment 3 Usul 2010-11-02 18:18:22 UTC 
Created attachment 53073 [details]
New crash information added by DrKonqi

plasma-desktop (0.3) on KDE Platform 4.5.1 (KDE 4.5.1) using Qt 4.7.0

Plasma crasched when I clicked on a working update-prog symbol

-- Backtrace (Reduced):
#6  0x00007fef4d421ddc in QMutex::lock (this=0x2d70d30) at thread/qmutex.cpp:151
#7  0x00007fef4d51d642 in QCoreApplication::postEvent (receiver=0x2df79c0, event=0x2d0ca90, priority=0) at kernel/qcoreapplication.cpp:1141
#8  0x00007fef30659c73 in StatusNotifierItemJob::contextMenuReady (this=0x2df79c0, menu=0x2ae0540) at ../../../../../plasma/generic/dataengines/statusnotifieritem/statusnotifieritemjob.cpp:53
#9  0x00007fef30659ce0 in StatusNotifierItemJob::qt_metacall (this=0x2df79c0, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff758c1f10) at ./statusnotifieritemjob.moc:75
[...]
#11 0x00007fef30653c7f in StatusNotifierItemSource::contextMenuReady (this=0x2d70d30, _t1=0x2ae0540) at ./statusnotifieritemsource.moc:109
Comment 4 Dario Andres 2011-01-01 15:06:36 UTC 
[Comment from a bug triager]
This was fixed recently for KDE SC 4.5.5 and 4.6.0.
Related to bug 254435 and bug 241562.
Regards
Comment 5 Dario Andres 2011-01-01 15:07:24 UTC 
*** Bug 255321 has been marked as a duplicate of this bug. ***
Comment 6 Beat Wolf 2011-01-21 00:06:01 UTC 
*** Bug 263796 has been marked as a duplicate of this bug. ***
Comment 7 Dario Andres 2011-01-29 14:07:04 UTC 
*** Bug 264298 has been marked as a duplicate of this bug. ***
Comment 8 Dave Plater 2011-01-29 14:21:52 UTC 
The strange behavior I reported was due to a samba share I have mounted and the server it was mounted from being shut down.

My original report:
Application: plasma-desktop (0.4)
KDE Platform Version: 4.5.95 (4.6 RC2)
Qt Version: 4.7.1
Operating System: Linux 2.6.34.7-0.7-desktop x86_64
Distribution: "openSUSE 11.3 (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:
My desktop system was "sticking" and I noticed the openSUSE update applet was
displaying signs of activity, I hovered my mouse pointer over it and tooltip
reported a dbus error. I right clicked and selected quit on the context menu,
hoping that I had at last found the cause of the freezing "kickoff application
launcher" and the crash occurred.

- Unusual behavior I noticed:
Since update to kde 4.5.95 I've had an intermittent frozen "kickoff application
launcher". It freezes up  after clicking on it's panel icon when it appears and
the entire panel becomes unusable for about 30 to 40 seconds. This usually
happens around midnight and continues until I restart x or logout/login. A
kded, sometimes a couple of them, I don't know if there's supposed to be more
than one running (I can't see any atm needed to complete this report), runs at
45% plus cpu usage. Also a knotify hogs cpu. I would appreciate some direction
to find the cause.
Comment 9 Dave Plater 2011-01-29 14:24:21 UTC 
I'm now on 4.6 and I'll let you know if it happens again but 4.6 is working well with non of the irritating slow downs since the beta stage.
Comment 10 Dario Andres 2011-02-08 00:51:45 UTC 
*** Bug 265736 has been marked as a duplicate of this bug. ***