GNOME Bugzilla – Bug 123181
Crash with terminal and gedit open
Last modified: 2004-12-22 21:47:04 UTC
Using a Gnome2.4 setup built on 24th September 2003. - Accessibility was turned on. - Nautilus was opened. - The only other apps open were gedit and gnome-terminal. Nautilus crashed. It doesn't happen every time, but Nautilus seems to dies quite frequently. Here is the trace output: ------------------------- gdb /opt/gnome-2.4/bin/nautilus GNU gdb Red Hat Linux 7.x (5.0rh-15) (MI_OUT) Copyright 2001 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditi ons. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for detail s. This GDB was configured as "i386-redhat-linux"... (gdb) run Starting program: /opt/gnome-2.4/bin/nautilus [New Thread 1024 (LWP 18216)] Bonobo accessibility support initialized GTK Accessibility Module initialized Atk Accessibilty bridge initialized [New Thread 2049 (LWP 18217)] [New Thread 1026 (LWP 18218)] [New Thread 2051 (LWP 18219)] [New Thread 3076 (LWP 18220)] [New Thread 4101 (LWP 18240)] (nautilus:18216): Bonobo-CRITICAL **: file bonobo-ui-component.c: line 1206 (impl_set_prop): assertion `container != CORBA_OBJECT_NIL' failed (nautilus:18216): Bonobo-WARNING **: Freeze/thaw mismatch on '18216-2' (nautilus:18216): Gtk-WARNING **: Calling gtk_widget_realize() on a widget that isn't inside a toplevel window is not going to work very well. Widgets must be inside a toplevel container before realizing them. (nautilus:18216): Gtk-CRITICAL **: file gtkstyle.c: line 789 (gtk_style_attach): assertion `window != NULL' failed ** ERROR **: file nautilus-icon-container.c: line 3003 (realize): assertion failed: (GTK_IS_WINDOW (gtk_widget_get_toplevel (widget))) aborting... Program received signal SIGABRT, Aborted.
+ Trace 40420
Thread 1024 (LWP 18216)
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 119370 ***