services-admin reorders acpid startup
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| gnome-system-tools (Ubuntu) |
Confirmed
|
Medium
|
Unassigned | ||
Bug Description
This bug relates to the 'services-admin' tool on edgy.
I used services-admin to not stop acpid (and not start during bootup). This worked fine. Then after booting up a few times I re-enabled acpid in the services-admin tool. But for some reason it wouldn't start and gave this error:
/proc/acpi/event: Device or resource busy
After some investigation I found that the hald daemon (started by dbus) was starting up before acpid and was spawning hal-addon-acpi. It looks like hal-addon-acpi takes control of the /proc/acpi/event file making it inaccessible to acpid.
The only reason for this error I can think of is that services-admin possibly reordered the start acpid (to occur after hald).
Manually changing /etc/rc2.d/S50acpid to /etc/rc2.d/S10acpid fixed the problem.
| Michael Vogt (mvo) wrote | #1 |
| Changed in gnome-system-tools: | |
| importance: | Undecided → Medium |
| status: | Unconfirmed → Confirmed |
| Tollef Fog Heen (tfheen) wrote | #2 |
Thanks for your bugreport.
I can confirm that behaviour. g-s-t changes the start value from S10 to S50 on disable/re-enable.
Cheers,
MIchael