Summary: | Typed password text appears on login prompt of secondary screen, not primary screen | ||
---|---|---|---|
Product: | [Plasma] plasmashell | Reporter: | BOF <bugs_kde_org.5.kuru> |
Component: | Theme - Breeze | Assignee: | Plasma Bugs List <plasma-bugs> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | kde, kde, kdedev, nate, visual-design |
Priority: | NOR | Keywords: | multiscreen |
Version First Reported In: | 6.4.3 | ||
Target Milestone: | 1.0 | ||
Platform: | Neon | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | 6.5.0 | |
Sentry Crash Report: |
Description
BOF
2025-07-29 14:11:33 UTC
Further testing: 1) Primary monitor For fun I tested to make the secondary monitor the primary one (as described in BugID 472542). There was no change, the secondary monitor still showed the password being typed while the laptop monitor showed the login screen. 2) Standby display I noticed that when you do not log in, after about a minute or so the screen enters some kind of screensaver mode (login field and buttons vanish, background is unblurred). If you are on the second screen with your mouse and move it around, only the secondary screen shows the login screen. As said: I have discovered this bug on a beamer. It was very unsettling that my laptop screen stayed in the 'standby' mode and didn't want to show any login screen (at the time I didn't know what effect this would have during a presentation or other scenarios with a second screen). Today I saw that if the mouse is moved the the laptop screen, it 'wakes up' to (show the login field), but the password is only typed on the secondary monitor. Moving to the right component I'm not able to reproduce this on git-master using the same steps 1. Shut down the system 2. Connect the HDMI cable to the laptop 3. Startup the machine 4. Type in your password I observed the obscured password being entered on both screens It looks like this has been fixed in git-master and so it should work this way on your system once it's updated to 6.5. Please reopen this report if you experience the same behavior in 6.5. Thanks! |