Red Hat Bugzilla – Bug 1283058
[abrt] kf5-kinit: __find_specmb(): kdeinit5 killed by SIGSEGV
Last modified: 2016-07-19 14:29:49 EDT
Description of problem:
After the latest updates my FN Keys do not work, i.e. I cannot adjust the volume or screen brightness. I think this is related to this problem.
Additionally the sentence "Could not start process. Cannot talk to klauncher. Not connected to D-Bus server." is printed on my desktop wallpaper.
Version-Release number of selected component:
cmdline: 'kmix [kdeinit5] -session 10d0726169000144781165100000017040036_1447827466_9760'
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 1095864 [details]
Created attachment 1095865 [details]
Created attachment 1095866 [details]
Created attachment 1095867 [details]
Created attachment 1095868 [details]
Created attachment 1095869 [details]
Created attachment 1095870 [details]
Created attachment 1095871 [details]
Created attachment 1095872 [details]
Created attachment 1095873 [details]
Created attachment 1095874 [details]
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.