Bug 338868

Summary: Old system tray icons, failing clipboard management, DrKonqi authentication, WiFi login, ACPI handling after returning from standby
Product: [I don't know] kde Reporter: Dennis Schridde <heri+kde>
Component: generalAssignee: Unassigned bugs mailing-list <unassigned-bugs>
Status: RESOLVED DUPLICATE    
Severity: normal    
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: Old system tray icons displayed after crash / return from standby

Description Dennis Schridde 2014-09-07 05:57:02 UTC
As I cannot send DrKonqi reports directly when in this stage ("Error sending the  crash report: /Received unexpected error code 410 from bugzilla. Error message was: You must login before using this part of KDE Bugtracking System../"), I post the contents of the kcrash report below. The report does not contain the KDE product and component, which DrKonqi identified, and I could neiher find a "kded" product, so I used kde/general instead.

Application: kded4 (4.13.3)
KDE Platform Version: 4.13.3
Qt Version: 4.8.6
Operating System: Linux 3.13.0-35-generic x86_64
Distribution: Ubuntu 14.04.1 LTS

-- Information about the crash:
- What I was doing when the application crashed:
I returned the computer from standby and plugged in the power chord.

- Unusual behavior I noticed:
* The icons in the system tray partly (not all of them) change from the current Oxygen style grey icons to the old colourful icons from the beginnings of the KDE 4 era.
* I cannot manage the clipboard anymore – Klipper does not react to my attempts to select one of the multiple clipboards, and copy and paste is broken.
* I am unable to login to WiFi networks.
* Pressing the computer's power button will shutdown the system immediately, instead of showing the KDE logout/shutdown/reboot dialog.

Restarting the computer resolves this issue until the next time I wake the computer from standby. The problem does not appear on every wakeup, though.

This is the first time, that DrKonqi displays for this issue – before KDE would only silently stop working in the manner described above. Since I suspected an undetected kded crash already, I take this crash report as an evidence of this hypothesis.

My guess is that this has something to do with failing interprocess communications, maybe because DBus is not reachable by the restarted kded?

The crash can be reproduced sometimes.

-- Backtrace:
Application: KDE Dæmon (kded4), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f010712e7c0 (LWP 1582))]

