GNOME Bugzilla – Bug 524155
crash in Open Folder: Distribution: Debian len...
Last modified: 2008-03-25 15:16:56 UTC
Version: 2.20.0 What were you doing when the application crashed? Distribution: Debian lenny/sid Gnome Release: 2.20.3 2008-01-09 (Parsix) BugBuddy Version: 2.20.1 System: Linux 2.6.23-parsix-17 #1 SMP PREEMPT Thu Feb 14 14:38:42 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Human Icon Theme: Human Memory status: size: 58195968 vsize: 58195968 resident: 25022464 share: 15593472 rss: 25022464 rss_rlim: 4294967295 CPU usage: start_time: 1206383864 rtime: 944 utime: 861 stime: 83 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' (no debugging symbols found) Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb6b236d0 (LWP 3213)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 193225
Thread 1 (Thread 0xb6b236d0 (LWP 3213))
----------- .xsession-errors --------------------- xrdb: "*Text.foreground" on line 238 overrides entry on line 192 Window manager warning: Failed to load theme "Human": Failed to find a valid file for theme Human xrdb: "*Label.background" on line 220 overrides entry on line 150 xrdb: "*Text.background" on line 226 overrides entry on line 191 xrdb: "*Label.foreground" on line 232 overrides entry on line 151 xrdb: "*Text.foreground" on line 238 overrides entry on line 192 (nautilus:3213): Eel-WARNING **: No extension, not implemented yet (nautilus:3213): Eel-WARNING **: No extension, not implemented yet ** (nautilus:3213): CRITICAL **: gmenu_tree_directory_get_contents: assertion `directory != NULL' failed ** (nautilus:3213): CRITICAL **: gmenu_tree_item_unref: assertion `item != NULL' 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 355018 ***