Bug 2055627

Summary: KDE login screen: strange behaviour
Product: [Fedora] Fedora Reporter: Marián Konček <mkoncek>
Component: sddmAssignee: Rex Dieter <rdieter>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 36CC: aleixpol, jgrulich, kde-sig, me, m, nate, ngompa13, pierluigi.fiorini, rdieter, travier
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-03-03 17:38:14 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Marián Konček 2022-02-17 12:03:04 UTC
I started off with a freshly instaalled Fedora KDE Live 34 and updated each release up to current rawhide (F37).
I noticed that after I updated from 35 to 36, the login screen was very weird.
1) The keyboard language layout in the login manager was reset to "af" (I assume because it is alphabetically first in the list). The actual layout was similar do English, I don't know if "af" is the same.
2) The "virtual keyboard" button does nothing
3) Attempting to change either the keyboard language layout or the window manager  session (X11 / Wayland) opens up a selestable menu bar in the top left corner of the screen and the rest of the screen starts flickering. Additionally, selecting a different keyboard layout ("sk" in my case) does not actually change the used layout.
4) After logging off of a started session I end up on the text virtual terminal (probably number 2). Pressing Ctrl + Alt + F1 switches to a black screen with only mouse visible.

This issue was noticed on F36 and also on the current rawhide (F37), restarting a few times did not change anything.

Comment 1 Timothée Ravier 2022-03-03 17:38:14 UTC
Thanks, likely a dup of 2054016

*** This bug has been marked as a duplicate of bug 2054016 ***