Can't start Plasma from SDDM anymore, only from CLI

This is really weird. It happened for the first time this morning even though I didn’t install any updates or change anything yesterday as far as I can recall. I was on Fedora 40, just now I upgraded to 41 but the issue persists. I’m on a laptop with Intel+NVIDIA graphics.

When I log in through SDDM, I just get a black screen and nothing happens.
I can switch to a TTY and log in to the console there, and running startplasma-wayland from there works just fine.
Although when I restart SDDM from the TTY and try to log in again, the system freezes completely.

The weird part is that there is absolutely nothing interesting in the systemd journal either.
It says
sddm-helper[3446]: Starting Wayland user session: "/etc/sddm/wayland-session" "/usr/libexec/plasma-dbus-run-session-if-needed /usr/bin/startplasma-wayland"
But after that there are no signs of Plasma ever actually starting, nor are there any error messages.

And again, I can launch Plasma from a TTY with startplasma-wayland.

1 Like

Okay so I still don’t quite know what went wrong but it had something to do with fish (the shell that I use).
I found that out by changing my users shell to bash which made me able to log in again. So I went back to fish and deleted my fish config files (which were barely changed from the default) as well as .profile (which had nothing of value in it anyways). Don’t know what was wrong before but it is fixed now.

your problem my be with powerdevil 6.2.3

try powerdevil 6.1.5

Well I already fixed it as I said and there were no errors so I don’t think it was powerdevil.
I think I did mess with my PATH variable a few days ago, thought I undid all that but maybe not. So it would make sense that deleting .profile and my fish config fixed it.

I got the exact same issue! I’m using Fedora 42 (Never upgraded, actually installed as Fedora 42) & I’m also using fish! Running startplasma-wayland got me into my desktop again too, but now me & the people I was talking to about this issue are also very very confused. I have three desktops with KDE Neon installed using Plasma on Wayland & fish with all the same settings, but none of them have had this issue. It seems to be specific to Fedora!

Here’s my thread where I got some help & collected information, incase there might be any relevant information that could help. I have a journalctl log too but I’m unsure how to attach it here.

And for @firlaev-hans . The solution to start Plasma Wayland with fish shell is:

  1. open $HOME/.profile
  2. Add this line export -n PROFILEREAD

I am a user of Fish and to start Plasma Wayland with my favourite shell I needed to do.

Regards