linuxmint / linuxmint/cinnamon

[SECURITY] screensaver (lockscreen) leak actual state

Open
#8,817 5 comments 4 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

BUG
Dominant language
JavaScript
Stars
5.6k
Forks
915
Avg merge
5d 22h
Merged PRs (30d)
3

Description

 * Cinnamon version 3.8.8
 * Distribution Debian 10 Buster
 * Graphics hardware *and* driver used :

lspci -nnk | grep -i vga -A3 
00:02.0 VGA compatible controller [0300]: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07)
	Subsystem: Dell UHD Graphics 620 [1028:081c]
	Kernel driver in use: i915
	Kernel modules: i915

 * 64 bit

Issue

The lock-screen can be partly bypass by adding a screen (HDMI and DVI tested).
Screen content behind lock-screen is displayed and mouse is partly usable.
Sometimes only the background is displayed, other times it's all actual work... I don't know why...
Nothing change visually wen typing but keyboad is always focused on password field and it's possible to login.

Steps to reproduce

  • Lock your screen
  • Add a display device
  • enjoy

Expected behaviour

lock-screen just lock the screen

Other information

Please forgive my poor English :'(

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the lock-screen behavior with an external display connected after locking, then trace the lock-screen and display-handling entry points involved. Compare what appears on the added screen and whether the password field still accepts input. Done means adding a display while locked never reveals the desktop or permits interaction before authentication.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
desktop, security
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.