** Changed in: gnome-power
Importance: Unknown = Medium
--
Suspends that are longer than 6 hours will inexplicably claim to fail, but not
really fail
https://bugs.launchpad.net/bugs/242713
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed
I have a Toshiba M60. Still there for me, too. I'd attach my pm-
suspend.log, but it's completely error-free.
--
Suspends that are longer than 6 hours will inexplicably claim to fail, but not
really fail
https://bugs.launchpad.net/bugs/242713
You received this bug notification because you are
I turned on the option to beep if problem occurs, and got a beep this
morning, with the new version, so it seems it's not fixed for me, also.
--
Suspends that are longer than 6 hours will inexplicably claim to fail, but not
really fail
https://bugs.launchpad.net/bugs/242713
You received this
Hi there, I have Hardy/Gnome running on my T61 laptop and do suspend it
over night. No problems experienced so far. more specifically, I do not
get an error message when I resume.
--
Suspends that are longer than 6 hours will inexplicably claim to fail, but not
really fail
** Tags added: verification-done
** Tags removed: verification-needed
--
Suspends that are longer than 6 hours will inexplicably claim to fail, but not
really fail
https://bugs.launchpad.net/bugs/242713
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
This bug was fixed in the package gnome-power-manager -
2.22.1-1ubuntu4.1
---
gnome-power-manager (2.22.1-1ubuntu4.1) hardy-proposed; urgency=low
* Add 75-ignore-long-failed-suspends.patch to prevent inaccurately
indicating failed suspends when they were = 6 hours. (LP:
So this actually doesn't work for anyone?
If it works for some, but not others, but otherwise doesn't introduce
regressions, the package can go to -updates and this bug stay open.
If it doesn't work for anyone, we should pull the -proposed package.
--
Suspends that are longer than 6 hours will
Here is my pm-suspend.log, fresh from this morning's suspend complete
with beeps.
** Attachment added: pm-suspend.log
http://launchpadlibrarian.net/17838277/pm-suspend.log
--
Suspends that are longer than 6 hours will inexplicably claim to fail, but not
really fail
I also experience the same symptoms still (both before and after the
patched gnome-power-manager (and a reboot), on a Dell Inspiron 6400) --
attached is pm-suspend.log (doesn't contain too much info, however...).
** Attachment added: pm-suspend.log
Here's my pm-suspend.log. The only problem mentioned is:
* Reconfiguring network interfaces...
ppp0: ERROR while getting interface flags: No such device
** Attachment added: pm-suspend from resume with beeps
http://launchpadlibrarian.net/17787235/pm-suspend.log
--
Suspends that are longer
Got exactly the same symptoms after last night's suspend...
--
Suspends that are longer than 6 hours will inexplicably claim to fail, but not
really fail
https://bugs.launchpad.net/bugs/242713
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
I need to retract my confirmation...sound was off on my computer. After
last night's suspend, beeps are still there.
--
Suspends that are longer than 6 hours will inexplicably claim to fail, but not
really fail
https://bugs.launchpad.net/bugs/242713
You received this bug notification because
I'm removing the verification-done tag since there hasn't been any ack's
of it really working (after Matt's retraction). Anyone who has seen
this failure still, do you have a /var/log/pm-suspend.log after a failed
suspend that you would be able to post?
** Tags added: verification-needed
**
No but I have dmesg and kern.log and messages - I've added pm-
suspend.log to my capture script so I should have one soon...
--
Suspends that are longer than 6 hours will inexplicably claim to fail, but not
really fail
https://bugs.launchpad.net/bugs/242713
You received this bug notification
Bother, I've just seen it looks like I've got the wrong version.
Unfortunately that's what I got from hardy-proposed (and apt-get upgrade
-t proposed doesn't show anything else)...
--
Suspends that are longer than 6 hours will inexplicably claim to fail, but not
really fail
I've tested this. Normal (short-term) suspend and hibernate work normally.
However, on my first overnight (9 hour) suspend and resume, I still got the
beeping sound and the message saying suspend failed to work properly. I can
attach any relevant log files if that would help (just tell me what,
OK, I've investigated and I was wrong about the version;
2.22.1-1ubuntu4.1 looks like it does have the fix (I'm on hardy).
I've looked at /var/log/kern.log and it seems bizarrely as though some
of the suspend code ran after the resume (although I could see that the
machine had a flashing light
** Attachment added: /var/log/kern.log from the time of the suspend till
resume is completed (this reported failure)
http://launchpadlibrarian.net/17716864/kern.log-relevant
--
Suspends that are longer than 6 hours will inexplicably claim to fail, but not
really fail
confirmed as fixed on my Thinkpad R52. Before update, beeps on resume
after overnight suspends. Now both short- and long-term (successful)
suspends are sound free.
--
Suspends that are longer than 6 hours will inexplicably claim to fail, but not
really fail
** Tags added: verification-done
** Tags removed: verification-needed
--
Suspends that are longer than 6 hours will inexplicably claim to fail, but not
really fail
https://bugs.launchpad.net/bugs/242713
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
I seem to have the same issue as before with my R52 after the update.
Still beeps and displays message of failed suspend.
--
Suspends that are longer than 6 hours will inexplicably claim to fail, but not
really fail
https://bugs.launchpad.net/bugs/242713
You received this bug notification
For verifying this, please don't only exercise the test case, but make
sure that a normal (short-term) suspend and hibernate still works
normally, too.
--
Suspends that are longer than 6 hours will inexplicably claim to fail, but not
really fail
https://bugs.launchpad.net/bugs/242713
You
Hardy upload sponsored. Assigning to Mario for driving the testing
process.
** Changed in: gnome-power-manager (Ubuntu Hardy)
Assignee: (unassigned) = Mario Limonciello (superm1)
Status: New = In Progress
** Changed in: gnome-power-manager (Ubuntu Hardy)
Status: In Progress =
(this still needs the hardy task done for an SRU)
** Changed in: gnome-power-manager (Ubuntu Hardy)
Status: Confirmed = New
--
Suspends that are longer than 6 hours will inexplicably claim to fail, but not
really fail
https://bugs.launchpad.net/bugs/242713
You received this bug
This bug was fixed in the package gnome-power-manager - 2.23.91-0ubuntu2
---
gnome-power-manager (2.23.91-0ubuntu2) intrepid; urgency=low
* Added two patches from Joakim Andersson [EMAIL PROTECTED] his
comments on the patches are below.
* Added
the bug has been fixed upstream and should be fixed in intrepid when the
new version is uploaded
** Changed in: gnome-power-manager (Ubuntu Hardy)
Importance: Undecided = Low
Status: New = Confirmed
** Changed in: gnome-power-manager (Ubuntu)
Importance: Undecided = Low
** Changed in: gnome-power
Status: New = Fix Released
--
Suspends that are longer than 6 hours will inexplicably claim to fail, but not
really fail
https://bugs.launchpad.net/bugs/242713
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
** Summary changed:
- Suspends that are longer than 6 hours will inexplicably fail
+ Suspends that are longer than 6 hours will inexplicably claim to fail, but
not really fail
** Description changed:
Binary package hint: gnome-power-manager
The bug is present in both Ubuntu 8.04 and
28 matches
Mail list logo
