GNOME Bugzilla – Bug 530498
crash in Open Folder: accessing a NAS as windo...
Last modified: 2008-04-29 07:11:48 UTC
Version: 2.20.0 What were you doing when the application crashed? accessing a NAS as windows 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 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: 77946880 vsize: 77946880 resident: 23642112 share: 15761408 rss: 23642112 rss_rlim: 4294967295 CPU usage: start_time: 1209450222 rtime: 200 utime: 178 stime: 22 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 0xb6b83720 (LWP 4106)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 196412
Thread 1 (Thread 0xb6b83720 (LWP 4106))
----------- .xsession-errors --------------------- Couldn't Get password 9 ** (evolution:4582): DEBUG: mailto URL command: evolution %s ** (evolution:4582): DEBUG: mailto URL program: evolution (gnome-terminal:6763): Vte-WARNING **: No handler for control sequence `device-control-string' defined. 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 ***