GNOME Bugzilla – Bug 496737
crash in Home Folder: according to the advice ...
Last modified: 2007-11-15 11:29:41 UTC
What were you doing when the application crashed? according to the advice given on my [Bug 496429], I retried after installing *-dbg packages and did same thing. All I did is just inserted my vfat 2GB usb memory, and right-clicked and saw property of the icon appeared on desktop right after insertion of the stick. then the property window crashed before anything and Bug Buddy appears. hello. Distribution: Debian lenny/sid Gnome Release: 2.18.3 2007-07-03 (Debian) BugBuddy Version: 2.18.1 System: Linux 2.6.21-2-amd64 #1 SMP Tue Jul 10 21:39:38 UTC 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: MidnightBlackPlastic Icon Theme: OSX Memory status: size: 390512640 vsize: 390512640 resident: 31195136 share: 17657856 rss: 31195136 rss_rlim: 18446744073709551615 CPU usage: start_time: 1195037950 rtime: 190 utime: 162 stime: 28 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 0x2b7cf8889bc0 (LWP 3812)] 0x00002b7cf1e10c7f in waitpid () from /lib/libpthread.so.0
+ Trace 177654
Thread 1 (Thread 0x2b7cf8889bc0 (LWP 3812))
----------- .xsession-errors (6359 sec old) --------------------- ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 Premature end of JPEG file Premature end of JPEG file --------------------------------------------------
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 ***