Bug 229315 - Can't find the way, how to configure suspending action by closing laptop's lid
Summary: Can't find the way, how to configure suspending action by closing laptop's lid
Status: RESOLVED DUPLICATE of bug 221715
: 227411 (view as bug list)
Alias: None
Product: openSUSE 10.2
Classification: openSUSE
Component: Mobile Devices (show other bugs)
Version: Final
Hardware: i686 Other
: P5 - None : Enhancement (vote)
Target Milestone: ---
Assignee: Danny Al-Gaaf
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-12-18 13:03 UTC by Tanel Kokk
Modified: 2006-12-29 01:58 UTC (History)
2 users (show)

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tanel Kokk 2006-12-18 13:03:37 UTC
Thiskind of configuration feature - how to suspend the system, when closing laptop's lid - were in SuSE 10.1. Now in 10.2 it seems be gone. Why?
Comment 1 Siegfried Olschner 2006-12-20 09:13:59 UTC
Mobile devices team?
Comment 2 Matej Horvath 2006-12-20 12:57:45 UTC
Just to be sure: do you mean a feature in the yast?
Comment 3 Tanel Kokk 2006-12-20 22:17:44 UTC
To Matej: yes. Before (as I remember from 10.1) there were possibility in Yast powersawe module to configure lid closing action/policy (screensaver, suspend2ram, hibernate etc.)
Comment 5 Holger Macht 2006-12-28 22:54:40 UTC
The configuration option was removed from yast because this functionality has moved (or should have moved) to kpowersave. So either you have to wait for a new kpowersave update (maybe an online update) or just use gnome-power-manager. Danny already wrote something in his blog how to configure this manually with the kpowersave config file: http://dkukawka.blogspot.com/2006/11/kpowersave-config-tutorial.html
Comment 6 Holger Macht 2006-12-28 23:00:15 UTC
*** Bug 227411 has been marked as a duplicate of this bug. ***
Comment 7 Danny Al-Gaaf 2006-12-29 01:58:15 UTC

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