You are not logged in.
Two months ago, I replaced an AMD GPU with an NVIDIA GPU. I had a number of issues configuring the NVIDIA driver to boot properly. At the conclusion of that effort, SDDM was starting X correctly, but Wayland crashed every time SDDM tried to start it. I resolved that problem with the help of the KDE Bugtracking team last week. However, since I got Wayland working, X no longer starts properly. When I select Plasma (X11) at the greeter, enter my credentials, and press "login," the cursor freezes and the system remains frozen in that state for up to 20 minutes (the longest I have let it sit there, so far). A momentary press of the power button does initiate a "poweroff."
/etx/X11/xorg.conf: http://0x0.st/HJAQ.txt (generated by nvidia-xconfig)
/var/log/Xorg.0.log: http://0x0.st/HJAj.txt
The only potential log entry that I see that might be an issue is
[ 26.790] (II) GLX: Another vendor is already registered for screen 0Searching for that indicates the other vendor might be Mesa, but doesn't lead to any potential resolution.
Last edited by GaryScottMartin (2023-10-20 08:21:10)
Offline
enerated by nvidia-xconfig
Step #1: remove that again.
The server ran for ~15 seconds, there's an output detected and no obvious error.
Try to log into eg. an openbox session and inspect the system journal - this is probably rather a plasma than X11 issue.
Wildly speculating: kscreen, https://wiki.archlinux.org/title/KDE#Un … lution_set
Offline
By "remove that again", I assume that you meant that I should delete '/etc/X11/xorg.conf', was that what you intended?
I find no config files in '~/.local/share/kscreen/', though there is a log file there from 2017.
Here are the contents of that directory:
[gary@TehachapiMtn kscreen]$ ls
drwxr-xr-x - gary 8 Nov 2019 control/
drwxr-xr-x - gary 25 Aug 22:16 outputs/
.rw-r--r-- 481 gary 25 Aug 22:16 ff6e29a294593fb1c26667e4aed37a5a
.rw-r--r-- 594 gary 12 Oct 06:04 bfc8ea93730194a64eb84ded25d4801b
.rw-r--r-- 776 gary 13 Oct 16:32 3783fe0a1f34bafe2512ffae47d21a86
.rw-r--r-- 1.1k gary 26 Aug 00:06 3cd76cf31972136b74efa8e97df1c2bc
.rw-r--r-- 525k gary 4 Feb 2017 kscreen.logHere is the boot journal from my last attempt to start an X session. I noticed that it is trying to load Wayland based on the environment variables:
QT_QPA_PLATFORMTHEME="wayland;xcb"
QT_QPA_PLATFORM="wayland"I defined these in '~/.config/environment.d/envvars.conf' based on the explanation provided in the Wiki for defining environment variables per Wayland session: https://wiki.archlinux.org/title/Enviro … nd_session
Apparently '~/.config/environment.d/envvars.conf' is not sourced only for Wayland sessions.
Last edited by GaryScottMartin (2023-10-20 08:15:25)
Offline
Sorry, I lost the link to the boot journal. However, commenting out the definitions of QT_QPA_PLATFORMTHEME and QT_QPA_PLATFORM in '~/.config/environment.d/envvars.conf' fixed the problem with X sessions without breaking Wayland sessions. I was able to launch both from SDDM.
That leaves the question: do you know the correct method of defining environment variables per Wayland session only? Not critical at this point, but it would be nice to correct the Wiki.
Offline
You don't have to set these environment variables unless you absolutely need to on a case by case basis. Defaults of Qt will do the correct thing without them. That wiki section is pretty misleading as nothing about these files and their location has any relation to wayland. If you wanted to do this properly you'd have to at least have a conditional on XDG_SESSION_TYPE=wayland or so.
Offline
Thanks
Offline