It can't start, only if I execute setenforce 0
It can't start, only if I execute setenforce 0
KI've got it on 3 devices, all enforcing
Kno idea what's going on there
FIt's an access problem to var/lib/waydroid, related with getattr and search
FI fixed it adding it:
sudo ausearch -c 'waydroid' --raw | audit2allow -M mi-waydroid
sudo semodule -i mi-waydroid.ppsudo semanage fcontext -a -t waydroid_data_t "/var/lib/waydroid(/.*)?"
sudo restorecon -R /var/lib/waydroidsudo systemctl restart waydroid-container.serviceBtw, it can work with it too:
Just letting SELinux permissive only for waydroid permanently
sudo semanage permissive -a waydroid_tJust letting SELinux permissive only for waydroid permanently
Kthere must be something else wrong here
Kexactly none of that is required to use waydroid in a new install
Uis there a list of gaming-related things bazzite ships with that stock fedora doesn't?
Uwow it was in the readme this entire time, thanks
Aperhaps the workaround before was sticky?
Arechunk does not handle /var
Awhy was that workaround needed?
Kworkaround was for /usr/lib which rechunker fixes, /var is not needed because those folders are made when waydroid is downloaded
KIE: not in image
Athen probably setenforce 0 broke everything
Kyeah, very likely
K@antheas question
Krechunker fixes xattrs since selinux works, does it also handle caps?
KIE: CAP_SYS_ADMIN
Athe thing with those is very weird and i will need help with that
Kkk, asking because we had a separate workaround for that for gamescope and kde-sysmonitor
KI'll leave in place for now
Ai saw gamescope had correct xattrs in the docker image
Aactually im confused
Ai have the following problem with rechunk
Awhen i mount the container
Athe caps from kinoite are missing
Aand the caps from gamescope are there
Aso i have to quirk the missing caps from kinoite manually
Abut the ones you added in the container image are there
Aand should be frozen to the ostree commit afterwards
Rsuper low priority niche question, but is it possible to set the system wide "grace period" for unresponsive processes a bit higher?
right now it is really annoyed with any game loading for a second or two and immediately offers to force terminate it lol
right now it is really annoyed with any game loading for a second or two and immediately offers to force terminate it lol
FBut it doesn't, I tried it before from my Arch in a VM, didn't worked, I thought it was related bc trying of run it inside another VM, but now in real hardware happens the same...
Jyeah I hate this too
KCan't reproduce
KJust set it up again in a VM
KNo issues
![Froggyman [R5 7600X RX9070XT]](https://cdn.discordapp.com/avatars/1040372203390238790/0e5f5f4a3d1ee3f8b3e335b297241872.webp?size=40)
Frog ally X users with bazzite, anyone testing black myth wukong? 
Aif you remounted an existing var dir it wont be labeled properly
FWorkaround is to increase timeout to something like 20s
Aif you came from arch
FYou can see current timeout here in ms:
gsettings get org.gnome.mutter check-alive-timeoutFif you're using Gnome
FYou can increase it to something like 20s with this command:
gsettings set org.gnome.mutter check-alive-timeout 20000FI think that Nobara increases this too for the reasons you mentioned
CWasn't there a file that was added for you to configure that?
CI vaguely remember a commit like that
J@Kyle Gospo I wanna set this in bluefin it's infuriating.
JWas thinking 20000 is fine?
