MASTER network-manager crashes when wpasupplicant ctrl socket is not available
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
NetworkManager |
Fix Released
|
Critical
|
|||
network-manager (Ubuntu) |
Fix Released
|
High
|
Alexander Sack | ||
wpasupplicant (Ubuntu) |
Invalid
|
Medium
|
Unassigned |
Bug Description
Binary package hint: network-manager
network-manager crashes when it cannot connect to wpasupplicant ctrl socket.
A typical log for this issue looks like: from https:/
ep 17 05:34:48 uber NetworkManager: <info> Activation (eth1) New wireless user key for network 'name' received.
Sep 17 05:34:48 uber NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) scheduled...
Sep 17 05:34:48 uber NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) started...
Sep 17 05:34:48 uber NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) scheduled...
Sep 17 05:34:48 uber NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) complete.
Sep 17 05:34:48 uber NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) starting...
Sep 17 05:34:48 uber NetworkManager: <info> Activation (eth1/wireless): access point 'name' is encrypted, and a key exists. No new key needed.
Sep 17 05:34:49 uber NetworkManager: <info> supplicant_
Sep 17 05:34:49 uber NetworkManager: <info> supplicant_
Sep 17 05:34:49 uber NetworkManager: <info> supplicant_
Sep 17 05:34:49 uber NetworkManager: <info> supplicant_
Sep 17 05:34:49 uber NetworkManager: <info> supplicant_
Sep 17 05:34:49 uber NetworkManager: <info> supplicant_
Sep 17 05:34:50 uber NetworkManager: <info> supplicant_
Sep 17 05:34:50 uber NetworkManager: <info> supplicant_
Sep 17 05:34:50 uber NetworkManager: <info> supplicant_
Sep 17 05:34:50 uber NetworkManager: <info> supplicant_
Sep 17 05:34:50 uber NetworkManager: <info> supplicant_
Sep 17 05:34:50 uber NetworkManager: <info> supplicant_
Sep 17 05:34:50 uber NetworkManager: <info> supplicant_
Sep 17 05:34:50 uber NetworkManager: <info> supplicant_
Sep 17 05:34:50 uber NetworkManager: <info> supplicant_
Sep 17 05:34:50 uber NetworkManager: <info> supplicant_
Sep 17 05:34:51 uber NetworkManager: <info> supplicant_
Sep 17 05:34:51 uber NetworkManager: <info> supplicant_
Sep 17 05:34:51 uber NetworkManager: <info> supplicant_
Sep 17 05:34:51 uber NetworkManager: <info> SUP: sending command 'INTERFACE_ADD eth1^I^
Sep 17 05:34:51 uber NetworkManager: <info> SUP: response was 'OK'
Sep 17 05:34:51 uber NetworkManager: <info> Error opening control interface to supplicant.
Sep 17 05:34:51 uber NetworkManager: <WARN> real_act_
Sep 17 05:34:51 uber NetworkManager: <info> Activation (eth1) failure scheduled...
Sep 17 05:34:51 uber NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) complete.
Sep 17 05:34:51 uber NetworkManager: <info> Activation (eth1) failed for access point (name)
Sep 17 05:34:51 uber NetworkManager: <info> Activation (eth1) failed.
Sep 17 05:34:51 uber NetworkManager: <info> Deactivating device eth1.
Sep 17 05:34:51 uber NetworkManager: <WARN> nm_signal_
Sep 17 05:34:51 uber NetworkManager: ******************* START *******
Sep 17 05:34:53 uber NetworkManager: (no debugging symbols found)
Sep 17 05:34:53 uber NetworkManager: Using host libthread_db library "/lib/tls/
Sep 17 05:34:53 uber NetworkManager: (no debugging symbols found)
Sep 17 05:34:54 uber last message repeated 13 times
Sep 17 05:34:54 uber NetworkManager: [Thread debugging using libthread_db enabled]
Sep 17 05:34:54 uber NetworkManager: [New Thread -1212589632 (LWP 4650)]
Sep 17 05:34:54 uber NetworkManager: [New Thread -1229378672 (LWP 5612)]
Sep 17 05:34:54 uber NetworkManager: [New Thread -1220985968 (LWP 4765)]
Sep 17 05:34:54 uber NetworkManager: [New Thread -1212593264 (LWP 4759)]
Sep 17 05:34:54 uber NetworkManager: (no debugging symbols found)
Sep 17 05:34:54 uber last message repeated 3 times
Sep 17 05:34:54 uber NetworkManager: 0xffffe410 in __kernel_vsyscall ()
Sep 17 05:34:54 uber NetworkManager: ******************* END *******
Related branches
Changed in network-manager: | |
assignee: | nobody → asac |
importance: | Undecided → High |
status: | New → Confirmed |
Changed in network-manager: | |
status: | Unknown → New |
Changed in network-manager: | |
status: | New → Fix Released |
Changed in network-manager: | |
importance: | Unknown → Critical |
Thanks for help but isn't this a duplicate of https:/ /bugs.launchpad .net/ubuntu/ +source/ network- manager/ +bug/139966 ?