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 755420 - save/don't save dialog does not appear correctly on close
save/don't save dialog does not appear correctly on close
Status: RESOLVED DUPLICATE of bug 755294
Product: gedit
Classification: Applications
Component: general
3.17.x
Other Linux
: Normal normal
: ---
Assigned To: Gedit maintainers
Gedit maintainers
Depends on:
Blocks:
 
 
Reported: 2015-09-22 15:25 UTC by langdon
Modified: 2015-09-22 16:48 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
result of clicking on "X" or quit (1.50 MB, image/png)
2015-09-22 15:25 UTC, langdon 		Details

Description langdon 2015-09-22 15:25:53 UTC 
Created attachment 311880 [details]
result of clicking on "X" or quit

Verision 3.17.92-1

When I have a file I don't want to save, I click on the "X" (or quit from the top menu) to kill the window. I get a popup that is completely blank. Must kill the application from the command line.
Comment 1 Ondrej Holy 2015-09-22 16:20:13 UTC 
I can confirm this behavioral on Fedora 23 with gedit-3.17.92-1.fc23.x86_64. Following output is printed:

(gedit:9937): GLib-GObject-CRITICAL **: g_param_spec_internal: assertion '!(flags & G_PARAM_STATIC_NAME) || is_canonical (name)' failed

(gedit:9937): GLib-GObject-CRITICAL **: g_object_class_install_properties: assertion 'pspec != NULL' failed

(gedit:9937): GLib-GObject-CRITICAL **: g_object_new_valist: object class 'GeditCloseConfirmationDialog' has no property named 'unsaved_documents'
Comment 2 Paolo Borelli 2015-09-22 16:48:07 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 755294 ***