Comment 6 for bug 349060

Revision history for this message
Mathieu Trudel-Lapierre (cyphermox) wrote :

What seems to me is like this crash was caused by HAL being successively restarted, and NM's signals firing too slowly for the HAL state (with probably missing sanity checks along the way).

Mar 26 11:58:28 scott-laptop NetworkManager: <info> HAL disappeared
Mar 26 11:58:30 scott-laptop NetworkManager: <info> HAL re-appeared
Mar 26 11:58:30 scott-laptop NetworkManager: <info> (eth0): now unmanaged
Mar 26 11:58:30 scott-laptop NetworkManager: <info> (eth0): device state change: 2 -> 1
Mar 26 11:58:30 scott-laptop NetworkManager: <info> (eth0): cleaning up...
Mar 26 11:58:30 scott-laptop NetworkManager: <info> (eth0): taking down device.
Mar 26 11:58:30 scott-laptop NetworkManager: <info> Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889)
Mar 26 12:02:19 scott-laptop NetworkManager: <info> HAL disappeared
Mar 26 12:02:21 scott-laptop NetworkManager: <info> HAL re-appeared
Mar 26 12:02:21 scott-laptop NetworkManager: nm_device_get_managed: assertion `NM_IS_DEVICE (device)' failed
Mar 26 12:02:24 scott-laptop NetworkManager: <info> HAL disappeared

Fixing this however is going to be impractical since there is no longer archive packages for these releases -- closing as Won't Fix for lack of a better idea.