Bug 1893392 - When I log out, I don't get a login screen
Summary: When I log out, I don't get a login screen
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: sddm
Version: 33
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: X/OpenGL Maintenance List
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-10-31 01:09 UTC by Tom Horsley
Modified: 2021-01-30 18:26 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2021-01-30 18:26:53 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Tom Horsley 2020-10-31 01:09:23 UTC
Description of problem:

No clue if x11 is the right component for this, but I am using X and not Wayland. Using sddm as my login manager and running a custom fvwm session (though I saw the same thing running Gnome on Xorg as well), when I log out, I should get a new login screen, instead the background image just sits there with nothing responding to any keys or mouse clicks.

I have to do a Ctrl-Alt-F2, login as root, and systemctl restart sddm to get a new login.

Seems like this only happens the first time I try to logout after a reboot. If I try to reproduce it by logging out again after doing the sddm restart, I do get a new login screen.


Version-Release number of selected component (if applicable):
xorg-x11-server-Xorg-1.20.9-1.fc33.x86_64
sddm-0.18.1-8.fc33.x86_64
fvwm-2.6.9-4.fc33.x86_64


How reproducible:
100% the first time I logout following a reboot.

Steps to Reproduce:
1.see above
2.
3.

Actual results:
No new login prompt

Expected results:
New login prompt

Additional info:

Comment 1 Tom Horsley 2020-10-31 01:32:34 UTC
Changing component to sddm since I just tried switching to gdm, and I have no problem logging out and back in even right after a reboot.

Comment 2 Tom Horsley 2021-01-30 18:26:53 UTC
Just tried this again with the new sddm-0.19.0-5.fc33.x86_64 and the problem no longer shows up. I guess I'll close this bug.


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