Help needed . Cannot start plasma wayland session

English Applications
1

Hi, new openSuse tumbleweed user here, just made the switch from Kubuntu. After a first day of getting to know my way around the new OS, and installing stuff for work (mostly web development tools like ruby, nodejs and system libraries) all of this using a wayland session with no problems. Then this morning i’ve logged out and when i’ve tried to log back in all i could get was a black screen. Selecting x11 plasma session works just fine, but i’d prefer to go back to wayland, because to me it seems to work better on the external monitor connected to my laptop, and also because it was working before, and i don’t like when things breaks without an apparent reason.

Here are my laptop specs, hope someone can help debugging this problem.

Operating System: openSUSE Tumbleweed 20231015

KDE Plasma Version: 5.27.8

KDE Frameworks Version: 5.110.0

Qt Version: 5.15.11

Kernel Version: 6.5.6-1-default (64-bit)

Graphics Platform: X11

Processors: 12 × 12th Gen Intel® Core™ i5-1235U

Memory: 15.3 GiB of RAM

Graphics Processor: Mesa Intel® Graphics

Manufacturer: HP

Product Name: HP EliteBook 860 16 inch G9 Notebook PC

2

That’s the general consensus… Wayland works sometimes.

If it “works better”, then it would work.

I’ve tried off and on with Wayland, and it’s more trouble than it’s worth, when things need to get done. Which is why I always use X11 Plasma.

Thumbs crossed you get it figured out :+1:

3

Can you have a look at the journal for the failing boot with Wayland?

sudo journalctl -b -<X>

With -X being -1 for the one but last boot, -2 for the boot before that etc.

4

well it turned out it was fish as a default shell that was for some reason crashing plasma wayland session. Reverted back to zsh as default shell and everything works!

1 Like
5

Yes, you do need to be careful about the default shell. A known issue with sddm actually. Two of many such similar reports…

https://www.reddit.com/r/openSUSE/comments/vm4a3b/plasma_wayland_session_stopped_working_after/