GNOME Bugzilla – Bug 536838
crash in File Browser: open a video file
Last modified: 2008-06-05 17:47:18 UTC
Version: 2.20.0 What were you doing when the application crashed? open a video file 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: Clearlooks Icon Theme: gnome Memory status: size: 461139968 vsize: 461139968 resident: 35921920 share: 19554304 rss: 35921920 rss_rlim: 18446744073709551615 CPU usage: start_time: 1212682468 rtime: 139 utime: 129 stime: 10 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 0x2acbb3a03400 (LWP 5947)] (no debugging symbols found) 0x00002acbacc1dedf in waitpid () from /lib/libpthread.so.0
+ Trace 199654
Thread 1 (Thread 0x2acbb3a03400 (LWP 5947))
----------- .xsession-errors --------------------- ** Message: Hit unexpected error "Errore generico" while doing a file operation. Avviso del window manager: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2c0005d (Riprodutto) Avviso del window manager: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. (gnome-terminal:3952): Vte-WARNING **: Nessun gestore definito per la sequenza di controllo "device-control-string". ** (nautilus:3848): WARNING **: Hit unhandled case 19 (Non è una directory) in fm_report_error_loading_directory (nautilus:3848): Eel-WARNING **: No extension, not implemented yet Initializing gnome-mount extension (nautilus:5920): Eel-WARNING **: No extension, not implemented yet Initializing gnome-mount extension (nautilus:5947): 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 ***