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: kf5-kded-5.15.0-1.fc22 Additional info: reporter: libreport-2.6.3 backtrace_rating: 4 cmdline: /usr/bin/kded5 crash_function: __find_specmb executable: /usr/bin/kded5 global_pid: 2303 kernel: 4.2.5-201.fc22.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: 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] File: backtrace
Created attachment 1094374 [details] File: cgroup
Created attachment 1094375 [details] File: core_backtrace
Created attachment 1094376 [details] File: dso_list
Created attachment 1094377 [details] File: environ
Created attachment 1094378 [details] File: limits
Created attachment 1094379 [details] File: maps
Created attachment 1094380 [details] File: mountinfo
Created attachment 1094381 [details] File: open_fds
Created attachment 1094382 [details] File: proc_pid_status
Created attachment 1094383 [details] File: var_log_messages
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. reporter: libreport-2.6.3 backtrace_rating: 4 cmdline: /usr/bin/kded5 crash_function: __find_specmb executable: /usr/bin/kded5 global_pid: 6042 kernel: 4.2.5-201.fc22.x86_64 package: kf5-kded-5.16.0-1.fc22 reason: kded5 killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1026
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 ***