Bug 2097255 - Users cannot log out from the Plasma session properly.
Summary: Users cannot log out from the Plasma session properly.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: sddm
Version: 37
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Martin Bříza
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-06-15 09:49 UTC by Lukas Ruzicka
Modified: 2023-02-23 11:02 UTC (History)
11 users (show)

Fixed In Version: sddm-0.19.0^git20230201.3ee57e9-2.fc37
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-02-07 01:54:41 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Lukas Ruzicka 2022-06-15 09:49:47 UTC
Description of problem:

When a user wants to log out from the KDE session, it always ends up on a virtual console and will never return to the sddm for further operations and in journalctl, you can see the following error: 

"Auth: sddm-helper exited with 3"

Version-Release number of selected component (if applicable):
sddm-0.19.0^git20220321.e67307e-2

How reproducible:
Always


Steps to Reproduce:
1. Log out from a KDE user session.

Actual results:

SDDM will crash / not be available after log out and the machine ends up on TTY2.


Expected results:

SDDM reappears for the user to proceed with further log in.


Additional info:

Comment 1 Lukas Ruzicka 2022-06-15 09:54:03 UTC
This happens both on Wayland and Xorg.

Comment 2 David Tonhofer 2022-07-14 13:50:42 UTC
As of yesterday, I didn't end up on the virtual console but on the sddm greeter screen, with all widgets disabled, including the password-entry. There is no way to go on from.
Getting out means switching to the console and rebooting (there may be a better way)

However, as of today, after the latest updated for Fedora 36, where 

- plasma packages have been upgraded from '5.25.2 / 1.fc36' to '5.25.3 / 1.fc36' 
- sddm-breeze changed: '5.25.2 / 1.fc36' ---> '5.25.3.1 / 1.fc36'
- sddm-kcm    changed: '5.25.2 / 1.fc36' ---> '5.25.3 / 1.fc36'

it's even worse as logging out just brings a black screen ... and that it's. 

Again, getting out means switching to the console and rebooting (there may be a better way).

Comment 3 Ben Cotton 2022-08-09 13:17:59 UTC
This bug appears to have been reported against 'rawhide' during the Fedora Linux 37 development cycle.
Changing version to 37.

Comment 4 nucleo 2022-10-10 10:09:51 UTC
I can log out with sddm-0.19.0^git20220321.e67307e-4.fc37 but with latest sddm-0.19.0^git20220921.21e965a-1.fc37 sddm-helper hangs and I can log out only after kill -9 sddm-helper.

Comment 5 nucleo 2022-11-09 17:14:13 UTC
Looks like bug gone after update
https://bodhi.fedoraproject.org/updates/FEDORA-2022-23a0a34ea5

Comment 6 nucleo 2022-11-29 21:13:35 UTC
sddm-helper hangs with plasma 5.26.3 F37

Comment 7 Stephane Travostino 2023-01-18 09:38:06 UTC
Still an issue, and possibly related to https://bugzilla.redhat.com/show_bug.cgi?id=2116525

Comment 8 Fedora Update System 2023-02-02 17:47:08 UTC
FEDORA-2023-1a365f606b has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2023-1a365f606b

Comment 9 Fedora Update System 2023-02-03 02:56:15 UTC
FEDORA-2023-1a365f606b has been pushed to the Fedora 37 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-1a365f606b`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-1a365f606b

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 10 Fedora Update System 2023-02-07 01:54:41 UTC
FEDORA-2023-1a365f606b has been pushed to the Fedora 37 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 11 nucleo 2023-02-23 11:02:16 UTC
sddm-helper hangs again
sddm-0.19.0^git20230201.3ee57e9-2.fc37.x86_64


Note You need to log in before you can comment on or make changes to this bug.