https://bugzilla.novell.com/show_bug.cgi?id=259666 ------- Comment #1 from mboman@novell.com 2007-03-30 23:48 MST ------- 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. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

https://bugzilla.novell.com/show_bug.cgi?id=259666 hmacht@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |mboman@novell.com ------- Comment #3 from hmacht@novell.com 2007-04-02 02:40 MST ------- 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. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

https://bugzilla.novell.com/show_bug.cgi?id=259666 hmacht@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |hmacht@novell.com, dkukawka@novell.com AssignedTo|hmacht@novell.com |rodrigo@novell.com ------- Comment #5 from hmacht@novell.com 2007-04-02 03:54 MST ------- 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. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

https://bugzilla.novell.com/show_bug.cgi?id=259666 ------- Comment #7 from dkukawka@novell.com 2007-04-03 13:51 MST ------- (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). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

https://bugzilla.novell.com/show_bug.cgi?id=259666 ------- Comment #9 from ammulder@chariotsolutions.com 2007-04-10 10:47 MST ------- 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. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

https://bugzilla.novell.com/show_bug.cgi?id=259666 chrubis@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |axel.braun@gmx.de ------- Comment #11 from chrubis@novell.com 2007-06-06 06:40 MST ------- *** Bug 281331 has been marked as a duplicate of this bug. *** -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

https://bugzilla.novell.com/show_bug.cgi?id=259666 Rodrigo Moya <rodrigo@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=259666 User axel.braun@gmx.de added comment https://bugzilla.novell.com/show_bug.cgi?id=259666#c15 Axel Braun <axel.braun@gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Component|Mobile Devices |Mobile Devices Version|Alpha 2plus |Final Resolution|WONTFIX | Product|openSUSE 10.3 |openSUSE 11.1 --- Comment #15 from Axel Braun <axel.braun@gmx.de> 2009-02-21 02:07:33 MST --- 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) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.