linuxmint / linuxmint/cinnamon
No password required after hibernate despite lock settings enabled
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 5.6k
- Forks
- 915
- Avg merge
- 5d 22h
- Merged PRs (30d)
- 3
Description
System Information:
- Linux Mint: 22.1 (xia)
- Kernel: 6.8.0-57-generic
- Cinnamon: 6.4.8
- Desktop Environment: Cinnamon
Issue:
When returning from hibernate, the system does not require authentication despite having the following security settings enabled:
- org.cinnamon.desktop.screensaver lock-enabled = true
- org.cinnamon.settings-daemon.plugins.power lock-on-suspend = true
- org.cinnamon.desktop.screensaver idle-activation-enabled = true
Expected Behavior:
- System should require password authentication when returning from hibernate
- This is a basic security feature that should work by default
Actual Behavior:
- System returns from hibernate without requesting authentication
- Screen lock settings appear to be ignored during the hibernate/resume cycle
Security Impact:
This is a security concern as anyone can access the system and all open applications after hibernate without authentication.
Steps to Reproduce:
- Configure screen lock settings as listed above
- Hibernate the system
- Wake the system
- Observe that no password is required to access the desktop
Additional Notes:
- Manual screen locking works correctly (using dm-tool lock or Ctrl+Alt+L)
- Screen lock works properly for screen timeout
- Only the hibernate-resume cycle appears to bypass the lock screen
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 by reproducing the hibernate and resume cycle with the listed Cinnamon screensaver and power settings, then inspect how Cinnamon handles lock-on-suspend compared with manual locking via dm-tool lock or Ctrl+Alt+L. Done means resume consistently requires authentication while timeout and manual locking continue to work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- desktop-dev, operating-systems, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100