GNOME Bugzilla – Bug 534778
crash in Open Folder: right mouse button on an...
Last modified: 2008-05-25 16:33:22 UTC
Version: 2.18.3 What were you doing when the application crashed? right mouse button on an icon -> preferences Distribution: Debian lenny/sid Gnome Release: 2.22.1 2008-04-08 (Debian) BugBuddy Version: 2.20.1 System: Linux 2.6.22-3-686 #1 SMP Mon Nov 12 08:32:57 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: 81047552 vsize: 81047552 resident: 30285824 share: 14766080 rss: 30285824 rss_rlim: 4294967295 CPU usage: start_time: 1211729555 rtime: 147 utime: 139 stime: 8 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb6de9720 (LWP 32417)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 198599
Thread 1 (Thread 0xb6de9720 (LWP 32417))
----------- .xsession-errors --------------------- Window manager warning: Failed to read saved session file /home/korya/.metacity/sessions/default0.ms: Failed to open file '/home/korya/.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 (gnome-panel:32416): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -7 and height 24 ** (gnome-cups-icon:32468): WARNING **: IPP request failed with status 1280 ** (gnome-cups-icon:32468): WARNING **: IPP request failed with status 1280 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 --------------------------------------------------
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 ***