Description of problem: Well, the reproducer for this is a bit tricky. I'm testing a 23 Workstation image with the downgraded yelp 3.17.2 we're pulling into RC10. What I did was start opening installed apps, opening their help pages, clicking around a bit, quitting, and moving onto the next one. This crash seems to happen semi-reliably when I get to Clocks. I first run the apps in the Dash, skipping Evo as it takes forever to set up and Firefox as it doesn't use yelp, so: Rhythmbox Shotwell Nautilus Software (except it has no Help screen) then I move onto the overview: Boxes Cheese when I got to Cheese, I did a bit more testing - I ran a search and clicked on a result, and also added a bookmark, and maximized the window. I did that again when I reproduced it. I'm not *sure* if it's really needed, to reproduce the bug. The next app in the list is Clocks, and when I run it and open the Help, I hit this crash. It's happened three times so far. Subsequent attempts to launch the Clocks help work fine, the issue doesn't reliably recur. Version-Release number of selected component: yelp-3.17.2-2.fc23 Additional info: reporter: libreport-2.6.3 backtrace_rating: 4 cmdline: yelp help:cheese crash_function: gtk_application_impl_before_emit executable: /usr/bin/yelp global_pid: 3212 kernel: 4.2.3-300.fc23.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:4832 #6 g_main_context_iteration at gmain.c:3901 #7 g_application_run at gapplication.c:2331 #9 _start Potential duplicate: bug 1238389
Created attachment 1087758 [details] File: backtrace
Created attachment 1087759 [details] File: cgroup
Created attachment 1087760 [details] File: core_backtrace
Created attachment 1087761 [details] File: dso_list
Created attachment 1087762 [details] File: environ
Created attachment 1087763 [details] File: exploitable
Created attachment 1087764 [details] File: limits
Created attachment 1087765 [details] File: maps
Created attachment 1087766 [details] File: mountinfo
Created attachment 1087767 [details] File: open_fds
Created attachment 1087768 [details] File: proc_pid_status
Created attachment 1087769 [details] File: var_log_messages
Hmm, Googling shows several similar-looking reports: https://bugzilla.redhat.com/show_bug.cgi?id=1225900 https://bugzilla.redhat.com/show_bug.cgi?id=1226229 https://bugzilla.redhat.com/show_bug.cgi?id=1226010 https://bugzilla.redhat.com/show_bug.cgi?id=1235596 https://bugzilla.redhat.com/show_bug.cgi?id=1238389 https://bugzilla.redhat.com/show_bug.cgi?id=1247036 https://bugzilla.redhat.com/show_bug.cgi?id=1274461
Well I'm no C debugging champion, but it *looks* to me like possibly the issue there is that 'impl' is set to NULL when we hit gtk_application_impl_before_emit() ? In all the traces, it seems like we wind up with impl as '0x0' (which is NULL, right?) for the gtk_application_impl_before_emit() call. The thing that calls that is g_application_impl_method_call in glib, so I'm gonna tentatively assign this one to glib for now. Correct me if I'm completely wrong, of course :) g_application_impl_method_call appears to take an argument 'user_data' which it then turns into a GApplicationImpl called 'impl', and then it passes the 'app' property of that 'impl' object to gtk_application_impl_before_emit() as its 'impl' argument, and that's about as far as I got. If I'm approximately correct there, it would seem like this bug isn't really anything to do with yelp and so it's unlikely to be something that's regressed when we revert from yelp 3.18 to 3.17.2.
Although on the other hand, just possibly, https://git.gnome.org/browse/yelp/commit/?id=30b8883338e5f6df1898c72df8dea490d61f2a0f might help with this? I'm just spitballing, but I still haven't managed to reproduce it with yelp 3.18.1, so it's *possible* something between 3.17.2 and 3.18.1 did something about this...
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '23'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 23 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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 ***