GNOME Bugzilla – Bug 442373
crash in Network Manager: I wanted to create a new...
Last modified: 2007-06-04 04:39:19 UTC
What were you doing when the application crashed? I wanted to create a new wireless connection 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: 374452224 vsize: 374452224 resident: 17338368 share: 12066816 rss: 17338368 rss_rlim: 18446744073709551615 CPU usage: start_time: 1180546066 rtime: 21 utime: 18 stime: 3 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 3316)] (no debugging symbols found) 0x00002aaab050f89f in waitpid () from /lib64/libpthread.so.0
+ Trace 136852
Thread 1 (Thread 46912679091824 (LWP 3316))
----------- .xsession-errors (7 sec old) --------------------- localuser:lordkada being added to access control list SESSION_MANAGER=local/irony-reloaded:/tmp/.ICE-unix/3173 ** 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 error getting update info: Cannot open/read repomd.xml file for repository: fedora ** Message: <info> You are now connected to the wired network. --------------------------------------------------
*** This bug has been marked as a duplicate of 435036 ***