Bugzilla – Bug 1215987
Slowroll - XDM doesn't launch default Plasma X11 session
Last modified: 2024-03-31 03:26:45 UTC
Initial Summary: Slowroll - XDM doesn't launch default Plasma X11 session To reproduce: 1-install minimal X role 2-install patterns-kde-kde_plasma constrained by solver.onlyRequires = true 3-ensure no DM is installed except XDM 4-ensure plasma5.desktop is the default xsession : # inxi -S System: Host: ara88 Kernel: 6.4.12-1-default arch: x86_64 bits: 64 Console: pty pts/0 Distro: openSUSE Tumbleweed-Slowroll 20231001 # update-alternatives --display default-displaymanager default-displaymanager - manual mode link best version is /usr/lib/X11/displaymanagers/xdm link currently points to /usr/lib/X11/displaymanagers/xdm link default-displaymanager is /usr/lib/X11/displaymanagers/default-displaymanager /usr/lib/X11/displaymanagers/console - priority 5 /usr/lib/X11/displaymanagers/xdm - priority 10 # update-alternatives --display default-xsession.desktop default-xsession.desktop - manual mode link best version is /usr/share/xsessions/plasma5.desktop link currently points to /usr/share/xsessions/plasma5.desktop link default-xsession.desktop is /usr/share/xsessions/default.desktop /usr/share/xsessions/icewm-session.desktop - priority 15 /usr/share/xsessions/plasma5.desktop - priority 25 # Actual behavior: 1-yellow-gray display screens with a decoration-free Xterm launch 2-WINDOWMANAGER=startplasma-x11 startx in the Xterm launches an apparently normal Plasma session Expected behavior: 1-Plasma session launches directly Additional information: 1-This is not unique to Slowroll, or this particular PC. I have it happening in Leap installations as well. This particular Slowroll was was born as a zypper dup from a cloned 15.5, which has the same problem. 2-This is not a recent development. ISTR 15.4 did it too, at least 6 months ago, but rather than reporting I installed KDM3 or TDM on them instead of keeping XDM only.
Could you please attach the user's ~/.xsession-errors file? Thanks!
(In reply to Stefan Dirsch from comment #1) > Could you please attach the user's ~/.xsession-errors file? Thanks! Search for ~/.xsession-errors* and /var/log/xdm.errors
I removed last night's logs, then rebooted to get fresh ones to include here. # ls -gG /var/log/xdm* -rw-r--r-- 1 1597 Oct 6 09:31 /var/log/xdm.errors # ls -Gg .xsession-errors* -rw------- 1 164 Oct 6 09:31 .xsession-errors-:0 -rw-rw-r-- 1 2499 Oct 5 2020 .xsession-errors-plasma.1 -rw------- 1 1566 Oct 5 2020 .xsession-errors-plasma.2 -rw------- 1 31676 Jul 16 2022 .xsession-errors-tde # cat .xsession-errors-:0 Environment variable $XAUTHORITY not set, ignoring. gpg-connect-agent: no gpg-agent running in this session gpg-connect-agent: no gpg-agent running in this session # cat /var/log/xdm.errors xdm info (pid 772): Starting xdm 1.1.14 xdm info (pid 772): Starting X server on :0 X.Org X Server 1.21.1.8 X Protocol Version 11, Revision 0 Current Operating System: Linux ara88 6.4.12-1-default #1 SMP PREEMPT_DYNAMIC Fri Aug 25 08:26:31 UTC 2023 (f5aa89b) x86_64 Kernel command line: BOOT_IMAGE=/boot/vmlinuz root=LABEL=zd8p19sslo noresume ipv6.disable=1 net.ifnames=0 radeon.cik_support=0 amdgpu.cik_support=1 consoleblank=0 preempt=full mitigations=off Current version of pixman: 0.42.2 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Fri Oct 6 09:30:56 2023 (==) Using config directory: "/etc/X11/xorg.conf.d" (==) Using system config directory "/usr/share/X11/xorg.conf.d" DRI driver not from this Mesa build ('23.2.0-rc4' vs '23.1.7') failed to bind extensions DRI driver not from this Mesa build ('23.2.0-rc4' vs '23.1.7') failed to bind extensions DRI driver not from this Mesa build ('23.2.0-rc4' vs '23.1.7') failed to bind extensions DRI driver not from this Mesa build ('23.2.0-rc4' vs '23.1.7') failed to bind extensions xf86: remove device 0 /sys/devices/pci0000:00/0000:00:01.0/drm/card1 failed to find screen to remove xdm info (pid 821): sourcing /usr/etc/X11/xdm/Xsetup xdm info (pid 821): sourcing /usr/etc/X11/xdm/Xstartup xdm info (pid 896): executing session /usr/etc/X11/xdm/Xsession # rpm -qa | grep Mesa | sort Mesa-23.2.0-359.1.x86_64 Mesa-demo-egl-9.0.0-2.1.x86_64 Mesa-demo-x-9.0.0-2.1.x86_64 Mesa-dri-23.2.0-359.1.x86_64 Mesa-gallium-23.2.0-359.1.x86_64 Mesa-libEGL1-23.2.0-359.1.x86_64 Mesa-libGL1-23.2.0-359.1.x86_64 Mesa-libglapi0-23.2.0-359.1.x86_64 # ls -gG /dev/dri total 0 drwxr-xr-x 2 80 Oct 6 09:30 by-path crw-rw---- 1 226, 1 Oct 6 09:30 card1 crw-rw-rw- 1 226, 128 Oct 6 09:30 renderD128 #
>DRI driver not from this Mesa build ('23.2.0-rc4' vs '23.1.7') >[...] >Mesa-23.2.0-359.1.x86_64 > [....] > Mesa-dri-23.2.0-359.1.x86_64 I don't get this ...
(In reply to Stefan Dirsch from comment #4) > >DRI driver not from this Mesa build ('23.2.0-rc4' vs '23.1.7') > >[...] > >Mesa-23.2.0-359.1.x86_64 > > [....] > > Mesa-dri-23.2.0-359.1.x86_64 > > I don't get this ... I don't either. But, the upgrade from Leap initially failed to bring one of the Mesa packages from 23.1.7 to 23.2.0. It thwarted me running X for a couple of hours until I discovered that failure and upgraded it with rpm from local cache. I think it was libglapi0, which is absent from .bash_history.
Hmm. Maybe you're using X11:XOrg devel repo for Leap 15.5. For a short amount of time Mesa 23.2.0 was built there, but Mesa-drivers 23.2.0 failed, so you could update to an inconsistent state of Mesa packages. Meanwhile I disabled build of Mesa there, since it's no longer possible to build 23.2.0 on Leap 15.5 without updating also llvm (which I tried, but it didn't help in the end for some reason; so I gave up in the end).
Maybe you should first check to have Mesa in a consistent state and clean up the mess.
I don't see anything to clean: # zypper ref Repository 'Libdvdcss' is up to date. Repository 'NonOSS' is up to date. Repository 'OSS' is up to date. Repository 'TDE' is up to date. Repository 'TDEnoarch' is up to date. Retrieving repository 'Update' metadata ...............................................................................................................................................[done] Building repository 'Update' cache ....................................................................................................................................................[done] Repository 'openh264' is up to date. All repositories have been refreshed. # zypper lr -E | grep Yes 1 | Libdvdcss | Yes | (r ) Yes | http://opensuse-guide.org/repo/openSUSE_Tumbleweed/ 2 | NonOSS | Yes | (r ) Yes | http://cdn.opensuse.org/repositories/openSUSE:/ALP:/Experimental:/Slowroll/base/repo/non-oss/ 3 | OSS | Yes | (r ) Yes | http://cdn.opensuse.org/repositories/openSUSE:/ALP:/Experimental:/Slowroll/base/repo/oss/ 4 | TDE | Yes | ( ) No | http://archive.trinitydesktop.net/trinity/rpm/osstw/trinity-r14/RPMS/x86_64 5 | TDEnoarch | Yes | ( ) No | http://mirror.ppa.trinitydesktop.org/trinity/rpm/osstw/trinity-r14/RPMS/noarch 6 | Update | Yes | (r ) Yes | http://cdn.opensuse.org/repositories/openSUSE:/ALP:/Experimental:/Slowroll/standard/ 7 | openh264 | Yes | (r ) Yes | http://codecs.opensuse.org/openh264/openSUSE_Tumbleweed/ # zypper se -s Mesa | egrep -v 'devel|32bit|veau' | grep pack Reading installed packages... | libOSMesa8 | package | 23.2.0-359.1 | x86_64 | OSS i+ | Mesa | package | 23.2.0-359.1 | x86_64 | OSS | Mesa-demo | package | 9.0.0-2.1 | x86_64 | OSS i+ | Mesa-demo-egl | package | 9.0.0-2.1 | x86_64 | OSS | Mesa-demo-es | package | 9.0.0-2.1 | x86_64 | OSS i+ | Mesa-demo-x | package | 9.0.0-2.1 | x86_64 | OSS i+ | Mesa-dri | package | 23.2.0-359.1 | x86_64 | OSS i+ | Mesa-gallium | package | 23.2.0-359.1 | x86_64 | OSS | Mesa-libd3d | package | 23.2.0-359.1 | x86_64 | OSS i+ | Mesa-libEGL1 | package | 23.2.0-359.1 | x86_64 | OSS i+ | Mesa-libGL1 | package | 23.2.0-359.1 | x86_64 | OSS i+ | Mesa-libglapi0 | package | 23.2.0-359.1 | x86_64 | OSS | Mesa-libOpenCL | package | 23.2.0-359.1 | x86_64 | OSS | Mesa-libRusticlOpenCL | package | 23.2.0-359.1 | x86_64 | OSS | Mesa-libva | package | 23.2.0-359.1 | x86_64 | OSS | Mesa-vulkan-device-select | package | 23.2.0-359.1 | x86_64 | OSS | Mesa-vulkan-overlay | package | 23.2.0-359.1 | x86_64 | OSS #
A different host, also with early GCN AMD GPU, with Slowroll created in same fashion (clone of 15.5 upgraded), does not reproduce this: # inxi -GSaz --vs --zl --hostname inxi 3.3.31-00 (2023-11-02) System: Host: fi965 Kernel: 6.4.12-1-default arch: x86_64 bits: 64 compiler: gcc v: 13.2.1 clocksource: tsc available: hpet,acpi_pm parameters: root=LABEL=<filter> ipv6.disable=1 net.ifnames=0 radeon.si_support=0 amdgpu.si_support=1 noresume consoleblank=0 mitigations=off Desktop: KDE Plasma v: 5.27.9 tk: Qt v: 5.15.10 wm: kwin_x11 vt: 7 dm: XDM Distro: openSUSE Tumbleweed-Slowroll 20231003 Graphics: Device-1: AMD Oland [Radeon HD 8570 / R5 430 OEM R7 240/340 Radeon 520 OEM] vendor: Dell driver: amdgpu v: kernel alternate: radeon arch: GCN-1 code: Southern Islands process: TSMC 28nm built: 2011-20 pcie: gen: 1 speed: 2.5 GT/s lanes: 8 link-max: gen: 3 speed: 8 GT/s ports: active: DP-1,DVI-I-1 empty: none bus-ID: 01:00.0 chip-ID: 1002:6611 class-ID: 0300 temp: 48.0 C Display: x11 server: X.Org v: 21.1.9 compositor: kwin_x11 driver: X: loaded: amdgpu unloaded: modesetting alternate: fbdev,vesa dri: radeonsi gpu: amdgpu display-ID: :0 screens: 1 Screen-1: 0 s-res: 2560x2490 s-dpi: 120 s-size: 540x525mm (21.26x20.67") s-diag: 753mm (29.65") Monitor-1: DVI-I-1 mapped: DVI-I-0 pos: top model: Dell P2213 serial: <filter> built: 2012 res: 1680x1050 hz: 60 dpi: 90 gamma: 1.2 size: 473x296mm (18.62x11.65") diag: 558mm (22") ratio: 16:10 modes: max: 1680x1050 min: 720x400 Monitor-2: DP-1 mapped: DisplayPort-0 pos: primary,bottom model: Acer K272HUL serial: <filter> built: 2018 res: 2560x1440 hz: 60 dpi: 109 gamma: 1.2 size: 598x336mm (23.54x13.23") diag: 686mm (27") ratio: 16:9 modes: max: 2560x1440 min: 720x400 API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi device: 1 drv: swrast gbm: drv: radeonsi surfaceless: drv: radeonsi x11: drv: radeonsi inactive: wayland API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 23.2.0-rc4 glx-v: 1.4 direct-render: yes renderer: AMD Radeon R7 200 Series (oland LLVM 17.0.1 DRM 3.52 6.4.12-1-default) device-ID: 1002:6611 memory: 1000 MiB unified: no API: Vulkan Message: No Vulkan data available. # Plasma session launches directly from XDM.
Just had my first success with this, on host fi965: # zypper se -si Mesa | egrep -v 'devel|32bit|veau' | grep pack Reading installed packages... i | Mesa | package | 23.2.1-362.1 | x86_64 | Update i | Mesa | package | 23.2.1-362.1 | x86_64 | OSS i+ | Mesa-demo-egl | package | 9.0.0-2.1 | x86_64 | Update i+ | Mesa-demo-egl | package | 9.0.0-2.1 | x86_64 | OSS i+ | Mesa-demo-x | package | 9.0.0-2.1 | x86_64 | Update i+ | Mesa-demo-x | package | 9.0.0-2.1 | x86_64 | OSS i | Mesa-dri | package | 23.2.1-362.1 | x86_64 | Update i | Mesa-dri | package | 23.2.1-362.1 | x86_64 | OSS i | Mesa-gallium | package | 23.2.1-362.1 | x86_64 | Update i | Mesa-gallium | package | 23.2.1-362.1 | x86_64 | OSS i+ | Mesa-libd3d | package | 23.2.1-362.1 | x86_64 | Update i+ | Mesa-libd3d | package | 23.2.1-362.1 | x86_64 | OSS i | Mesa-libEGL1 | package | 23.2.1-362.1 | x86_64 | Update i | Mesa-libEGL1 | package | 23.2.1-362.1 | x86_64 | OSS i | Mesa-libGL1 | package | 23.2.1-362.1 | x86_64 | Update i | Mesa-libGL1 | package | 23.2.1-362.1 | x86_64 | OSS i | Mesa-libglapi0 | package | 23.2.1-362.1 | x86_64 | Update i | Mesa-libglapi0 | package | 23.2.1-362.1 | x86_64 | OSS i+ | Mesa-libOpenCL | package | 23.2.1-362.1 | x86_64 | Update i+ | Mesa-libOpenCL | package | 23.2.1-362.1 | x86_64 | OSS i+ | Mesa-libva | package | 23.2.1-362.1 | x86_64 | Update i+ | Mesa-libva | package | 23.2.1-362.1 | x86_64 | OSS Must be fixed? Is a small "xconsole <2>" window reporting "console log for hostname" (twice) supposed to open along with the Plasma desktop logged into?
15.5 on host ara88 presents the same problem. Startplasma-x11 is needed from the xterm that opens after XDM login. # zypper lr Repository priorities are without effect. All enabled repositories share the same priority. # | Alias | Enabled | GPG Check | URI --+--------------+---------+-----------+------------------------------------------------------------- 1 | NonOSS | Yes | (r ) Yes | http://cdn.opensuse.org/distribution/leap/15.5/repo/non-oss/ 2 | OSS | Yes | (r ) Yes | http://cdn.opensuse.org/distribution/leap/15.5/repo/oss/ 3 | Update | Yes | (r ) Yes | http://cdn.opensuse.org/update/leap/15.5/oss/ 4 | UpdateBP | Yes | (r ) Yes | http://cdn.opensuse.org/update/leap/15.5/backports/ 5 | UpdateNonOSS | Yes | (r ) Yes | http://cdn.opensuse.org/update/leap/15.5/non-oss/ 6 | UpdateSLE | Yes | (r ) Yes | http://cdn.opensuse.org/update/leap/15.5/sle/ 7 | openh264 | Yes | (r ) Yes | http://codecs.opensuse.org/openh264/openSUSE_Leap/ # zypsei lasm i | libKF5Plasma5 | package | 5.102.0-bp155.2.3.1 | x86_64 | UpdateBP i | plasma-framework | package | 5.102.0-bp155.2.3.1 | x86_64 | UpdateBP i | plasma-framework-components | package | 5.102.0-bp155.2.3.1 | x86_64 | UpdateBP i | plasma5-workspace-libs | package | 5.27.9-bp155.2.3.1 | x86_64 | UpdateBP i+ | plasma5-desktop | package | 5.27.9-bp155.2.3.1 | x86_64 | UpdateBP i+ | plasma5-integration-plugin | package | 5.27.9-bp155.2.3.1 | x86_64 | UpdateBP i+ | plasma5-session | package | 5.27.9-bp155.2.3.1 | noarch | UpdateBP i+ | plasma5-systemmonitor | package | 5.27.9-bp155.2.3.1 | x86_64 | UpdateBP i+ | plasma5-workspace | package | 5.27.9-bp155.2.3.1 | x86_64 | UpdateBP i+ | plasma5-workspace-wallpapers | package | 5.27.9-bp155.2.3.1 | noarch | UpdateBP # cat /usr/local/bin/zypsei #!/bin/sh zypper --no-refresh se -s -i $* | grep -Ev 'debug|devel|srcp|openSUSE-20' | grep -E 'x86|noarch'| sort #
(In reply to Felix Miata from comment #10) > Just had my first success with this, on host fi965: > # zypper se -si Mesa | egrep -v 'devel|32bit|veau' | grep pack > Reading installed packages... > i | Mesa | package | 23.2.1-362.1 | x86_64 | Update > i | Mesa | package | 23.2.1-362.1 | x86_64 | OSS > i+ | Mesa-demo-egl | package | 9.0.0-2.1 | x86_64 | Update > i+ | Mesa-demo-egl | package | 9.0.0-2.1 | x86_64 | OSS > i+ | Mesa-demo-x | package | 9.0.0-2.1 | x86_64 | Update > i+ | Mesa-demo-x | package | 9.0.0-2.1 | x86_64 | OSS > i | Mesa-dri | package | 23.2.1-362.1 | x86_64 | Update > i | Mesa-dri | package | 23.2.1-362.1 | x86_64 | OSS > i | Mesa-gallium | package | 23.2.1-362.1 | x86_64 | Update > i | Mesa-gallium | package | 23.2.1-362.1 | x86_64 | OSS > i+ | Mesa-libd3d | package | 23.2.1-362.1 | x86_64 | Update > i+ | Mesa-libd3d | package | 23.2.1-362.1 | x86_64 | OSS > i | Mesa-libEGL1 | package | 23.2.1-362.1 | x86_64 | Update > i | Mesa-libEGL1 | package | 23.2.1-362.1 | x86_64 | OSS > i | Mesa-libGL1 | package | 23.2.1-362.1 | x86_64 | Update > i | Mesa-libGL1 | package | 23.2.1-362.1 | x86_64 | OSS > i | Mesa-libglapi0 | package | 23.2.1-362.1 | x86_64 | Update > i | Mesa-libglapi0 | package | 23.2.1-362.1 | x86_64 | OSS > i+ | Mesa-libOpenCL | package | 23.2.1-362.1 | x86_64 | Update > i+ | Mesa-libOpenCL | package | 23.2.1-362.1 | x86_64 | OSS > i+ | Mesa-libva | package | 23.2.1-362.1 | x86_64 | Update > i+ | Mesa-libva | package | 23.2.1-362.1 | x86_64 | OSS > Must be fixed? > > Is a small "xconsole <2>" window reporting "console log for hostname" > (twice) supposed to open along with the Plasma desktop logged into? I think so, yes. With xdm.
Mesa package list. Mesa Mesa-KHR-devel Mesa-devel Mesa-dri Mesa-dri-devel Mesa-dri-nouveau Mesa-dri-vc4 Mesa-gallium Mesa-libEGL-devel Mesa-libEGL1 Mesa-libGL-devel Mesa-libGL1 Mesa-libGLESv1_CM-devel Mesa-libGLESv2-devel Mesa-libGLESv3-devel Mesa-libOpenCL Mesa-libRusticlOpenCL Mesa-libd3d Mesa-libd3d-devel Mesa-libglapi-devel Mesa-libglapi0 Mesa-libva Mesa-vulkan-device-select Mesa-vulkan-overlay libOSMesa-devel libOSMesa8 libgbm-devel libgbm1 libvdpau_nouveau libvdpau_r300 libvdpau_r600 libvdpau_radeonsi libvdpau_virtio_gpu libvulkan_broadcom libvulkan_freedreno libvulkan_intel libvulkan_lvp libvulkan_radeon libxatracker-devel libxatracker2 Save it in a file and run for i in $(cat Mesa-list); do rpm -q $i; done|grep -v "is not installed" on your affected machines.
From 15.5 on host ara88 (comment #11)(last updated 2023-12-19): # for i in $(cat mesalst); do rpm -q $i; done|grep -v "is not installed" Mesa-22.3.5-150500.75.2.x86_64 Mesa-dri-22.3.5-150500.75.2.x86_64 Mesa-gallium-22.3.5-150500.75.2.x86_64 Mesa-libEGL1-22.3.5-150500.75.2.x86_64 Mesa-libGL1-22.3.5-150500.75.2.x86_64 Mesa-libglapi0-22.3.5-150500.75.2.x86_64 libgbm1-22.3.5-150500.75.2.x86_64 # Slowroll on same host (comment #0)(last updated 2024-01-02): # for i in $(cat mesalst); do rpm -q $i; done|grep -v "is not installed" Mesa-23.2.1-363.1.x86_64 Mesa-dri-23.2.1-363.1.x86_64 Mesa-gallium-23.2.1-363.1.x86_64 Mesa-libEGL1-23.2.1-363.1.x86_64 Mesa-libGL1-23.2.1-363.1.x86_64 Mesa-libglapi0-23.2.1-363.1.x86_64 libgbm1-23.2.1-363.1.x86_64 #
Hmm. This looks consistent. I'm wondering if things are working when using sddm as displaymanager, which should be installed by default when installing KDE/Plasma5.
I don't know if my problem is related to this one. In the build service I get the build error for several packages: The build can not begin, because required packages are either missing or not explicitly defined. Repository has been published unresolvable: nothing provides Mesa = 22.3.5 needed by Mesa-dri, (got version 23.2.1-150600.80.1) If I look at the directories in the obs of SLES 15 SP6, then the mesa has a different version than the mesa-dri. So mesa has a different version than mesa-drivers. So could it be that there is a general problem with this package at the moment? Could it be that the division into mesa and mesa-drivers means that the two no longer fit together? Can anyone tell me who I should contact for this? Translated with DeepL.com (free version)
I don't think it's related to this issue. Your issue is known. I informed the llvm maintainer. It's related to issues with llvm build. (Mesa:drivers, which produces Mesa-dri, cannot be built right now). Check https://build.opensuse.org/project/monitor/X11:XOrg ..> search for Mesa Once this gets fixed, your build issues should also be fixed.
(SP6 seems is also affected by this)
(In reply to Stefan Dirsch from comment #17) > I don't think it's related to this issue. Your issue is known. I informed > the llvm maintainer. It's related to issues with llvm build. (Mesa:drivers, > which produces Mesa-dri, cannot be built right now). Check > > https://build.opensuse.org/project/monitor/X11:XOrg > ..> search for Mesa > > Once this gets fixed, your build issues should also be fixed. Thank you for your answer. I only see Tumblweed, 15.4 and 15.5 here. Nothing about 15.6 And I am talking about Leap 15.6. It does not work here either. Again, the versions of mesa and mesa-drivers are different. And in Leap there are certainly not the latest versions of Tumbleweed. I don't like this splitting of packages that depend on the same source. This problem confirms that once again. Because if it were a package, mesa itself would not have been built and therefore the bug would not exist. Can you perhaps point me in the direction of someone to whom I can report the exact problem with Leap 15.6? Then I'll just open a bug report. Hope to use the correct data.
@Eric Schirra The Mesa build issues have been fixed a long time ago in X11;XOrg. But update for 15.4 are no longer available. Only 15.5 and 15.6. @Felix Miata (In reply to Stefan Dirsch from comment #15) > Hmm. This looks consistent. I'm wondering if things are working when using > sddm as displaymanager, which should be installed by default when installing > KDE/Plasma5. Please try that.
SDDM v0.2 (as would GDM, conscripting any or all of ttys 1-3) conflicts with workflow here, so I've been slowly getting it purged it from all installations, which is how I found this problem. I wasn't able to find any way to get SDDM back up on tty7+, so by now I have maybe about 2 or 3 left among Slowrolls and TWs I will try when I can identify which. Most of those purged got KDM3, TDM or LightDM as a replacement. I haven't had any of them fail to launch startplasma-x11.
If things are working with lightdm I suggest to use this DM. AFAIK DMs like kdm3 and tdm are not shipped with our distribution. And using plasma without installing sddm is out of scope. I'm afraid KDE developers won't look into related issues.
On host g5eas on both TW and Slowroll, I used update-alternatives to switch from sddm to xdm, and both as expected launched startplasma-x11 on vt7. Afterward on Slowroll, I uninstalled sddm and rebooted to find xdm still launches startplasma-x11: # inxi -Cz CPU: Info: single core model: Intel Pentium 4 bits: 64 type: MT cache: L2: 2 MiB Speed (MHz): avg: 3200 min/max: N/A cores: 1: 3200 2: 3200 # inxi -GSaz System: Kernel: 6.6.23-1-longterm arch: x86_64 bits: 64 compiler: gcc v: 13.2.1 clocksource: tsc avail: hpet,acpi_pm parameters: root=LABEL=m25p19sslo ipv6.disable=1 net.ifnames=0 noresume consoleblank=0 mitigations=off Desktop: KDE Plasma v: 5.27.10 tk: Qt v: 5.15.12 info: frameworks v: 5.115.0 wm: kwin_x11 vt: 7 dm: XDM Distro: openSUSE Tumbleweed-Slowroll 20240213 Graphics: Device-1: XGI Z7/Z9 vendor: Gigabyte driver: N/A bus-ID: 0a:03.0 chip-ID: 18ca:0020 class-ID: 0300 Device-2: NVIDIA G98 [GeForce 8400 GS Rev. 2] vendor: PNY driver: nouveau v: kernel non-free: series: 340.xx status: legacy (EOL~2019-12-xx) last: release: 340.108 kernel: 5.4 xorg: 1.20 arch: Tesla process: 40-80nm built: 2006-2013 pcie: gen: 1 speed: 2.5 GT/s lanes: 1 link-max: lanes: 16 ports: active: DVI-I-1,VGA-1 empty: none bus-ID: 0b:00.0 chip-ID: 10de:06e4 class-ID: 0300 Display: x11 server: X.Org v: 21.1.11 compositor: kwin_x11 driver: X: loaded: modesetting unloaded: fbdev,vesa alternate: nouveau,nv,nvidia dri: nouveau gpu: nouveau display-ID: :0 screens: 1 Screen-1: 0 s-res: 3600x1200 s-dpi: 120 s-size: 762x254mm (30.00x10.00") s-diag: 803mm (31.62") Monitor-1: DVI-I-1 pos: primary,left model: NEC EA243WM serial: <filter> built: 2011 res: 1920x1200 hz: 60 dpi: 94 gamma: 1.2 size: 519x324mm (20.43x12.76") diag: 612mm (24.1") ratio: 16:10 modes: max: 1920x1200 min: 640x480 Monitor-2: VGA-1 pos: right model: Dell P2213 serial: <filter> built: 2012 res: 1680x1050 hz: 60 dpi: 90 gamma: 1.2 size: 473x296mm (18.62x11.65") diag: 558mm (22") ratio: 16:10 modes: max: 1680x1050 min: 720x400 API: EGL v: 1.5 hw: drv: nvidia nouveau platforms: device: 0 egl: 1.4 drv: nouveau device: 1 drv: swrast gbm: egl: 1.4 drv: nouveau surfaceless: egl: 1.4 drv: nouveau x11: egl: 1.4 drv: nouveau inactive: wayland API: OpenGL v: 4.5 compat-v: 3.3 vendor: mesa v: 23.3.6 glx-v: 1.4 direct-render: yes renderer: NV98 device-ID: 10de:06e4 memory: 483.4 MiB unified: no I need to get back to comment #0 host to retest.