Bug 2059837

Summary:	Clicking on the login button in sddm on Wayland usually didn't log in to Plasma on Wayland in Fedora 36
Product:	[Fedora] Fedora	Reporter:	Matt Fagnani <matt.fagnani>
Component:	sddm	Assignee:	Martin Bříza <m>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	36	CC:	jgrulich, kde-sig, me, m, pierluigi.fiorini, rdieter, travier
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	---
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-04-25 17:22:43 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 Matt Fagnani 2022-03-02 07:24:50 UTC

Description of problem:

When I clicked on the login button labelled > to the right of the password box in sddm on Wayland with the correct password entered in a Fedora 36 KDE Plasma installation, sddm didn't log in to Plasma on Wayland most of the time. When I clicked on the login button in sddm on Wayland with an incorrect password entered, sddm usually didn't show an incorrect password error. However, the missing Sleep, Restart, Shut down, and Other options under the password box appeared for about a second when I clicked on the login button before disappearing. I reported the missing Sleep, Restart, Shut down, and Other options at https://bugzilla.redhat.com/show_bug.cgi?id=2058468

If I hit Enter with the correct password entered, sddm always logged in to Plasma on Wayland.

Version-Release number of selected component (if applicable):
sddm-0.19.0^git20220228.c257a40-2.fc36.x86_64
sddm-wayland-plasma-5.24.2-1.fc36.noarch
kwin-5.24.2-2.fc36.x86_64
qt5-qtbase-5.15.2-33.fc36.x86_64

How reproducible:
Clicking on the login button with the correct password didn't log in most of the time. Clicking on the login button with an incorrect password didn't show an error message on most tries.

Steps to Reproduce:
1. Boot a Fedora 36 KDE Plasma installation updated to 2022-3-1 with updates-testing enabled and sddm-0.19.0^git20220228.c257a40-2.fc36.x86_64 and sddm-wayland-plasma-5.24.2-1.fc36.noarch installed
2. Enter the correct password for a user in sddm on Wayland
3. Click on the login button labelled >
4. Enter an incorrect password for a user in sddm
5. Click on the login button labelled >

Actual results:
Clicking on the login button labelled > in sddm on Wayland usually didn't log in to Plasma on Wayland with a correct password or give an error message with an incorrect password.

Expected results:
Clicking on the login button labelled > in sddm would log in to Plasma on Wayland normally if the correct password was entered or give an error message if the password was incorrect.

Additional info:

Comment 1 Matt Fagnani 2022-03-08 16:10:17 UTC

Clicking the login button in sddm on Wayland with a correct password logged in to Plasma on Wayland each time using plasma-workspace-5.24.2-3.fc36 and sddm-0.19.0^git20220228.c257a40-3.fc36 and with an incorrect password showed Login failed. Thanks for the fix.

Comment 2 Ben Cotton 2023-04-25 16:54:41 UTC

This message is a reminder that Fedora Linux 36 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 36 on 2023-05-16.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '36'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 36 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 3 Matt Fagnani 2023-04-25 17:22:43 UTC

This problem was fixed as I mentioned in comment 1.