http://www.freedesktop.org/wiki/Software/hal/
** Changed in: hal (Ubuntu)
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/211302
Title:
[hardy] resume displays
I used to get this message frequently, but I haven't seen it appear in
quite some time, certainly never with karmic. Maybe it's been fixed?
--
[hardy] resume displays Policy timeout is not valid. Please wait a few seconds
and try again
https://bugs.launchpad.net/bugs/211302
You received this
I noticed this message briefly appear (almost flicker - could just make out the
text 'policy timeout') on my Toshiba Satelite pro (U200) running Hardy.
It's the first time I noticed it and it probably was because, I opened
the lid and then pressed the power button. Opening the lid is normally
Iæm affected by this too (aren't everybody?). I understand it could be a
feature, but it's more annoying than helpful. Is it difficult fix or is
just forgotten on the TO DO list? ;)
--
[hardy] resume displays Policy timeout is not valid. Please wait a few seconds
and try again
I get this problem from time to time aswell on my 8.04.1 system.
--
[hardy] resume displays Policy timeout is not valid. Please wait a few seconds
and try again
https://bugs.launchpad.net/bugs/211302
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
I see the same issue on an averatec 2100 series laptop.
uname:
Linux abc 2.6.24-19-generic #1 SMP Fri Jul 11 21:01:46 UTC 2008 x86_64 GNU/Linux
In my laptop, the first suspend/resume cycle happens fine. However,
after 1 cycle, it is unable to resume from suspend or hibernate. I have
to do a
balak,
Your problem could be a different bug. Suspend-resume always works for
my T43, I just see the notification message when resuming.
--
[hardy] resume displays Policy timeout is not valid. Please wait a few seconds
and try again
https://bugs.launchpad.net/bugs/211302
You received this bug
Same problem with a T43 on 8.04.1
--
[hardy] resume displays Policy timeout is not valid. Please wait a few seconds
and try again
https://bugs.launchpad.net/bugs/211302
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Same problem on my X60 with Hardy.
Seems quite a lot is having this problem - hope someone smart finds a
way to fix it...
--
[hardy] resume displays Policy timeout is not valid. Please wait a few seconds
and try again
https://bugs.launchpad.net/bugs/211302
You received this bug notification
I don't actually use ubuntu, but based on what I'm seeing on debian
lenny, I would guess that the extra event is coming from acpi-support,
as it invokes 'acpi_fakekey $KEY_SLEEP' when it processes a sleep button
acpi event and finds that gnome-power-manager or klaptopdaemon is
running. (this will
I have the same problem on X61.
--
[hardy] resume displays Policy timeout is not valid. Please wait a few seconds
and try again
https://bugs.launchpad.net/bugs/211302
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Just reporting I have Hardy on an X60 and experience the same bug
whenever I resume from suspend, while having AC power connected.
--
[hardy] resume displays Policy timeout is not valid. Please wait a few seconds
and try again
https://bugs.launchpad.net/bugs/211302
You received this bug
Oops. Didn't mean to press the also needs a fix here button for gnome-
power-manager.
** Changed in: gnome-power-manager (Ubuntu)
Status: New = Invalid
--
[hardy] resume displays Policy timeout is not valid. Please wait a few seconds
and try again
https://bugs.launchpad.net/bugs/211302
So in other words, the policy insists that there should be no two APM events in
5 seconds gap and blocks them?
If unplugging the AC adapter is considered as APM event, then the fact that I
don't get a lid closed (or button pressed for that matter) suspend after I
unplug the adapter - is not a
Here's an unfiltered gpm log for the X40, with a single suspend event.
I have occasionally seen messages saying that suspend failed, even
though the machine suspended, which seems to align with getting two
sleep events.
** Attachment added: gpm.log
It looks to me from that log like we're getting two sleep button events
for everytime you're pressing the sleep button. I'm unsure of why in
one case they're both before the suspend and the second they're split
across it. I'm reassigning this to hal as we shouldn't be getting those
dual events
Having looked at the code in gnome-power-manager, the first error in my
log file could be bogus. It looks like this error comes up if it
receives two commands too quickly (inside the timeout value). The first
suspend may have been initiated pretty quickly after the previous
resume, which is why
Taking my cue from the original reporter, here is a full log of
gnome-power-manager --no-daemon --verbose --debug power gpm.txt 21
It contains two suspends. On the first, the error popped up just as the
screen was fading out to suspend. On the second, it appeared when the
desktop came back on
I see exactly the same thing on my X40. (Rather unhelpful as an error
message...) Let me know if I can help debug.
--
[hardy] resume displays Policy timeout is not valid. Please wait a few seconds
and try again
https://bugs.launchpad.net/bugs/211302
You received this bug notification because
It'd be useful to determine if this is X40 specific ... does anyone not
on an X40 see this error? I don't know enough about gnome-power-manager
to offer much other debugging suggestions.
** Changed in: gnome-power-manager (Ubuntu)
Status: New = Confirmed
--
[hardy] resume displays
Could you readd the messages in the last ? It would be useful to
know what actions it is surpressing.
--
[hardy] resume displays Policy timeout is not valid. Please wait a few seconds
and try again
https://bugs.launchpad.net/bugs/211302
You received this bug notification because you are a
I have HP compaq 6720s and I get same problem. Suspend is taking rather
long time. I don't quite remember how this was in Gutsy but I think it
was much faster. Even in Hardy waking from suspend was quick
It takes about 10 sec.
--
[hardy] resume displays Policy timeout is not valid. Please wait
22 matches
Mail list logo