Bug 404992 - Impossible to log in with virtual keyboard on touch-screen-only machines - wrong keys?
Summary: Impossible to log in with virtual keyboard on touch-screen-only machines - wr...
Status: RESOLVED UPSTREAM
Alias: None
Product: plasmashell
Classification: Plasma
Component: Lock/logout (show other bugs)
Version: 5.12.7
Platform: Ubuntu Linux
: NOR major
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-03-02 15:41 UTC by Uwe Dippel
Modified: 2020-01-13 03:52 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Uwe Dippel 2019-03-02 15:41:22 UTC
SUMMARY


STEPS TO REPRODUCE
1. Try to log in using touch-screen
2. Enter correct password
3. 

OBSERVED RESULT
System says 'invalid'.
Just plugging in a keyboard and enetering the same password, however, logs one in.


EXPECTED RESULT
Possiblity to log in through touch-screen


SOFTWARE/OS VERSIONS
Windows: 
MacOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
Comment 1 Christoph Feck 2019-03-24 14:16:09 UTC
Which login manager are you using? SDDM?
Comment 2 Uwe Dippel 2019-03-24 15:11:11 UTC
(In reply to Christoph Feck from comment #1)
> Which login manager are you using? SDDM?

I would actually think so, the default one in kubuntu 18.04. I also have the sddm-package. 
How can I verify 100%? I'd like to get this solved, at least worked-around, because I tend to go walking about with my tablet and then I can't log in. 

Plus, as a *nix-user for 20+ years, I feel embarrassed when after that much of time, a screen keyboard can't accept and transfer proper keys. ;-)

I can't make the stars show the underlying characters.
Though, I can see that with all the characters that have variations in i18 (n, e, ,,,) one star pops up when I touch the character on the keyboard, and so does the alternative above that key, and when chosing the correct one from there, another star is added. That can never work.
Comment 3 Uwe Dippel 2019-04-08 16:51:39 UTC
I have found these two:
https://bbs.archlinux.org/viewtopic.php?id=194408
https://forum.kde.org/viewtopic.php?f=309&t=138783
and tried this solution, but it doesn't do anything. Here, the layouts do not show, contrary to the screenshot given.
In any case, the keyboard layout shouldn't matter too much, since I use my fingers to select the keys as displayed. So I don't confound Z and Y, for example. The keyboard seems to be another one from those mentioned elsewhere (onboard, florence), and has British English written across the blank key. And when one presses this blank once, it starts filling the password field with a constant flow of stars. 
Something seems to be very wrong here.
Comment 4 Uwe Dippel 2019-04-09 06:59:56 UTC
Another small step: It has nothing to do with the layout, since logging in by clicking the correct letters and numbers with a mouse always works. Touching them with my fingertip never works. 
Even stranger ...
Comment 5 Uwe Dippel 2019-04-09 16:35:51 UTC
One more to go: Pen input.
While the login screen accepts pen input (like touching the 'Virtual keyboard' in the lower left corner with a pen, the upcoming virtual keyboard itself ignores any pen input. So the only possible input is either with a mouse or with a finger. 
Together with the unwanted 'almost infinite blanks' at touching the space bar, the problem seems to lie with the virtual keyboard as offered. 
I wonder if - as workaround - it might be possible to pop up another virtual keyboard, like onboard or florence?
Comment 6 Christoph Feck 2019-04-25 10:42:37 UTC
Virtual keyboard not supporting pen input would be a Qt bug.

For QtWidget applications, pen input is automatically converted to mouse input when the application doesn't know about a pen. Not sure if this also is supposed to work for QtQuick applications, or if support for the pen has to be added expliticely.

I suggest to report virtual keyboard issues directly to Qt developers.
Comment 7 Nate Graham 2020-01-13 03:52:31 UTC
Yeah sounds like a Qt issue.