Arch Linux

hully

Member

Registered: 2022-11-14

Posts: 164

startwayland-plasma hanged because I didn't install the session

I installed Arch Linux following the Installation guide.

After logging in to the tty, I typed "startplasma-wayland" and it hanged.

Since it worked with SDDM, I was going to post here, but then I realized that SDDM was starting a X11 session, and that I didn't have the "plasma-wayland-session" package installed.

After I installed  the package, "startplasma-wayland" works.

I feel it should throw me an error, most likely command not found, not just hangs and block the PC. I had to cold reboot.

In effect, the command is provided by the package "extra/plasma-workspace". But it doesn't work without "plasma-wayland-session".

So I feel this command should either be moved to "plasma-wayland-session", or [EDIT] throw an error if the wayland session is not installed, instead of hanging the PC.

@Seth: I feel this is not my fault

Last edited by hully (2023-11-10 17:18:22)

Zod

Member

From: Hoosiertucky

Registered: 2019-03-10

Posts: 636

Re: startwayland-plasma hanged because I didn't install the session

What's preventing you from opening a bug report with upstream?

hully

Member

Registered: 2022-11-14

Posts: 164

Re: startwayland-plasma hanged because I didn't install the session

The fact that I don't know if my reasoning is correct

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 76,064

Re: startwayland-plasma hanged because I didn't install the session

This would constitute a cyclic dependency and seems odd, to say the least.
https://archlinux.org/packages/extra/x8 … d-session/ only provides a session entry for DMs and the session file does nothing but launching startplasma-wayland

To enable support for Wayland in Plasma, also install the plasma-wayland-session package.

However this might just reference "from a DM",  startplasma-wayland depending on a specific sesssion entry that could only be used to trigger it sounds nuts and would certainly be an upstream bug (or I'm curious for that explanation…), but you want to make sure that that is really the case, eg. remove the package again and try to launch plasma, in doubt using "dbus-run-session".

If upstream insists on that behavior, the packages need to be merged - The split was apparently a workaround for plasma-wayland being useless … 7 years ago.
https://gitlab.archlinux.org/archlinux/ … 652ab999d6
https://gitlab.archlinux.org/archlinux/ … 5ecad33bcd

@Seth: I feel this is not my fault

Try to not make this a personal thing.

Last edited by seth (2023-11-10 18:32:27)

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

hully

Member

Registered: 2022-11-14

Posts: 164

Re: startwayland-plasma hanged because I didn't install the session

I also installed `plasma-wayland-protocols` together with `plasma-wayland-session` ... could this be it?

Yes the latter seems only to be a desktop session file

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 76,064

Re: startwayland-plasma hanged because I didn't install the session

"plasma-wayland-protocols" isn't a runtime dependecy for anything and should most certainly not be required to run plasma.
Remove the two packages, try to run "startplasma-wayland" again.
If it fails again, try "dbus-run-session startplasma-wayland".

If you're convinced that the presence of the plasma-wayland-session package is the critical difference, file a bug against the package to have it re-merged w/ plasma-workspace.
It's a wtf condition but upstream ships them together and there's no (longer a) reason for the split.

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc