KDE is an international technology team creating user-friendly free and open source software for desktop and portable computing. KDE’s software runs on GNU/Linux, BSD and other operating systems, including Windows.
If you encounter a bug, proceed to https://bugs.kde.org, check whether it has been reported.
If it hasn't, report it yourself.
PLEASE THINK CAREFULLY BEFORE POSTING HERE.
Developers do not look for reports on social media, so they will not see it and all it does is clutter up the feed.
Why not just log in as the user in TTY and then start it?
I'n not sure I understand the use-case of why it needs a Plasma session to start a script that needs to keep running afterwards. If the script itself does not need a plasma session, then you can just start it as a user service with systemd.
Thanks for your answer!
I am writing a setup script which installs and configures my system automatically.
As the creation of rclone configurations requires passwords, I wanted to boot up a Plasma Wayland session (for each user which needs to be created) and prompt them to create the necessary rclone configurations and sign out afterwards.
My current (non functioning) draft of the script looks like this: https://git.nuth.ch/manuth/PortValhalla/src/commit/c88be78a7bce6b5d4d3bb64456b58366d1a1305d/scripts/Common/Software/rclone/main.fish#L10-L60
Alright, so I found an absolute trainwreck of a solution.
All the ways I have tested (sudo, login, openvt, machinectl, systemd-run) don't work because important variables like XDG_SESSION_ID are not created. So probably these methods don't open up a real session or something...?
What I did is to automatically open up a session for the specified user - in this case using getty.
Using these code lines, I created a systemd-configuration and booted it up by running systemctl daemon-reload:
{
printf %s\n \
"[Service]" \
"ExecStart=" \
"ExecStart=-/sbin/agetty -o '-p -f -- \\u' --noclear --autologin $TARGET_USER %I \$TERM"
} | sudo tee "/etc/systemd/system/getty@tty2.service.d/autologin.conf"
sudo systemctl daemon-reload
sudo systemctl restart getty@tty2
source: https://wiki.archlinux.org/title/Getty
After this, the user has a running session and proper environment variables set up.
I use pgrep to wait for the expected process to show up:
sessionPid=""
while [ -z "$sessionPid" ]; do
sessionPid=$(sudo pgrep -t tty2 -u "$TARGET_USER")
done
The environment variables of the process with the PID $sessionPid can then be borrowed to run startplasma-wayland properly as the desired user:
sudo -u "$TARGET_USER" \
env \
$(sudo -u "$TARGET_USER" fish -c "cat /proc/$sessionPid/environ | string split0)") \
/usr/lib/plasma-dbus-run-session-if-needed startplasma-wayland
The fact, that this command would always end up focussing on tty2 after exiting the plasma session, I kind of abused the openvt-command to force the focus to return to the previous tty:
openvt -sw -- \
sudo -u "$TARGET_USER" \
env \
$(sudo -u "$TARGET_USER" fish -c "cat /proc/$sessionPid/environ | string split0)") \
/usr/lib/plasma-dbus-run-session-if-needed startplasma-wayland
I also did some quirks like using openvt to find an unused tty.
If you want to see the whole thing in action - script is here: