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 662138 - Gtk-CRITICAL **: gtk_widget_destroy: assertion `GTK_IS_WIDGET (widget)' failed
Gtk-CRITICAL **: gtk_widget_destroy: assertion `GTK_IS_WIDGET (widget)' failed
Status: RESOLVED OBSOLETE
Product: gtk+
Classification: Platform
Component: Printing
3.0.x
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2011-10-18 20:57 UTC by Andreas J. Guelzow
Modified: 2018-04-15 00:09 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Don't crash when cancelling printing (1.44 KB, patch)
2014-03-13 12:57 UTC, Marek Kašík 		none Details | Review

Description Andreas J. Guelzow 2011-10-18 20:57:30 UTC 
When printing using the gtkprintoperation with progress report and closing the progress report window using the window close box the following critical is printed on the console:

(/home/aguelzow/gnumeric/bin/gnumeric:22805): Gtk-CRITICAL **: gtk_widget_destroy: assertion `GTK_IS_WIDGET (widget)' failed
Comment 1 Marek Kašík 2014-03-13 12:57:20 UTC 
Created attachment 271707 [details] [review]
Don't crash when cancelling printing

Thank you for this report. The attached patch fixes the problem for me.
Comment 2 Matthias Clasen 2018-02-10 04:59:06 UTC 
We're moving to gitlab! As part of this move, we are moving bugs to NEEDINFO if they haven't seen activity in more than a year. If this issue is still important to you and still relevant with GTK+ 3.22 or master, please reopen it and we will migrate it to gitlab.
Comment 3 Matthias Clasen 2018-04-15 00:09:16 UTC 
As announced a while ago, we are migrating to gitlab, and bugs that haven't seen activity in the last year or so will be not be migrated, but closed out in bugzilla.

If this bug is still relevant to you, you can open a new issue describing the symptoms and how to reproduce it with gtk 3.22.x or master in gitlab:

https://gitlab.gnome.org/GNOME/gtk/issues/new