Bug 186331

Summary:	suspend to ram can get confused; re-suspend
Product:	[Fedora] Fedora	Reporter:	William Murray <w.j.murray>
Component:	gnome-power-manager	Assignee:	John (J5) Palmieri <johnp>
Status:	CLOSED DUPLICATE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	5	CC:	austin, jkeck, kdekorte, lowe, richard
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2006-04-11 22:32:58 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description William Murray 2006-03-22 23:05:22 UTC

Description of problem:
Sometimes resume from suspend-to-ram 'bounces' back to sleep
after briefly waking up. Inspection of /var/log/messages shows
messages such as:
Mar 22 16:14:32 billmurray gnome-power-manager: Suspending computer because the
lid has been closed on ac power
Mar 22 16:33:16 billmurray gnome-power-manager: Suspending computer because the
lid has been closed, and the ac adapter removed

This ocurred when I removed the power cable half way through suspending the
machine. I think something similar happens if I suspend for longer than
the inactive time set in gnome-power-manager: On resume it sees it has
been inactive and suspends.

Version-Release number of selected component (if applicable):
FC5 release

How reproducible:
I will try to be systematic when I have two machines to use.

Steps to Reproduce:
1. Suspend and resume a few times.
2. Watch the resume. Sometimes it flashes up and disappeears again.
3.
  
Actual results:
Watch the resume. Sometimes it flashes up and disappeears again.
Eventually it resumes.

Expected results:
Resume in ~8 seconds.


Additional info:

Comment 1 David L. 2006-03-26 14:02:53 UTC

I have a similar problem. If I hibernate by a lid close, then on resume hal
still thinks the lid is closed:

lshal | grep button.state
  button.state.value = true  (bool)

If I then pull the AC, it immediately goes into hibernate again. See gnome bug
http://bugzilla.gnome.org/show_bug.cgi?id=334220  for more info.

Actually, its a bit more complicated than that -- for example, if you restart
gnome-power-manager, hal still displays the wrong lid state, but the system no
longer goes into hibernate when you pull the AC.

Comment 2 Austin Jackson 2006-03-27 01:31:45 UTC

I can confirm this bug on a Dell Latitude X1.  For me, it happens when I put the
computer to sleep with the adapter plugged-in then try to resume with the
computer unplugged.

The machine will stay awake after waking it from the second suspend.

Comment 3 Austin Jackson 2006-03-27 01:54:59 UTC

(In reply to comment #2)
> I can confirm this bug on a Dell Latitude X1.  For me, it happens when I put the
> computer to sleep with the adapter plugged-in then try to resume with the
> computer unplugged.
> 
> The machine will stay awake after waking it from the second suspend.
> 
> 

Just to update this: the lit state appears to get lost when there is a change in
power state.  Putting the machine to sleep using the sleep button provides a
temporary work-around.

Comment 4 Kevin DeKorte 2006-03-28 13:54:09 UTC

I my IBM T41p if I put the machine to sleep using Fn-F4, letting it go to sleep
and then hitting Fn to wake it back up, it bounces back asleep and I have to hit
Fn again. After that the machine wakes up fine.

gnome-power-manager-2.14.0-1  on FC5

Comment 5 Rod Nayfield 2006-04-11 22:32:58 UTC


*** This bug has been marked as a duplicate of 183709 ***