You are not logged in.
- Topics: Active | Unanswered
#1 2025-10-06 13:46:01
- Sidekick
- Member
- Registered: 2024-06-23
- Posts: 52
SDDM does not show login when no screen is switched on during boot
Hi,
this is a bit of a weird one: I usually have two screens connected to my PC, sometimes both are switched off when the PC shuts down, upon starting the PC I don't always switch a monitor on immediately and in those cases I'm 'greeted' by a cursor blinking on a black screen. I can then switch to an alternative TTY, login and then restart SDDM and I'm greeted by my normal login screen.
My question is then why does this happen and what can I do to make SDDM react to a screen being switched on at a later point in time? Both screens are connected through DisplayPort and I'm using KDE with Wayland.
The log:
[root@MAIN sidekick]# journalctl -b -1--unit session-c1.scope --unit sddm --no-host --output short-monotonic
[ 13.407087] systemd[1]: Started Simple Desktop Display Manager.
[ 13.454886] sddm[1176]: Initializing...
[ 13.457932] sddm[1176]: Starting...
[ 13.457999] sddm[1176]: Logind interface found
[ 13.458234] sddm[1176]: Adding new display...
[ 13.461953] sddm[1176]: Loaded empty theme configuration
[ 13.462059] sddm[1176]: Using VT 1
[ 13.462066] sddm[1176]: Display server started.
[ 13.462080] sddm[1176]: Socket server starting...
[ 13.462196] sddm[1176]: Socket server started.
[ 13.463084] sddm[1176]: Loading theme configuration from "/usr/share/sddm/themes/breeze/theme.conf"
[ 13.464081] sddm[1176]: Greeter starting...
[ 13.472929] sddm-helper[1190]: [PAM] Starting...
[ 13.472936] sddm-helper[1190]: [PAM] Authenticating...
[ 13.472985] sddm-helper[1190]: [PAM] returning.
[ 13.473492] sddm-helper[1190]: pam_unix(sddm-greeter:session): session opened for user sddm(uid=991) by (uid=0)
[ 13.701843] systemd[1]: Started Session c1 of User sddm.
[ 13.702787] sddm-helper[1217]: Jumping to VT 1
[ 13.703761] sddm-helper[1217]: VT mode fixed
[ 13.704786] sddm[1176]: Greeter session started successfully
[ 13.707060] sddm-helper-start-wayland[1217]: Starting Wayland process "kwin_wayland --drm --no-lockscreen --no-global-sho>
[ 13.707328] sddm-helper-start-wayland[1217]: started succesfully "kwin_wayland --drm --no-lockscreen --no-global-shortcut>
[ 13.848615] sddm-helper-start-wayland[1217]: Directory "/run/user/991" has changed, checking for Wayland socket
[ 13.850283] sddm-helper-start-wayland[1217]: Found Wayland socket "/run/user/991/wayland-0"
[ 13.855052] sddm-helper-start-wayland[1217]: "Accepting client connections on sockets: QList(\"wayland-0\")\n"
[ 13.860964] sddm-greeter-qt6[1222]: High-DPI autoscaling Enabled
[ 14.313378] sddm-helper-start-wayland[1217]: "\"applications.menu\" not found in QList(\"/etc/xdg/menus\")\n"
[ 14.662247] sddm-greeter-qt6[1222]: Reading from "/usr/local/share/wayland-sessions/plasma.desktop"
[ 14.662256] sddm-greeter-qt6[1222]: Reading from "/usr/share/wayland-sessions/plasma.desktop"
[ 14.662766] sddm-greeter-qt6[1222]: Loading theme configuration from "/usr/share/sddm/themes/breeze/theme.conf"
[ 14.670612] sddm-greeter-qt6[1222]: Connected to the daemon.
[ 14.670685] sddm[1176]: Message received from greeter: Connect
[ 14.699489] sddm-greeter-qt6[1222]: Loading file:///usr/share/sddm/themes/breeze/Main.qml...
[ 14.962350] sddm-greeter-qt6[1222]: Adding view for "DP-1" QRect(0,0 2048x1152)
[ 14.963637] sddm-greeter-qt6[1222]: Message received from daemon: Capabilities
[ 14.963930] sddm-greeter-qt6[1222]: Message received from daemon: HostName
[ 20.369153] sddm-greeter-qt6[1222]: There are no outputs - creating placeholder screen
[ 20.370211] sddm-greeter-qt6[1222]: Loading file:///usr/share/sddm/themes/breeze/Main.qml...
[ 20.525819] sddm-greeter-qt6[1222]: Adding view for "" QRect(0,0 0x0)
[ 20.682171] sddm-helper-start-wayland[1217]: wayland greeter finished 0 QProcess::NormalExit
[ 20.682179] sddm-helper-start-wayland[1217]: quitting helper-start-wayland
[ 20.682183] sddm-helper-start-wayland[1217]: Stopping... "kwin_wayland"
[ 20.701791] sddm-helper-start-wayland[1217]: wayland compositor finished 15 QProcess::NormalExit
[ 20.701798] sddm-helper-start-wayland[1217]: quitting helper-start-wayland
[ 20.702155] sddm-helper[1190]: [PAM] Closing session
[ 20.702185] sddm-helper[1190]: pam_unix(sddm-greeter:session): session closed for user sddm
[ 20.839770] sddm-helper[1190]: [PAM] Ended.
[ 20.840543] sddm[1176]: Auth: sddm-helper exited successfully
[ 20.840550] sddm[1176]: Greeter stopped. SDDM::Auth::HELPER_SUCCESS
[ 20.840560] systemd[1]: session-c1.scope: Deactivated successfully.
[ 20.840701] systemd[1]: session-c1.scope: Consumed 1.246s CPU time, 421M memory peak.
<screen is switched on somewhere here, login to TTY 2 and systemctl restart sddm>
[ 76.601731] sddm[1176]: Signal received: SIGTERM
[ 76.601797] systemd[1]: Stopping Simple Desktop Display Manager...
[ 76.601844] sddm[1176]: Socket server stopping...
[ 76.601848] sddm[1176]: Socket server stopped.
[ 76.602937] systemd[1]: sddm.service: Deactivated successfully.
[ 76.603098] systemd[1]: Stopped Simple Desktop Display Manager.
[ 76.603810] systemd[1]: Started Simple Desktop Display Manager.
[ 76.634556] sddm[1550]: Initializing...
[ 76.635840] sddm[1550]: Starting...
[ 76.635881] sddm[1550]: Logind interface found
[ 76.636091] sddm[1550]: Adding new display...
[ 76.636184] sddm[1550]: Loaded empty theme configuration
[ 76.636408] sddm[1550]: Using VT 1
[ 76.636413] sddm[1550]: Display server started.
[ 76.636427] sddm[1550]: Socket server starting...
[ 76.636539] sddm[1550]: Socket server started.
[ 76.636608] sddm[1550]: Loading theme configuration from "/usr/share/sddm/themes/breeze/theme.conf"
[ 76.636708] sddm[1550]: Greeter starting...
[ 76.642401] sddm-helper[1557]: [PAM] Starting...
[ 76.642407] sddm-helper[1557]: [PAM] Authenticating...
[ 76.642582] sddm-helper[1557]: pam_unix(sddm-greeter:session): session opened for user sddm(uid=991) by (uid=0)
[ 76.642456] sddm-helper[1557]: [PAM] returning.
[ 76.838342] sddm[1550]: Greeter session started successfully
[ 77.271287] sddm[1550]: Message received from greeter: Connect
[ 85.738251] sddm[1550]: Message received from greeter: Login
[ 85.738265] sddm[1550]: Reading from "/usr/share/wayland-sessions/plasma.desktop"
[ 85.739046] sddm[1550]: Session "/usr/share/wayland-sessions/plasma.desktop" selected, command: "/usr/lib/plasma-dbus-run>
[ 85.751839] sddm-helper[1763]: [PAM] Starting...
[ 85.751848] sddm-helper[1763]: [PAM] Authenticating...
[ 85.755793] sddm-helper[1763]: [PAM] Preparing to converse...
[ 85.755801] sddm-helper[1763]: [PAM] Conversation with 1 messages
[ 85.758889] sddm-helper[1763]: gkr-pam: unable to locate daemon control file
[ 85.758896] sddm-helper[1763]: gkr-pam: stashed password to try later in open session
[ 85.758903] sddm-helper[1763]: pam_kwallet5(sddm:auth): pam_kwallet5: pam_sm_authenticate
[ 85.758994] sddm-helper[1763]: [PAM] returning.
[ 85.760135] sddm[1550]: Authentication for user "sidekick" successful
[ 85.760241] sddm-helper[1763]: pam_kwallet5(sddm:setcred): pam_kwallet5: pam_sm_setcred
[ 85.760438] sddm-helper[1763]: pam_unix(sddm:session): session opened for user sidekick(uid=1000) by sidekickuid=0)
[ 85.809972] sddm-helper[1763]: gkr-pam: unlocked login keyring
[ 85.809980] sddm-helper[1763]: pam_kwallet5(sddm:session): pam_kwallet5: pam_sm_open_session
[ 85.831254] sddm-helper[1763]: Starting Wayland user session: "/usr/share/sddm/scripts/wayland-session" "/usr/lib/plasma->
[ 85.834973] sddm[1550]: Session started true
[ 85.923211] sddm[1550]: Auth: sddm-helper exited successfully
[ 85.923219] sddm[1550]: Greeter stopped. SDDM::Auth::HELPER_SUCCESSFor reference, this is what it looks like when one of the screens is switched on from the start:
[ 12.650224] systemd[1]: Started Simple Desktop Display Manager.
[ 12.698380] sddm[1179]: Initializing...
[ 12.701470] sddm[1179]: Starting...
[ 12.701516] sddm[1179]: Logind interface found
[ 12.701728] sddm[1179]: Adding new display...
[ 12.705509] sddm[1179]: Loaded empty theme configuration
[ 12.705634] sddm[1179]: Using VT 1
[ 12.705641] sddm[1179]: Display server started.
[ 12.705655] sddm[1179]: Socket server starting...
[ 12.705754] sddm[1179]: Socket server started.
[ 12.706708] sddm[1179]: Loading theme configuration from "/usr/share/sddm/themes/breeze/theme.conf"
[ 12.707644] sddm[1179]: Greeter starting...
[ 12.716505] sddm-helper[1191]: [PAM] Starting...
[ 12.716511] sddm-helper[1191]: [PAM] Authenticating...
[ 12.716559] sddm-helper[1191]: [PAM] returning.
[ 12.717048] sddm-helper[1191]: pam_unix(sddm-greeter:session): session opened for user sddm(uid=991) by (uid=0)
[ 12.923653] systemd[1]: Started Session c1 of User sddm.
[ 12.924495] sddm-helper[1219]: Jumping to VT 1
[ 12.925460] sddm-helper[1219]: VT mode fixed
[ 12.926674] sddm[1179]: Greeter session started successfully
[ 12.928926] sddm-helper-start-wayland[1219]: Starting Wayland process "kwin_wayland --drm --no-lockscreen --no-global-sho>
[ 12.929165] sddm-helper-start-wayland[1219]: started succesfully "kwin_wayland --drm --no-lockscreen --no-global-shortcut>
[ 13.070093] sddm-helper-start-wayland[1219]: Directory "/run/user/991" has changed, checking for Wayland socket
[ 13.071781] sddm-helper-start-wayland[1219]: Found Wayland socket "/run/user/991/wayland-0"
[ 13.072035] sddm-helper-start-wayland[1219]: "Accepting client connections on sockets: QList(\"wayland-0\")\n"
[ 13.081914] sddm-greeter-qt6[1225]: High-DPI autoscaling Enabled
[ 13.839210] sddm-greeter-qt6[1225]: Reading from "/usr/local/share/wayland-sessions/plasma.desktop"
[ 13.839219] sddm-greeter-qt6[1225]: Reading from "/usr/share/wayland-sessions/plasma.desktop"
[ 13.839721] sddm-greeter-qt6[1225]: Loading theme configuration from "/usr/share/sddm/themes/breeze/theme.conf"
[ 13.847457] sddm-greeter-qt6[1225]: Connected to the daemon.
[ 13.847528] sddm[1179]: Message received from greeter: Connect
[ 13.875381] sddm-greeter-qt6[1225]: Loading file:///usr/share/sddm/themes/breeze/Main.qml...
[ 14.140489] sddm-greeter-qt6[1225]: Adding view for "DP-1" QRect(0,0 2048x1152)
[ 14.141677] sddm-greeter-qt6[1225]: Message received from daemon: Capabilities
[ 14.141920] sddm-greeter-qt6[1225]: Message received from daemon: HostName
[ 23.503679] sddm-greeter-qt6[1225]: file:///usr/share/sddm/themes/breeze/Main.qml:232:17 Parameter "username" is not decl>
[ 23.503696] sddm-greeter-qt6[1225]: Reading from "/usr/share/wayland-sessions/plasma.desktop"
[ 23.504027] sddm[1179]: Message received from greeter: Login
[ 23.504042] sddm[1179]: Reading from "/usr/share/wayland-sessions/plasma.desktop"
[ 23.504553] sddm[1179]: Session "/usr/share/wayland-sessions/plasma.desktop" selected, command: "/usr/lib/plasma-dbus-run>
[ 23.518520] sddm-helper[1346]: [PAM] Starting...
[ 23.518527] sddm-helper[1346]: [PAM] Authenticating...
[ 23.522761] sddm-helper[1346]: [PAM] Preparing to converse...
[ 23.522768] sddm-helper[1346]: [PAM] Conversation with 1 messages
[ 23.525855] sddm-helper[1346]: gkr-pam: unable to locate daemon control file
[ 23.525859] sddm-helper[1346]: gkr-pam: stashed password to try later in open session
[ 23.525862] sddm-helper[1346]: pam_kwallet5(sddm:auth): pam_kwallet5: pam_sm_authenticate
[ 23.525915] sddm-helper[1346]: [PAM] returning.
[ 23.526950] sddm[1179]: Authentication for user "sidekick" successful
[ 23.527008] sddm-greeter-qt6[1225]: Message received from daemon: LoginSucceeded
[ 23.527051] sddm-helper[1346]: pam_kwallet5(sddm:setcred): pam_kwallet5: pam_sm_setcred
[ 23.527238] sddm-helper[1346]: pam_unix(sddm:session): session opened for user sidekick(uid=1000) by sidekick(uid=0)
[ 23.653356] sddm-helper-start-wayland[1219]: wayland greeter finished 0 QProcess::NormalExit
[ 23.653363] sddm-helper-start-wayland[1219]: quitting helper-start-wayland
[ 23.653368] sddm-helper-start-wayland[1219]: Stopping... "kwin_wayland"
[ 23.666104] sddm-helper-start-wayland[1219]: "kwin_scene_opengl: Could not delete render time query because no context is>
[ 23.688009] sddm-helper-start-wayland[1219]: wayland compositor finished 15 QProcess::NormalExit
[ 23.688018] sddm-helper-start-wayland[1219]: quitting helper-start-wayland
[ 23.688424] sddm-helper[1191]: [PAM] Closing session
[ 23.688453] sddm-helper[1191]: pam_unix(sddm-greeter:session): session closed for user sddm
[ 23.987338] sddm-helper[1191]: [PAM] Ended.
[ 23.988071] sddm[1179]: Auth: sddm-helper exited successfully
[ 23.988074] systemd[1]: session-c1.scope: Deactivated successfully.
[ 23.988079] sddm[1179]: Greeter stopped. SDDM::Auth::HELPER_SUCCESS
[ 23.988234] systemd[1]: session-c1.scope: Consumed 990ms CPU time, 359.4M memory peak.
[ 24.030984] sddm-helper[1346]: gkr-pam: unlocked login keyring
[ 24.030996] sddm-helper[1346]: pam_kwallet5(sddm:session): pam_kwallet5: pam_sm_open_session
[ 24.052120] sddm-helper[1346]: Starting Wayland user session: "/usr/share/sddm/scripts/wayland-session" "/usr/lib/plasma->
[ 24.053929] sddm[1179]: Session started trueLast edited by Sidekick (2025-10-09 18:57:16)
Offline
#2 2025-10-08 13:57:30
- Wozzeck56
- Member
- Registered: 2025-07-31
- Posts: 3
Re: SDDM does not show login when no screen is switched on during boot
I don't know what is your problem, but personally I don't encounter such issue.
I have a second monitor I can swith on off whenever I want, and immediately SDDM is duplicating the login screen on the second monitor.
Anyway, starting with plasma 6.5.0 (around october 20th), SDDM won't be no more the default login manager.
KDE team showed some unsatisfaction regarding SDDM, so they will ressurrect "KDM" (the exact name... I don't know for this moment)
SDDM being designed as an "agnostic" login manager (contrary to GDM which is tied to Gnome Desktop), there are many drawbacks.
KDE Team promises a much more integrated, flexible login manager, with the return of virtual keyboard broken since many months now...
I guess the new "KDM" could solve in the row many issue including yours.
Don't forget to do the migration to the new login manager at the given date.
Last edited by Wozzeck56 (2025-10-08 13:58:40)
Offline
#3 2025-10-08 15:05:19
- seth
- Member
- From: Don't DM me only for attention
- Registered: 2012-09-03
- Posts: 69,070
Re: SDDM does not show login when no screen is switched on during boot
Please use [code][/code] tags, not "quote" tags. Edit your post in this regard.
Or rather please post your complete system journal for such boot:
sudo journalctl -b | curl -F 'file=@-' 0x0.stThere's a chance this is actually unrelated to the monitor power condition but an overall race condition: https://bbs.archlinux.org/viewtopic.php … 8#p2256488
Edit:
[ 14.962350] sddm-greeter-qt6[1222]: Adding view for "DP-1" QRect(0,0 2048x1152)
[ 14.963637] sddm-greeter-qt6[1222]: Message received from daemon: Capabilities
[ 14.963930] sddm-greeter-qt6[1222]: Message received from daemon: HostName
[ 20.369153] sddm-greeter-qt6[1222]: There are no outputs - creating placeholder screen
[ 20.370211] sddm-greeter-qt6[1222]: Loading file:///usr/share/sddm/themes/breeze/Main.qml...
[ 20.525819] sddm-greeter-qt6[1222]: Adding view for "" QRect(0,0 0x0)Depending on what actually happens you might have to https://wiki.archlinux.org/title/Kernel … s_and_EDID
Last edited by seth (2025-10-08 15:06:58)
Online
#4 2025-10-10 15:32:09
- Sidekick
- Member
- Registered: 2024-06-23
- Posts: 52
Re: SDDM does not show login when no screen is switched on during boot
I don't know what is your problem, but personally I don't encounter such issue.
I have a second monitor I can swith on off whenever I want, and immediately SDDM is duplicating the login screen on the second monitor.
Start your PC with all connected screens switched off, wait a sufficient amount of time until the system should have reached the login screen, then switch on any of your screens. In my case I see a black screen with a blinking, white cursor and that's it. I thought I had described the issue well enough but I guess I rambled too much.
Please use tags, not "quote" tags. Edit your post in this regard.
done.
There's a chance this is actually unrelated to the monitor power condition but an overall race condition
ah, I have an AMD GPU, no Nvidia here and I'm also on Wayland. Seems like what is discussed in that thread is exclusive to Nvidia or X11?
Depending on what actually happens you might have to
yeah the resolution does look weird, even when I switch that screen on while booting it lists the same resolution in the log. The second screen has the correct resolution listed, when it is switched on. Also if neither screen is switched on, should there then not be a log entry for 'DP-1'?
That is the EDID output for the screen attached to DP-1. Note that the resolution of 2048x1152, which is mentioned in both logs, is not part of the EDID information.
# card1-DP-1 #######################
Block 0, Base EDID:
EDID Structure Version & Revision: 1.4
Vendor & Product Identification:
Manufacturer: BNQ
Model: 32581
Serial Number: 21573 (0x00005445)
Made in: week 24 of 2017
Basic Display Parameters & Features:
Digital display
Bits per primary color channel: 8
DisplayPort interface
Maximum image size: 60 cm x 34 cm
Gamma: 2.20
DPMS levels: Off
Supported color formats: RGB 4:4:4, YCrCb 4:4:4, YCrCb 4:2:2
Default (sRGB) color space is primary color space
First detailed timing includes the native pixel format and preferred refresh rate
Display supports continuous frequencies
Color Characteristics:
Red : 0.6494, 0.3378
Green: 0.3125, 0.6259
Blue : 0.1494, 0.0517
White: 0.3125, 0.3281
Established Timings I & II:
IBM : 720x400 70.081663 Hz 9:5 31.467 kHz 28.320000 MHz
DMT 0x04: 640x480 59.940476 Hz 4:3 31.469 kHz 25.175000 MHz
DMT 0x06: 640x480 75.000000 Hz 4:3 37.500 kHz 31.500000 MHz
DMT 0x09: 800x600 60.316541 Hz 4:3 37.879 kHz 40.000000 MHz
DMT 0x0b: 800x600 75.000000 Hz 4:3 46.875 kHz 49.500000 MHz
Apple : 832x624 74.551266 Hz 4:3 49.726 kHz 57.284000 MHz
DMT 0x10: 1024x768 60.003840 Hz 4:3 48.363 kHz 65.000000 MHz
DMT 0x12: 1024x768 75.028582 Hz 4:3 60.023 kHz 78.750000 MHz
DMT 0x24: 1280x1024 75.024675 Hz 5:4 79.976 kHz 135.000000 MHz
Apple : 1152x870 75.061550 Hz 192:145 68.681 kHz 100.000000 MHz
Standard Timings:
DMT 0x52: 1920x1080 60.000000 Hz 16:9 67.500 kHz 148.500000 MHz
DMT 0x55: 1280x720 60.000000 Hz 16:9 45.000 kHz 74.250000 MHz
DMT 0x1c: 1280x800 59.810326 Hz 16:10 49.702 kHz 83.500000 MHz
DMT 0x23: 1280x1024 60.019740 Hz 5:4 63.981 kHz 108.000000 MHz
DMT 0x53: 1600x900 60.000000 Hz 16:9 60.000 kHz 108.000000 MHz (RB)
DMT 0x3a: 1680x1050 59.954250 Hz 16:10 65.290 kHz 146.250000 MHz
GTF : 1920x1080 119.999987 Hz 16:9 138.840 kHz 368.759000 MHz
Detailed Timing Descriptors:
DTD 1: 2560x1440 59.950550 Hz 16:9 88.787 kHz 241.500000 MHz (598 mm x 336 mm)
Hfront 48 Hsync 32 Hback 80 Hpol P
Vfront 3 Vsync 5 Vback 33 Vpol N
Display Product Serial Number: 'M6H02186SL0'
Display Range Limits:
Monitor ranges (Range Limits Only): 40-144 Hz V, 222-222 kHz H, max dotclock 600 MHz
Display Product Name: 'ZOWIE XL LCD'
Extension blocks: 1
Checksum: 0x9f
----------------
Block 1, CTA-861 Extension Block:
Revision: 3
Underscans IT Video Formats by default
Basic audio support
Supports YCbCr 4:4:4
Supports YCbCr 4:2:2
Native detailed modes: 1
Video Data Block:
VIC 1: 640x480 59.940476 Hz 4:3 31.469 kHz 25.175000 MHz
VIC 2: 720x480 59.940060 Hz 4:3 31.469 kHz 27.000000 MHz
VIC 3: 720x480 59.940060 Hz 16:9 31.469 kHz 27.000000 MHz
VIC 4: 1280x720 60.000000 Hz 16:9 45.000 kHz 74.250000 MHz
VIC 5: 1920x1080i 60.000000 Hz 16:9 33.750 kHz 74.250000 MHz
VIC 16: 1920x1080 60.000000 Hz 16:9 67.500 kHz 148.500000 MHz (native)
VIC 17: 720x576 50.000000 Hz 4:3 31.250 kHz 27.000000 MHz
VIC 18: 720x576 50.000000 Hz 16:9 31.250 kHz 27.000000 MHz
VIC 19: 1280x720 50.000000 Hz 16:9 37.500 kHz 74.250000 MHz
VIC 20: 1920x1080i 50.000000 Hz 16:9 28.125 kHz 74.250000 MHz
VIC 31: 1920x1080 50.000000 Hz 16:9 56.250 kHz 148.500000 MHz
Audio Data Block:
Linear PCM:
Max channels: 2
Supported sample rates (kHz): 48 44.1 32
Supported sample sizes (bits): 24 20 16
Speaker Allocation Data Block:
FL/FR - Front Left/Right
Detailed Timing Descriptors:
DTD 2: 2560x1440 119.880775 Hz 16:9 182.818 kHz 482.640000 MHz (598 mm x 336 mm)
Hfront 8 Hsync 32 Hback 40 Hpol P
Vfront 7 Vsync 8 Vback 70 Vpol N
DTD 3: 2560x1440 144.002728 Hz 16:9 208.660 kHz 538.760000 MHz (598 mm x 336 mm)
Hfront 4 Hsync 16 Hback 2 Hpol P
Vfront 1 Vsync 1 Vback 7 Vpol P
DTD 4: 1920x1080 143.850475 Hz 16:9 166.435 kHz 332.870000 MHz (598 mm x 336 mm)
Hfront 8 Hsync 32 Hback 40 Hpol P
Vfront 63 Vsync 8 Vback 6 Vpol N
DTD 5: 2560x1440 99.897150 Hz 16:9 150.845 kHz 398.230000 MHz (598 mm x 336 mm)
Hfront 8 Hsync 32 Hback 40 Hpol P
Vfront 56 Vsync 8 Vback 6 Vpol N
DTD 6: 2560x1440 143.855928 Hz 16:9 221.970 kHz 586.000000 MHz (598 mm x 336 mm)
Hfront 8 Hsync 32 Hback 40 Hpol P
Vfront 25 Vsync 8 Vback 70 Vpol N
Checksum: 0xa8
----------------
EDID conformity: PASSLast edited by Sidekick (2025-10-10 15:33:53)
Offline
#5 2025-10-10 19:43:04
- seth
- Member
- From: Don't DM me only for attention
- Registered: 2012-09-03
- Posts: 69,070
Re: SDDM does not show login when no screen is switched on during boot
Seems like what is discussed in that thread is exclusive to Nvidia or X11?
Possibly nvidia but the problem would really just (still) be that the DM launches before the GPU is properly initialized
Also if neither screen is switched on, should there then not be a log entry for 'DP-1'?
The outputs don't necessarily have to be fully powered to register - the output seems scaled to 80%
Was the EDID drawn w/ the output turned off?
But then SDDM determines that there're no outputs and creates a 0x0 dummy screen and never switches away from that.
https://bbs.archlinux.org/viewtopic.php … 2#p2265422
Try to force-enable the output: https://www.kernel.org/doc/Documentation/fb/modedb.rst
Online
#6 2025-10-10 22:42:14
- Sidekick
- Member
- Registered: 2024-06-23
- Posts: 52
Re: SDDM does not show login when no screen is switched on during boot
Possibly nvidia but the problem would really just (still) be that the DM launches before the GPU is properly initialized
ah, I could see that happening if the GPU doesn't have screens connected that are turned on, sure. Will check if that is happening.
The outputs don't necessarily have to be fully powered to register - the output seems scaled to 80%
Was the EDID drawn w/ the output turned off?
no, both screens were active I just only posted the DP-1 output. If only DP-1 is switched on, it is also the only one being displayed.
And just now I think you solved this, if I switch off DP-1, which is also my primary screen - nothing changes. The secondary screen stays the secondary screen, I can move the mouse 'out of bounds' on the side where the screen connected via DP-1 is connected and windows/applications that were open on that screen are not moved to the screen connected through DP-3. The EDID information also does not change. What is even more curious is that if I switch the screen back on, for a split second KDE displays a "screen disconnected" notification, my secondary screen becomes my primary screen, all opened apps appear on the DP-3 screen and then the logo on the DP-1 screen disappears and everything moves back over to the DP-1 screen. It's like for some reason KDE does not notice the screen being switched off.
Having
journalctl -frunning showed no output when switching off the monitor connected via DP-1. When switching it back on this appeared
[ 6107.906405] kmix[2411]: org.kde.kmix: No such icon "audio-card-analog"
[ 6107.906625] kmix[2411]: org.kde.kmix: No such icon "audio-card-analog"
[ 6107.906826] kmix[2411]: org.kde.kmix: No such icon "audio-card-analog"
[ 6107.907483] kmix[2411]: adding 4 mixers
[ 6107.907490] kmix[2411]: mixer "PulseAudio::Playback_Devices:1" "Wiedergabegeräte"
[ 6107.907496] kmix[2411]: PulseAudio adding 2 devices
[ 6107.907501] kmix[2411]: adding "alsa_output.usb-SteelSeries_Arctis_Nova_3-00.iec958-stereo" "Arctis Nova 3 Digitales Stereo (IEC958)"
[ 6107.907512] kmix[2411]: adding "alsa_output.pci-0000_19_00.6.iec958-stereo" "Family 17h/19h/1ah HD Audio Controller Digitales Stereo (IEC958)"
[ 6107.907518] kmix[2411]: mixer "PulseAudio::Capture_Devices:1" "Aufnahmegeräte"
[ 6107.907523] kmix[2411]: PulseAudio adding 1 devices
[ 6107.907528] kmix[2411]: adding "alsa_input.usb-SteelSeries_Arctis_Nova_3-00.iec958-stereo" "Arctis Nova 3 Digitales Stereo (IEC958)"
[ 6107.907540] kmix[2411]: mixer "PulseAudio::Playback_Streams:1" "Wiedergabestreams"
[ 6107.907544] kmix[2411]: PulseAudio adding 0 devices
[ 6107.907549] kmix[2411]: mixer "PulseAudio::Capture_Streams:1" "Aufnahmestreams"
[ 6107.907553] kmix[2411]: PulseAudio adding 0 devices
[ 6107.907607] kmix[2411]: org.kde.kmix: No such icon "audio-card-analog"
[ 6107.907859] kmix[2411]: org.kde.kmix: No such icon "audio-card-analog"
[ 6107.908179] kmix[2411]: org.kde.kmix: No such icon "audio-card-analog"
[ 6107.908426] kmix[2411]: org.kde.kmix: No such icon "audio-card-analog"
[ 6107.908678] kmix[2411]: org.kde.kmix: No such icon "audio-card-analog"
[ 6107.910425] kmix[2411]: org.kde.kmix: No such icon "audio-card-analog"
[ 6107.910600] kmix[2411]: org.kde.kmix: No such icon "audio-card-analog"
[ 6107.910793] kmix[2411]: org.kde.kmix: No such icon "audio-card-analog"
[ 6107.910948] kmix[2411]: org.kde.kmix: No such icon "audio-card-analog"
[ 6107.911547] kmix[2411]: adding 4 mixers
[ 6107.911553] kmix[2411]: mixer "PulseAudio::Playback_Devices:1" "Wiedergabegeräte"
[ 6107.911557] kmix[2411]: PulseAudio adding 3 devices
[ 6107.911560] kmix[2411]: adding "alsa_output.usb-SteelSeries_Arctis_Nova_3-00.iec958-stereo" "Arctis Nova 3 Digitales Stereo (IEC958)"
[ 6107.911568] kmix[2411]: adding "alsa_output.pci-0000_19_00.6.iec958-stereo" "Family 17h/19h/1ah HD Audio Controller Digitales Stereo (IEC958)"
[ 6107.911572] kmix[2411]: adding "alsa_output.pci-0000_03_00.1.hdmi-stereo-extra4" "Navi 21/23 HDMI/DP Audio Controller Digital Stereo (HDMI 5)"
[ 6107.911576] kmix[2411]: mixer "PulseAudio::Capture_Devices:1" "Aufnahmegeräte"
[ 6107.911579] kmix[2411]: PulseAudio adding 1 devices
[ 6107.911582] kmix[2411]: adding "alsa_input.usb-SteelSeries_Arctis_Nova_3-00.iec958-stereo" "Arctis Nova 3 Digitales Stereo (IEC958)"
[ 6107.911589] kmix[2411]: mixer "PulseAudio::Playback_Streams:1" "Wiedergabestreams"
[ 6107.911593] kmix[2411]: PulseAudio adding 0 devices
[ 6107.911595] kmix[2411]: mixer "PulseAudio::Capture_Streams:1" "Aufnahmestreams"
[ 6107.911600] kmix[2411]: PulseAudio adding 0 devices
[ 6107.911639] kmix[2411]: org.kde.kmix: No such icon "audio-card-analog"
[ 6107.911832] kmix[2411]: org.kde.kmix: No such icon "audio-card-analog"
[ 6107.912080] kmix[2411]: org.kde.kmix: No such icon "audio-card-analog"
[ 6107.912262] kmix[2411]: org.kde.kmix: No such icon "audio-card-analog"
[ 6107.912435] kmix[2411]: org.kde.kmix: No such icon "audio-card-analog"
[ 6107.912615] kmix[2411]: org.kde.kmix: No such icon "audio-card-analog"
[ 6107.953319] wireplumber[1400]: wp-event-dispatcher: <WpAsyncEventHook:0x55ffe33d6c90> failed: failed to activate item: Object activation aborted: proxy destroyed
[ 6107.955076] kded6[1654]: kf.notifications: Failed to notify "Created too many similar notifications in quick succession"
[ 6108.196805] org_kde_powerdevil[1784]: [ 13552] Removing connected display on bus 6
[ 6108.196814] org_kde_powerdevil[1784]: [ 13552] Emitting DDCA_Display_Status_Event[6072.347: DDCA_EVENT_DISPLAY_DISCONNECTED, card1-DP-1, dref: DDCA_Display_Ref[12], io_path:/dev/i2c-6, ddc working: false]
[ 6108.196817] org_kde_powerdevil[1784]: [ 13552] Starting 1 callback threads
[ 6108.196850] org_kde_powerdevil[1784]: [ 13552] libddcutil callback thread 0x7feff0021300 started
[ 6108.196852] org_kde_powerdevil[1784]: [ 13552] Started 1 event callback thread(s)
[ 6108.196868] org_kde_powerdevil[1784]: [ 13712] Invoking callback function 0x7ff019935050 for event DDCA_Display_Status_Event[6072.347: DDCA_EVENT_DISPLAY_DISCONNECTED, card1-DP-1, dref: DDCA_Display_Ref[12], io_path:/dev/i2c-6, ddc working: false] in this thread [ 13712]
[ 6108.196881] org_kde_powerdevil[1784]: [ 13712] Callback function 0x7ff019935050 for event DDCA_Display_Status_Event[6072.347: DDCA_EVENT_DISPLAY_DISCONNECTED, card1-DP-1, dref: DDCA_Display_Ref[12], io_path:/dev/i2c-6, ddc working: false] complete
[ 6108.614004] kwin_wayland[1503]: kwin_xwl: Could not find a matching X RandR CRTC/output to set as primary for KWin::DrmOutput(0x55ecca4d30f0, name="DP-1", geometry=QRect(0,0 2560x1440), scale=1)
[ 6108.619175] kwin_wayland[1503]: kwin_xwl: Could not find a matching X RandR CRTC/output to set as primary for KWin::DrmOutput(0x55ecca4d30f0, name="DP-1", geometry=QRect(0,0 2560x1440), scale=1)
[ 6108.714955] kded6[1654]: kf.notifications: Failed to notify "Created too many similar notifications in quick succession"
[ 6108.733039] kmix[2411]: org.kde.kmix: No such icon "audio-card-analog"
[ 6108.733256] kmix[2411]: org.kde.kmix: No such icon "audio-card-analog"
[ 6108.733456] kmix[2411]: org.kde.kmix: No such icon "audio-card-analog"
[ 6108.734267] kmix[2411]: adding 4 mixers
[ 6108.734274] kmix[2411]: mixer "PulseAudio::Playback_Devices:1" "Wiedergabegeräte"
[ 6108.734277] kmix[2411]: PulseAudio adding 2 devices
[ 6108.734282] kmix[2411]: adding "alsa_output.usb-SteelSeries_Arctis_Nova_3-00.iec958-stereo" "Arctis Nova 3 Digitales Stereo (IEC958)"
[ 6108.734289] kmix[2411]: adding "alsa_output.pci-0000_19_00.6.iec958-stereo" "Family 17h/19h/1ah HD Audio Controller Digitales Stereo (IEC958)"
[ 6108.734293] kmix[2411]: mixer "PulseAudio::Capture_Devices:1" "Aufnahmegeräte"
[ 6108.734297] kmix[2411]: PulseAudio adding 1 devices
[ 6108.734301] kmix[2411]: adding "alsa_input.usb-SteelSeries_Arctis_Nova_3-00.iec958-stereo" "Arctis Nova 3 Digitales Stereo (IEC958)"
[ 6108.734309] kmix[2411]: mixer "PulseAudio::Playback_Streams:1" "Wiedergabestreams"
[ 6108.734312] kmix[2411]: PulseAudio adding 0 devices
[ 6108.734316] kmix[2411]: mixer "PulseAudio::Capture_Streams:1" "Aufnahmestreams"
[ 6108.734319] kmix[2411]: PulseAudio adding 0 devices
[ 6108.734359] kmix[2411]: org.kde.kmix: No such icon "audio-card-analog"
[ 6108.734551] kmix[2411]: org.kde.kmix: No such icon "audio-card-analog"
[ 6108.734743] kmix[2411]: org.kde.kmix: No such icon "audio-card-analog"
[ 6108.734936] kmix[2411]: org.kde.kmix: No such icon "audio-card-analog"
[ 6108.735108] kmix[2411]: org.kde.kmix: No such icon "audio-card-analog"
[ 6108.742509] kmix[2411]: org.kde.kmix: No such icon "audio-card-analog"
[ 6108.742727] kmix[2411]: org.kde.kmix: No such icon "audio-card-analog"
[ 6108.742926] kmix[2411]: org.kde.kmix: No such icon "audio-card-analog"
[ 6108.743095] kmix[2411]: org.kde.kmix: No such icon "audio-card-analog"
[ 6108.743746] kmix[2411]: adding 4 mixers
[ 6108.743754] kmix[2411]: mixer "PulseAudio::Playback_Devices:1" "Wiedergabegeräte"
[ 6108.743761] kmix[2411]: PulseAudio adding 3 devices
[ 6108.743765] kmix[2411]: adding "alsa_output.usb-SteelSeries_Arctis_Nova_3-00.iec958-stereo" "Arctis Nova 3 Digitales Stereo (IEC958)"
[ 6108.743774] kmix[2411]: adding "alsa_output.pci-0000_19_00.6.iec958-stereo" "Family 17h/19h/1ah HD Audio Controller Digitales Stereo (IEC958)"
[ 6108.743778] kmix[2411]: adding "alsa_output.pci-0000_03_00.1.hdmi-stereo" "Navi 21/23 HDMI/DP Audio Controller Digitales Stereo (HDMI)"
[ 6108.743783] kmix[2411]: mixer "PulseAudio::Capture_Devices:1" "Aufnahmegeräte"
[ 6108.743788] kmix[2411]: PulseAudio adding 1 devices
[ 6108.743792] kmix[2411]: adding "alsa_input.usb-SteelSeries_Arctis_Nova_3-00.iec958-stereo" "Arctis Nova 3 Digitales Stereo (IEC958)"
[ 6108.743801] kmix[2411]: mixer "PulseAudio::Playback_Streams:1" "Wiedergabestreams"
[ 6108.743804] kmix[2411]: PulseAudio adding 0 devices
[ 6108.743808] kmix[2411]: mixer "PulseAudio::Capture_Streams:1" "Aufnahmestreams"
[ 6108.743810] kmix[2411]: PulseAudio adding 0 devices
[ 6108.743865] kmix[2411]: org.kde.kmix: No such icon "audio-card-analog"
[ 6108.744107] kmix[2411]: org.kde.kmix: No such icon "audio-card-analog"
[ 6108.744361] kmix[2411]: org.kde.kmix: No such icon "audio-card-analog"
[ 6108.744551] kmix[2411]: org.kde.kmix: No such icon "audio-card-analog"
[ 6108.744808] kmix[2411]: org.kde.kmix: No such icon "audio-card-analog"
[ 6108.745062] kmix[2411]: org.kde.kmix: No such icon "audio-card-analog"
[ 6108.798297] org_kde_powerdevil[1784]: [ 13552] Adding connected display with bus 6
[ 6109.841907] org_kde_powerdevil[1784]: [ 13552] busno=6, Feature 0xdd should not exist but ddc_get_nontable_vcp_value() succeeds, returning mh=0x00 ml=0x64 sh=0x00 sl=0x64
[ 6110.050596] org_kde_powerdevil[1784]: [ 13552] busno=6, Feature 0x41 should not exist but ddc_get_nontable_vcp_value() succeeds, returning mh=0x00 ml=0x19 sh=0x00 sl=0x19
[ 6110.259313] org_kde_powerdevil[1784]: [ 13552] busno=6, Feature 0x00 should not exist but ddc_get_nontable_vcp_value() succeeds, returning mh=0x00 ml=0x19 sh=0x00 sl=0x19Disconnecting power after switching it off does not change anything. However, disconnecting power while the screen is still switched on will make my secondary (DP-3) screen the primary screen. Upon reconnecting power to the DP-1 screen nothing happens and when switching it back on it becomes the primary screen again. This is weird.
Disconnected the DisplayPort cable always has the same effect, regardless of whether or not I switch the screen off first: KDE recognizes the disconnect and DP-3 becomes the primary screen. That being said, the moment I reconnect the DisplayPort cable to the screen, I get the "screen connected" noise and the DP-3 screen becomes the secondary screen again,that is even if the DP-1 screen is turned off while the cable is reconnected.
*edit*
Additional information: I had never tried this before, but if after reaching the login screen with both screens switched off, I switch on the screen connected to DP-3 first, everything works. I can then also switch on the other screen and it also displays the login screen correctly.
Last edited by Sidekick (2025-10-13 07:14:07)
Offline
#7 2025-10-11 15:46:57
- seth
- Member
- From: Don't DM me only for attention
- Registered: 2012-09-03
- Posts: 69,070
Re: SDDM does not show login when no screen is switched on during boot
And just now I think you solved this, if I switch off DP-1, which is also my primary screen - nothing changes. The secondary screen stays the secondary screen, I can move the mouse 'out of bounds' on the side where the screen connected via DP-1 is connected and windows/applications that were open on that screen are not moved to the screen connected through DP-3.
Is that w/ or w/o the output being force-enabled? Did that change anything about the original problem?
Online
#8 2025-10-11 22:59:15
- Sidekick
- Member
- Registered: 2024-06-23
- Posts: 52
Re: SDDM does not show login when no screen is switched on during boot
And just now I think you solved this, if I switch off DP-1, which is also my primary screen - nothing changes. The secondary screen stays the secondary screen, I can move the mouse 'out of bounds' on the side where the screen connected via DP-1 is connected and windows/applications that were open on that screen are not moved to the screen connected through DP-3.
Is that w/ or w/o the output being force-enabled? Did that change anything about the original problem?
That is without any force enabling.
Offline
#9 2025-10-12 13:20:42
- seth
- Member
- From: Don't DM me only for attention
- Registered: 2012-09-03
- Posts: 69,070
Re: SDDM does not show login when no screen is switched on during boot
… and if you do force the output to be enabled?
Online