Comment 22 for bug 204868
Revision history for this message
| Steve Langasek (vorlon) wrote Re: NM can't use wireless networks | #22 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
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.