Proper way to start a KDE wayland session from console?

[cruzki123]

Hi,

I am trying to fully remove X from my world file. Th last package to use it is sddm which is kind of bummer. If I use the regular way from sddm to log in in kde wayland I get the usual desktop. I am having some problems with saving the session at restart but the rest of the things seems to be working as expected. But if I enable wayland sddm and try to log in to a plasma wayland session the only think I get is a black screen with a cursor. If I press alt+f2 I get krunner and from that I can lounch plasmashell and gentoo-pipewire-launcher to get a relastive functional KDE environment. At this point I was considering that the sddm wayland is too experimental but when I tried to start KDE directly from the console throght

[flexibeast]

`exec` in the context of shell means "completely replace the currently running process with this other process"; it doesn't just mean "run this program" (unlike, say, `exec` in various non-shell config files, e.g. the config file for Sway). So when you call something with `exec` in a shell script, nothing else after that line in the script gets run - the shell script has been entirely replaced by first program you called via `exec`.

i'm not a Plasma user, but in general:

* Don't use `exec` on the command line, just run the program you want:

[Goverp]

AFAIR the standard way to start plasma with wayland is

[finoderi]

DESKTOP_SESSION is a legacy variable and most likely not needed.
Just 'dbus-run-session startplasma-wayland' in .bash_profile would suffice.

[cruzki123]

Thanks to all for your answers.

OK, it seems like dbus-run-session startplasma-wayland works the first time I do the thing but after a reboot, I came back to the black screen of death. I am not sure how to get a propoer log of this. Shoudl I run something like

[Goverp]

When you say "first time" and "after a reboot", I take it the difference is a power-off (as compared with booting vs after hibernate or suspend). In which case something appears to be carried over when you reboot that's not the case from a cold start. I can think of two possible scenarios - perhaps someone might come up with others -
1. You're using "kexec" to reboot. This seems unlikely, it's a pretty esoteric thing, and fragile (i.e. I can't get it to work...)
2. You're using the EFI framebuffer after a cold boot, but (as EFI isn't involved) after a reboot your system is trying to use some other video driver - perhaps amdgpu or the Nvidia equivalent - and that's not working. Typically problems of this sort are down to compiling the kernel support as modules or not, and the availability of firmware in the kernel if not a module, or other kernel misconfiguration.
_________________
Greybeard

[cruzki123]