I am not sure how network-manager should deal with a wpasupplicant that
doesn't bring up its socket. Anyway, crashing is definitly not the right
answer.
** Changed in: network-manager (Ubuntu)
Importance: Undecided => High
Assignee: (unassigned) => Alexander Sack
Status: New => Confirmed
** Also affects: wpasupplicant (Ubuntu)
Importance: Undecided
Status: New
--
Network Manager signal 11 in kernel_vsyscall
https://bugs.launchpad.net/bugs/140905
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
