Is Gamescope incompatible w/BlendOS?
So this has been a question I've been dying to ask but I don't want to waste anyone's time on something I could solve myself.
I amended -gamescope to my /system.yaml file naturally give it a whirl & the following results return to me.
(I'll share the log file after posting, too long to copy/paste - so check comments bellow)
My natural assumption based on what I've read is that gamescope as a package is incompatible with the host system.
(I've tried many troubleshooting solutions specific to gamescope & system.yaml such as post_install:)
So naturally this seems like the perfect usecase for a container, without over bloating this thread with the same command on repeat.
The results were similar in my Arch/Fedora containers where I ensured Gamescope had neccesary packages needed to function properly.
So the Host & Container solution failed for the most part, I can share all of my troubleshooting steps but this is the conclusion I've come to I just more or less want know if I'm right or if something else could be amiss here.
Seems gamescope may want access to files its not privy to due to Read only file system.
14 Replies
logs from Konsole
Example of my /system.yaml file:
@πππ½πππ₯π£πͺ-ππ, you've gained the level
2It is a working test file, so it's not permenant, but has no concoctions or errors.
It seems to be something to do with Vulkan
i think
cap_sys_nice+eip should be cap_sys_nice=eip (https://github.com/ValveSoftware/gamescope/issues/521)
but it should still work fineGitHub
[NVIDIA] Setting CAP_SYS_NICE makes gamescope unusable Β· Issue #52...
I'm on Arch using gamescope-git (3.11.31.beta6.r0.gb1c3859-1) and the latest Nvidia driver (515.48.07). Gamescope runs fine but outputs this warning message in the terminal: No CAP_SYS_NICE, fa...
i highly doubt it's a blendos bug
probably just a config issue
it's not like gamescope could write to the root filesystem regardless of whether it's read-only or not, given it doesn't run as root
as a test, you can try running
gamescope -- vkcube
but what exactly goes wrong? maybe i'm just not parsing your messages right, but all i see is a log file that shows nothing going wrong, besides that CAP_SYS_NICE isn't being applied for whatever reasonForgot to mention.. If I try setcap manually via Konsole(KDE) I get:
Failed to set capabilities on file 'setcap': Read-only file system
I can adjust the command I set in system.yaml & see if it persists but I don't exactly have high hopes for that.
try running gamescope -- vkcube
The end result is..
After the usual DRM format codes you saw aboveβ
Running just vkcube normally does work as expected.ohhh i didn't see that discord cut off the log lol
yeah i'm guessing you need to install mesa
https://wiki.archlinux.org/title/Vulkan
Welp. - I'll add it to the yaml file and report back
Yeah as Triller pointed out I was actually missing some vulkan libraries in my Yaml file.
Let alone mesa, I had these in my original file but my current one is a recreation of it since my system got nuked when the TTY-Login bug happened.
So I was actually missing necessary libraries I hadn't realized
Ah you're right it is "=" not "+".
Running this in the terminal gives me the message:
Failed to set capabilities on file 'setcap' : Read-only file system
(Which yeah, immutable)
Is there an alternate way to persist this?
For example at the end of my system.yaml file I have..
(Corrected)
This was my attempt to try & persist, but as I see has failed.
Just curious if you have any ideas?
Personally as long as gamescope works period that's good enough for me.
Nice cap being properly set would just be a plus.
oh uh post_install isn't a thing
it should be
commandsSo the end of system.yaml should look like:
(Corrected)
As an example?
yueah
yeah