Bug 387270 - virtual keyboard state inverted after session switch
Summary: virtual keyboard state inverted after session switch
Status: RESOLVED WORKSFORME
Alias: None
Product: kscreenlocker
Classification: Unmaintained
Component: breeze-theme (other bugs)
Version First Reported In: unspecified
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-11-24 16:36 UTC by Harald Sitter
Modified: 2020-01-13 14:12 UTC (History)
3 users (show)

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


Attachments
screenshots (3.38 MB, application/x-xz)
2017-11-24 16:36 UTC, Harald Sitter
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Harald Sitter 2017-11-24 16:36:08 UTC
Created attachment 109039 [details]
screenshots

There seems to be a fairly peculiar state loss of whether the virtual keyboard is on in between session switching.

I am going to attach a sequence of screenshots which probably show the problem best. The screenshots cover the following

- screen locked
- virtual keyboard active
- virtual keyboard gets hidden by clicking the icon in the lower left corner
- switch user gets clicked
- start a new session gets clicked
- sddm comes up
- login & logout of second session
- vt switch back to the original session
- the last screenshot is the original session's lock screen but it now suddenly has the virtual keyboard toggled on even though it was toggled off when the new session was started
Comment 1 Harald Sitter 2018-02-07 12:26:17 UTC
As it turns out this is only a problem with QEMU's cirrus VGA, or more to the point it doesn't happen with QEMU's qxl VGA :S
Not quite sure what to make of it
Comment 2 Nate Graham 2020-01-12 23:25:51 UTC
How bizarre. Is there anything actionable here?
Comment 3 Harald Sitter 2020-01-13 10:16:59 UTC
I'd be fine with closing this worksforme if nobody has a guess what's wrong. Cirrus is no longer used by us, so assuming that really was the only scenario where the bug happens it hardly matters anymore.
Comment 4 Nate Graham 2020-01-13 14:12:33 UTC
Let's do that for everyone's sanity, yeah. :)