Read-only filesystem error when running command to fix Sunshine KMS display capture

I have read-only filesystem error when sudo setcap cap_sys_admin+p /usr/bin/sunshine when sunshine installed from flathub. I tried to install it manually, but it throws an error at the same stage journalctl output: Apr 21 23:39:17 fedora rpm-ostree(sunshine.post)[6813]: /usr/sbin/setcap cap_sys_admin+p /usr/bin/sunshine Apr 21 23:39:18 fedora rpm-ostree(sunshine.post)[6822]: Failed to send reload request: No such file or directory Apr 21 23:39:18 fedora rpm-ostree(sunshine.post)[6824]: uinput: Failed to write 'change' to '/sys/devices/virtual/misc/uinput/uevent': Read-only file system I've fixed error=remount-ro on /boot/efi - no effect I've changed /sysroot to rw (idea came from nowhere, possibly stupid, bazzite fixed it on next startup) - no effect I've tried fsck.mode=force in GRUB, because sudo touch /forcefsck returns no permission error - no effect (nothing visually happend during startup) Bazzite is installed on ssd where windows is already installed, but same error was when bazzite was on separate hdd
18 Replies
1/4 Life
1/4 Life2mo ago
1: you cannot setcap a flatpak 2: the root filesystem is read only, you cannot setcap on it and should undo your fstab/other changes immediately 3: we ship a service that does this for you if you layer sunshine, use the sunshine ujust to install it
(IV)(V)(VI)
(IV)(V)(VI)2mo ago
Sunshine reccomends it before streaming "for KMS display capture to work" fixed
1/4 Life
1/4 Life2mo ago
I don't think they intend that to be applied to the flatpak That's just for normal distro packages
(IV)(V)(VI)
(IV)(V)(VI)2mo ago
and as for 3: streaming just don't work and my first thought is for that reccomended fix
1/4 Life
1/4 Life2mo ago
It doesn't work right because you're using the flatpak Layer it with our ujust and you'll be all set No further tweaks You can uninstall the flatpak as well
(IV)(V)(VI)
(IV)(V)(VI)2mo ago
Haven't heard about ujust, brb
1/4 Life
1/4 Life2mo ago
ujust in a terminal will give you full details on what you can do with it
(IV)(V)(VI)
(IV)(V)(VI)2mo ago
wow it tells me that sunshine isn't installed probably because I've tried to install it manually, I'll try to fix problem with it, brb when something will happen Succesfuly installed it, if recommendation is meant to be ignored, then the issue is that sunshine can't find display and all encoders failed
1/4 Life
1/4 Life2mo ago
Hmm? Can you show a log of trying to run it?
(IV)(V)(VI)
(IV)(V)(VI)2mo ago
[2024:04:22:00:47:11]: Warning: Missing Wayland wire for wlr-export-dmabuf [2024:04:22:00:47:11]: Error: Failed to gain CAP_SYS_ADMIN [2024:04:22:00:47:11]: Info: /dev/dri/card1 -> evdi [2024:04:22:00:47:11]: Warning: No render device name for: /dev/dri/card1 [2024:04:22:00:47:11]: Error: Failed to gain CAP_SYS_ADMIN [2024:04:22:00:47:11]: Info: /dev/dri/card2 -> evdi [2024:04:22:00:47:11]: Warning: No render device name for: /dev/dri/card2 [2024:04:22:00:47:11]: Error: Failed to gain CAP_SYS_ADMIN [2024:04:22:00:47:11]: Info: /dev/dri/card3 -> evdi [2024:04:22:00:47:11]: Warning: No render device name for: /dev/dri/card3 [2024:04:22:00:47:11]: Error: Failed to gain CAP_SYS_ADMIN [2024:04:22:00:47:11]: Info: /dev/dri/card4 -> evdi [2024:04:22:00:47:11]: Warning: No render device name for: /dev/dri/card4
1/4 Life
1/4 Life2mo ago
Did you restart after running the ujust command?
(IV)(V)(VI)
(IV)(V)(VI)2mo ago
[2024:04:22:00:47:11]: Error: Failed to gain CAP_SYS_ADMIN [2024:04:22:00:47:11]: Info: /dev/dri/card5 -> nvidia-drm [2024:04:22:00:47:11]: Error: Failed to gain CAP_SYS_ADMIN [2024:04:22:00:47:11]: Error: Couldn't get handle for DRM Framebuffer [97]: Probably not permitted [2024:04:22:00:47:11]: Fatal: You must run [sudo setcap cap_sys_admin+p $(readlink -f sunshine)] for KMS display capture to work! [2024:04:22:00:47:11]: Info: Found display [wayland-0] [2024:04:22:00:47:11]: Info: Found display [wayland-0] [2024:04:22:00:47:11]: Info: Found interface: zxdg_output_manager_v1(32) version 3 [2024:04:22:00:47:11]: Info: Found interface: wl_output(49) version 4 [2024:04:22:00:47:11]: Info: Found interface: wl_output(50) version 4 [2024:04:22:00:47:11]: Info: Resolution: 1280x1024 [2024:04:22:00:47:11]: Info: Resolution: 1920x1080 [2024:04:22:00:47:11]: Info: Offset: 1920x446 [2024:04:22:00:47:11]: Info: Logical size: 1024x1280 [2024:04:22:00:47:11]: Info: Name: HDMI-A-1 [2024:04:22:00:47:11]: Info: Found monitor: Acer Technologies AL1716/6303 [2024:04:22:00:47:11]: Info: Offset: 0x0 [2024:04:22:00:47:11]: Info: Logical size: 1920x1080 [2024:04:22:00:47:11]: Info: Name: DP-1 [2024:04:22:00:47:11]: Info: Found monitor: AOC 22E1W/GPEKBHA040969 os? no
1/4 Life
1/4 Life2mo ago
Then you have two problems You haven't restarted so it's not installed, and you have some other version of it still installed in a way I'm not at all sure of Let's start with a restart
(IV)(V)(VI)
(IV)(V)(VI)2mo ago
I have uninstalled previous version from flathub, I think it's okay
1/4 Life
1/4 Life2mo ago
Flatpak will never exist in /usr/bin It's not that
(IV)(V)(VI)
(IV)(V)(VI)2mo ago
aw K, restarting You're right, now it's a new program Aaaaand error from home screen gone But it's a bit old version Info: Detecting connected monitors Info: Detected monitor 0: DVI-D-0, connected: false Info: Detected monitor 1: HDMI-0, connected: true Info: Detected monitor 2: DP-0, connected: true And there's an offset in monitor detection, actual DP monitor is 1 But that's alright, thank you very much :happy_green_trees:
©TriMoon™
©TriMoon™2mo ago
That means you have installed bazzite on a NTFS filesystem. If you shutdown win$@$ while "fastboot" is enabled, it leaves the filesystem in a non-clean state, which causes it to be mounted R/O in Linux... Do a search how to disable that default functionality in Win$@$, so it shutsdown properly... PS: It's not recomended, at least i strongly advise against it, to insatll Linux on NTFS...
(IV)(V)(VI)
(IV)(V)(VI)2mo ago
I've configured partitions manually, of course no ntfs