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 upgrade. It's been more than a month. Is that normal or there is some issue on my system?Krpm-ostree status -a
MSo, we should probably add a tmpfiles conf file for setroubleshoot
MAnd maybe a sysusers as well
KIs creating a setroubleshoot directory with setrobleshoot ownership fine
MYeah that's the issue
MIt's not created
MWell it's made during build time but gets nuked since it's in /var
Zcan confirm, chowning it worked
VYes
SHow do I check which version/hash of Bazzite I'm currently running?
Krpm-ostree status -aVrpm-ostree status
Vffs
Vagain
M
Myay spammers
VIs that real
Mdon't fucking do that
KYes its a real picture of a 50$ bill
VWow!
SI assume the second one is the older image from before an update
VYep
KThe dot is your current version
VIf there's three, top will be the one that's waiting to be applied on reboot.
Tlibostree and all the atomic advantages while fedora workstation will still be the regular fedora that works like a traditional linux system with no read-only root parts
SGot it. Just installed. Working so far...
