GNOME Bugzilla – Bug 601356
crash in File Manager: After opening file manag...
Last modified: 2009-11-10 04:33:49 UTC
Version: 2.26.3 What were you doing when the application crashed? After opening file manager and choosing "preferences", the application died. Distribution: Debian squeeze/sid Gnome Release: 2.28.0 2009-09-27 (Debian) BugBuddy Version: 2.28.0 System: Linux 2.6.30.4-agnus #4 Mon Oct 19 21:52:34 BRT 2009 i686 X Vendor: The X.Org Foundation X Vendor Release: 10605000 Selinux: No Accessibility: Disabled GTK+ Theme: Unity Icon Theme: gnome-alternative GTK+ Modules: gnomebreakpad Memory status: size: 95121408 vsize: 95121408 resident: 34152448 share: 21417984 rss: 34152448 rss_rlim: 18446744073709551615 CPU usage: start_time: 1257818037 rtime: 222 utime: 206 stime: 16 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' [Thread debugging using libthread_db enabled] [New Thread 0xb47beb90 (LWP 8785)] 0xffffe424 in __kernel_vsyscall ()
+ Trace 218970
Thread 1 (Thread 0xb6f2b760 (LWP 8773))
Inferior 1 [process 8773] will be detached. Quit anyway? (y or n) [answered Y; input not from terminal] ---- Critical and fatal warnings logged during execution ---- ** Gtk **: gtk_combo_box_append_text: assertion `GTK_IS_COMBO_BOX (combo_box)' failed ** Gtk **: gtk_combo_box_append_text: assertion `GTK_IS_COMBO_BOX (combo_box)' failed ** Gtk **: gtk_combo_box_append_text: assertion `GTK_IS_COMBO_BOX (combo_box)' failed ** Gtk **: gtk_combo_box_append_text: assertion `GTK_IS_COMBO_BOX (combo_box)' failed ** Gtk **: gtk_combo_box_append_text: assertion `GTK_IS_COMBO_BOX (combo_box)' failed ** Gtk **: gtk_combo_box_append_text: assertion `GTK_IS_COMBO_BOX (combo_box)' failed ** Gtk **: gtk_combo_box_append_text: assertion `GTK_IS_COMBO_BOX (combo_box)' failed ** Gtk **: gtk_combo_box_append_text: assertion `GTK_IS_COMBO_BOX (combo_box)' failed ** Gtk **: gtk_combo_box_append_text: assertion `GTK_IS_COMBO_BOX (combo_box)' failed ** Gtk **: gtk_combo_box_append_text: assertion `GTK_IS_COMBO_BOX (combo_box)' failed ** GLib-GObject **: g_object_set_data_full: assertion `G_IS_OBJECT (object)' failed ** Gtk **: gtk_widget_set_sensitive: assertion `GTK_IS_WIDGET (widget)' failed ** GLib-GObject **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed ** GLib-GObject **: g_signal_handlers_block_matched: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed ** GLib-GObject **: g_object_get_data: assertion `G_IS_OBJECT (object)' failed ----------- .xsession-errors (1499731 sec old) --------------------- xrdb: "*Label.foreground" on line 232 overrides entry on line 151 xrdb: "*Text.foreground" on line 238 overrides entry on line 192 Window manager warning: Failed to read saved session file /home/hdab/.metacity/sessions/default0.ms: Failed to open file '/home/hdab/.metacity/sessions/default0.ms': No such file or directory Bluetooth OBEX server failed: The name org.openobex was not provided by any .service files Bluetooth FTP server failed: The name org.openobex was not provided by any .service files seahorse nautilus module initialized ** (nautilus:12660): WARNING **: /usr/lib/nautilus/extensions-1.0/libnautilus-gksu.so: cannot open shared object file: No such file or directory Initializing gnome-mount extension (gnome-panel:12659): GConf-WARNING **: Directory `/apps/panel/toplevels/bottom_panel_screen1/screen' was not being monitored by GConfClient 0x80ec838 (gnome-panel:12659): GConf-WARNING **: Directory `/apps/panel/toplevels/top_panel_screen1/screen' was not being monitored by GConfClient 0x80ec838 Window manager warning: CurrentTime used to choose focus window; focus window may not be correct. Window manager warning: Got a request to focus the no_focus_window with a timestamp of 0. This shouldn't happen! --------------------------------------------------
Thanks for taking the time to report this bug. 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. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of bug 594302 ***