Bug 7882

Summary: KDE ignores power management settings - hibernates anyway on laptop close
Product: Mageia Reporter: Frank Griffin <ftg>
Component: RPM PackagesAssignee: Mageia Bug Squad <bugsquad>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: Normal CC: balcaen.john, mageia, mageia
Version: Cauldron   
Target Milestone: ---   
Hardware: x86_64   
OS: Linux   
See Also: https://bugs.mageia.org/show_bug.cgi?id=7731
Whiteboard:
Source RPM: kde CVE:
Status comment:

Description Frank Griffin 2012-10-23 13:51:23 CEST
I have explicitly set KDE Power Management to only black the screen when the lid is closed, but it consistently puts the machine into hibernation.
Comment 1 Frank Griffin 2012-10-23 14:09:30 CEST
BTW, this worked fine up until a feww weeks ago.
Comment 2 Manuel Hiebel 2012-10-26 23:08:35 CEST
iirc there is/was a similar bug in gnome, I have only to found it
Manuel Hiebel 2012-10-26 23:10:04 CEST

CC: (none) => balcaen.john, mageia, nicolas.lecureuil
See Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=7731

Comment 3 Colin Guthrie 2012-10-28 13:36:05 CET
The issue is a lower level change.

systemd now handles lid close by default unless the higher levels specifically opt out and declare they will handle it themselves.

This is a decision made to deal with the issues that are quite specific to lid closes - e.g. even if a program (e.g. CD Burner) inhibits suspend, if the user slams his lid shut and puts his laptop in his backback and runs for a bus/train, then damage to any rotating disks (the CD is not critical but the data on the HD likely is!) might occur.

Therefore handling of lid closure has to be done differently to other user initiated suspend requires (e.g. pressing power button/selecting suspend from a menu etc), which can prompt the user with GUIs that indicate why hey may not currently be allowed to suspend (e.g. "You are currently burning a CD. Please wait for this operation to complete before suspend. Alternative, to override this warning, please enter the root password.").

Anyway, that's the why. No we have to make KDE allow overriding of this (they user is always right!).

So recently, Mikala merged some fedora patches into KDE workspace that *should* go some way to resolving this, but there does need to be a good bit more work to do it fully.

Essentially it needs a patch like this one for Gnome:
https://bugzilla.gnome.org/show_bug.cgi?id=680689

In the mean time, you can disable systemd handling of lid close via /etc/systemd/logind.conf although this should just be a stop gap until the higher level stuff is updated.




NB Mikala, the patch: http://svnweb.mageia.org/packages/cauldron/kdebase4-workspace/current/SOURCES/kde-workspace-4.8.0-bug796969.patch?view=log shouldn't be required - it was a bug a long time ago but it was ultimately fixed in systemd. We did used to carry that patch but dropped it when things were fixed in systemd IIRC. That said, I'm not sure if the changes in it are technically correct anyway!).
Comment 4 John Balcaen 2012-10-28 18:30:06 CET
(In reply to comment #3)
[...]
> 
> NB Mikala, the patch:
> http://svnweb.mageia.org/packages/cauldron/kdebase4-workspace/current/SOURCES/kde-workspace-4.8.0-bug796969.patch?view=log
> shouldn't be required - it was a bug a long time ago but it was ultimately
> fixed in systemd. We did used to carry that patch but dropped it when things
> were fixed in systemd IIRC. That said, I'm not sure if the changes in it are
> technically correct anyway!).
Well when i did test it was not working correctly without this patch, that's why i added it.
Comment 5 Colin Guthrie 2012-10-28 18:31:22 CET
Ahh well, perhaps I'm misremembering :s
Comment 6 Frank Griffin 2013-01-28 17:38:06 CET
This appears to be fixed now.

Status: NEW => RESOLVED
Resolution: (none) => FIXED