Bug 419216 - KDE: Screen saver fails to lock screen while display is switched to a different virtual terminal
Summary: KDE: Screen saver fails to lock screen while display is switched to a differe...
Status: RESOLVED DUPLICATE of bug 369137
Alias: None
Product: kde
Classification: I don't know
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR critical
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-03-25 09:32 UTC by Josef Wolf
Modified: 2020-04-15 07:39 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Josef Wolf 2020-03-25 09:32:51 UTC
SUMMARY
On several freshly installed systems with KDE, the screen saver won't lock the screen while a different virtual terminal is active.

STEPS TO REPRODUCE
1. Configure the screen saver to 1 minute and require the password after additional 5 seconds.

2. While the screen saver in not active, activate a different virtual terminal (e.g. by pressing CTL-ALT-F2)

3. Wait for more than 70 seconds.

4. Switch back to the desktop

OBSERVED RESULT
when switching back, all the open applications (possibly
showing confidential data!) are visible for about one second. Only then the screen starts to dim. And due to the setting of 5 seconds for password requirement,
one can stop the screen saver just by typing some key or moving the mouse.

EXPECTED RESULT
Screen saver is active and only the password screen is visible.

SOFTWARE/OS VERSIONS
I can see the Problem with opensuse-Leap-15.1 as well as with ubuntu-18.04 (when kubuntu-desktop is installed).

ADDITIONAL INFORMATION
Result of mailing list discussion so far:
- Problem can be reproduced by other people
- Problem does appear with sddm, lightdm and kdm
- Problem does not seem to appear with gdm and xfce

Mailing list thread: https://lists.opensuse.org/opensuse/2020-03/msg00267.html
Comment 1 Christoph Feck 2020-04-15 07:39:16 UTC

*** This bug has been marked as a duplicate of bug 369137 ***