GNOME Bugzilla – Bug 535574
crash in Home Folder: habe auf einen Windows X...
Last modified: 2008-05-30 11:18:52 UTC
What were you doing when the application crashed? habe auf einen Windows XP Rechner im Netzwerk zugegriffen. 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: SphereCrystal Icon Theme: SphereCrystal Memory status: size: 453615616 vsize: 453615616 resident: 31047680 share: 17731584 rss: 31047680 rss_rlim: 18446744073709551615 CPU usage: start_time: 1212090344 rtime: 810 utime: 752 stime: 58 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 0x2b3882d2a240 (LWP 3437)] (no debugging symbols found) 0x00002b387c520edf in waitpid () from /lib/libpthread.so.0
+ Trace 199041
Thread 1 (Thread 0x2b3882d2a240 (LWP 3437))
----------- .xsession-errors --------------------- CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: full-authentication!!! ** (nautilus:3437): WARNING **: Hit unhandled case 31 (Vorgang abgebrochen) in fm_report_error_loading_directory ** (nautilus:3437): WARNING **: Hit unhandled case 2 (Allgemeiner Fehler) in fm_report_error_loading_directory warning: .dynamic section for "/usr/lib/libXau.so.6" is not at the expected address (wrong library or version mismatch?) --------------------------------------------------
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 ***