SUMMARY My system wouldnt boot into sddm at first, so i booted into a TTY. After some research and log analysis, SDDM was reading the kde_settings.conf file located in /etc/sddm.conf.d/ and trying to load that. Since i had autologin selected in system settings, this section was added to that .conf file. However, it is written Session=plasma, which i guess SDDM may have had a recent update that requires the .desktop extension in .conf files. After changing this to 'Session=plasmax11.desktop' my system booted normally. Referring back to the logs from journalctl, i noticed that after reading that file, even though I had DisplayServer=x11 automatically generated in SDDM system .conf file, since it was not specified in kde_settings.conf, for error handling SDDM tried to instead start a Wayland session, which i do not have properly configured on my system, thus resulting in kwin-wayland pageflip time-outs as well as nvidia-drm time-outs. STEPS TO REPRODUCE 1. Make sure Wayland is not properly configured 2. Make sure it is indeed set 'Session=plasma' in /etc/sddm.conf.d/kde_settings.conf AFTER enabling autologin in system settings. If it is instead Session=plasmax11.desktop, then this bug report is null, and there may be a different cause or service dynamically changing it on my system, or possibly not caching it properly. 3. Reboot the system normally. It should fail and try to start a wayland session. OBSERVED RESULT Failure to show splash screen and the rest of kde EXPECTED RESULT When applying settings related to sddm, lde_settings.conf should be dynamically edited with valid values. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION
If you know that the wayland session isn't properly configured on your system, then wouldn't it be expected that trying to log into it fails? I'm not understanding what the problem is, sorry.
Created attachment 166995 [details] attachment-2239664-0.html I didn't try to login. I have 'Autologin' enabled. I do not have Wayland configured. SDDM is automatically trying to start a wayland session because 'Session=plasma' does not work anymore, it must be 'plasmax11.desktop' and it is not addressed in KDE's latest update. Also I would appreciate a more respectful tone when I am making an effort to improve such a robust an interesting project. Receiving a response like this from a developer is disheartening. On Mon, Mar 11, 2024 at 5:51 PM Nate Graham <bugzilla_noreply@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=483006 > > Nate Graham <nate@kde.org> changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > Resolution|--- |WAITINGFORINFO > CC| |nate@kde.org > Status|REPORTED |NEEDSINFO > > --- Comment #1 from Nate Graham <nate@kde.org> --- > If you know that the wayland session isn't properly configured on your > system, > then wouldn't it be expected that trying to log into it fails? I'm not > understanding what the problem is, sorry. > > -- > You are receiving this mail because: > You reported the bug.
Created attachment 166996 [details] attachment-2240159-0.html Not to mention I clearly included all of the above information in the bug report which makes it seem like you didn't really make an effort to understand it. On Mon, Mar 11, 2024 at 6:47 PM Dylan <dylanmyers316@gmail.com> wrote: > I didn't try to login. I have 'Autologin' enabled. I do not have Wayland > configured. SDDM is automatically trying to start a wayland session because > 'Session=plasma' does not work anymore, it must be 'plasmax11.desktop' and > it is not addressed in KDE's latest update. Also I would appreciate a more > respectful tone when I am making an effort to improve such a robust an > interesting project. Receiving a response like this from a developer is > disheartening. > > On Mon, Mar 11, 2024 at 5:51 PM Nate Graham <bugzilla_noreply@kde.org> > wrote: > >> https://bugs.kde.org/show_bug.cgi?id=483006 >> >> Nate Graham <nate@kde.org> changed: >> >> What |Removed |Added >> >> ---------------------------------------------------------------------------- >> Resolution|--- |WAITINGFORINFO >> CC| |nate@kde.org >> Status|REPORTED |NEEDSINFO >> >> --- Comment #1 from Nate Graham <nate@kde.org> --- >> If you know that the wayland session isn't properly configured on your >> system, >> then wouldn't it be expected that trying to log into it fails? I'm not >> understanding what the problem is, sorry. >> >> -- >> You are receiving this mail because: >> You reported the bug. > >
Basically, the situation is pretty much expected: what plasma.desktop does was changed to log into Wayland by default, not X11. This was intentional because we wanted to recommend the Wayland session by default in Plasma 6, not the X11 session. However in your setup, you've indicated that you've got the Wayland session not set up properly. Hence, the new default setting does not work for you. So there are two solutions to the problem: 1. If you want to not use Wayland, that's fine, just change your auto-login settings to log into the X11 session. 2. If you do want to use Wayland, fix it on your system so that logging into it works.
Created attachment 166998 [details] attachment-2242941-0.html This took me two days to fix. I'm sure there are less intrusive means of suggesting Wayland to users than changing their default configuration. On Mon, Mar 11, 2024 at 6:54 PM Nate Graham <bugzilla_noreply@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=483006 > > Nate Graham <nate@kde.org> changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > Status|NEEDSINFO |RESOLVED > Resolution|WAITINGFORINFO |INTENTIONAL > > --- Comment #4 from Nate Graham <nate@kde.org> --- > Basically, the situation is pretty much expected: what plasma.desktop does > was > changed to log into Wayland by default, not X11. This was intentional > because > we wanted to recommend the Wayland session by default in Plasma 6, not the > X11 > session. > > However in your setup, you've indicated that you've got the Wayland > session not > set up properly. Hence, the new default setting does not work for you. > > So there are two solutions to the problem: > 1. If you want to not use Wayland, that's fine, just change your auto-login > settings to log into the X11 session. > 2. If you do want to use Wayland, fix it on your system so that logging > into it > works. > > -- > You are receiving this mail because: > You reported the bug.
I'm sorry it caused you pain. Nonetheless, the goal was not to suggest the Wayland session, but to make it the new default one. It was expected that distros would do the necessary work to package and install it properly so that changing what plasma.desktop does would work. For DIY distros like Arch, that expectation also falls on you, the end user, in the form of choosing to install the necessary packages. And this plan was communicated months ago, multiple times. If you're not up for this kind of thing to happen every now and then, it might be a sign that Arch isn't the right distro for you, and it's possible you may have a better time with a distro that sets up everything automatically.
Created attachment 167001 [details] attachment-2251093-0.html I just discovered KDE a couple of weeks ago. I'm very new to linux, and I appreciate your advice, being that I should understand that for DIY distros, system stability is heavily dependent on me. However, I do enjoy learning how everything works, and about how to control my own system. I also enjoyed discovering the solution to this problem for my system, and writing a bug report for a part of KDE6 that I didn't think was intended. I definitely didn't expect your initial response though, like I thought I was really being helpful and then you hit me with that. I understand you guys are probably under a lot of stress and working around the clock since you're in kahoots with Valve. But it's my opinion that having a good rapport with users is pretty important. On Mon, Mar 11, 2024 at 7:11 PM Nate Graham <bugzilla_noreply@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=483006 > > --- Comment #6 from Nate Graham <nate@kde.org> --- > I'm sorry it caused you pain. Nonetheless, the goal was not to suggest the > Wayland session, but to make it the new default one. It was expected that > distros would do the necessary work to package and install it properly so > that > changing what plasma.desktop does would work. For DIY distros like Arch, > that > expectation also falls on you, the end user, in the form of choosing to > install > the necessary packages. And this plan was communicated months ago, multiple > times. If you're not up for this kind of thing to happen every now and > then, it > might be a sign that Arch isn't the right distro for you, and it's > possible you > may have a better time with a distro that sets up everything automatically. > > -- > You are receiving this mail because: > You reported the bug.
It's all good. Yes, we are getting a lot of bug reports. :) Sometimes it can be a bit disheartening to have an intended change reported as a bug, especially after a messaging blitz to get the word out there so that people understand it's an intended change. I understand how it wouldn't reach relatively new users though. Anyway, let's move on; I'm sure we both have something more productive we can use our time on! :D
Created attachment 167113 [details] attachment-2861634-0.html For sure, I see your perspective. Next time I'll do some research before I start typing up a bug report. Good luck to you! On Wed, Mar 13, 2024 at 1:28 PM Nate Graham <bugzilla_noreply@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=483006 > > --- Comment #8 from Nate Graham <nate@kde.org> --- > It's all good. Yes, we are getting a lot of bug reports. :) > > Sometimes it can be a bit disheartening to have an intended change > reported as > a bug, especially after a messaging blitz to get the word out there so that > people understand it's an intended change. I understand how it wouldn't > reach > relatively new users though. > > Anyway, let's move on; I'm sure we both have something more productive we > can > use our time on! :D > > -- > You are receiving this mail because: > You reported the bug.
*** Bug 484259 has been marked as a duplicate of this bug. ***
*** Bug 484260 has been marked as a duplicate of this bug. ***