Hi, I am randomly having an issue with KDE whereby having started it from SDDM (irrespective of whether it is using Wayland or Xorg) when KDE displays its desktop it drops back to the SDDM login screen. A subsequent start of KDE seems to then run it fine. What should I look at the next time it occurs to try to determine why this is occurring?
regards, Steve
Stephen Morris composed on 2024-11-05 09:15 (UTC+1100):
I am randomly having an issue with KDE whereby having started it from SDDM (irrespective of whether it is using Wayland or Xorg) when KDE displays its desktop it drops back to the SDDM login screen. A subsequent start of KDE seems to then run it fine. What should I look at the next time it occurs to try to determine why this is occurring?
Are you using default Breeze SDDM theme? If yes, see if a different one helps.
On 5/11/24 10:17, Felix Miata via kde wrote:
Stephen Morris composed on 2024-11-05 09:15 (UTC+1100):
I am randomly having an issue with KDE whereby having started it from SDDM (irrespective of whether it is using Wayland or Xorg) when KDE displays its desktop it drops back to the SDDM login screen. A subsequent start of KDE seems to then run it fine. What should I look at the next time it occurs to try to determine why this is occurring?
Are you using default Breeze SDDM theme? If yes, see if a different one helps.
I am using the Breeze theme as opposed to the Breeze Fedora theme, as these are the only two themes for sddm I have installed. I'll see if I can find some other themes I like the look of and see if it makes any difference. The other thing I should have mentioned and forgot to was, I was getting this issue in F40 and the F41 upgrade hasn't resolved it.
regards, Steve
Stephen Morris composed on 2024-11-06 08:16 (UTC+1100):
Felix Miata via kde wrote:
Stephen Morris composed on 2024-11-05 09:15 (UTC+1100):
I am randomly having an issue with KDE whereby having started it from SDDM (irrespective of whether it is using Wayland or Xorg) when KDE displays its desktop it drops back to the SDDM login screen. A subsequent start of KDE seems to then run it fine. What should I look at the next time it occurs to try to determine why this is occurring?
Are you using default Breeze SDDM theme? If yes, see if a different one helps.
I am using the Breeze theme as opposed to the Breeze Fedora theme, as these are the only two themes for sddm I have installed. I'll see if I can find some other themes I like the look of and see if it makes any difference.
sddm-themes in F39 contains elarun, maldives and maya. I don't remember what maya is like, but I like both maldives and elarun (and nearly everything else on the planet) better than breeze. That said, I have few installations with SDDM. On most I use either TDM or KDM, with or without Plasma installed.
On 6/11/24 11:03, Felix Miata via kde wrote:
sddm-themes in F39 contains elarun, maldives and maya. I don't remember what maya is like, but I like both maldives and elarun (and nearly everything else on the planet) better than breeze. That said, I have few installations with SDDM. On most I use either TDM or KDM, with or without Plasma installed.
The sddm-themes package wasn't installed on my F41 system, probably because it has never been installed on any previous version of Fedora. I have now switched over to the Maldives theme and I'll see how that goes. My system was originally installed with F38 from a live cd, so originally only had gnome with gdm, so I installed kde via a dnf group install and continued to use gdm (What is TDM?) but at a later point in time switched over to sddm because people on the Fedora mail list kept telling me I should be using sddm with kde when I was raising issues.
I'm finding since F40 that sddm takes a long time to display the login screen after the gui boot screen finishes, and then when I launch kde it takes a long time to display the desktop and sits there thrashing the hard disk for several minutes after the desktop gets displayed, which then makes it difficult to run anything. I did check I/O's while this was happening via htop, but the app performing the most I/O's kept changing, so it was hard to try to pin down the culprit.
With one of the system updates I put on recently, I ran a needs-restarting --service after the updates were finished, and that listed a whole bunch of services that needed restarting. Two of them were kmod-static-nodes and akmods which made sense as the nvidia drivers were updated to a new version. It also listed sddm as needing restarting, so I mistakenly did so, which dropped me back to the sddm login screen, so I logged back into kde and kde went completely haywire, moving the mouse kept leaving pointer trails all over the screen, and I couldn't click on any desktop icons nor could I click on the kde throbber to restart the system because after a little the mouse pointer actually stopped moving, so the only way I could restart was to use the hardware restart facility.
regards, Steve
Stephen Morris composed on 2024-11-07 08:16 (UTC+1100):
(What is TDM?)
KDE3 fork's DM, indistinguishable from Fedora's KDM: https://en.wikipedia.org/wiki/Trinity_Desktop_Environment https://www.trinitydesktop.org/ https://wiki.trinitydesktop.org/Fedora_Trinity_Repository_Installation_Instructions (Wiki needs update for F41, which is ready for it, and here severally installed)
-
Felix Miata -
Stephen Morris