GNOME Bugzilla – Bug 551268
crash in File Browser: I tried to open a .mp3 f...
Last modified: 2008-09-09 12:17:07 UTC
Version: 2.20.0 What were you doing when the application crashed? I tried to open a .mp3 file (maybe corrupted: it's impossible to know the details of this file), but it didn't go well; so I used the option 'open with...' and the application crashed. I had sent also another bug message,but now there is the package gnome-dbg installed on my pc! Distribution: Debian lenny/sid Gnome Release: 2.22.1 2008-04-08 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.24-1-amd64 #1 SMP Sat May 10 09:28:10 UTC 2008 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Tactile Icon Theme: TuxnTosh Memory status: size: 582479872 vsize: 582479872 resident: 33984512 share: 19836928 rss: 33984512 rss_rlim: 18446744073709551615 CPU usage: start_time: 1220812053 rtime: 245 utime: 209 stime: 36 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 0x2b07c38f4240 (LWP 3575)] 0x00002b07bcde8edf in waitpid () from /lib/libpthread.so.0
+ Trace 206459
Thread 1 (Thread 0x2b07c38f4240 (LWP 3575))
----------- .xsession-errors --------------------- /etc/gdm/Xsession: Beginning session setup... SESSION_MANAGER=local/debian1:/tmp/.ICE-unix/3491 ** Message: another SSH agent is running at: /tmp/ssh-feEdMK3491/agent.3491 ** (gnome-settings-daemon:3551): WARNING **: Failed to open file '/etc/gnome/config/General.ad': No such file or directory Avviso del window manager: Lettura del file della sessione /home/niccos/.metacity/sessions/default0.ms fallita: Failed to open file '/home/niccos/.metacity/sessions/default0.ms': No such file or direc seahorse nautilus module initialized Initializing gnome-mount extension (nautilus:3575): Eel-WARNING **: No extension, not implemented yet --------------------------------------------------
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 ***