GNOME Bugzilla – Bug 453248
crash in Network Manager: starting network manager...
Last modified: 2007-07-05 20:47:16 UTC
What were you doing when the application crashed? starting network manager service Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.2 2007-05-28 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3228.fc7 #1 Tue Jun 12 14:38:06 EDT 2007 ppc X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Clearlooks Memory status: size: 79810560 vsize: 79810560 resident: 37163008 share: 35024896 rss: 37163008 rss_rlim: 4294967295 CPU usage: start_time: 1183410937 rtime: 46 utime: 39 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 "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 805972640 (LWP 2638)] (no debugging symbols found) 0x0fa00298 in __waitpid_nocancel () from /lib/libpthread.so.0
+ Trace 145361
Thread 1 (Thread 805972640 (LWP 2638))
----------- .xsession-errors --------------------- ** (nm-applet:2638): WARNING **: <WARN> nma_dbus_net_properties_cb(): dbus returned an error. (org.freedesktop.DBus.Error.NoReply) Message did not receive a reply (timeout by message bus) process 2638: arguments to dbus_message_new_method_call() were incorrect, assertion "_dbus_check_is_valid_path (path)" failed in file dbus-message.c line 1074. This is normally a bug in some application using the D-Bus library. D-Bus not built with -rdynamic so unable to print a backtrace warning: .dynamic section for "/usr/lib/libnm-util.so.0" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/lib/libselinux.so.1" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations --------------------------------------------------
*** This bug has been marked as a duplicate of 444319 ***