|
Bugzilla – Full Text Bug Listing |
| Summary: | Suspend with fn+f4 and waking up with power button put's computer back to sleep | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 11.1 | Reporter: | Magnus Boman <mboman> |
| Component: | Mobile Devices | Assignee: | E-mail List <mobile-bugs> |
| Status: | VERIFIED WONTFIX | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P3 - Medium | CC: | ammulder, atuel, axel.braun, behlert, mcfrost |
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Magnus Boman
2007-03-31 05:39:07 UTC
Sorry, I was wrong. The same thing happens (it will go straight back to sleep) even if I use FN+F4 to STR and then FN+F4 to wake it up. The second time I wake it up with FN+F4 it works. Holger, Rodrigo, this sounds like g-p-m conflicting with some signal. It shouldn't be necessary to press FN-F4 to bring the system back up. FN should be enough. I suspect the power button emitting an event via the input layer after the system is back up which gnome-power-manager handles. If so, g-p-m somehow should ignore this event. Magnus, can you please also try with kpowersave. We need to know if it's also affected. Thanks. Tried with kpowersave and it works perfectly. Went back to GPM and then only pressed FN to resume, but it still went back to sleep the first time. Danny, does kpowersave handle anything coming from the input layer which g-p-m does? Anyway, due to the fact that it works with kpowersave, reassigning to Rodrigo. *** Bug 257356 has been marked as a duplicate of this bug. *** (In reply to comment #5) > Danny, does kpowersave handle anything coming from the input layer which g-p-m > does? No, KPowersave handle only events from HAL, nothing from the normal input layer (and as it look atm I don't plan to let KPowersave read from the input layer). *** Bug 262213 has been marked as a duplicate of this bug. *** I reported Bug 262213 and in that case, I had the problem with KDE and kpowersave. I believe I used Fn-F4 to suspend, and when I just hit Fn it didn't wake up, so I used the power button to wake it up, whereupon it starting resuming and then suspended again and woke up properly the second time (when I hit the power button again). When it was first suspended and the Fn key didn't wake it up, I believe I also closed and reopened the lid with no effect. So it is definitely a problem with KDE too. I don't hugely care whether I have to use the Fn key or power button to wake it up manually, but it would certainly be nice if the lid open caused it to resume. Also, I had the same double-suspend problem with Suspend to Disk. In that case, I only tried using the power button to get it to resume, but during the resume process, it suspended to disk again, and on the second resume it came up normally. A fix was suggested for openSUSE 10.2 in Bug #264692 and that worked for me, so I hope a similar fix will resolve the issue here too. *** Bug 281331 has been marked as a duplicate of this bug. *** I solved this Problem by installing hal 5.10 from http://download.opensuse.org/repositories/home:/btimothy/openSUSE_10.3/ At least now my machine doesn't go into suspend twice. I guess we don't have the time to look into this for 10.3 anymore. If you're still seeing this in 11.1, or even factory, please reopen. Sorry. reopen for 11.1. The machine mentioned in Bug 281331 (comment 11) shows the same problem again, when using Fn+F4: after wakeup it turns into suspend again. calling s2ram from the command line works fine (only 1 suspend) Christian, is anybody looking at this for 11.2? Please reopen for 12.1 if necessary |