GNOME Bugzilla – Bug 505544
crash in Computer: open 2 properties of 2 d...
Last modified: 2008-07-23 21:28:27 UTC
Version: 2.18.3 What were you doing when the application crashed? open 2 properties of 2 directories with same name on 2 diferent physical drive (one is hard disk other is digital camera flash memory) Distribution: Debian lenny/sid Gnome Release: 2.20.2 2007-11-29 (Debian) BugBuddy Version: 2.20.1 System: Linux 2.6.18-4-k7 #1 SMP Wed May 9 23:42:01 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 111005696 vsize: 111005696 resident: 28430336 share: 15462400 rss: 28430336 rss_rlim: 4294967295 CPU usage: start_time: 1198578171 rtime: 2611 utime: 2458 stime: 153 cutime:3 cstime: 1 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 -1226983760 (LWP 3845)] (no debugging symbols found) 0xb7630321 in __waitpid_nocancel () from /lib/libpthread.so.0
+ Trace 182982
Thread 1 (Thread -1226983760 (LWP 3845))
----------- .xsession-errors --------------------- ** 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 ** Message: drive = 0 ** Message: volume = 0 Failed to read a valid object file image from memory. --------------------------------------------------
the bug can be reproduce : - on the desktop open the directory new_photo - the unique file in it is 105_pana right-click on it and select properties - keep the properties open and double click on the icon representing the USB mass storage disk (/media/disk) (digital camera) - open /media/disk/dcim directory - the unique file in it is 105_pana right-click on it and select properties The bug occure !
Thanks for taking the time to report this bug. Unfortunately, the stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Could you please help fixing this by installing some debugging packages [1], start the application as normal, and try to reproduce the crash, if possible? Once bug-buddy pops up, you can find the stacktrace in the 'Details', now containing way more information. Please copy that stacktrace and paste it as a comment here. Thanks in advance! [1] Please install debug packages for nautilus, glib2, gtk2, pango, gnome-vfs2, libgnome, and libgnomeui. More details can be found here: http://live.gnome.org/GettingTraces
http://bugzilla.gnome.org/show_bug.cgi?id=505544 Hello, my testing is not fully "up-to-date" so some dbg package are not installable without changing the library version ; so in a first time I keep the version and try reproduce bug dbg symbol installation status: - nautilus ok - libglib2 ok - libgtk2 ok - libpango ok - libgnome-vfs2.0 not ok 1:2.20.0-1 (now) 1:2.20.1-1 (testing) - libgnomeui-0 not ok 2.18.1-2 (now) 2.20.1.1-1 (testing) - libgnome2-0 not ok 2.18.0-4 (now) 2.20.1.1-1 (testing) and no libgnome2-0-dbg package found the bug is reproduce : - I first try the intial file /media/disk/dcim/105_pana right click then select properties (I say file but it's a directory containing photos, sorry for the mistake) where bug appear and it appear again with this stack : Distribution: Debian lenny/sid Gnome Release: 2.20.2 2007-11-29 (Debian) BugBuddy Version: 2.20.1 System: Linux 2.6.18-4-k7 #1 SMP Wed May 9 23:42:01 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 79605760 vsize: 79605760 resident: 22376448 share: 14778368 rss: 22376448 rss_rlim: 4294967295 CPU usage: start_time: 1198979104 rtime: 240 utime: 228 stime: 12 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 0xb6d7b6b0 (LWP 1269)] 0xb75e6321 in waitpid () from /lib/libpthread.so.0
+ Trace 183502
after that I quit gdb then make a killall nautilus to have it restarted. well it's not simple but I hope it's usefull. Thanks for paying attention to this problem and good luck contact me if need more informations best regards, Gilles
Another Debian only problem. *** This bug has been marked as a duplicate of 440988 ***