Description of problem: after restart system . Version-Release number of selected component: kmix-15.04.0-1.fc22 Additional info: reporter: libreport-2.6.3 backtrace_rating: 4 cmdline: /bin/kmix -session 1028c1d320b210000144771150100000017510008_1447713053_614911 crash_function: _IO_vfprintf_internal executable: /usr/bin/kmix global_pid: 1913 kernel: 4.2.5-201.fc22.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 _IO_vfprintf_internal at vfprintf.c:257 #1 buffered_vfprintf at vfprintf.c:2348 #2 _IO_vfprintf_internal at vfprintf.c:1296 #3 ___fprintf_chk at fprintf_chk.c:35 #4 fprintf at /usr/include/bits/stdio2.h:98 #5 qDefaultMessageHandler at global/qlogging.cpp:1486 #6 qt_message_print at global/qlogging.cpp:1540 #7 qt_message(QtMsgType, const QMessageLogContext &, const char *, typedef __va_list_tag __va_list_tag *) at global/qlogging.cpp:262 #8 QMessageLogger::warning at global/qlogging.cpp:540 #9 QSystemTrayIcon::setVisible at util/qsystemtrayicon.cpp:268
Created attachment 1095878 [details] File: backtrace
Created attachment 1095879 [details] File: cgroup
Created attachment 1095880 [details] File: core_backtrace
Created attachment 1095881 [details] File: dso_list
Created attachment 1095882 [details] File: environ
Created attachment 1095883 [details] File: limits
Created attachment 1095885 [details] File: maps
Created attachment 1095886 [details] File: mountinfo
Created attachment 1095887 [details] File: open_fds
Created attachment 1095888 [details] File: proc_pid_status
Created attachment 1095889 [details] File: var_log_messages
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 bug. Thank you for reporting this bug and we are sorry it could not be fixed.