GNOME Bugzilla – Bug 534527
crash in Open Folder: accessing hardrive netwo...
Last modified: 2008-05-23 23:21:20 UTC
Version: 2.20.0 What were you doing when the application crashed? accessing hardrive network 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: 75837440 vsize: 75837440 resident: 20840448 share: 14553088 rss: 20840448 rss_rlim: 4294967295 CPU usage: start_time: 1211566784 rtime: 150 utime: 130 stime: 20 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 0xb6b9c720 (LWP 3872)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 198478
Thread 1 (Thread 0xb6b9c720 (LWP 3872))
----------- .xsession-errors --------------------- ** (x-session-manager:3764): WARNING **: Host name lookup failure on localhost. Window manager warning: Failed to read saved session file /home/trillaud/.metacity/sessions/default0.ms: Failed to open file '/home/trillaud/.metacity/sessions/default0.ms': No such file or directory Initializing gnome-mount extension seahorse nautilus module initialized 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!!! Window manager warning: GtkMenu failed to grab the pointer 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 ***