GNOME Bugzilla – Bug 536304
crash in Home Folder: i did the update with sy...
Last modified: 2008-06-02 22:44:57 UTC
What were you doing when the application crashed? i did the update with synaptic, and tried to opena shared folder on a windows system with user and password Distribution: Debian lenny/sid Gnome Release: 2.22.2 2008-05-29 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.25-2-amd64 #1 SMP Tue May 27 12:45:24 UTC 2008 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 429273088 vsize: 429273088 resident: 32067584 share: 17440768 rss: 32067584 rss_rlim: 18446744073709551615 CPU usage: start_time: 1212434607 rtime: 186 utime: 164 stime: 22 cutime:0 cstime: 3 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 0x7fc58834a7a0 (LWP 3654)] (no debugging symbols found) 0x00007fc583497edf in waitpid () from /lib/libpthread.so.0
+ Trace 199427
Thread 1 (Thread 0x7fc58834a7a0 (LWP 3654))
----------- .xsession-errors --------------------- connection_message_func(): Callback CALLBACK: full-authentication!!! ** (nm-applet:3672): WARNING **: <WARN> nma_dbus_init(): could not acquire its service. dbus_bus_acquire_service() says: 'Connection ":1.24" is not allowed to own the service "org.freedesktop.Networ ** (nm-applet:3672): WARNING **: <WARN> nma_dbus_init(): could not acquire its service. dbus_bus_acquire_service() says: 'Connection ":1.24" is not allowed to own the service "org.freedesktop.Networ ** (nm-applet:3672): WARNING **: <WARN> nma_dbus_init(): could not acquire its service. dbus_bus_acquire_service() says: 'Connection ":1.24" is not allowed to own the service "org.freedesktop.Networ connection_message_func(): Callback CALLBACK: save-authentication!!! connection_message_func(): Callback CALLBACK: save-authentication!!! --------------------------------------------------
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 ***