Thread 7 (Thread 0x7f00ea8a2700 (LWP 1738)):
#0  0x00007f01049b2bc4 in pthread_mutex_unlock (mutex=0x7f00e4000a60) at forward.c:194
#1  0x00007f0101ad79c1 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f0101a960f6 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f0105dd17be in QEventDispatcherGlib::processEvents (this=0x7f00e40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:436
#4  0x00007f0105da30af in QEventLoop::processEvents (this=this@entry=0x7f00ea8a1e20, flags=...) at kernel/qeventloop.cpp:149
#5  0x00007f0105da33a5 in QEventLoop::exec (this=this@entry=0x7f00ea8a1e20, flags=...) at kernel/qeventloop.cpp:204
#6  0x00007f0105c9fc5f in QThread::exec (this=<optimized out>) at thread/qthread.cpp:537
#7  0x00007f0105ca232f in QThreadPrivate::start (arg=0x136c2f0) at thread/qthread_unix.cpp:349
#8  0x00007f0102178182 in start_thread (arg=0x7f00ea8a2700) at pthread_create.c:312
#9  0x00007f01049a4fbd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 6 (Thread 0x7f00e1773700 (LWP 1748)):
#0  0x00007f0101ad7620 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x00007f0101ad7989 in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f0101a951f8 in g_main_context_release () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f0101a95f91 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x00007f0101a960ec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x00007f0105dd17be in QEventDispatcherGlib::processEvents (this=0x7f00dc0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:436
#6  0x00007f0105da30af in QEventLoop::processEvents (this=this@entry=0x7f00e1772de0, flags=...) at kernel/qeventloop.cpp:149
#7  0x00007f0105da33a5 in QEventLoop::exec (this=this@entry=0x7f00e1772de0, flags=...) at kernel/qeventloop.cpp:204
#8  0x00007f0105c9fc5f in QThread::exec (this=this@entry=0x13b8690) at thread/qthread.cpp:537
#9  0x00007f0105d84823 in QInotifyFileSystemWatcherEngine::run (this=0x13b8690) at io/qfilesystemwatcher_inotify.cpp:265
#10 0x00007f0105ca232f in QThreadPrivate::start (arg=0x13b8690) at thread/qthread_unix.cpp:349
#11 0x00007f0102178182 in start_thread (arg=0x7f00e1773700) at pthread_create.c:312
#12 0x00007f01049a4fbd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 5 (Thread 0x7f00d8da3700 (LWP 1936)):
#0  0x00007f0104997c6d in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x00007f0101a95fe4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f0101a9630a in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f00d92abe16 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#4  0x00007f0101abaf15 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x00007f0102178182 in start_thread (arg=0x7f00d8da3700) at pthread_create.c:312
#6  0x00007f01049a4fbd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 4 (Thread 0x7f00c7fff700 (LWP 1937)):
#0  0x00007f0104997c71 in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x00007f0101a95fe4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f0101a960ec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f0105dd17be in QEventDispatcherGlib::processEvents (this=0x7f00b80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:436
#4  0x00007f0105da30af in QEventLoop::processEvents (this=this@entry=0x7f00c7ffede0, flags=...) at kernel/qeventloop.cpp:149
#5  0x00007f0105da33a5 in QEventLoop::exec (this=this@entry=0x7f00c7ffede0, flags=...) at kernel/qeventloop.cpp:204
#6  0x00007f0105c9fc5f in QThread::exec (this=<optimized out>) at thread/qthread.cpp:537
#7  0x00007f00e3bc9027 in KCupsConnection::run() () from /usr/lib/libkcupslib.so
#8  0x00007f0105ca232f in QThreadPrivate::start (arg=0x138fc40) at thread/qthread_unix.cpp:349
#9  0x00007f0102178182 in start_thread (arg=0x7f00c7fff700) at pthread_create.c:312
#10 0x00007f01049a4fbd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 3 (Thread 0x7f00c77fe700 (LWP 1938)):
#0  0x00007f0101ad762d in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x00007f0101ad79b9 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f0101a95fd9 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f0101a960ec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x00007f0105dd17be in QEventDispatcherGlib::processEvents (this=0x7f00c00008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:436
#5  0x00007f0105da30af in QEventLoop::processEvents (this=this@entry=0x7f00c77fde20, flags=...) at kernel/qeventloop.cpp:149
#6  0x00007f0105da33a5 in QEventLoop::exec (this=this@entry=0x7f00c77fde20, flags=...) at kernel/qeventloop.cpp:204
#7  0x00007f0105c9fc5f in QThread::exec (this=<optimized out>) at thread/qthread.cpp:537
#8  0x00007f0105ca232f in QThreadPrivate::start (arg=0x143f260) at thread/qthread_unix.cpp:349
#9  0x00007f0102178182 in start_thread (arg=0x7f00c77fe700) at pthread_create.c:312
#10 0x00007f01049a4fbd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 2 (Thread 0x7f00bc98d700 (LWP 2228)):
#0  0x00007f0101a67360 in pthread_mutex_unlock@plt () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x00007f0101ad79c1 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f0101a95f91 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f0101a960ec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x00007f0105dd17be in QEventDispatcherGlib::processEvents (this=0x7f00a40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:436
#5  0x00007f0105da30af in QEventLoop::processEvents (this=this@entry=0x7f00bc98cde0, flags=...) at kernel/qeventloop.cpp:149
#6  0x00007f0105da33a5 in QEventLoop::exec (this=this@entry=0x7f00bc98cde0, flags=...) at kernel/qeventloop.cpp:204
#7  0x00007f0105c9fc5f in QThread::exec (this=this@entry=0x137e000) at thread/qthread.cpp:537
#8  0x00007f0105d84823 in QInotifyFileSystemWatcherEngine::run (this=0x137e000) at io/qfilesystemwatcher_inotify.cpp:265
#9  0x00007f0105ca232f in QThreadPrivate::start (arg=0x137e000) at thread/qthread_unix.cpp:349
#10 0x00007f0102178182 in start_thread (arg=0x7f00bc98d700) at pthread_create.c:312
#11 0x00007f01049a4fbd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 1 (Thread 0x7f010712e7c0 (LWP 1582)):
[KCrash Handler]
#6  0x00007f00e9c1ca96 in PowerDevil::Core::onResumingFromIdle (this=0x1407430) at ../../../powerdevil/daemon/powerdevilcore.cpp:691
#7  0x00007f00e9c212e5 in PowerDevil::Core::qt_static_metacall (_o=0x177bbe9, _id=22, _a=0x7fff13c40080, _c=<optimized out>) at ./powerdevilcore.moc:126
#8  0x00007f0105db887a in QMetaObject::activate (sender=sender@entry=0x139adc0, m=m@entry=0x7f00e9c06120 <KIdleTime::staticMetaObject>, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x0) at kernel/qobject.cpp:3539
#9  0x00007f00e99ff950 in KIdleTime::resumingFromIdle (this=this@entry=0x139adc0) at ./kidletime.moc:123
#10 0x00007f00e99ff968 in KIdleTimePrivate::_k_resumingFromIdle (this=<optimized out>) at ../../kutils/kidletime/kidletime.cpp:231
#11 0x00007f0105db887a in QMetaObject::activate (sender=sender@entry=0x1381040, m=m@entry=0x7f00e9c063e0 <AbstractSystemPoller::staticMetaObject>, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x0) at kernel/qobject.cpp:3539
#12 0x00007f00e9a00ae0 in AbstractSystemPoller::resumingFromIdle (this=this@entry=0x1381040) at ./abstractsystempoller.moc:121
#13 0x00007f00e9a02787 in XSyncBasedPoller::x11Event (this=0x1381040, event=0x7fff13c404d0) at ../../kutils/kidletime/xsyncbasedpoller.cpp:246
#14 0x00007f0106b23a3e in publicx11Event (e=<optimized out>, this=<optimized out>) at ../../kdeui/kernel/kapplication.cpp:918
#15 KApplication::x11EventFilter (this=0x177bbe9, _event=0x7fff13c404d0) at ../../kdeui/kernel/kapplication.cpp:930
#16 0x00007f01051a65dc in qt_x11EventFilter (ev=0x7fff13c404d0) at kernel/qapplication_x11.cpp:442
#17 0x00007f01051b6e40 in QApplication::x11ProcessEvent (this=0x7fff13c409d0, event=event@entry=0x7fff13c404d0) at kernel/qapplication_x11.cpp:3461
#18 0x00007f01051dfb02 in x11EventSourceDispatch (s=0x10efc20, callback=0x0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146
#19 0x00007f0101a95e04 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#20 0x00007f0101a96048 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#21 0x00007f0101a960ec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#22 0x00007f0105dd17a1 in QEventDispatcherGlib::processEvents (this=0x104f6d0, flags=...) at kernel/qeventdispatcher_glib.cpp:434
#23 0x00007f01051dfbb6 in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#24 0x00007f0105da30af in QEventLoop::processEvents (this=this@entry=0x7fff13c408a0, flags=...) at kernel/qeventloop.cpp:149
#25 0x00007f0105da33a5 in QEventLoop::exec (this=this@entry=0x7fff13c408a0, flags=...) at kernel/qeventloop.cpp:204
#26 0x00007f0105da8b79 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1225
#27 0x00007f010513c37c in QApplication::exec () at kernel/qapplication.cpp:3828
#28 0x00007f00f02bcd1b in kdemain (argc=1, argv=0x10d0640) at ../../kded/kded.cpp:940
#29 0x00000000004083ee in launch (argc=argc@entry=1, _name=_name@entry=0x40afc7 "kded4", args=args@entry=0x0, cwd=cwd@entry=0x0, envc=envc@entry=0, envs=<optimized out>, envs@entry=0x0, reset_env=reset_env@entry=false, tty=tty@entry=0x0, avoid_loops=avoid_loops@entry=false, startup_id_str=startup_id_str@entry=0x40ae56 "0") at ../../kinit/kinit.cpp:738
#30 0x00000000004059a3 in main (argc=4, argv=<optimized out>, envp=0x7fff13c41130) at ../../kinit/kinit.cpp:1853

Possible duplicates by query: bug 336966, bug 335512, bug 335185.

Report to https://bugs.kde.org/

Reproducible: Always
Comment 1 Dennis Schridde 2014-09-07 05:58:30 UTC
Created attachment 88599 [details]
Old system tray icons displayed after crash / return from standby
Comment 2 Christoph Feck 2014-09-07 23:28:11 UTC

*** This bug has been marked as a duplicate of bug 328535 ***
Comment 3 Christoph Feck 2014-09-07 23:32:29 UTC
All symptoms you see are caused by crashed kded. You can restart kded by running "kded4" in krunner or konsole. If the crash persists, try disabling power management in "kcmshell4 kded" until Solid developers can reproduce the bug.
Comment 4 Dennis Schridde 2014-09-08 05:00:40 UTC
(In reply to Christoph Feck from comment #3)
> All symptoms you see are caused by crashed kded. You can restart kded by
> running "kded4" in krunner or konsole.

Starting kded4 from a console does not fix the icons or make Klipper operational again (e.g. "clear clipboard history" has no effect). I did not try the other actions yet, to see if they work again.

> If the crash persists, try disabling
> power management in "kcmshell4 kded" until Solid developers can reproduce
> the bug.

The problem persists since a long time and returns after a few times of returning from standby.