Created attachment 1947312 [details]
screencast from the issue on a VM
Description of problem:
At F38 KDE login screen, when trying to enable the virtual keyboard nothing happens (only the green dot disapears and the options sleep, restart, shut Down and Other show below the password box)
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.start F38 kde
2.try to enable the virtual keyboard
Virtual keyboard doesn't appears
The lower half of the screen turn to be a virtual keyboard where one can use mouse clicks to input password at the right field.
Proposed as a Blocker and Freeze Exception for 38-beta by Fedora user geraldosimiao using the blocker tracking app because:
As this criterion aplies: Shutting down, rebooting, logging in and logging out must work using standard console commands and the mechanisms offered (if any) by all release-blocking desktops.
If we offer a virtual keyboard button on the login screen, for people to input their password, then this must work properly.
+5 in https://pagure.io/fedora-qa/blocker-review/issue/1061 , marking accepted.
I've proposed workaround in https://src.fedoraproject.org/rpms/sddm/pull-request/7# (revert to X11 sddm and verified the fix, scratch builds will be in the PR page in a bit).
Do we really need scratch builds? We've reverted to X11 umpteen times before, we should know how to do it by now. If that's what we're doing can we just get an official build?
Taking down the FE proposal as this is an AcceptedBlocker.
Discussed during the 2023-03-06 blocker review meeting: 
The decision to classify this bug as a "RejectedBlocker (Beta)" and an "AcceptedBlocker (Final)" was made as discussion on this bug brought up that the virtual keyboard *does* work in the case where no physical keyboard is connected, so there is only a problem when a physical keyboard is connected but the user cannot or does not want to use it. We agreed this is acceptable for Beta but should still block Final.
Created attachment 1952100 [details]
new screencast, with updated system, showing the strange behavior, with descriptions.
Created attachment 1952101 [details]
Is there any news on this, KDE folks? Do we have any plan besides 'just go back to running on X again'? This is a Final blocker and the Final freeze is in a couple of weeks, so it'd be good to see some movement. Thanks!
It's unlikely this is going to change upstream in a timely manner (afaik this is not as easy to "fix" as it might seem).
I personally don't consider this a bug. The virtual keyboard **works** and the "button" mentioned in this bug also works as intended: it does enable/disable the keyboard (see the green little ball). What it doesn't do is **bring up** the virtual keyboard.
The confusion now is only happening because in X11 works differently. That doesn't mean it's the *correct* way.
I am trying to find the criteria mentioned at https://bugzilla.redhat.com/show_bug.cgi?id=2174563#c1 but I cannot find it. I am checking: https://fedoraproject.org/wiki/Basic_Release_Criteria but do not see the wording used in the comment.
As I pointed at the matrix room, the criterion is this: https://fedoraproject.org/wiki/Fedora_38_Beta_Release_Criteria#Shutdown,_reboot,_login,_logout
It is a beta blocker criteron, and as stated here https://fedoraproject.org/wiki/Fedora_38_Final_Release_Criteria#Beta_criteria_met beta criteria must be met for final release.
I just see no point in having a button for "enable/disable" virtual keyboard that doesn't do nothing if you don't have touchscreen hardware. So its just a promise of something that isn't there? Confusing for the users that was using F37 with sddm-x11 with a virtualkeyboard that apears on the screen even if we use the mouse to click on it, just like we do on Fedora workstation with gdm on wayland.