GNOME Bugzilla – Bug 467818
crash in Network Manager: clicking "connect to ano...
Last modified: 2007-10-06 18:03:21 UTC
What were you doing when the application crashed? clicking "connect to another wireless network" Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:47:07 EDT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 375676928 vsize: 375676928 resident: 18292736 share: 12341248 rss: 18292736 rss_rlim: 18446744073709551615 CPU usage: start_time: 1187388637 rtime: 75 utime: 68 stime: 7 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nm-applet' (no debugging symbols found) Using host libthread_db library "/lib64/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 46912679091824 (LWP 3843)] (no debugging symbols found) 0x00002aaab050f89f in waitpid () from /lib64/libpthread.so.0
+ Trace 156032
Thread 1 (Thread 46912679091824 (LWP 3843))
----------- .xsession-errors (18 sec old) --------------------- localuser:bryce being added to access control list SESSION_MANAGER=local/localhost.localdomain:/tmp/.ICE-unix/3704 ** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name Unable to open desktop file /usr/share/applications/openoffice.org-1.9-writer.desktop for panel launcher: No such file or directory Unable to open desktop file /usr/share/applications/openoffice.org-1.9-impress.desktop for panel launcher: No such file or directory Unable to open desktop file /usr/share/applications/openoffice.org-1.9-calc.desktop for panel launcher: No such file or directory --------------------------------------------------
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 435036 ***