Bug 19759 - Un-suspend password prompt screen does not paint
Summary: Un-suspend password prompt screen does not paint
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: KDE maintainers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-11-11 16:31 CET by Frank Griffin
Modified: 2017-03-20 19:50 CET (History)
2 users (show)

See Also:
Source RPM: plasma
CVE:
Status comment:


Attachments

Description Frank Griffin 2016-11-11 16:31:40 CET
For the last week or so, if you suspend Plasma and then click the power button to get the password prompt screen to unlock the desktop, the resulting screen does not paint window events.

The mouse cursor is visible and moves, but clicking on the password field does not appear visually to give that field focus.  However, the field does in fact have the focus.  If you type a password, the characters will not be painted in the field, but if you follow the password with ENTER, the screen unlocks.

So, in fact, clicking on the field does give it the focus and the typed characters are received and processed, but there is no visual indication of this.

Unfortunately, anyone who doesn't figure this out will only see that there is no way to unlock the screen.
Marja Van Waes 2016-11-11 20:27:08 CET

CC: (none) => marja11
Assignee: bugsquad => kde

Comment 1 Nicolas Lécureuil 2017-03-19 22:41:24 CET
is it still valid on current cauldron ?

CC: (none) => mageia

Comment 2 Frank Griffin 2017-03-20 00:05:42 CET
Yes.  After months of this, I can't swear that the focus *isn't* on the password field (I suspect it is), it's just that the text cursor doesn't appear there so you have no indication that the field actually has the focus, and you don't get the expected obscuring bullets as you type the password characters.
Comment 3 Frank Griffin 2017-03-20 00:10:59 CET
Actually, I'll postpone comment on this because cauldron is currently updating at a crawl, so I can't swear to what happens under "current" cauldron.
Comment 4 Frank Griffin 2017-03-20 19:50:01 CET
Under today's cauldron, this has been fixed.

Status: NEW => RESOLVED
Resolution: (none) => FIXED


Note You need to log in before you can comment on or make changes to this bug.