Description of problem: gnome-tweak-tool 3.6 doesn't change laptop lid close behavior. If I select blank or nothing when laptop lid is closed, it still suspends This seemed to break when 3.6 was first released. It seemed to work before then. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3.
This seems to be an interaction with the new systemd behavior.... https://bugzilla.redhat.com/show_bug.cgi?id=859224 Should patch mageia with fedora patch...
thanks !
Keywords: (none) => PATCHCC: (none) => fundawang, mageia, olav
We've already got that patch for over a week! http://svnweb.mageia.org/packages/cauldron/gnome-settings-daemon/current/SOURCES/gnome-settings-daemon-3.6.0-bgo680689-logind-power-suspend.patch?revision=302722&view=markup That said, I wasn't aware that it was meant to solve any problems with settings in gnome-tweak-tool. I think this is somewhat separate. Certainly running systemd-inhibit --list before and afer setting that value in g-t-t doesn't change anything. I would expect to see a "handle-lid-switch" option there if it was handled. As a temporary workaround, just run the following in a terminal: systemd-inhibit --what=handle-lid-switch --who="Me" --why="Because I wanna" --mode=block bash I guess further patches are needed to make g-t-t option work.
I can confirm this bug for the released version! Looks like the new option "lid-close-suspend-with-external-monitor" is responsible for this behaviour.
CC: (none) => mageiaHardware: i586 => AllVersion: Cauldron => 3
removing the PATCH keyword since the patch didn't solve the problem
Keywords: PATCH => (none)
Mageia 3 changed to end-of-life (EOL) status 4 months ago. http://blog.mageia.org/en/2014/11/26/lets-say-goodbye-to-mageia-3/ Mageia 3 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Mageia please feel free to click on "Version" change it against that version of Mageia and reopen this bug. Thank you for reporting this bug and we are sorry it could not be fixed. -- The Mageia Bugsquad
Status: NEW => RESOLVEDResolution: (none) => OLD