Resume (from memory) goes back to sleep automatically
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Linux |
Fix Released
|
Medium
|
|||
gnome-power |
Invalid
|
Undecided
|
Unassigned | ||
acpi-support (Ubuntu) |
Fix Released
|
Medium
|
Steve Langasek | ||
Jaunty |
Fix Released
|
Medium
|
Steve Langasek | ||
gnome-power-manager (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Jaunty |
Fix Released
|
Undecided
|
Unassigned | ||
hal (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Jaunty |
Invalid
|
Undecided
|
Unassigned | ||
pm-utils (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Jaunty |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Upon resuming from suspend-to-RAM, the system will start to wake, and will immediately go back to sleep. If I cycle it one or two times more, it will stay awake. I have reproduced this exact behavior with Jaunty on the new kernel as well as on Fedora 10 (https:/
It has been observed that this happens when suspending via hotkey but not when suspending command (details in comments, below).
As a conjecture, it is behaving as if due to some race condition it has not yet cleared that it has a suspend event, so it immediately re-processes the suspend upon waking.
ProblemType: Bug
Architecture: amd64
DistroRelease: Ubuntu 9.04
NonfreeKernelMo
Package: linux-image-
ProcCmdLine: root=UUID=
ProcEnviron:
PATH=/
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSign
SourcePackage: linux
description: | updated |
description: | updated |
Changed in linux: | |
status: | Unknown → Confirmed |
Changed in linux: | |
assignee: | nobody → apw |
importance: | Undecided → Medium |
status: | New → In Progress |
Changed in linux: | |
status: | Confirmed → In Progress |
Changed in linux: | |
importance: | Unknown → Medium |
status: | In Progress → Fix Released |
I added the reference to an upstream defect in gnome-power-manager because Matt Garrett, whom I respect, seems to believe that it is gnome-power-manager related, and reading all of the open defects against gnome-power-manager in upstream, I found one that described the behavior. Keep in mind that I do not have this problem with either Hardy or Intrepid, just Fedora 10 and Jaunty.