GNOME Bugzilla – Bug 494671
crash in Open Folder: klicked with right mouse...
Last modified: 2007-11-07 22:23:19 UTC
Version: 2.18.3 What were you doing when the application crashed? klicked with right mouse button on the icon of a usb stick which was connected before booting the computer and selected properties with the left mouse button Distribution: Debian lenny/sid Gnome Release: 2.18.3 2007-07-03 (Debian) BugBuddy Version: 2.18.1 System: Linux 2.6.22-2-powerpc #1 Thu Aug 30 20:52:24 CEST 2007 ppc X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 98283520 vsize: 98283520 resident: 30474240 share: 17645568 rss: 30474240 rss_rlim: 4294967295 CPU usage: start_time: 1194454832 rtime: 220 utime: 193 stime: 27 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 0x300409e0 (LWP 3449)] 0x0f187994 in waitpid () from /lib/libpthread.so.0
+ Trace 176098
Thread 1 (Thread 0x300409e0 (LWP 3449))
----------- .xsession-errors (27 sec old) --------------------- /etc/gdm/PreSession/Default: Registering your session with wtmp and utmp /etc/gdm/PreSession/Default: running: /usr/bin/sessreg -a -w /var/log/wtmp -u /var/run/utmp -x "/var/lib/gdm/:0.Xservers" -h "" -l ":0" "dirk" /etc/gdm/Xsession: Beginning session setup... SESSION_MANAGER=local/mini:/tmp/.ICE-unix/3379 Window manager warning: Failed to read saved session file /home/dirk/.metacity/sessions/default0.ms: Failed to open file '/home/dirk/.metacity/sessions/default0.ms': No such file or directory ** Message: Not starting remote desktop server Initializing gnome-mount extension (gnome-panel:3446): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -9 and height 24 --------------------------------------------------
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 been fixed in version 2.20. 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 ***