seems the selinux troubleshooter is kneecapped by selinux itself 😂
seems the selinux troubleshooter is kneecapped by selinux itself 
BIf its not a problem, is there anything else I can try?
MIt doesn't create /var/lib/setroubleshoot so it freaks out
ZYeah can see that
Zrather cant touch anything at /var/lib/setroubleshoot ( that after
mkdir -p /var/lib/setroubleshoot/; touch /var/lib/setroubleshoot/setroubleshoot_database.xml)
Axwayland is not x11
Aits not going away
Aits perfectly fine to use xwayland right now, apart from fractional scaling
Awhich looks like garbage on x11 apps
ZHmm seems
sudo restorecon -rv /var/lib/setroubleshoot didnt fix it
KCheck with your adapter is what I say, the partition manager should list your partitions fine
HHit's probably here to stay like multilib lmao
Hwouldnt be surprised if a certain valve company will keep clinging to x11 for their client until it's physically impossible for it to function
Adid you rebase from kinoite?
Zyep
Ayea one of the bugs i found during rechunking bazzite is that
Aif you rebase you lose the setroubleshoot user
AAthis is what should happen and didnt
Zcan be done manually i guess?
Aif you install bazzite with the ISO, these are added to the initial passwd and group files
Aif you rebase from kinoite no
VHello I got a little question here, are there any security concerns about bazzite os or is it as secure as fedora silverblue?
BAwesome. Shot. I'll try another adaptor. Thanks
Aadd them to /etc/passwd /etc/group
Asince you cant write to the lib files
KWhy is my clevis IDs different
Aprobably clevis recreated the user
Awith a different id
KAnd setrobleshoot
Aadd the missing ones
Aif there are any missing
KJust the groups I think
ZNow that I checked, it seems i had those beforehand(?)
KYeah the groups are there too
KVery strange
Aif they are they got autoadded
Abut its one of the potential issues i found
KWhat's the permissions on /var/lib/setroubleshoot?
KActually I have this bluefin vm right here I can check
Kwait its not there
ZYeah
Zliterally, selinux doesnt even let create the directory
ZI mean using sudo I can
Zbut not setroubleshootd
KDoesn't run on the bluefin vm either?
KIt runs after a
chown
AHi all! Since I've rebase to bazzite (ostree-image-signed:docker://ghcr.io/ublue-os/bazzite:stable) I am not getting updates with
rpm-ostree upgraderpm-ostree status -aSo, we should probably add a tmpfiles conf file for setroubleshoot
