GNOME Bugzilla – Bug 544885
crash in File Browser: przed awarią przeglądałe...
Last modified: 2008-07-27 09:55:44 UTC
Version: 2.20.0 What were you doing when the application crashed? przed awarią przeglądałem zasoby innego urzytkownika sieci Distribution: Debian lenny/sid Gnome Release: 2.22.3 2008-06-30 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.25-2-686 #1 SMP Fri Jul 18 17:46:56 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10402000 Selinux: No Accessibility: Disabled GTK+ Theme: SphereCrystal Icon Theme: SphereCrystal Memory status: size: 67137536 vsize: 67137536 resident: 23257088 share: 15097856 rss: 23257088 rss_rlim: 4294967295 CPU usage: start_time: 1217109708 rtime: 230 utime: 220 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) [Thread debugging using libthread_db enabled] [New Thread 0xb6b94720 (LWP 3491)] (no debugging symbols found) 0xb7fc5424 in __kernel_vsyscall ()
+ Trace 203861
Thread 1 (Thread 0xb6b94720 (LWP 3491))
----------- .xsession-errors (7 sec old) --------------------- /etc/gdm/Xsession: Beginning session setup... SESSION_MANAGER=local/debian:/tmp/.ICE-unix/3409 ** (gnome-settings-daemon:3468): WARNING **: Failed to open file '/etc/gnome/config/General.ad': Nie ma takiego pliku ani katalogu Ostrzeżenie menedżera okien: Nie można odczytać zapisanego pliku sesji "/home/rosin/.metacity/sessions/default0.ms": Failed to open file '/home/rosin/.metacity/sessions/default0.ms': Nie ma takieg Initializing gnome-mount extension seahorse nautilus module initialized ** Message: <info> Połączono z siecią kablową. ** Message: <info> Połączono z siecią kablową. connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: fill-authentication!!! --------------------------------------------------
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 ***