GNOME Bugzilla – Bug 510879
crash in File Browser: Dopo aver montato un har...
Last modified: 2008-01-23 19:12:46 UTC
Version: 2.18.3 What were you doing when the application crashed? Dopo aver montato un hard disk esterno, volevo verificarne il contenuto e i permessi. Distribution: Debian lenny/sid Gnome Release: 2.20.2 2007-11-29 (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: 105648128 vsize: 105648128 resident: 28995584 share: 16322560 rss: 28995584 rss_rlim: 4294967295 CPU usage: start_time: 1200818032 rtime: 5043 utime: 4723 stime: 320 cutime:6 cstime: 8 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/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb6ccc6b0 (LWP 2599)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 186112
Thread 1 (Thread 0xb6ccc6b0 (LWP 2599))
----------- .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 warning: .dynamic section for "/usr/lib/libORBit-2.so.0" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/usr/lib/libORBitCosNaming-2.so.0" is not at the expected address (wrong library or version mismatch?) --------------------------------------------------
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
Distribution: Debian lenny/sid Gnome Release: 2.20.3 2008-01-12 (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: 77115392 vsize: 77115392 resident: 26042368 share: 15802368 rss: 26042368 rss_rlim: 4294967295 CPU usage: start_time: 1201099720 rtime: 1141 utime: 972 stime: 169 cutime:0 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/i686/cmov/libthread_db.so.1". (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb6c7f6b0 (LWP 2653)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 186511
Thread 1 (Thread 0xb6c7f6b0 (LWP 2653))
----------- .xsession-errors (758 sec old) --------------------- *** Gnome Registry Session: yes. *** Gnome Registry Session: yes. *** Gnome Registry Session: yes. *** Gnome Registry Session: yes. *** Gnome Registry Session: yes. *** Gnome Registry Session: yes. Avviso del window manager: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x260001d (Gestore di) Avviso del window manager: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. Avviso del window manager: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2a00056 (OpenOffice) Avviso del window manager: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. Avviso del window manager: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2a00056 (OpenOffice) Avviso del window manager: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. Avviso del window manager: last_user_time (3076383792) is greater than comparison timestamp (2808998270). This most likely represents a buggy client sending inaccurate timestamps in messages such as Avviso del window manager: 0x2800091 (Synaptic) appears to be one of the offending windows with a timestamp of 3076383792. Working around... /usr/lib/iceweasel/firefox-bin: Symbol `SSL_ImplementedCiphers' has different size in shared object, consider re-linking --------------------------------------------------
not much better, it still misses any calls here:
+ Trace 186524