Bug 507516 - Performing a swipe gesture with a touchscreen, the password input field is visible during the gesture and hides after completion again.
Summary: Performing a swipe gesture with a touchscreen, the password input field is vi...
Status: CONFIRMED
Alias: None
Product: plasmashell
Classification: Plasma
Component: Screen locking (other bugs)
Version First Reported In: 6.4.3
Platform: Other Linux
: NOR minor
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords: regression
Depends on:
Blocks:
 
Reported: 2025-07-26 17:06 UTC by kde.elm430
Modified: 2025-09-25 09:26 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description kde.elm430 2025-07-26 17:06:32 UTC 
SUMMARY
Performing a swipe gesture with a touchscreen, the password input field is visible during the gesture and hides after completion again.

STEPS TO REPRODUCE
1. Lock the screen
2. Swipe one the screen

OBSERVED RESULT
The password input field is visible only during the swipe gesture

EXPECTED RESULT
The password input field should be permanently displayed after completing the swipe gesture

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch Linux
KDE Plasma Version: 6.4.3
KDE Frameworks Version: 6.16.0
Qt Version: 6.9.1
Comment 1 kde.elm430 2025-08-04 20:36:30 UTC 
Introduced by https://invent.kde.org/plasma/plasma-desktop/-/commit/305d88e050ffe4018544e6d4b7c5c6730ca5c0d4.
Qt synthesizes a mouse event, therefore `containsMouse` is false and the fadeoutTimer is restarted.
I unfortunately don't have any knowledge in Qt/Qml, but per documentation wrapping the MouseArea in a MultiPointTouchArea might help.
Comment 2 tramonti.luca18 2025-09-25 09:26:48 UTC 
I am also experiencing this bug, unlocking the device using touch is very hard and awkward to do (you have to tap and hold anywhere on the screen and quickly tap the password field before it fades out), hope it gets fixed soon. This should probably be higher than low priority