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 497415 - Failed assertion upon exit
Failed assertion upon exit
Status: RESOLVED FIXED
Product: gnome-utils
Classification: Deprecated
Component: baobab
2.20.x
Other Linux
: Normal normal
: ---
Assigned To: Fabio Marzocca
gnome-utils Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-11-16 16:15 UTC by Josselin Mouette
Modified: 2007-12-14 20:55 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description Josselin Mouette 2007-11-16 16:15:30 UTC 
Steps to reproduce the bug easily:
 1. run "baobab /" in a terminal
 2. close the window while it is scanning the disk
 3. It displays:

(baobab:9989): Gtk-CRITICAL **: gtk_main_quit: assertion `main_loops != NULL' failed

A quick analysis shows that in this situation, GTK+ is already exiting, but on_delete_activate calls gtk_main_quit again, which seems to cause this error.

Original bug: http://bugs.debian.org/447016 by Francesco Potortì
Comment 1 Paolo Borelli 2007-12-14 20:55:49 UTC 
Since the scan of a dir iterates the main loop manually the normal main loop was never properly started in this case. Hence the assertion.

I fixed this on trunk by starting the dir scan in an idle only after the real main loop has been started.