Community Packages

Please read this before reporting a bug:
http://wiki.archlinux.org/index.php/Reporting_Bug_Guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#39609 - [cinnamon-screensaver] Lock screen on suspend broke (regression)

Attached to Project: Community Packages
Opened by sb56637 (sb56637) - Monday, 24 March 2014, 14:32 GMT
Last edited by Balló György (City-busz) - Tuesday, 22 April 2014, 18:20 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Balló György (City-busz)
Alexandre Filgueira (faidoc)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Hi there,
I have been running Cinnamon for quite a while now. The most recent update to cinnamon-screensaver 2.0.3-4 and cinnamon-settings-daemon 2.0.8-4 seems to have introduced a regression. The dconf setting org.cinnamon.settings-daemon.plugin.power "lock on suspend" doesn't work anymore. My laptop does suspend, but upon resuming there is no lock screen. I downgraded to cinnamon-screensaver 2.0.3-3 and cinnamon-settings-daemon 2.0.8-2 and screen locking works again.

DISCLAIMER: I use Manjaro, not Arch. However, I'm 99% sure that the package was pulled directly from Arch and this bug undoubtedly affects Arch users too.

The Cinnamon devs claim it's a distro-specific packaging bug. (https://github.com/linuxmint/Cinnamon/issues/2961)

Thanks a lot for the help with this bug!
This task depends upon

Closed by  Balló György (City-busz)
Tuesday, 22 April 2014, 18:20 GMT
Reason for closing:  Fixed
Comment by Balló György (City-busz) - Monday, 24 March 2014, 15:53 GMT
Previously the screensaver activated even if you disabled the lock on suspend setting. It has been fixed in cinnamon-screensaver 2.0.3-4 and cinnamon-settings-daemon 2.0.8-4 so if you set lock-on-suspend setting to true then the screen will be locked on suspend:

$ gsettings set org.cinnamon.settings-daemon.plugins.power lock-on-suspend true

If it doesn't work, then make sure that you won't disabled the power plugin of cinnamon-settings-daemon or cinnamon-screensaver:

$ gsettings set org.cinnamon.settings-daemon.plugins.power active true
$ gsettings set org.cinnamon.desktop.screensaver lock-enabled true
$ gsettings set org.cinnamon.desktop.lockdown disable-lock-screen false
Comment by sb56637 (sb56637) - Monday, 24 March 2014, 16:07 GMT
Thanks György for the reply. But doesn't the "org.cinnamon.desktop.screensaver lock-enabled true" setting make the screen lock every time the screensaver activates after inactivity?

EDIT: Yes, "org.cinnamon.desktop.screensaver lock-enabled true" does make the screen lock when the screensaver activates, which is not what I want. I just want the "Require my password when waking from suspend" option in the Screensaver & Lock Settings to work, which is currently broken in this most recent update.
Comment by sb56637 (sb56637) - Friday, 11 April 2014, 15:13 GMT
Hello, I reported this bug to the Cinnamon bug tracker, but they claim it is a distro-specific packaging bug:
https://github.com/linuxmint/Cinnamon/issues/2961
Comment by sb56637 (sb56637) - Tuesday, 22 April 2014, 12:48 GMT
  • Field changed: Percent Complete (100% → 0%)
Hello, thank you very much for looking into this issue. I tried cinnamon-settings-daemon 2.0.8-6, but the issue persists. I enabled org.cinnamon.settings-daemon.plugins.power lock-on-suspend, but it does not lock when suspending.
Comment by Balló György (City-busz) - Tuesday, 22 April 2014, 16:43 GMT
It works here. Please make sure that you set the following settings properly:
$ gsettings set org.cinnamon.settings-daemon.plugins.power active true
$ gsettings set org.cinnamon.settings-daemon.plugins.power lock-on-suspend true
$ gsettings set org.cinnamon.desktop.lockdown disable-lock-screen false

If you still have this problem on an up-to-date Arch Linux, then report the problem to upstream.
Comment by sb56637 (sb56637) - Tuesday, 22 April 2014, 17:20 GMT
It also works for me on an updated installation.
Comment by Balló György (City-busz) - Tuesday, 22 April 2014, 17:26 GMT
Okay, then I'm closing this bug.

Loading...