GNOME Bugzilla – Bug 537583
crash in Computer: Exploration d'un lecteur...
Last modified: 2008-06-10 15:26:18 UTC
Version: 2.20.0 What were you doing when the application crashed? Exploration d'un lecteur sur un poste distant ... Distribution: Debian lenny/sid Gnome Release: 2.22.2 2008-05-29 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.24-1-686 #1 SMP Thu May 8 02:16:39 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Gorilla Icon Theme: Gorilla Memory status: size: 77221888 vsize: 77221888 resident: 22577152 share: 15589376 rss: 22577152 rss_rlim: 4294967295 CPU usage: start_time: 1213097519 rtime: 1119 utime: 1038 stime: 81 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/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb6c0b720 (LWP 3625)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 200029
Thread 1 (Thread 0xb6c0b720 (LWP 3625))
----------- .xsession-errors --------------------- amidi-plug(i_backend.c:i_backend_unload:164): unloading backend 'fluidsynth' amidi-plug(i_backend.c:i_backend_unload:167): backend 'fluidsynth' unloaded LASTFM: (cleanup) Cleanup finished ** (gnome-system-monitor:15718): WARNING **: SELinux was found but is not enabled. /usr/lib/icedove/run-mozilla.sh: line 131: 4096 Processus arrêté "$prog" ${1+"$@"} warning: .dynamic section for "/usr/lib/libgnome-menu.so.2" is not at the expected address (wrong library or version mismatch?) warning: .dynamic section for "/usr/lib/gnome-vfs-2.0/modules/libfile.so" is not at the expected address (wrong library or version mismatch?) warning: .dynamic section for "/usr/lib/libhal.so.1" is not at the expected address (wrong library or version mismatch?) warning: .dynamic section for "/usr/lib/libhal-storage.so.1" 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 522534 ***