Power manager locks screen but does not show lock-screen
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| xfce4-power-manager (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
There are circumstances when the power manager locks the screen and suspends the computer, but on wake-up no lock-screen is shown. Nevertheless, the screen is locked and a password has to be entered into the invisible input box.
1. This happens when the display is in 'presentation mode'. On shutting the laptop lid everything proceeds as expected except that on re-opening the lid I can still see the display as it was, no mouse or key-presses work, and the screen is locked until I enter the unlock password in a dialogue box that is not visible.
2. If working with an external display with the laptop lid shut, then if I unplug the external monitor a similar thing happens. When I open the laptop lid I get a locked screen but the original display is still visible.
For me this is no more than a minor nuisance, but it would appear to be a security issue in that possibly private information is visible to anyone who opens the laptop lid.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xfce4-power-manager 4.16.0-1
ProcVersionSign
Uname: Linux 5.15.0-58-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
CasperMD5CheckR
CurrentDesktop: XFCE
Date: Wed Feb 15 11:38:32 2023
InstallationDate: Installed on 2020-09-17 (880 days ago)
InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
SourcePackage: xfce4-power-manager
UpgradeStatus: Upgraded to jammy on 2022-10-30 (107 days ago)
| Raphael Mankin (raph-p) wrote | #1 |
| Marc Deslauriers (mdeslaur) wrote | #2 |
| information type: | Private Security → Public Security |
| tags: | added: community-security |
Thanks for taking the time to report this bug and helping to make Ubuntu better. Since the package referred to in this bug is in universe or multiverse, it is community maintained. If you are able, I suggest coordinating with upstream and posting a debdiff for this issue. When a debdiff is available, members of the security team will review it and publish the package. See the following link for more information: https:/