GNOME Bugzilla – Bug 512329
crash in Open Folder: Eating a popsicle. Was ...
Last modified: 2008-01-27 11:50:38 UTC
Version: 2.18.3 What were you doing when the application crashed? Eating a popsicle. Was not at the computer nor running a background process. Distribution: Debian lenny/sid Gnome Release: 2.20.3 2008-01-12 (Debian) BugBuddy Version: 2.20.1 System: Linux 2.6.22-3-k7 #1 SMP Mon Nov 12 09:12:50 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 75472896 vsize: 75472896 resident: 26079232 share: 14979072 rss: 26079232 rss_rlim: 4294967295 CPU usage: start_time: 1201409822 rtime: 97 utime: 90 stime: 7 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 0xb6db46b0 (LWP 3578)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 186933
Thread 1 (Thread 0xb6db46b0 (LWP 3578))
----------- .xsession-errors (9 sec old) --------------------- /etc/gdm/Xsession: Beginning session setup... SESSION_MANAGER=local/down2007:/tmp/.ICE-unix/3519 Window manager warning: Failed to read saved session file /home/joeg/.metacity/sessions/default0.ms: Failed to open file '/home/joeg/.metacity/sessions/default0.ms': No such file or directory 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 Initializing gnome-mount extension --------------------------------------------------
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 ***