i think it's a package you have layered by the way, but first sign the image: ``` rpm-ostree rebase
i think it's a package you have layered by the way, but first sign the image:
Thold on that copied wrong
3kk
3tell me whe it's good
D@nickname i've installed bazzite on 3 devices now and its never signed:
ostree-unverified-image:docker://ghcr.io/ublue-os/bazzite:latest i thought that was normalT
Dheh im in danger
3problem
Tyeah it's wrong still
3ah
Tshould be good
3:panik:
Jghcr.io not ghcr.1oTjorge im on a 2gb of ram chromebook rn
Tif you saw this setup
JI meant to @3L0_
Ti have insane input lag
Jthat's why they're getting that error
3oh okay
3SHIT
3same
3output
3message.txt10.53KB
Tit's a package you have layered
TdkmsTmost likely
3what do i do then ?
Trpm-ostree uninstall dkms3kk
3then i try to update again?
3reboot before i suppose 
Tyes reboot first
3
3writing rpmdb atm
3@nicknameseems ujust update is working again!
Tyeah i figured it was a package conflict
Tnow im curious why so many here said their image hasnt been signed
Tthat was supposed to happen on the first boot
3oh
T(also why was dkms layered?)
3not signed?
Tfirst boot like after the desktop starts up or....?
Tyeah you just removed the dkms package
Tnow rebase it
Tshould work now
3maybe bcuz of rebase
Tno no, the rebase should sign it
Tits just that you can only do a single rpm-ostree operation per boot i think
Tthis should sign it now
T(also sorry for pinging)
3 this?
