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

[email protected] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[email protected]
             Status|RESOLVED                    |REOPENED
     Ever confirmed|0                           |1
         Resolution|NOT A BUG                   |---

--- Comment #2 from [email protected] ---
(In reply to Vlad Zahorodnii from comment #1)
> This looks like an AI generated bug report. We expect humans to report bug
> reports to other humans.

After an exchange with somebody on reddit
(https://www.reddit.com/r/linux/comments/1wn6hse/comment/pbf6unm/?force-legacy-sct=1)
who said this was a blocking accessibility issue for them as they absolutely
needed a custom OSK but couldn't even get into KDE with this bug I tried to
replicate it in bazzite KDE.

I found 2 issues:
1. No virtual keyboard button on initial Login.

When logging in there is no "virtual keyboard" button on the bottom left
corner.
Steps to replicate:

1. Have a machine with bazzite kde installed
2. Boot up the machine and reach the login screen
3. Look at the bottom left corner, there is no "virtual keyboard" button

2. Broken virtual keyboard button in lock-screen

Once you are already logged in and then lock your screen, you will get a
"virtual keyboard"-button in the bottom left.
Clicking it however will lead to nothing happening.

Steps to replicate:

1. Have a machine with bazzite kde installed
2. Login to your machine
3. Press super + L to lock the screen or however else you lock the screen on
your machine
4. Look at the bottom left corner, there is a "virtual keyboard" button
5. Click the button, nothing happens

Bazzite system info:
bazzite-nvidia-open:stable 
Linux 7.2.4-ogc3.1.fc44.x86_64

Therefore this is an existing, unresolved bug. Or rather, it's 2 bugs, though
maybe they're related.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to