As per IRC discussion; there seems to be issues with, as a first step,
the device not activating properly. There's microcode errors in the logs
and I sadly don't know enough about the driver internals to go deeper
there; but I do think it deserves investigation. The microcode errors
(with what looks to me like timing issues) and the direct probes timing
out are probably linked -- I'm adding a task for 'linux'.
The second issue is with the authentication windows popping up and
stacking over one another rather than just ever keeping one window
around. That's an issue with auto-activation that should be fixed in git
already, but will need further testing -- I should prepare ppa packages
for that.
** Changed in: network-manager (Ubuntu)
Status: New => Triaged
** Changed in: network-manager (Ubuntu)
Importance: Undecided => Medium
** Changed in: network-manager (Ubuntu)
Importance: Medium => High
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1021516
Title:
wpa_supplicant crashed with SIGSEGV in nla_put()
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1021516/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
