GNOME Bugzilla – Bug 530252
crash in File Browser: SMB
Last modified: 2008-04-27 22:26:11 UTC
Version: 2.20.0 What were you doing when the application crashed? SMB Distribution: Debian lenny/sid Gnome Release: 2.22.1 2008-04-08 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.22-3-686 #1 SMP Sun Feb 10 20:20:49 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: 87703552 vsize: 87703552 resident: 29188096 share: 17133568 rss: 29188096 rss_rlim: 4294967295 CPU usage: start_time: 1209331249 rtime: 250 utime: 230 stime: 20 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 0xb6b65720 (LWP 4823)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 196279
Thread 1 (Thread 0xb6b65720 (LWP 4823))
----------- .xsession-errors --------------------- connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: fill-authentication!!! ** (nm-applet:4843): WARNING **: <WARN> nma_dbus_init(): could not acquire its service. dbus_bus_acquire_service() says: 'Connection ":1.19" is not allowed to own the service "org.freedesktop.Networ ** (nautilus:4823): WARNING **: Possibly invalid new URI 'smb://czlowiek.mikrus.pw.edu.pl/Nowy folder 10/Kasabian' This can cause subtle evils like #48423 ** (nautilus:4823): WARNING **: Possibly invalid new URI 'smb://czlowiek.mikrus.pw.edu.pl/Nowy folder 10' This can cause subtle evils like #48423 ** (nautilus:4823): WARNING **: Nie odnaleziono opisu typu MIME "x-directory/smb-share" (plik "Nowy folder 10"), napisz na listę gnome-vfs (w języku angielskim). --------------------------------------------------
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 ***