GNOME Bugzilla – Bug 506275
crash in Home Folder:
Last modified: 2007-12-30 01:29:36 UTC
What were you doing when the application crashed? Distribution: Debian lenny/sid Gnome Release: 2.20.2 2007-11-29 (Debian) BugBuddy Version: 2.20.1 System: Linux 2.6.22-3-686 #1 SMP Mon Nov 12 08:32:57 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 85671936 vsize: 85671936 resident: 28053504 share: 16683008 rss: 28053504 rss_rlim: 4294967295 CPU usage: start_time: 1198940291 rtime: 19086 utime: 17799 stime: 1287 cutime:75 cstime: 26 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 0xb6d366b0 (LWP 3447)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 183459
Thread 1 (Thread 0xb6d366b0 (LWP 3447))
----------- .xsession-errors --------------------- (nautilus:5410): Eel-WARNING **: "nautilus-metafile.c: metafiles" hash table still has 1 element at quit time (keys above) --- Hash table keys for warning below: --> file:///media/RAMUDF15 (nautilus:5410): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above) ** (nm-applet:3464): WARNING **: <WARN> nma_dbus_init(): could not acquire its service. dbus_bus_acquire_service() says: 'Connection ":1.16" is not allowed to own the service "org.freedesktop.Networ ** (nm-applet:3464): WARNING **: <WARN> nma_dbus_init(): could not acquire its service. dbus_bus_acquire_service() says: 'Connection ":1.16" is not allowed to own the service "org.freedesktop.Networ ** (nm-applet:3464): WARNING **: <WARN> nma_dbus_init(): could not acquire its service. dbus_bus_acquire_service() says: 'Connection ":1.16" is not allowed to own the service "org.freedesktop.Networ --------------------------------------------------
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 ***