Linux Flatpak release incomplete, autostart, resolution change and permissions broken #1352
Comments
|
same issues here, there is no way of autostart the flatpak on wayland, it needs sudo. |
|
It's not the best practice from security standpoint, but you can echo your password into sudo command like this: you have to add This is the way I got autostart working, but that doesn't really matter for me until #93 is fixed. |
|
Since linux generally saves your command history, that is really not a good idea. Better to just make it so you don't need a password for specific commands. https://askubuntu.com/a/159009 |
|
@ReenigneArcher |
|
👋 @3sv , It seems this issue hasn't had any activity in the past 90 days. If it's still something you'd like addressed, please let us know by leaving a comment. Otherwise, to help keep our backlog tidy, we'll be closing this issue in 10 days. Thanks! |
|
It seems this issue hasn't had any activity in the past 90 days. If it's still something you'd like addressed, please let us know by leaving a comment. Otherwise, to help keep our backlog tidy, we'll be closing this issue in 10 days. Thanks! |
|
This issue was closed because it has been stalled for 10 days with no activity. |
Is there an existing issue for this?
Is your issue described in the documentation?
Is your issue present in the nightly release?
Describe the Bug
With the Flatpak release, auto-start is not possible by default, and permissions are unclear.
Documentation mentions that is preferred to install as root, but then systemd user service runs as normal user.
The example start line is "sudo -i PULSE_SERVER=unix:$(pactl info | awk '/Server String/{print$3}') flatpak run dev.lizardbyte.sunshine" requiring manually starting it and entering password every time.
Additionally the default application for normal and high quality are not working either from the flatpak version.
Expected Behavior
Easy waty to start/stop and use the flatpak release. (Seems to be the best option for most distributions, tested on Fedora 37 myself)
Additional Context
As a test to improve the situation, I created the following improvements, but not there yet completely.
Created /usr/local/bin/sunshine:
Changed ~/.config/systemd/user/sunshine.service to:
Added these lines to visudo:
USERNAME ALL= NOPASSWD: /usr/local/bin/sunshineTested also with graphical-session.target instead of default.target, but both don't give auto-start after enabling:
systemctl --user enable sunshine
Manually executing start/stop works fine now as user without the need to enter password:
works fine with these changes now.
Don't understand why its still not auto-starting upon user login? What I'm missing here?
For the resolution change, I would like to have 2 applications, 1 offering a 4K stream, and 1 offering a 2K stream with wayland on gnome.
I created the following scripts that allow changing the resolution of the system unattended:
sudo dnf install ydotool
sudo systemctl --user enable --now ydotool
/home/dries/Apps/Scripts/2k.sh
/home/dries/Apps/Scripts/4k.sh
However I still fail to execute these script from within the flatpak sandbox.
I changed the settings with Flatseal to give access to these scripts:
But somehow this isn't enough to start these scripts from within sunshine:
Any ideas what I'm missing here to get it started from within sunshine flatpak?
Additionally, can my attempts to improve the flatpak installation be added to the flatpak installer somehow? Or can an alternative be added that would result in the same improved user experience that would allow for auto-start from userspace but running with sudo/root privileges as the actual user? Could the scripts for resolution change be integrated somehow?
As a sidenote: I discoceverd this project because my son is gaming, and really like the project. In such a way that I'm trying to use it for every day general remote desktop, as it is the best remote desktop solution with hardware acceleration support and delivering an amazing capable desktop as if you would be working locally! despite other generic remote desktop solutions were typical the hardware acceleration is missing, and such high resolution and low latencies are not reachable at all.
Host Operating System
Linux
Operating System Version
Linux, Fedora 37 Flatpak
Architecture
64 bit
Sunshine commit or version
0.20.0
Package
Linux - flatpak
GPU Type
Nvidia
GPU Model
amdgpu,nouveau
GPU Driver/Mesa Version
23.0.3
Capture Method (Linux Only)
KVM
Config
fps = [30,60] resolutions = [ 1920x1080, 3840x2160 ]Apps
{ "env": { "PATH": "$(PATH):$(HOME)\/.local\/bin" }, "apps": [ { "name": "Desktop", "image-path": "desktop.png", "prep-cmd": [ { "do": "\/home\/dries\/Apps\/Scripts\/4k.sh", "undo": "" }, { "do": "", "undo": "" }, { "do": "", "undo": "" } ], "exclude-global-prep-cmd": "false", "working-dir": "" }, { "name": "Low Res Desktop", "image-path": "desktop.png", "prep-cmd": [ { "do": "\/home\/dries\/Apps\/Scripts\/2k.sh", "undo": "" } ], "exclude-global-prep-cmd": "false", "working-dir": "" }, { "name": "Steam Big Picture", "detached": [ "flatpak-spawn --host setsid steam steam:\/\/open\/bigpicture" ], "image-path": "steam.png" } ] }Relevant log output
The text was updated successfully, but these errors were encountered: