We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
Thank you for taking the time to report this bug and helping to make
Ubuntu better. You reported this bug a while ago and there hasn't been
any activity in it recently. We were wondering is this still an issue
for you? Can you try with latest Ubuntu release? Thanks in advance.
--
[Edgy] issues
affected me on an ubuntu feisty server install, running openbox. is
this still a hald-addon-acpi issue? if so, shouldn't there be a
relatively easy fix?
--
[Edgy] issues with dbus, powersaved, acpid and kpowersave
https://bugs.launchpad.net/bugs/64646
You received this bug notification because
** Changed in: acpid (Ubuntu)
Importance: Undecided = Medium
Status: Incomplete = Confirmed
--
[Edgy] issues with dbus, powersaved, acpid and kpowersave
https://bugs.launchpad.net/bugs/64646
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
Does this problem still exist in Feisty?
** Changed in: acpi (Ubuntu)
Status: New = Invalid
--
[Edgy] issues with dbus, powersaved, acpid and kpowersave
https://bugs.launchpad.net/bugs/64646
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
In fact I have the same problem with GNOME battery applets. If I add the
battery applet to the panel, I get this error message:
Can't access ACPI events in /var/run/acpi.socket! Make sure the ACPI
subsystem is working and the acpid daemon is running.
And
$ sudo /etc/init.d/acpid start
*
Forgot to say that the applet which gives me that message is the one the
user can add to the panel and not the default one (I think there two
applets). Moreover the default one is configurable by the power
management entry in the Gnome preferences (don't know its names) and is
not fully working,
I have the same problem described before:
After booting, my CPU stays at 100% and there is no menu entry to change the
cpu frequency behaviour in KPowersave.
This issue is fixed by restarting powersaved, i.e. the menu items in
KPowersave return and CPU frequency eventually goes down.
Please
I can get my laptop to suspend by doing the following steps:
$ killall -QUIT hald-addon-acpi
$ /etc/init.d/powersaved restart
$ acpitool -s
So what the heck? Its obviously not my hardware thats broken, its hald-
addon-acpi!
--
[Edgy] issues with dbus, powersaved, acpid and kpowersave
It seems that some other process has /proc/acpi/event file opened.
Can you provide output of the following command:
sudo fuser -v /proc/acpi/event
** Changed in: dbus (Ubuntu)
Sourcepackagename: dbus = acpid
Status: Unconfirmed = Needs Info
--
[Edgy] issues with dbus, powersaved,
As in previous bug #64387, I will add that:
1) KDE fonts are smaller, though font settings aren't changed (I checked
in control center). I use default fonts at size 9 and antialiasing with
RGB Full subpixel hinting.
2) Some functionalities of Control Center are unreachable or unusable.
For
$ sudo fuser -v /proc/acpi/event
USERPID ACCESS COMMAND
/proc/acpi/event:haldaemon 3951 f hald-addon-acpi
For dmseg and lsmod outputs, please read bug #64387
--
[Edgy] issues with dbus, powersaved, acpid and kpowersave
https://launchpad.net/bugs/64646
12 matches
Mail list logo
