*** This bug is a duplicate of bug 259503 ***
https://bugs.launchpad.net/bugs/259503
** This bug has been marked a duplicate of bug 259503
MASTER NetworkManager 0.7 crashed with SIGSEGV in nm_device_get_act_request()
--
0.7 N-M Segfault when reloading drivers in broken state
https://bugs.
I see the same with the latest network-manager
0.7~~svn20080818t061112+eni0-0ubuntu1. I have to remove and reload the
iwl4965 module after ACPI S3 suspend to get my wireless working
reliably, NetworkManager dies every time.
Latest messages in the syslog are:
Aug 23 01:43:34 schleppi NetworkManager
Here is one I did earlier before installing other debug symbols. This
looks more like the same crash:
Aug 7 21:15:49 fizz NetworkManager: nm_signal_handler(): Caught signal
11. Generating backtrace...
Aug 7 21:15:49 fizz NetworkManager: *** START
***
It doesn't even look the same...
Aug 7 21:24:33 fizz NetworkManager: nm_signal_handler(): Caught signal
11. Generating backtrace...
Aug 7 21:24:33 fizz NetworkManager: *** START
**
Aug 7 21:24:33 fizz NetworkManager: [Thread debugging using
please insetall the network-manager-dbgsym and libnm-util0-dbgsym and
libnm-glib0-dbgsym packages and maybe the same for the glib and gobject
libraries.
Then reproduce this crash and attach the backtrace.
Thanks!
** Changed in: network-manager (Ubuntu)
Importance: Undecided => High
Sta
** Summary changed:
- N-M Segfault when reloading drivers in broken state
+ 0.7 N-M Segfault when reloading drivers in broken state
--
0.7 N-M Segfault when reloading drivers in broken state
https://bugs.launchpad.net/bugs/255834
You received this bug notification because you are a member of Ubu
