Description of problem: /proc/acpi/event is root-only for read Version-Release number of selected component (if applicable): 2.6.1-1.57 How reproducible: Every time! Steps to Reproduce: 1. $ cat /proc/acpi/event 2. -EPERM 3. there is no step 3. Actual results: -EPERM Expected results: Glorious ACPI events. The lack of readibility makes writing battery monitors ... tricky. Additional info: Hey, at least chmod() on it works!
not any more it doesn't 8-) is this actually a problem? Battery monitors seem to work fine for me.
Is acpid running when your battery monitor is working?
yes, why is that a problem ?
Does the battery monitor work once you turn off acpid?
no, as the battery applet talks to the acpid socket. This isn't supposed to work afaict. I don't see what we benefit by making /proc/acpi/event world readable, other than a bunch of headaches. (Note that it can only have one exclusive reader by design)
Well, the battery applet has code to work without acpid... as long as it's readable. I suppose it's simpler to just get all the acpi notification on the kernel events layer, or similar.
"the battery applet has code to work without acpid" Why ?
Probably because acpid is crap. Not sure, though. :)
I don't think there's a compelling argument to keep this one open.