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 756343 - Crash when destroy()ing a main GtkApplicationWindow when a modal GtkDialog is run()
Crash when destroy()ing a main GtkApplicationWindow when a modal GtkDialog is...
Status: RESOLVED DUPLICATE of bug 755490
Product: mutter
Classification: Core
Component: wayland
3.18.x
Other Linux
: Normal critical
: ---
Assigned To: mutter-maint
mutter-maint
Depends on:
Blocks:
 
 
Reported: 2015-10-10 14:01 UTC by Arnaud B.
Modified: 2015-10-10 14:04 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Arnaud B. 2015-10-10 14:01:05 UTC 
I have a systematic crasher of my Wayland session with Dconf Editor master[1]:
* opening a GtkDialog modal of the main GtkApplicationWindow with “dialog.run()” (the ones for editing the keys value –when you click on a row– work, for example, but also a simpler GtkMessageDialog);
* calling from the application’s menu the custom “quit_cb() { get_active_window ().destroy (); }” function.

journalctl gives me something that begins with:
oct. 10 15:30:49 meregee gnome-session[25532]: **
oct. 10 15:30:49 meregee gnome-session[25532]: mutter:ERROR:wayland/meta-wayland-surface.c:380:toplevel_surface_commit: assertion failed: (window != NULL)

[1] https://git.gnome.org/browse/dconf-editor/tree/?id=c2c7b17049923776f03eae285cdfacd0588b7ad6
Comment 1 Jonas Ådahl 2015-10-10 14:04:52 UTC 
Thanks for taking the time to report this.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed in the code repository.

*** This bug has been marked as a duplicate of bug 755490 ***