GNOME Bugzilla – Bug 526229
crash in Home Folder:
Last modified: 2008-04-05 13:39:48 UTC
What were you doing when the application crashed? Distribution: Debian lenny/sid Gnome Release: 2.22.0 2008-03-14 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.24-1-686 #1 SMP Mon Feb 11 14:37:45 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: 84635648 vsize: 84635648 resident: 33468416 share: 16773120 rss: 33468416 rss_rlim: 4294967295 CPU usage: start_time: 1207326674 rtime: 1229 utime: 1162 stime: 67 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 0xb6b90720 (LWP 3716)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 194244
Thread 1 (Thread 0xb6b90720 (LWP 3716))
----------- .xsession-errors --------------------- ** (nm-applet:3744): 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 ** (nm-applet:3744): 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 ** (nm-applet:3744): 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 ** (nm-applet:3744): 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:3716): Eel-WARNING **: No extension, not implemented yet --------------------------------------------------
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 355018 ***