GNOME Bugzilla – Bug 509138
crash in Home Folder: I just changed propertie...
Last modified: 2008-01-13 23:18:53 UTC
What were you doing when the application crashed? I just changed properties of Nautilus to display content in 'browser mode'. Then tried to open 'sttings' again (wanted to change Icon size). Desktop theme is 'SphereCrystal'. System is Lenny amd64 Distribution: Debian lenny/sid Gnome Release: 2.20.2 2007-11-29 (Debian) BugBuddy Version: 2.20.1 System: Linux 2.6.22-3-amd64 #1 SMP Sun Nov 4 18:18:09 UTC 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: SphereCrystal Icon Theme: SphereCrystal Memory status: size: 409657344 vsize: 409657344 resident: 39317504 share: 16199680 rss: 39317504 rss_rlim: 18446744073709551615 CPU usage: start_time: 1200232331 rtime: 289 utime: 265 stime: 24 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/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0x2b8ae6f1b540 (LWP 4803)] (no debugging symbols found) 0x00002b8ae04a034f in waitpid () from /lib/libpthread.so.0
+ Trace 185163
Thread 1 (Thread 0x2b8ae6f1b540 (LWP 4803))
----------- .xsession-errors --------------------- ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** (nm-applet:3184): WARNING **: <WARN> nma_dbus_init(): could not acquire its service. dbus_bus_acquire_service() says: 'Connection ":1.27" is not allowed to own the service "org.freedesktop.Networ ** (nm-applet:3184): WARNING **: <WARN> nma_dbus_init(): could not acquire its service. dbus_bus_acquire_service() says: 'Connection ":1.27" 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 ***