Startplasma-wayland options


TLDR: How to configure startplasma-wayland?

Longer version:
For complicated reasons I am trying to start Plasma on a Wayland Server (weston is my choice) inside an X-Server.

It is working (it shows up and appears to be usable), basically starting with:
WAYLAND_DISPLAY=wayland-1 /usr/lib/plasma-dbus-run-session-if-needed /usr/bin/startplasma-wayland # as a user

But there are several problems, among them:

  1. The display resolution is limited to 1024x768. The settings say that the display is limited to this.
  2. The lockscreen is activated after some time and I can’t seem to login.

I tried using the following options I found online, but they don’t seem to work at all:
WAYLAND_DISPLAY=wayland-1 /usr/lib/plasma-dbus-run-session-if-needed /usr/bin/startplasma-wayland --width 1280 --height 720 --xwayland --no-lockscreen

Now I would like to know, what I have to do to achieve these options.

Thx in advance.

More Info:
I use Plasma 6 on Archlinux in X11 Mode for this.
I also use weston with the following options:

weston --width=1920 --height=1080 --xwayland --config="weston-plus-x.ini"



1 Like

I could not find an answer to my initial question yet.

But a workaround is to use an X-Server e.g. XWayland as Display instead of the Wayland Server Display (directly).

Run something like this instead:

DISPLAY=:2 /usr/lib/plasma-dbus-run-session-if-needed /usr/bin/startplasma-wayland

Where DISPLAY=:2 is the XWayland Socket in my case.
This allows you to increase the screen size of the KDE Plasma Session inside the (Weston) Wayland window.

Sadly the lockscreen problem remains, so I can’t relogin, maybe I can change the energy saving settings, so the session never enters lockscreen automatically.

For those interested in further “research” for the initial question:

The startplasma-wayland binary seems to be part of the plasma-workspace package.
The relevant parts can be found in subfolder “startkde”:

As far as I understand it, startplasma-wayland is a wrapper script, so it starts other scripts and binaries and e.g. the KWin options are given inside of those, I assume.
But I did not “analyze” much of it, because it is written code.

My theory is that 1024x768 is the set standard resolution and that KWin is unable to read the maximum screen size of the given Wayland Display, but it can read the maximum screen size of the given X-Server Display (as described in above workaround).