After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 685995 - Crash in g_menu_exporter_name_vanished
Crash in g_menu_exporter_name_vanished
Status: RESOLVED FIXED
Product: glib
Classification: Platform
Component: gio
2.34.x
Other Linux
: Normal critical
: ---
Assigned To: gtkdev
gtkdev
Depends on:
Blocks:
 
 
Reported: 2012-10-11 18:53 UTC by Michael Terry
Modified: 2012-10-16 16:32 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
GMenuExporter: allow NULL bus on _name_vanished (1.07 KB, patch)
2012-10-16 16:31 UTC, Allison Karlitskaya (desrt) 		committed Details | Review

Description Michael Terry 2012-10-11 18:53:21 UTC 
The assert in g_menu_exporter_name_vanished() is being triggered in downstream bug https://bugs.launchpad.net/glib/+bug/1044322

The assert is:
g_assert (exporter->connection == connection);

Stacktrace here:
https://bugs.launchpad.net/glib/+bug/1044322/+attachment/3285593/+files/Stacktrace.txt
Comment 1 Allison Karlitskaya (desrt) 2012-10-16 16:30:53 UTC 
This was caused by a lack of documentation (see bug 686231 for the fix).
Comment 2 Allison Karlitskaya (desrt) 2012-10-16 16:31:24 UTC 
Created attachment 226567 [details] [review]
GMenuExporter: allow NULL bus on _name_vanished

GBusNameVanishedCallback is called with a NULL GDBusConnection in the
case that the connection has vanished.  We were doing an assert to
verify that it was the same as we had exported the menu on and that
assert was failing.
Comment 3 Allison Karlitskaya (desrt) 2012-10-16 16:32:28 UTC 
Attachment 226567 [details] pushed as 212ffcc - GMenuExporter: allow NULL bus on _name_vanished