GNOME Bugzilla – Bug 530533
crash in Home Folder: Ich habe einen SMB share...
Last modified: 2008-04-30 08:58:27 UTC
What were you doing when the application crashed? Ich habe einen SMB share ausgewaehlt. 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: 108167168 vsize: 108167168 resident: 30437376 share: 17502208 rss: 30437376 rss_rlim: 4294967295 CPU usage: start_time: 1209459675 rtime: 2842 utime: 2704 stime: 138 cutime:3 cstime: 2 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 0xb6c40720 (LWP 4046)] [New Thread 0xb5fc0b90 (LWP 6320)] [New Thread 0xb3cf9b90 (LWP 6319)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 196428
Thread 1 (Thread 0xb6c40720 (LWP 4046))
----------- .xsession-errors (590 sec old) --------------------- connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: full-authentication!!! ** (nautilus:4046): WARNING **: Hit unhandled case 24 (Vorgang nicht erlaubt) in fm_report_error_loading_directory connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: full-authentication!!! ** (nautilus:4046): WARNING **: Possibly invalid new URI 'smb://ESPL_001;rz.fh-ingolstadt.de%5Cei5306@ iw-fs4.rz.fh-ingolstadt.de/' This can cause subtle evils like #48423 --------------------------------------------------
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 ***