I can confirm it too in edgy. If I login just after it is possible all
goes ok. But if I wait for some time I get such problem. On dapper I had
this problem too.
--
Failed to initalize HAL.
https://launchpad.net/bugs/25931
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists
Done as in wiki but without removing/connecting device.
--
HAL do not display my wireless device so I cannot use NM.
https://launchpad.net/bugs/50864
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Problem is: my device is attached all the time. When I first time
start up my notebook the device is in the HAL. But when I reboot it
the device disappears from HAL but driver sees it and the
corresponding device ( wlan0 ) is available.
On 7/21/06, Martin Pitt <[EMAIL PROTECTED]> wrote:
> Hal is s
I think it is because hal startes after loading at76c503a driver and
udev message about this device goes to /dev/null ...
--
HAL do not display my wireless device so I cannot use NM.
https://launchpad.net/bugs/50864
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.
I removed device. Unloaded drivers and inserted device. It appeared in
hal. So maybe problem is that this device is inserted on bootup?
--
HAL do not display my wireless device so I cannot use NM.
https://launchpad.net/bugs/50864
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https:/
