Bug 310692

Summary:	standby s1 from kickoff menu doesn't work
Product:	[openSUSE] openSUSE 11.1	Reporter:	kibana dai <kibana>
Component:	Mobile Devices	Assignee:	Forgotten User ZhJd0F0L3x <forgotten_ZhJd0F0L3x>
Status:	RESOLVED DUPLICATE	QA Contact:	E-mail List <qa-bugs>
Severity:	Minor
Priority:	P3 - Medium
Version:	Factory
Target Milestone:	---
Hardware:	32bit
OS:	openSUSE 10.3
Whiteboard:
Found By:	Other	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description kibana dai 2007-09-14 19:26:39 UTC

Hi,

I have Dell Inspiron 5150 with bios A38 with Nvidia graphics board. As subject says if I select standby from kickoff menu a dialog box appears from kde saying "suspend failed". The same things doesn't work from kpowersave applet also by right clicking and selecting standby. It was perfectly working with Opensuse 10.2 using both methods (via kickoff menu and kpowersave applet). However, when I do echo standby > /sys/power/state works perfectly fine. I don't see any log anywhere so I don't know how and what to check. I hope someone can throw some light on this.

Comment 1 Timo Hoenig 2007-09-18 10:51:50 UTC

Seife, can you give further instructions and reassign accordingly?  Thanks!

Comment 2 Forgotten User ZhJd0F0L3x 2007-09-19 11:37:27 UTC

Standby (S1) is right now not supported at all. The question is, why is it still appearing in kpowersave and the Kickoff menu?

Comment 3 kibana dai 2007-09-20 13:11:33 UTC

(In reply to comment #2 from Stefan Seyfried)
> Standby (S1) is right now not supported at all. The question is, why is it
> still appearing in kpowersave and the Kickoff menu?
> 

Do you mean it is stopped to be supported from Opensuse 10.3? Untill opensuse 10.2, it was working perfectly fine with me !!

Comment 4 Forgotten User ZhJd0F0L3x 2007-09-20 14:06:33 UTC

yes, it is basically a missing feature.
We want to select S1 or S3 transparently for the user depending on the capabilities and features of the machine. Unfortunately this is not yet implemented.

pm-utils basically only knows about 2 suspend states:
- suspend (suspend to RAM)
- hibernate (suspend to disk)
(and hybrid suspend, which is a mixture of those two).
It does not know about standby.

So i have to resolve this bug as "later", since we will implement something, but not in time for 10.3.

Comment 5 Danny Al-Gaaf 2007-10-15 14:38:27 UTC

Reopen to reassign

Comment 6 Danny Al-Gaaf 2007-10-15 14:39:09 UTC

reassign to Seife to handle comment #4 and pm-utils

Comment 7 Danny Al-Gaaf 2007-10-15 14:39:50 UTC

set back to old status.

Comment 8 Stephan Kulow 2008-06-25 09:10:44 UTC

mass reopening of later+remind bugs of 11.0

Comment 9 Forgotten User ZhJd0F0L3x 2008-07-21 18:28:32 UTC

We will have to watch linux kernel upstream, since eventually S1 support might go away completely.

Comment 10 Forgotten User ZhJd0F0L3x 2008-10-15 10:58:34 UTC

Is this still present in 11.1 betas?
Danny, do you still offer standby from HAL?

Comment 11 Andreas Jaeger 2008-11-14 10:38:18 UTC

Danny, please answer comment #10.

Comment 13 Timo Hoenig 2008-11-14 10:45:57 UTC

(In reply to comment #10 from Stefan Seyfried)

> Danny, do you still offer standby from HAL?

It does.

org.freedesktop.Hal.Device.SystemPowerManagement offers the following functions:

* Hibernate()
* Reboot()
* SetPowerSave()
* Shutdown()
* Standby()
* Suspend()
* SuspendHibernate()

I guess that standby puts the system into S1 -- but I'm not completely sure.

Comment 14 Danny Al-Gaaf 2008-11-14 19:08:44 UTC


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