Details
-
Bug
-
Resolution: Unresolved
-
P1: Critical
-
None
-
6.8.2
-
None
Description
The issue appeared with Qt 6.8.2. It looks like as it appeared since change https://codereview.qt-project.org/c/qt/qtdeclarative/+/603061 from QTBUG-127122
Upon creation of a MouseArea a onPositionChanged signal is beeing generated by the QEvent::HoverEnter handler although the position of the mouse has not changed.
For example imagine the following (KDE Lock Screen)
The system is idle
say the position of the mouse is 960,540
system idle since 5min, KDE lock screen being activated
creation of MouseArea by KDE lock screen for the whole screen (0,0 ; 1920,1080)
Since the position of the mouse was 960,540, the mouse is already within the MouseArea upon creation
mouse was NOT moved
QEvent::HoverEnter handler firing onPositionChanged signal
Hence, KDE lock screen is acting like user wants to unlock screen (although system is still idle and user not present)
Detailed explanation:
Since Qt 6.8.2 was upgraded on my the system, KDE lock screen prompts for password immediately after KDE lock screen being activated.
Since I am using a U2F USB Security Key as second factor, that is prompting for touching it (blinking LED). Since when I am not on the computer (the reason for the Lock Screen to be activated), the USB Security key always runs into a timeout. And this timeout always results in an unlock failure after I enter the password.
solution so far without spamming the logs with invalid logins: disable U2F. But lets be hones, this is not really the sense of having U2F, is ist?
Also see https://bugs.kde.org/show_bug.cgi?id=499637
Thanks to Marc Payne who tackled the issue down and identified it as a Qt regression