yeah try `rpm-ostree update` first
yeah try
rpm-ostree update
Jyeah you'll need to be more aggressive on the updates
M[normand64@Normand64 .var]$ rpm-ostree update
Pulling manifest: ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-nvidia:38
Importing: ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-nvidia:38 (digest: sha256:58e5521a6ab890e106f9b21a0f44625c82cdde5052db80a4d140883eacaf4379)
ostree chunk layers already present: 53
ostree chunk layers needed: 12 (662.6 MB)
custom layers needed: 4 (1.5 GB)
not sure if it's still processing.
Pulling manifest: ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-nvidia:38
Importing: ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-nvidia:38 (digest: sha256:58e5521a6ab890e106f9b21a0f44625c82cdde5052db80a4d140883eacaf4379)
ostree chunk layers already present: 53
ostree chunk layers needed: 12 (662.6 MB)
custom layers needed: 4 (1.5 GB)
not sure if it's still processing.
MI'll be right back.
Jyeah that'll take a bit
Tgood to know that there is an update so just sit tight
Wyeah it just silently updates
MSo what do I do to get the just files back?
Mrpm-md repo 'updates-archive'; generated: 2023-09-23T02:26:21Z solvables: 38222
Resolving dependencies... done
Will download: 1 package (158.6 kB)
Downloading from 'copr:copr.fedorainfracloud.org:kylegospo:oversteer'... done
Importing packages... done
Relabeling... done
Checking out packages... done
Running pre scripts... done
Running post scripts... done
Running posttrans scripts... done
Writing rpmdb... done
Writing OSTree commit... done
Staging deployment... done
Freed: 492.6 MB (pkgcache branches: 0)
Upgraded:
container-selinux 2:2.221.1-1.fc38 -> 2:2.222.0-1.fc38
gstreamer1 1.22.5-1.fc38 -> 1.22.6-1.fc38
oversteer 0.0.git.316.bf27c8ba-1.fc38 -> 0.0.git.319.86040501-1.fc38
oversteer-udev 0.0.git.317.579bab90-1.fc38 -> 0.0.git.319.86040501-1.fc38
pipewire-codec-aptx 0.3.79-1.fc38 -> 0.3.80-1.fc38
ublue-os-just 0.3-1.fc38 -> 0.4-1.fc38
zip 3.0-36.fc38 -> 3.0-37.fc38
Run "systemctl reboot" to start a reboot
Oh. Looks like the thing finished when I went to check on laundry.
Resolving dependencies... done
Will download: 1 package (158.6 kB)
Downloading from 'copr:copr.fedorainfracloud.org:kylegospo:oversteer'... done
Importing packages... done
Relabeling... done
Checking out packages... done
Running pre scripts... done
Running post scripts... done
Running posttrans scripts... done
Writing rpmdb... done
Writing OSTree commit... done
Staging deployment... done
Freed: 492.6 MB (pkgcache branches: 0)
Upgraded:
container-selinux 2:2.221.1-1.fc38 -> 2:2.222.0-1.fc38
gstreamer1 1.22.5-1.fc38 -> 1.22.6-1.fc38
oversteer 0.0.git.316.bf27c8ba-1.fc38 -> 0.0.git.319.86040501-1.fc38
oversteer-udev 0.0.git.317.579bab90-1.fc38 -> 0.0.git.319.86040501-1.fc38
pipewire-codec-aptx 0.3.79-1.fc38 -> 0.3.80-1.fc38
ublue-os-just 0.3-1.fc38 -> 0.4-1.fc38
zip 3.0-36.fc38 -> 3.0-37.fc38
Run "systemctl reboot" to start a reboot
Oh. Looks like the thing finished when I went to check on laundry.
Treboot
Tthen hopefully the justfiles are back
MLooks like I gotta do a reboot. So I'll be back and let you know if I see anything different.
MComputer is fine but the bad news is I still don't have Bazzite arch yet. I suppose that is only for providing the Just Files?
Tyup
Thopefully you have the justfiles now
Ttry the previous commands
MI'll give it try.
Moh wait! Should I do this one first?
Tif you do it'll probably just say you're up to date lol
Twould try
just reset-bazzite-archMgotchya nevermind
MOk
Tim not sure if it actually needs
--unstableMBefore I do what exactly is reset arch gonna do? It's not going to reset the whole computer right?
Tno
MThank god!
Tit just deletes the old container, if there, and pulls the newest bazzite-arch image
Moh and the current terminal is under .var]$ and my hostname is that fine?
Tyeah it should be fine
MIMAGE_INFO="/usr/share/ublue-os/image-info.json" && BASE_IMAGE_NAME=$(jq -r '."base-image-name"' < $IMAGE_INFO) && distrobox stop bazzite-arch && distrobox rm bazzite-arch --force && if [[ ${BASE_IMAGE_NAME} == 'kinoite' ]]; then podman image rm bazzite-arch --force; else podman image rm bazzite-arch-gnome --force; fi && /usr/bin/just --unstable install-bazzite-arch
Do you really want to stop bazzite-arch? [Y/n]:
Do you really want to stop bazzite-arch? [Y/n]:
TY
Tenter that
MY
Error: no container with name or ID "bazzite-arch" found: no such container
error: Recipe
[normand64@Normand64 .var]$
Error: no container with name or ID "bazzite-arch" found: no such container
error: Recipe
reset-bazzite-arch failed on line 121 with exit code 125[normand64@Normand64 .var]$
Mhmmmm
Twhat LOL ok. no big deal this SHOULD work hopefully. this command i suggested was newer so i guess it has some issues? idk
this hopefully works!!!
this hopefully works!!!
just install-bazzite-archTlike if this doesnt IDK what else to do
TOh you know what
Tit's probably because there was no bazzite-arch container preinstalled to begin with
MIt looks like its working
Tthats why you had that error
Tlet's go!
Tbtw stuff from bazzite portal shouldn't give you an error anymore
MOOH!!! Steam is updating!
Tthat means it's working
MContainer Setup Complete!
Generating locales...
en_US.UTF-8... done
Generation complete.
Application steam successfully exported.
OK!
steam will appear in your applications list in a few seconds.
Application lutris successfully exported.
OK!
lutris will appear in your applications list in a few seconds.
Application protontricks successfully exported.
OK!
protontricks will appear in your applications list in a few seconds.
/usr/bin/steamcmd from bazzite-arch exported successfully in /home/normand64/.steam.
OK!
Starting Steam...
Creating desktop shortcuts...
Finalizing...
Generating locales...
en_US.UTF-8... done
Generation complete.
Application steam successfully exported.
OK!
steam will appear in your applications list in a few seconds.
Application lutris successfully exported.
OK!
lutris will appear in your applications list in a few seconds.
Application protontricks successfully exported.
OK!
protontricks will appear in your applications list in a few seconds.
/usr/bin/steamcmd from bazzite-arch exported successfully in /home/normand64/.steam.
OK!
Starting Steam...
Creating desktop shortcuts...
Finalizing...
Tyou can go inside that container anytime and install scrcpy too!
MFinally!
TGlad it's working
MI hope they come out with an update soon in the future that can solve this problem with the Bazzite portal. It's just more convenient.
Tbazzite portal should work now
Tmost of the stuff from it relies on just
