GNOME Bugzilla – Bug 533116
crash in Home Folder:
Last modified: 2008-05-14 16:52:46 UTC
What were you doing when the application crashed? 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 Sat Apr 19 00:37:55 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 72208384 vsize: 72208384 resident: 28540928 share: 14987264 rss: 28540928 rss_rlim: 4294967295 CPU usage: start_time: 1210773107 rtime: 123 utime: 115 stime: 8 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 0xb6c13720 (LWP 3458)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 197707
Thread 1 (Thread 0xb6c13720 (LWP 3458))
----------- .xsession-errors (10 sec old) --------------------- SESSION_MANAGER=local/verao:/tmp/.ICE-unix/3387 ** Message: another SSH agent is running at: /tmp/ssh-eUDPVL3387/agent.3387 Aviso do gerenciador de janelas: Falha ao ler o arquivo de sessão salvo /home/suporte/.metacity/sessions/default0.ms: Failed to open file '/home/suporte/.metacity/sessions/default0.ms': Arquivo ou di Initializing gnome-mount extension seahorse nautilus module initialized xrdb: "*Label.background" on line 220 overrides entry on line 150 xrdb: "*Text.background" on line 226 overrides entry on line 191 xrdb: "*Label.foreground" on line 232 overrides entry on line 151 xrdb: "*Text.foreground" on line 238 overrides entry on line 192 connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: full-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 ***