GNOME Bugzilla – Bug 545805
crash in File Browser: I'm try to access to sub...
Last modified: 2008-08-01 08:14:36 UTC
Version: 2.20.0 What were you doing when the application crashed? I'm try to access to sub folder ino a net folder Distribution: Debian lenny/sid Gnome Release: 2.22.3 2008-06-30 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.25-2-686-bigmem #1 SMP Fri Jul 18 18:30:55 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10402000 Selinux: No Accessibility: Disabled GTK+ Theme: Amaranth Icon Theme: Amaranth Memory status: size: 75902976 vsize: 75902976 resident: 23314432 share: 15638528 rss: 23314432 rss_rlim: 4294967295 CPU usage: start_time: 1217576793 rtime: 164 utime: 144 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) [Thread debugging using libthread_db enabled] [New Thread 0xb6b2e720 (LWP 4778)] (no debugging symbols found) 0xb7f61424 in __kernel_vsyscall ()
+ Trace 204342
Thread 1 (Thread 0xb6b2e720 (LWP 4778))
----------- .xsession-errors (544 sec old) --------------------- ** (nm-applet:2753): WARNING **: <WARN> nma_dbus_init(): could not acquire its service. dbus_bus_acquire_service() says: 'Connection ":1.20" is not allowed to own the service "org.freedesktop.Networ ** (nm-applet:2753): WARNING **: <WARN> nma_dbus_init(): could not acquire its service. dbus_bus_acquire_service() says: 'Connection ":1.20" is not allowed to own the service "org.freedesktop.Networ ** (nm-applet:2753): WARNING **: <WARN> nma_dbus_init(): could not acquire its service. dbus_bus_acquire_service() says: 'Connection ":1.20" is not allowed to own the service "org.freedesktop.Networ ** (nm-applet:2753): WARNING **: <WARN> nma_dbus_init(): could not acquire its service. dbus_bus_acquire_service() says: 'Connection ":1.20" is not allowed to own the service "org.freedesktop.Networ ...Too much output, ignoring rest... --------------------------------------------------
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 ***