GNOME Bugzilla – Bug 538753
crash in Computer: connection to a samba se...
Last modified: 2008-06-17 17:53:18 UTC
Version: 2.20.0 What were you doing when the application crashed? connection to a samba serveur, opening a folder Distribution: Debian lenny/sid Gnome Release: 2.22.2 2008-05-29 (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: 86482944 vsize: 86482944 resident: 28430336 share: 14241792 rss: 28430336 rss_rlim: 4294967295 CPU usage: start_time: 1213474229 rtime: 6134 utime: 5836 stime: 298 cutime:511 cstime: 120 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 0xb6bfb720 (LWP 3437)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 200646
Thread 1 (Thread 0xb6bfb720 (LWP 3437))
----------- .xsession-errors (17 sec old) --------------------- Error: Couldn't read xref table Error: May not be a PDF file (continuing anyway) Error: PDF file is damaged - attempting to reconstruct xref table... Error: Couldn't find trailer dictionary Error: Couldn't read xref table connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: full-authentication!!! connection_message_func(): Callback CALLBACK: save-authentication!!! connection_message_func(): Callback CALLBACK: save-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 ***