GNOME Bugzilla – Bug 529152
crash in Open Folder: connecting to a SMB shar...
Last modified: 2008-04-21 16:03:59 UTC
Version: 2.20.0 What were you doing when the application crashed? connecting to a SMB share 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 Thu Mar 27 17:45:04 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: 76296192 vsize: 76296192 resident: 22319104 share: 15138816 rss: 22319104 rss_rlim: 4294967295 CPU usage: start_time: 1208756305 rtime: 218 utime: 199 stime: 19 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 0xb6b88720 (LWP 3465)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 195734
Thread 1 (Thread 0xb6b88720 (LWP 3465))
----------- .xsession-errors (7 sec old) --------------------- Window manager warning: Failed to read saved session file /home/leec/.metacity/sessions/default0.ms: Failed to open file '/home/leec/.metacity/sessions/default0.ms': No such file or directory seahorse nautilus module initialized Initializing gnome-mount extension /usr/lib/python2.4/site-packages/apt/__init__.py:18: FutureWarning: apt API not stable yet warnings.warn("apt API not stable yet", FutureWarning) Window manager warning: last_user_time (3076469808) is greater than comparison timestamp (1870720903). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NE Window manager warning: 0x2a00003 (Software U) appears to be one of the offending windows with a timestamp of 3076469808. Working around... current dist not found in meta-release file Window manager warning: Treating resize request of legacy application 0x2e0000b (mythfronte) as a fullscreen request connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: full-authentication!!! --------------------------------------------------
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 522534 ***