linuxmint / linuxmint/cinnamon
org.cinnamon.desktop.lockdown keys are unefficient
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 5.6k
- Forks
- 915
- Avg merge
- 5d 22h
- Merged PRs (30d)
- 3
Description
* Cinnamon version (cinnamon --version)
3.8.2 and 3.6.7
* Distribution - (Mint 17.2, Arch, Fedora 25, etc...)
Archlinux 27 and Mint 18.3
* Graphics hardware *and* driver used
No matters
* 32 or 64 bit
64 bits
Issue
The value of the keys in org.cinnamon.desktop.lockdown (disable-lock-screen, disable-log-out, disable-switching-user) is not considered by Cinnamon.
Example: the script /usr/share/cinnamon-screensaver/cinnamon-screensaver-command.py doesn't consider the boolean value of the disable-lock-screen key, when called by the command cinnamon-screensaver-command --lock.
No more considered are the keys in org.gnome.desktop.lockdown.
,
Steps to reproduce
Use dconf-editor to set to true the value of the disable-lock-screen key in org.cinnamon.desktop.lockdown and in org.gnome.desktop.lockdown.
Then, use the command cinnamon-screensaver-command --lock or the "Lock Screen" button in the menu.
The screen becomes locked.
Expected behaviour
That screen locking, user switching, or logout become prohibited when the value of the corresponding key is set to true.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with /usr/share/cinnamon-screensaver/cinnamon-screensaver-command.py and reproduce the issue using dconf-editor, cinnamon-screensaver-command --lock, and the Lock Screen menu button. Trace how the disable-lock-screen, disable-log-out, and disable-switching-user keys are read, then verify that true values prohibit the corresponding actions for both Cinnamon and GNOME lockdown settings.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, python
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100