GNOME Bugzilla – Bug 444319
crash in Network Manager: firefox , pidgin
Last modified: 2007-11-15 22:28:48 UTC
What were you doing when the application crashed? firefox , pidgin 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: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 273649664 vsize: 273649664 resident: 12509184 share: 9097216 rss: 12509184 rss_rlim: 18446744073709551615 CPU usage: start_time: 1181032951 rtime: 242 utime: 202 stime: 40 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 46912496327472 (LWP 3227)] (no debugging symbols found) 0x0000003deac0d865 in waitpid () from /lib64/libpthread.so.0
+ Trace 138428
Thread 1 (Thread 46912496327472 (LWP 3227))
----------- .xsession-errors --------------------- ** (nm-applet:3227): WARNING **: <WARN> nma_dbus_net_properties_cb(): dbus returned an error. (org.freedesktop.NetworkManager.NetworkNotFound) The requested network does not exist for this device. ** (nm-applet:3227): WARNING **: <WARN> nma_dbus_net_properties_cb(): dbus returned an error. (org.freedesktop.NetworkManager.NetworkNotFound) The requested network does not exist for this device. process 3227: 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 --------------------------------------------------
*** This bug has been marked as a duplicate of 435036 ***
*** Bug 444842 has been marked as a duplicate of this bug. ***
Actually, the stack looks slightly different. Re-opening. It would be good to figure out what is going on here.
*** Bug 447158 has been marked as a duplicate of this bug. ***
*** Bug 447584 has been marked as a duplicate of this bug. ***
Unclear if this is in dbus or NetworkManager itself. Can someone install NetworkManager-debuginfo and dbus-debuginfo and then reproduce the crash to get the extra debugging symbols which will help track down the problem?
I'll install both packages but I can't reproduce the crash, it'll be a case of waiting for it to happen again, that's if it ever does happen again.
*** Bug 451138 has been marked as a duplicate of this bug. ***
*** Bug 451692 has been marked as a duplicate of this bug. ***
*** Bug 452300 has been marked as a duplicate of this bug. ***
*** Bug 453300 has been marked as a duplicate of this bug. ***
*** Bug 453339 has been marked as a duplicate of this bug. ***
*** Bug 453386 has been marked as a duplicate of this bug. ***
*** Bug 453248 has been marked as a duplicate of this bug. ***
*** Bug 454339 has been marked as a duplicate of this bug. ***
*** Bug 456468 has been marked as a duplicate of this bug. ***
*** Bug 457425 has been marked as a duplicate of this bug. ***
*** Bug 462195 has been marked as a duplicate of this bug. ***
*** Bug 464776 has been marked as a duplicate of this bug. ***
*** Bug 468045 has been marked as a duplicate of this bug. ***
*** Bug 475816 has been marked as a duplicate of this bug. ***
*** Bug 476802 has been marked as a duplicate of this bug. ***
*** Bug 482827 has been marked as a duplicate of this bug. ***
*** Bug 482828 has been marked as a duplicate of this bug. ***
From bug 482828: "Think I found the reason for this. I have a third party softmodem package installed, conexant hsfmodem, see http://www.linuxant.com/drivers/hsf/full/downloads.php. Disabling this at startup makes nm stable again. This goes for bug #482827 too. As the hsfmodem driver taints the kernel, I'm not sure if the nm developers want to support it's functionality. It works as a "normal" modem through the symlinked /dev/modem, though."
*** This bug has been marked as a duplicate of 436553 ***