Bug 794145

Summary:	When resuming by opening laptop lid, system returns to standby
Product:	[openSUSE] openSUSE Tumbleweed	Reporter:	Howard Moreland <hrm_sfo>
Component:	Basesystem	Assignee:	E-mail List <bnc-team-screening>
Status:	RESOLVED FIXED	QA Contact:	E-mail List <qa-bugs>
Severity:	Normal
Priority:	P5 - None	CC:	hrm_sfo
Version:	13.1 Milestone 1
Target Milestone:	---
Hardware:	i686
OS:	SUSE Other
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	as requested

Description Howard Moreland 2012-12-12 17:07:58 UTC

User-Agent:       Opera/9.80 (X11; Linux i686) Presto/2.12.388 Version/12.11

On a ThinkPad X-41, the system suspends to RAM correctly. When the lid is opened, it starts for just a few seconds, then returns to standby. Pushing the Fn key then resumes the system correctly.
With 12.2, opening the lid gets a correct resume.

Reproducible: Always

Steps to Reproduce:
1. Suspend to RAM: Fn+F4 or close lid
2. Open lid
3.
Actual Results:  
When lid opens, systems initially starts like it should, but then goes back to suspend after a few seconds. Then, by pressing Fn key, system resumes correctly.

Expected Results:  
Open lid, system comes out of standby and stays that way.

Comment 1 Jiaying Ren 2012-12-13 02:27:13 UTC

(In reply to comment #0)
> User-Agent:       Opera/9.80 (X11; Linux i686) Presto/2.12.388 Version/12.11
> 
> On a ThinkPad X-41, the system suspends to RAM correctly. When the lid is
> opened, it starts for just a few seconds, then returns to standby. Pushing the
> Fn key then resumes the system correctly.
> With 12.2, opening the lid gets a correct resume.
> 
> Reproducible: Always
> 
> Steps to Reproduce:
> 1. Suspend to RAM: Fn+F4 or close lid
> 2. Open lid

Hi~Howard,would you please add your /var/log/pm-suspend.log ?

Comment 2 Howard Moreland 2012-12-13 03:48:27 UTC

Created attachment 516830 [details]
as requested

Jiaying,
Here's the file.
Regards,
Howard

Comment 3 Howard Moreland 2012-12-14 01:11:19 UTC

I updated this system today from 12.3 milestone 1 to 2, and the problem is gone.
Thanks,
Howard