Version-Release number of selected component:
libreport version: 2.0.9
:Thread no. 1 (2 frames)
: #5 emit_signal_instance_in_idle_cb at gdbusconnection.c
: #10 IA__gtk_main at gtkmain.c
Created attachment 925828 [details]
Created attachment 925829 [details]
Created attachment 925830 [details]
Created attachment 925831 [details]
Created attachment 925832 [details]
Created attachment 925833 [details]
Created attachment 925834 [details]
Created attachment 925835 [details]
Stack trace looks a little different, but I think this might be another dupe of bug 1126916. I'll just reassign it for now so as not to be too hasty.
Something is apparently very wrong with GObject's type registration in RHEL 6.
I don't see the commonality - the stacktrace here looks entirely different from the one in 1126916.
Ray found this very relevant looking fix that went into glib 2.29 (ie newer than our backport):
Bug 651133 - race condition in GDBusConnection's emit_signal_instance_in_idle_cb (edit)
setting devack+ since we have a pretty likely fix
The correct link looks like: https://bugzilla.gnome.org/show_bug.cgi?id=651133
So looking at that bug, there were several followup fixes. Matthew, are you going to try backporting them?
How reproducible is this crash?
(In reply to Colin Walters from comment #15)
> So looking at that bug, there were several followup fixes. Matthew, are you
> going to try backporting them?
Yeah, taking a crack at it now.
I'm OK with the updated patches here: http://pkgs.devel.redhat.com/cgit/rpms/glib2/commit/?h=rhel-6.6&id=59e30689e73af14ccbf33caa33e090b9dbe2d07e
The patches are nontrivial, but they're backports of commits that have existed upstream for some time. An additional mitigating factor is that the patches only affect the GDBus code, which is new with this rebase, and thus nothing else can be using it (yet).
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.