Ok, confirmed that bug is not in guidance-power-manager as HAL is not reporting
proper state after resume.
It may be that this is actually kernel bug (not refreshing the state of
ac_adapter after resume).
See also bug 63123 for similar issue with multiple HP laptops.
** Changed in: hal (Ubuntu)
I attached them to my mail reply. I guess they aren't automatically attached
to the bug by the mailgate. Will upload them shortly.
--
guidance-power-manager doesn't detect changes during hibernation
https://bugs.launchpad.net/bugs/102084
You received this bug notification because you are a member
lshal after hibernation wake-up.
** Attachment added: "toshiba-satellite-u200-after.txt.gz"
http://librarian.launchpad.net/7552379/toshiba-satellite-u200-after.txt.gz
--
guidance-power-manager doesn't detect changes during hibernation
https://bugs.launchpad.net/bugs/102084
You received this b
lshal before hibernation
** Attachment added: "toshiba-satellite-u200-before.txt.gz"
http://librarian.launchpad.net/7552374/toshiba-satellite-u200-before.txt.gz
--
guidance-power-manager doesn't detect changes during hibernation
https://bugs.launchpad.net/bugs/102084
You received this bug not
Diff does not help. We need full lshal after resume or at least output
of this:
lshal | grep ac_adapter
This will tell us what HAL thinks about ac_adapter state. Otherwise this
sounds like bug 63123.
--
guidance-power-manager doesn't detect changes during hibernation
https://bugs.launchpad.ne
Here are my lshal before and after hibernation. I unplugged while hibernated
and after wakeup it still says plugged-in.
And here is the diff for quick check (diff before after):
39a40,84
> udi = '/org/freedesktop/Hal/devices/computer_logicaldev_input_3'
> info.udi = '/org/freedesktop/Hal/device
Can you provide output of "lshal" after resume? I suspect that it is HAL
that does not properly report state after resume...
** Changed in: kde-guidance (Ubuntu)
Assignee: (unassigned) => Luka Renko
Status: Confirmed => Needs Info
--
guidance-power-manager doesn't detect changes duri
I am also experiencing this bug on a different laptop to the one
mentioned above. Very annoying.
This bug was not present before I upgraded my system to Feisty (/kde
3.5.6)
--
guidance-power-manager doesn't detect changes during hibernation
https://bugs.launchpad.net/bugs/102084
You received thi
It becomes a greater nuisance if you don't have the AC with you. Any
known workaround for that situation besides rebooting?
--
guidance-power-manager doesn't detect changes during hibernation
https://bugs.launchpad.net/bugs/102084
You received this bug notification because you are a member of Kub
Confirmed in a different laptop (MSI MegaBook S262) experiencing `fully
charged' AC-powered state from kde-guidance-powermanager while laptop's
actually running on battery.
Workaround is to simply plug the laptop on AC power again, waiting until
kde-guidance detects the change, then unplugging to
10 matches
Mail list logo