GNOME Bugzilla – Bug 512362
crash in File Browser: right-clic menu -> prope...
Last modified: 2008-01-27 14:05:31 UTC
Version: 2.18.3 What were you doing when the application crashed? right-clic menu -> properties on a folder in a mounted disk /dev/hda2 on /media/hda2 Distribution: Debian lenny/sid Gnome Release: 2.20.3 2008-01-12 (Debian) BugBuddy Version: 2.20.1 System: Linux 2.6.22-3-amd64 #1 SMP Sun Nov 4 18:18:09 UTC 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Glossy P Icon Theme: OSX Memory status: size: 332439552 vsize: 332439552 resident: 29167616 share: 16773120 rss: 29167616 rss_rlim: 18446744073709551615 CPU usage: start_time: 1201440900 rtime: 217 utime: 190 stime: 27 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/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0x2b4a1c075540 (LWP 16665)] (no debugging symbols found) 0x00002b4a153ff34f in waitpid () from /lib/libpthread.so.0
+ Trace 186952
Thread 1 (Thread 0x2b4a1c075540 (LWP 16665))
----------- .xsession-errors --------------------- ** 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 warning: .dynamic section for "/usr/lib/libcairo.so.2" is not at the expected address (wrong library or version mismatch?) warning: .dynamic section for "/usr/lib/libgstreamer-0.10.so.0" is not at the expected address (wrong library or version mismatch?) --------------------------------------------------
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 ***