[plasmashell] [Bug 499637] Lockscreen sometimes prompts for password immediately after locking, and sometimes doesn't

[Ketan]

https://bugs.kde.org/show_bug.cgi?id=499637

--- Comment #18 from Ketan <k3tan at pm.me> ---
(In reply to Marc Payne from comment #17)
> (In reply to Ketan from comment #15)
> > (In reply to Marc Payne from comment #8)
> > > I've been seeing this 'immediate password prompt' issue on several systems,
> > > all running Arch. I've compared package versions between affected and
> > > not-affected systems and have concluded that it is the update of Qt 6.8.1 ->
> > > 6.8.2 causing this.
> > > 
> > > I added some additional logging output to LockScreenUi.qml
> > > (/usr/share/plasma/shells/org.kde.plasma.desktop/contents/lockscreen/) and
> > > it seems that Item::MouseArea::onPositionChanged is being called immediately
> > > even when the system is idle (no mouse movement), setting uiVisible = true.
> > > A quick search of the Qt 6.8.2 release notes finds QTBUG-127122 - this is an
> > > intentional change emitting the positionChanged event in response to a
> > > QEvent::HoverEnter event. No matter where the pointer is positioned, it will
> > > enter the newly created full-screen MouseArea when the lock screen is
> > > displayed and onPositionChanged will be called.
> > > 
> > > I have temporarily fixed the issue on a couple of systems by introducing a
> > > new boolean property 'ignorePositionChanged' and using it to make the first
> > > call of onPositionChanged a no-op (uiVisible = !ignorePositionChanged;
> > > ignorePositionChanged = false). I don't have any experience with Qt so
> > > perhaps there is a more elegant solution.
> > 
> > Are you able to share what you've changed in the LockScreenUI.qml file to
> > temporarily fix this? Or even attach your edited LockScreenUI.qml file?
> > Thank you!
> 
> Sure, I've attached a diff which will apply with the patch command. Or you
> can apply the changes by hand. It just introduces an additional boolean
> property and modifies the onPositionChanged handler.

thank you so much! this fix worked perfectly!

-- 
You are receiving this mail because:
You are on the CC list for the bug.