GNOME Bugzilla – Bug 544153
crash in Home Folder: Ich hab auf ne SMB-Freig...
Last modified: 2008-07-22 12:33:25 UTC
What were you doing when the application crashed? Ich hab auf ne SMB-Freigabe zugegriffen und da drinne einen Ordner geöffnet. Distribution: Debian lenny/sid Gnome Release: 2.22.3 2008-06-30 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.25-2-486 #1 Fri Jun 27 02:39:22 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10402000 Selinux: No Accessibility: Disabled GTK+ Theme: Glossy Icon Theme: gnome Memory status: size: 77049856 vsize: 77049856 resident: 26980352 share: 16089088 rss: 26980352 rss_rlim: 4294967295 CPU usage: start_time: 1216736048 rtime: 468 utime: 136 stime: 332 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb6b64720 (LWP 2426)] (no debugging symbols found) 0xb7f8c422 in __kernel_vsyscall ()
+ Trace 203487
Thread 1 (Thread 0xb6b64720 (LWP 2426))
----------- .xsession-errors (39 sec old) --------------------- (gnome-panel:2424): GLib-GIO-WARNING **: Missing callback called fullpath = /home/gu4rdi4n/.config/menus/gnome-applications.menu ** (nautilus:2426): WARNING **: Keine Beschreibung für MIME-Type »x-directory/smb-share« gefunden (Datei ist »C%24«), teilen Sie dies der gnome-vfs-Mailingliste mit. 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: fill-authentication!!! connection_message_func(): Callback CALLBACK: fill-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 ***