Comment 1 for bug 185082

Revision history for this message
Juan-Carlos Amengual (jcamen) wrote :

More info: today's experience (till now :-)

In kpowersave, I have configured the general settings to "suspend to RAM" when lid close button in button events.

1. This morning: I turned the laptop on an began to work. Then I had to go to another desk, so I closed the lid (like I used to in Feisty). Automatically laptop went into suspend mode as in Feisty. Everything OK.
2. When I arrived to the other desk, I opened the laptop, then it resumed and after almost 30 seconds of tension :-) the screen showed my KDE desktop OK... ¡but the sound didn't work! (even restarting artsd) Modules were loaded, no error message at all, but I couldn't listen to any sound. Well, I kept on working till the moment of returning at my desk.
3. Then, I closed the lid ... ¡and nothing happened! Laptop didn't go into suspend mode. Well, that was annoying, but I right clicked in the kpowersave icon and chose the "suspend to RAM" option. Then, laptop went into suspend mode and I closed the lid.
4. Now, I am at my desk. I have opened the lid and laptop has resumed. Everything is OK (not like yesterday, for instance): X is OK (KDE desktop OK), everything OK ... ¡¡¡and now sound works perfect!!! :-¿? I can listen to system sounds, music, ... even tried to play a xvid movie with mplayer and everything was OK.

To be continued... ;-)