9 Replies
So, I've tried:
and
doing
sudo systemctl enable /home/deck/.local/share/systemd/user/waydroid.service enables it for the system user, then you can start/stop waydroid.service just like normal, but it doesn't log anything here
You shouldn't use sudo for user-level units
I…know what I’m doing
I’m storing the unit file as the user but I’m executing the file as root—this was intentional for testing at least
it does read the file just fine and creates the symlink just fine
you could try disabling selinux temporarily, might be causing issues?
likely
correct
yeah, something about the context that systemd tries to start waydroid's container in is blocked by SELinux--both the provided service and my custom service are fixed
I guess I could set permissive and log what needs some love
Yeah, is there an existing policy already? (Like upstream or something)
I would have imagined--though, it may be in mainline, but not in silverblue?
interesting--gamescope supports xdg_shell, so the whole nested-compositor thing might be more diable than I thought? sway might make it easier, as you could just give sway a config that launches waydroid; but I'm kinda determined to get something working using just a session start script in ~/
endgame android apps in gamescope so you can have chat apps or whatever running in the background while your game is in the foreground--or like, offline youtube in the background with Premium, etc
It is broken due to https://github.com/ostreedev/ostree-rs-ext/issues/510
oh man Waydroid doesn't handle multimonitor well--I mean, how could it? but like--oof