GNOME Bugzilla – Bug 538752
crash in Open Folder: I was trying to browse a...
Last modified: 2008-06-17 17:53:25 UTC
Version: 2.20.0 What were you doing when the application crashed? I was trying to browse a windows share 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: 89608192 vsize: 89608192 resident: 32518144 share: 16826368 rss: 32518144 rss_rlim: 4294967295 CPU usage: start_time: 1213626049 rtime: 6998 utime: 5670 stime: 1328 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 0xb6bf6720 (LWP 2476)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 200644
Thread 1 (Thread 0xb6bf6720 (LWP 2476))
----------- .xsession-errors (7 sec old) --------------------- QObject: Do not delete object, 'unnamed', during its event handler! (gnome-terminal:2665): Vte-WARNING **: No handler for control sequence `device-control-string' defined. ** (nautilus:2476): WARNING **: No description found for mime type "x-directory/smb-share" (file is "BKP_Robinson"), please tell the gnome-vfs mailing list. 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 ***