Thanks to all for helping to pin down this bug. While for most users
the fixes in hal 0.5.11~rc2-1ubuntu2 were sufficient, it appears that
even with hal working as it did before there are some chipsets for which
hal still returns a null kernel driver name, leading to this segfault.
It's unfortunate that we had uploads of both hal and network-manager
introducing regressions at nearly the same time with near-identical
symptoms, making it more difficult to distinguish the causes.
I'm working on fixing the regression in network-manager, for upload
shortly; I think we'll want to also open a task against hal, to figure
out why the broadcom driver is giving a null kernel driver name.
** Changed in: network-manager (Ubuntu)
Importance: Low => High
Assignee: (unassigned) => Steve Langasek (vorlon)
Status: Triaged => In Progress
Target: None => ubuntu-8.04
--
NM can't use wireless networks
https://bugs.launchpad.net/bugs/204868
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
