Trying to rebase to 41.20241230
I keep getting this error that says:
error: Creating importer: failed to invoke method OpenImage: failed to invoke method OpenImage: reading manifest stable-40.20241230.0 in ghcr.io/blue-os/bazzite-deck: manifest unknown
I’m on a Legion Go. Anyone know why this is happening?
33 Replies
Rebasing to stable seems to work so far. But only stable.
how did you rebase
rpm-ostree rebase
command
or brh
there is a typo in the URL btw, it is ublue-os, not blue-osI used brh first, then ostree
Also yes, I meant to type ublue, thanks for catching that
also 40.something does not exist
that version is based upon F41
Oh. Seems like my issue might’ve been a simple typo then
Lemme see if it works now
Same error
Oh wait
Second times the charm?
It didn’t work
It said it did, and then I rebooted it when prompted, but it didn’t actually change what version I’m on
I used brh
Please show the full brh command
On sec I’ll grab it
But I’m pretty sure it was bazzite-rollback-helper rebase stable-41.20241230
Yeah that’s it
Wait
Now it’s what I actually put it
Even doing the brh current command, it’s showing that it didn’t change
I’m trying it again. Staging deployment rn
Okay, now it’s prompted me to do systemctl reboot
Didn’t work. Same situation. Said it would apply on reboot, but didn’t
Trying again with ostree
Didn’t work.
Please show the full
rpm-ostree rebase
command and the output of itrpm-ostree rebase ostree-unverified-registry:ghcr.io/ublue-os/bazzite-deck:stable-41.20241230
I’ll need to run the command again to get the output, but it seems like it just displayed the regular working output
No errors or anything
I just realized I can’t change up update version at all
I can’t update
Just tried switching to a testing image. Still didn’t work. I’m stuck on stable-41.20250106
yes, you are on the
bazzite-deck:stable-41.20241230
there are no updates pushed to that tag,
it is also the cause for your error in your first message, that image does not exist exist anymore, they will get cleaned up eventually
PLEASE SHOW YOUR rpm-ostree status
first
sudo rpm-ostree rebase ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-deck:stable
One sec, I’ll run that
deck@bazzite:~$ rpm-ostree status
State: idle
Warning: failed to finalize previous deployment
error: Bootloader write config: grub2-mkconfig: Child process exited with code 1
check
journalctl -b -1 -u ostree-finalize-staged.service
Deployments:
● ostree-unverified-registry:ghcr.io/ublue-os/bazzite-deck:stable-41.20250106
Digest: sha256:e1583266e40ea96e8f1b19f9b6099e0e8bb45605757a3cc6ed03fb3a19169556
Version: 41.20250106 (2025-01-06T05:47:17Z)
ostree-unverified-registry:ghcr.io/ublue-os/bazzite-deck:stable-41.20250124
Digest: sha256:480dbd151a8475b19c54997f8005dc18c0d5cbb2b237fcc6d1f31f0fbfb9476a
Version: 41.20250124 (2025-01-24T08:14:52Z)
Running second command nowidk, why you got that grub error
the rebase should work tho
Nothing changed
rpm-ostree status?
output of rebase?
I’ll run it again
deck@bazzite:~$ rpm-ostree status
State: idle
Warning: failed to finalize previous deployment
error: Bootloader write config: grub2-mkconfig: Child process exited with code 1
check
journalctl -b -1 -u ostree-finalize-staged.service
Deployments:
● ostree-unverified-registry:ghcr.io/ublue-os/bazzite-deck:stable-41.20250106
Digest: sha256:e1583266e40ea96e8f1b19f9b6099e0e8bb45605757a3cc6ed03fb3a19169556
Version: 41.20250106 (2025-01-06T05:47:17Z)
ostree-unverified-registry:ghcr.io/ublue-os/bazzite-deck:stable-41.20250124
Digest: sha256:480dbd151a8475b19c54997f8005dc18c0d5cbb2b237fcc6d1f31f0fbfb9476a
Version: 41.20250124 (2025-01-24T08:14:52Z)Output of the journalctl command
Running rebase again
just reboot
Through the terminal?
restart button
Alright
deck@bazzite:~$ rpm-ostree status
State: idle
Warning: failed to finalize previous deployment
error: Bootloader write config: grub2-mkconfig: Child process exited with code 1
check
journalctl -b -1 -u ostree-finalize-staged.service
Deployments:
● ostree-unverified-registry:ghcr.io/ublue-os/bazzite-deck:stable-41.20250106
Digest: sha256:e1583266e40ea96e8f1b19f9b6099e0e8bb45605757a3cc6ed03fb3a19169556
Version: 41.20250106 (2025-01-06T05:47:17Z)
ostree-unverified-registry:ghcr.io/ublue-os/bazzite-deck:stable-41.20250124
Digest: sha256:480dbd151a8475b19c54997f8005dc18c0d5cbb2b237fcc6d1f31f0fbfb9476a
Version: 41.20250124 (2025-01-24T08:14:52Z)
deck@bazzite:~$yeah, idk why it doesn't write your bootloader
maybe someone else knows
Hm
I need to rebase because the recent updates have made games unplayable, so I wonder if that’s related
your storage isn't full is it?
please post output of
df -h
Lemme check
deck@bazzite:~$ df -h
Filesystem Size Used Avail Use% Mounted on
/dev/nvme0n1p7 951G 918G 30G 97% /sysroot
composefs 40M 40M 0 100% /
devtmpfs 4.0M 0 4.0M 0% /dev
tmpfs 7.5G 197M 7.3G 3% /dev/shm
efivarfs 148K 117K 27K 82% /sys/firmware/efi/efivars
tmpfs 3.0G 2.4M 3.0G 1% /run
tmpfs 1.0M 0 1.0M 0% /run/credentials/systemd-journald.service
tmpfs 1.0M 0 1.0M 0% /run/credentials/systemd-network-generator.service
tmpfs 1.0M 0 1.0M 0% /run/credentials/systemd-udev-load-credentials.service
tmpfs 1.0M 0 1.0M 0% /run/credentials/systemd-tmpfiles-setup-dev-early.service
tmpfs 1.0M 0 1.0M 0% /run/credentials/systemd-sysctl.service
tmpfs 1.0M 0 1.0M 0% /run/credentials/systemd-tmpfiles-setup-dev.service
tmpfs 1.0M 0 1.0M 0% /run/credentials/systemd-vconsole-setup.service
tmpfs 7.5G 59M 7.4G 1% /tmp
/dev/nvme0n1p7 951G 918G 30G 97% /var
/dev/nvme0n1p6 974M 319M 588M 36% /boot
/dev/nvme0n1p7 951G 918G 30G 97% /var/home
/dev/nvme0n1p5 300M 13M 288M 5% /boot/efi
tmpfs 1.0M 0 1.0M 0% /run/credentials/systemd-tmpfiles-setup.service
tmpfs 1.0M 0 1.0M 0% /run/credentials/systemd-resolved.service
tmpfs 1.5G 228K 1.5G 1% /run/user/1000
I have 30 gigs free
I remember there being something in rpm-ostree that wants it to have some % of storage free, no matter how much gb are free
I’ll try deleting something
sudo rpm-ostree cleanup --rollback
removes your rollbackI can’t seem to uninstall any games
Or maybe it’s just lagging
deck@bazzite:~$ sudo rpm-ostree cleanup --rollback
error: cleanup: GDBus.Error:org.projectatomic.rpmostreed.Error.Failed: Bootloader write config: grub2-mkconfig: Child process exited with code 1
deck@bazzite:~$
Okay so: I think I’ve figured out what the issue is
I have four ostrees in my grub menu, instead of two. Two 0s, and two 1s
Update: now on todays new update, although since games still aren’t working I still need to rollback to an earlier build, which I can’t seem to do still
Update again: I rebased to the version released on nov 29th. Seems to have worked
I’m not really sure what I did to fix it though
irrelevant
first set is bootloader config (new) grub
2nd set is "legacy config" grub (in case you updated from an ancient install, does not apply to 100% of our users, but the entry is made automatically by the fedora installer)