Bug 232075

Summary:	T43 suspend to RAM detection unreliable
Product:	[openSUSE] openSUSE 10.2	Reporter:	Thorsten Kukuk <kukuk>
Component:	Mobile Devices	Assignee:	Holger Macht <hmacht>
Status:	RESOLVED DUPLICATE	QA Contact:	E-mail List <qa-bugs>
Severity:	Normal
Priority:	P5 - None	CC:	behlert
Version:	Final
Target Milestone:	---
Hardware:	x86
OS:	Other
Whiteboard:
Found By:	Other	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Thorsten Kukuk 2007-01-05 12:46:13 UTC

Standard IBM T43 (no 43p).

With SL10.1, closing the lid starts reliable suspend to RAM.
With openSUSE 10.2 (all updates installed), closing the lid only starts suspend to RAM in very few cases. In the other cases, you have to use in about 50% of the cases the keys (Fn + Suspend), in the other 50% you have to call powersave.

Couldn't find a pattern in which cases which method will work until now.

Comment 1 Danny Al-Gaaf 2007-01-06 11:49:16 UTC

Which Desktop do you use? KDE? Or do you mean also suspend on lidclose if you are not logged in to KDE?

Comment 2 Thorsten Kukuk 2007-01-06 11:57:44 UTC

I use gdm as display manager and KDE as desktop.

Closing the lid starts the KDE screensaver, but does not always activate suspend to RAM.

Suspend on lidclose on console (not logged in) shows the same problems.

Comment 3 Danny Al-Gaaf 2007-01-06 12:56:22 UTC

sounds (for 10.1) for me like a problem with powersave or s2ram.

Comment 4 Thorsten Kukuk 2007-01-06 14:26:58 UTC

(In reply to comment #3)
> sounds (for 10.1) for me like a problem with powersave or s2ram.

Why "for 10.1"? There it works reliable.

Comment 5 Thorsten Kukuk 2007-01-08 09:42:29 UTC

Ok, I did some more tests yesterday.

It works flawless until I log in into the KDE environment the first time, after that the problems starts ...

Comment 6 Forgotten User ZhJd0F0L3x 2007-01-08 15:57:34 UTC

Ok, then it is the "kpowersave has no button handling implemented yet" bug.

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

Comment 7 Thorsten Kukuk 2007-01-08 16:07:15 UTC

Ok, found the typo in my config and now it seems to work.