Red Hat Bugzilla – Bug 1282184
[abrt] kf5-kded: __find_specmb(): kded5 killed by SIGSEGV
Last modified: 2015-11-19 17:43:50 EST
Description of problem:
After the update I have shutted down the computer and in the next day I just started it.
Version-Release number of selected component:
runlevel: N 5
Thread no. 1 (10 frames)
#0 __find_specmb at printf-parse.h:108
#1 _IO_vfprintf_internal at vfprintf.c:1315
#2 buffered_vfprintf at vfprintf.c:2348
#3 _IO_vfprintf_internal at vfprintf.c:1296
#4 ___fprintf_chk at fprintf_chk.c:35
#5 fprintf at /usr/include/bits/stdio2.h:98
#6 qDefaultMessageHandler at global/qlogging.cpp:1486
#7 qt_message_print at global/qlogging.cpp:1540
#8 qt_message(QtMsgType, const QMessageLogContext &, const char *, typedef __va_list_tag __va_list_tag *) at global/qlogging.cpp:262
#9 QMessageLogger::warning at global/qlogging.cpp:540
Created attachment 1094373 [details]
Created attachment 1094374 [details]
Created attachment 1094375 [details]
Created attachment 1094376 [details]
Created attachment 1094377 [details]
Created attachment 1094378 [details]
Created attachment 1094379 [details]
Created attachment 1094380 [details]
Created attachment 1094381 [details]
Created attachment 1094382 [details]
Created attachment 1094383 [details]
Another user experienced a similar problem:
The problem emerged about 2 days ago after reboot. I suspect some of recent kf5 updates.
After every login to KDE Plasma shell kded5 eats 100% of one CPU, strace shows it's looking for some icons which are not present.
After some time (~2 minutes) kded5 dies leaving KDE in a semi-broken state (I'm able to connect to networks by calling nm-cli from shell) which is mostly unusable.
The problem is not limited to my regular user, I observe this behavior with newly created user account as well.
reason: kded5 killed by SIGSEGV
runlevel: N 5
After today's updates (mostly qt5) the problem has disappeared, KDE seems to be functional now.
*** This bug has been marked as a duplicate of bug 1282261 ***