https://bugzilla.novell.com/show_bug.cgi?id=192090 seife@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED ------- Comment #12 from seife@novell.com 2006-09-12 08:49 MST ------- (In reply to comment #10)

(In reply to comment #9)

...

What desktop are you running (yes, it matters :-)?

KDE.

...

One problem with "lid close: ignore" is, that this event setting is only respected if kpowersave and gnome-power-manager are not running.

;-) Kpowersave is running.

...

Once they are running, they handle the lid events and you can configure the action to take on lid close in their configuration.

Are you sure -- I see only locking screen on lid close, and it is not an action, just a checkbox.

Yes, you are right. I was already thinking of the yet-to-be-implemented features :-)

...

So one question is: does the machine really suspend when you close the lid

I never said that. I said that the screen is dead. The system fully runs all the time.

...

The other question is: can you reanimate the display e.g. with a switch from X to console and back (ctrl-alt-f1, alt-f7) or (from X) simply with "xset dpms force off".

Yes, switching to quasi-text mode back and forth helps. And vice versa -- if I close the lid working in text mode, switching to X back and forth also helps.

Aha, so this also happens if you close the lid while already in text mode. It seems to be some kind of BIOS issue, but i am not sure. It can probably be worked around (at least for the "close the lid while in X" case) by setting EVENT_BUTTON_LID_OPEN="switch_vt" in /etc/powersave/event, this does a switch to VT1 and back to X on every lid-open event, so it should automate this. However, this is only a work-around and the real issue is still a mistery for me :-( -- 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.