GNOME Bugzilla – Bug 601161
crash in File Manager: Steps I did from the GNO...
Last modified: 2009-11-08 20:52:45 UTC
Version: 2.26.3 What were you doing when the application crashed? Steps I did from the GNOME desktop are: 1. Select Places from the GNOME panel at the top of the desktop. 2. Select Home folder. 3. Wait for Nautilus window to be displayed. 4. Pull down Edit menu, then select Preferences --> Crash occurs. I had installed gnome-dbg package to insure full stack traces. This is repeatable. I even created a separate brand new account with no customizations and it crashes consistently on that new user account. The Crash Details states I am using squeeze/sid but I have my /etc/apt/sources.list file that reads differently (set to "testing", but maybe "squeeze" is synonymous with "testing"; I don't know): deb http://ftp.us.debian.org/debian/ testing main contrib non-free deb-src http://ftp.us.debian.org/debian/ testing main contrib non-free deb http://security.debian.org/ testing/updates main contrib deb-src http://security.debian.org/ testing/updates main contrib deb http://security.debian.org testing/updates main Distribution: Debian squeeze/sid Gnome Release: 2.28.0 2009-09-27 (Debian) BugBuddy Version: 2.28.0 System: Linux 2.6.30-1-686 #1 SMP Sat Aug 15 19:11:58 UTC 2009 i686 X Vendor: The X.Org Foundation X Vendor Release: 10402000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome GTK+ Modules: gnomebreakpad, canberra-gtk-module Memory status: size: 72376320 vsize: 72376320 resident: 30547968 share: 21827584 rss: 30547968 rss_rlim: 18446744073709551615 CPU usage: start_time: 1257694184 rtime: 113 utime: 108 stime: 5 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 0xb489eb90 (LWP 7714)] 0xb7f2c424 in __kernel_vsyscall ()
+ Trace 218930
Thread 1 (Thread 0xb6d87760 (LWP 7712))
---- Critical and fatal warnings logged during execution ---- ** Eel **: eel_preferences_get_boolean: assertion `name != NULL' failed ** Eel **: eel_preferences_add_callback_while_alive: assertion `G_IS_OBJECT (alive_object)' failed ** Eel **: eel_preferences_get: assertion `name != NULL' failed ** Eel **: eel_preferences_add_callback_while_alive: assertion `G_IS_OBJECT (alive_object)' failed ** Eel **: eel_preferences_get: assertion `name != NULL' failed ** Eel **: eel_preferences_add_callback_while_alive: assertion `G_IS_OBJECT (alive_object)' failed ** Eel **: eel_preferences_get: assertion `name != NULL' failed ** Eel **: eel_preferences_add_callback_while_alive: assertion `G_IS_OBJECT (alive_object)' failed ** Eel **: eel_preferences_get: assertion `name != NULL' failed ** Eel **: eel_preferences_add_callback_while_alive: assertion `G_IS_OBJECT (alive_object)' failed ** Eel **: eel_preferences_get: assertion `name != NULL' failed ** Eel **: eel_preferences_add_callback_while_alive: assertion `G_IS_OBJECT (alive_object)' failed ** Eel **: eel_preferences_get: assertion `name != NULL' failed ** Eel **: eel_preferences_add_callback_while_alive: assertion `G_IS_OBJECT (alive_object)' failed ** Eel **: eel_preferences_get_integer: assertion `name != NULL' failed ----------- .xsession-errors --------------------- (nautilus:7712): Eel-CRITICAL **: eel_preferences_get: assertion `name != NULL' failed (nautilus:7712): Eel-CRITICAL **: eel_preferences_add_callback_while_alive: assertion `G_IS_OBJECT (alive_object)' failed (nautilus:7712): Eel-CRITICAL **: eel_preferences_get: assertion `name != NULL' failed (nautilus:7712): Eel-CRITICAL **: eel_preferences_add_callback_while_alive: assertion `G_IS_OBJECT (alive_object)' failed (nautilus:7712): Eel-CRITICAL **: eel_preferences_get: assertion `name != NULL' failed (nautilus:7712): Eel-CRITICAL **: eel_preferences_add_callback_while_alive: assertion `G_IS_OBJECT (alive_object)' failed (nautilus:7712): Eel-CRITICAL **: eel_preferences_get_integer: assertion `name != NULL' failed sys:1: GtkWarning: gtk_widget_set_sensitive: assertion `GTK_IS_WIDGET (widget)' failed --------------------------------------------------
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 ***