Bug 1214457 - Switch to tty1 after login with sddm
Summary: Switch to tty1 after login with sddm
Status: NEW
Alias: None
Product: openSUSE Distribution
Classification: openSUSE
Component: KDE Workspace (Plasma) (show other bugs)
Version: Leap 15.5
Hardware: Other Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: E-Mail List
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-08-22 07:35 UTC by Luigi Baldoni
Modified: 2023-11-26 18:50 UTC (History)
3 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments
lastlog for console after login (25.90 KB, text/plain)
2023-08-22 07:35 UTC, Luigi Baldoni
Details
sddm logs with and without plymouth (780 bytes, application/gzip)
2023-08-29 07:41 UTC, Luigi Baldoni
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Luigi Baldoni 2023-08-22 07:35:55 UTC
Created attachment 868932 [details]
lastlog for console after login

This is an intermittent problem which I think I've started having with 15.5.
I use a plasma/wayland session and about once in 3 cold boots, after entering my credentials in sddm, instead of a graphical desktop I'm shown a console.
I normally log in and restart display-manager at that point (haven't tried loginctl yet, but I see the sddm gui still up, albeit ghosted).

See attached lastlog snippet.
Comment 1 Stefan Dirsch 2023-08-26 13:03:48 UTC
Not sure what happens here. @Plasma team: Could you investigate? Thanks!
Comment 2 Fabian Vogt 2023-08-26 17:57:21 UTC
Is there anything in ~/.local/share/sddm/wayland-session.log?

I have the suspicion this is a race condition very similar to the issues with autologin (bug 1200436). I'm surprised that tty1 is free according to VT_OPENQRY, there should be a getty fairly early on.

Do you use plymouth? If yes, does the issue still appear with "plymouth.enable=0" on the kernel cmdline?
Comment 3 Luigi Baldoni 2023-08-29 07:41:27 UTC
Created attachment 869072 [details]
sddm logs with and without plymouth

> Is there anything in ~/.local/share/sddm/wayland-session.log?

See attachment.

> Do you use plymouth? If yes, does the issue still appear with "plymouth.enable=0" on the kernel cmdline?

Alas it doesn't appear to make a difference.