GNOME Bugzilla – Bug 534963
crash in File Browser: open red
Last modified: 2008-05-26 22:17:22 UTC
Version: 2.20.0 What were you doing when the application crashed? open red Distribution: Debian lenny/sid Gnome Release: 2.22.1 2008-04-08 (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: Clearlooks Icon Theme: gnome Memory status: size: 74825728 vsize: 74825728 resident: 27541504 share: 16314368 rss: 27541504 rss_rlim: 4294967295 CPU usage: start_time: 1211829895 rtime: 663 utime: 625 stime: 38 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 0xb6b52720 (LWP 3002)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 198710
Thread 1 (Thread 0xb6b52720 (LWP 3002))
----------- .xsession-errors (22 sec old) --------------------- Advertencia del gestor de ventanas: Ocurrió un error al leer el archivo de sesión guardado /home/jose/.metacity/sessions/default0.ms: Failed to open file '/home/jose/.metacity/sessions/default0.ms': Initializing gnome-mount extension seahorse nautilus module initialized connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: fill-authentication!!! Initializing gnome-mount extension seahorse nautilus module initialized ** (nautilus:3002): WARNING **: Hit unhandled case 24 (Operación no permitida) in fm_report_error_setting_permissions ** (nautilus:3002): WARNING **: Hit unhandled case 24 (Operación no permitida) in fm_report_error_setting_permissions ** (nautilus:3002): WARNING **: Hit unhandled case 24 (Operación no permitida) in fm_report_error_setting_permissions --------------------------------------------------
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 ***