|
Bugzilla – Full Text Bug Listing |
| Summary: | Fn+F12 Thinkpad hotkey does not suspend to disk (S2Disk / hibernate) | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 11.2 | Reporter: | Christoph Nagel <c.Nagel> |
| Component: | Mobile Devices | Assignee: | E-mail List <mobile-bugs> |
| Status: | VERIFIED WONTFIX | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Major | ||
| Priority: | P2 - High | CC: | anshulajain, filalv, user2304 |
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | x86-64 | ||
| OS: | openSUSE 11.2 | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Christoph Nagel
2009-11-17 08:45:33 UTC
One solution I found could be: In the file /usr/lib/acpid/thinkpad_handler add the lines: if [ "$WHAT" = "00000080" -a "$SERIAL" = "0000100c" ]; then /usr/sbin/pm-hibernate fi I have exactly the same Suse 11.2/Gnome from live CD install and the same symptoms described above. Added the lines as in Nagel's suggestion and it works fine! Machine: Thinkpad T42, 14'', P-M 1.7 GHz, Radeon M10 / 9600. Hello, still have same problems with 11.3 MS 7 and Thinkpad X200t here. I added the suggested lines to "thinkpad_handler", that works, but seems to be more like a workaround. Up to OS 11.1 i could configure the suspend-actions of FN+F4 an FN+F12 via the graphical menu of kpowersave and could add options like "Lock screen on resume" for example. A tweaking of thinkpad_handler was not necessary. It seems to me, that something different was broken between 11.1 and 11.2. Unfortunately, i don't really know how to find out what. Any clues ? Regards. *** Bug 593590 has been marked as a duplicate of this bug. *** The lifecycle of openSUSE 11.2 ended on May 12th 2011. I'm closing this bug to make it easier to focus on upcoming releases. Thank you for reporting this issue and we are sorry that we have not be able to fix it before this version reached its end of life. If you would still like to see this bug fixed and are able to reproduce it against a maintained version, please reopen this bug and change the 'version' of this bug to the applicable version. |