this is my current default settings as i find them in /etc/rc2.d:
S12dbus
S24hal
S30gdm
it seems to be fixed and concurrency=shell works fine :)
running ubuntu hardy 8.04
--
HAL fails to initialise when /etc/init.d/rc sets CONCURRENCY=shell
https://bugs.launchpad.net/bugs/149881
You received this
I can confirm this in Hardy as well with the latest updates (including
proposed). The workaround does solve the issue, but the average user
will simply get frustrated.
--
HAL fails to initialise when /etc/init.d/rc sets CONCURRENCY=shell
https://bugs.launchpad.net/bugs/149881
You received this b
pls reopen this bug. it affects hardy too.
although below command fixed it,
mv /etc/rc2.d/S12hal /etc/rc2.d/S13hal
(thanks Andrea Corbellini)
--
HAL fails to initialise when /etc/init.d/rc sets CONCURRENCY=shell
https://bugs.launchpad.net/bugs/149881
You received this bug notification because you
I can confirm the same issue on Hardy (upgraded from gutsy).
--
HAL fails to initialise when /etc/init.d/rc sets CONCURRENCY=shell
https://bugs.launchpad.net/bugs/149881
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mai
I've just been bitten by this bug, using the Hardy Beta Kubuntu "remix" with
KDE4, on an AMD64 (Turion) based laptop.
In /etc/rc2.d, I had:
s12dbus
S24hal
s13kdm
And I needed to do this to get past the problem:
mv S24hal S13hal
mv s13kdm s14kdm
And yes, I suggest that this bug is far w
Confirmed in Hardy Beta. But my hal and dbus are both set to S12 in the
rc#.d folders, not 24 (though gdm is at 30).
Yes, there's a workaround, but doesn't it make sense to set the two of
them a little apart by default? Editing init.d filenames is not the most
user-friendly of actions. Will the ab
In Hardy, hal now starts at priority 24, and gdm at 30, so this should
be fixed.
** Changed in: hal (Ubuntu)
Status: Triaged => Fix Released
--
HAL fails to initialise when /etc/init.d/rc sets CONCURRENCY=shell
https://bugs.launchpad.net/bugs/149881
You received this bug notification beca
Bug and workaround confirmed in Kubuntu Gutsy amd64, in Kubuntu Hardy
amd64 there isn't bug
--
HAL fails to initialise when /etc/init.d/rc sets CONCURRENCY=shell
https://bugs.launchpad.net/bugs/149881
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Tags added: patch
--
HAL fails to initialise when /etc/init.d/rc sets CONCURRENCY=shell
https://bugs.launchpad.net/bugs/149881
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu
Bug and workaround confirmed here on Ubuntu Gutsy amd64.
--
HAL fails to initialise when /etc/init.d/rc sets CONCURRENCY=shell
https://bugs.launchpad.net/bugs/149881
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs m
This is a race condition between hal and dbus which happens when the two
initscripts are started concurrently by upstart.
This should not happen because hal initscript requires dbus for starting
but instead happens when upstart concurrency is enabled because the
scripts have been symlinked with th
Bug #164127 seems related without being a duplicate (at least I think
so).
--
HAL fails to initialise when /etc/init.d/rc sets CONCURRENCY=shell
https://bugs.launchpad.net/bugs/149881
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
Couldn't this be fixed with the dependencies mechanism of upstart ?
--
HAL fails to initialise when /etc/init.d/rc sets CONCURRENCY=shell
https://bugs.launchpad.net/bugs/149881
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ub
I change the priority to Low because the problem can be easily solved
with a workaround.
** Changed in: hal (Ubuntu)
Importance: Undecided => Low
Status: Fix Committed => Triaged
--
HAL fails to initialise when /etc/init.d/rc sets CONCURRENCY=shell
https://bugs.launchpad.net/bugs/14988
Rarely HAL doesn't start anymore (I've got 2 very fast processors :D),
so I've added `sleep 1` to /etc/rc/hal.
--
HAL fails to initialise when /etc/init.d/rc sets CONCURRENCY=shell
https://bugs.launchpad.net/bugs/149881
You received this bug notification because you are a member of Ubuntu
Bugs, w
I confirm that solution. More I've added a point to /etc/rc2.d/S13gdm to
be sure it's invoked just after hal as were before.
--
HAL fails to initialise when /etc/init.d/rc sets CONCURRENCY=shell
https://bugs.launchpad.net/bugs/149881
You received this bug notification because you are a member of
I can confirm the bug. After setting CONCURRENCY=shell, HAL attempts to
initialise before DBus, causing an error. HAL starts fine manually after
boot up, and changing it's starting level fixes the problem as Andrea
mentioned above.
--
HAL fails to initialise when /etc/init.d/rc sets CONCURRENCY=s
The proble is that HAL starts more quickly than DBus so it says that DBus is
not running. So to solve this issue I changed the starting level of HAL with
mv /etc/rc2.d/S12hal /etc/rc2.d/S13hal
Now I works fine!
** Changed in: hal (Ubuntu)
Status: New => Fix Committed
--
HAL fails to init
I can confirm this as well, running Kubuntu 7.10 on intel C2D e4300.
--
HAL fails to initialise when /etc/init.d/rc sets CONCURRENCY=shell
https://bugs.launchpad.net/bugs/149881
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
u
I can confirm this as well running Gutsy Beta on Dell Latitude D520
--
HAL fails to initialise when /etc/init.d/rc sets CONCURRENCY=shell
https://bugs.launchpad.net/bugs/149881
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ub
I can confirm this as well, seems to be some kind of order dependency
issue between dbus and HAL.
--
HAL fails to initialise when /etc/init.d/rc sets CONCURRENCY=shell
https://bugs.launchpad.net/bugs/149881
You received this bug notification because you are a member of Ubuntu
Bugs, which is the b
I can confirm, I tried this in the beta of gutsy (x64), and it still
shows this behaviour.
I run it on a dell xps m1710, a core2 duo platform...
If hardware specs or logfiles are needed, i'm willing to provide them,
so just let know here!
--
HAL fails to initialise when /etc/init.d/rc sets CONC
Happened to me too. I read online that this option would multi-thread
the boot up and speed it up. I'm running an Opteron 165 dual core with
Gutsy x64.
Setting the /etc/init.d/rc back to "concurrency=none" fixed the issue.
--
HAL fails to initialise when /etc/init.d/rc sets CONCURRENCY=shell
h
23 matches
Mail list logo
