*** This bug is a duplicate of bug 149881 ***
https://bugs.launchpad.net/bugs/149881
>Personally though, since CONCURRENCY=shell worked in feisty I am a bit
>surprise that it doesn't work in gusty
Oh, thanks, then this is a duplicate of bug #149881, and I am marking this bug
as such.
Any fur
Hey, Paul.
Actually just last week I figured out how to solve my problem. After a bunch
of Googling I found this http://ubuntuforums.org/showthread.php?p=3549705 which
it turns out is the same issue here. Personally though, since CONCURRENCY=shell
worked in feisty I am a bit surprise that it d
Possibly a duplicate of bug #158425.
Please give the output of "dpkg --audit", I hope to see if hal is correctly
installed.
Oh well, please also give the output of: "dpkg -l|grep hal"
--
hald failed to initialize on start up, Gusty
https://bugs.launchpad.net/bugs/157258
You received this bug no
Reassigning to hal (was network-manager).
Let's find out what is the problem with your hald, hoping it will fix your
network-manger problem.
I had that problem once, it was caused by me removing haldaemon, you may look
at this by:
cat /etc/group|grep hal
and see if a line like:
haldaemon:x:116:
