Comment 8 for bug 145683

Since the patch, I am noticing that while NetworkManager doesn't seem to disappear from the system tray spontaneously as before, it does become non-operational (i.e. the nm-applet says "No network Devices have been found"). Thus, if the problem I'm experiencing is indeed a duplicate of this bug (which it was marked as), the bug is not in fact fixed.

Output from daemon.log when NetworkManager "dies":

Oct 5 14:30:01 thully-laptop NetworkManager: <WARN> nm_hal_deinit(): libhal shutdown failed - Connection is closed
Oct 5 14:30:01 thully-laptop NetworkManager: <WARN> nm_signal_handler(): Caught signal 11. Generating backtrace...
Oct 5 14:30:01 thully-laptop NetworkManager: <info> Successfully reconnected to the system bus.
Oct 5 14:30:02 thully-laptop NetworkManager: ******************* START **********************************
Oct 5 14:30:02 thully-laptop NetworkManager: (no debugging symbols found)
Oct 5 14:30:02 thully-laptop NetworkManager: Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
Oct 5 14:30:02 thully-laptop NetworkManager: (no debugging symbols found)
Oct 5 14:30:02 thully-laptop last message repeated 12 times
Oct 5 14:30:02 thully-laptop NetworkManager: [Thread debugging using libthread_db enabled]
Oct 5 14:30:02 thully-laptop NetworkManager: [New Thread -1211914576 (LWP 4996)]
Oct 5 14:30:02 thully-laptop NetworkManager: [New Thread -1220310128 (LWP 7382)]
Oct 5 14:30:02 thully-laptop NetworkManager: [New Thread -1211917424 (LWP 7295)]
Oct 5 14:30:02 thully-laptop NetworkManager: (no debugging symbols found)
Oct 5 14:30:02 thully-laptop last message repeated 4 times
Oct 5 14:30:02 thully-laptop NetworkManager: 0xffffe410 in __kernel_vsyscall ()
Oct 5 14:30:02 thully-laptop NetworkManager: ******************* END **********************************

I don't know if this is indeed a dupe, as I simply have wireless on and don't connect to andy networks when this happens. It doesn't happen, however, with my wireless (madwifi) disabled.

Reopening - if it is determined that my bug is separate from this, please reopen mine (140034) and close this again