Version-Release number of selected component: yelp-3.16.1-1.fc22 Additional info: reporter: libreport-2.6.0 backtrace_rating: 4 cmdline: yelp crash_function: gtk_application_impl_before_emit executable: /usr/bin/yelp global_pid: 5492 kernel: 4.0.6-300.fc22.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (6 frames) #0 gtk_application_impl_before_emit at gtkapplicationimpl.c:83 #1 g_application_impl_method_call at gapplicationimpl-dbus.c:272 #2 call_in_idle_cb at gdbusconnection.c:4884 #6 g_main_context_iteration at gmain.c:3869 #7 g_application_run at gapplication.c:2328 #9 _start
Created attachment 1045183 [details] File: backtrace
Created attachment 1045184 [details] File: cgroup
Created attachment 1045185 [details] File: core_backtrace
Created attachment 1045186 [details] File: dso_list
Created attachment 1045187 [details] File: environ
Created attachment 1045188 [details] File: limits
Created attachment 1045189 [details] File: maps
Created attachment 1045190 [details] File: mountinfo
Created attachment 1045191 [details] File: namespaces
Created attachment 1045192 [details] File: open_fds
Created attachment 1045193 [details] File: proc_pid_status
Created attachment 1045194 [details] File: var_log_messages
Another user experienced a similar problem: Started Help initially, then pressed F1 while in Setting->Power. reporter: libreport-2.6.2 backtrace_rating: 4 cmdline: yelp crash_function: gtk_application_impl_before_emit executable: /usr/bin/yelp global_pid: 7673 kernel: 4.1.3-201.fc22.x86_64 package: yelp-3.16.1-1.fc22 reason: yelp killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
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.
*** This bug has been marked as a duplicate of bug 1226229 ***