# Issue updating Bazzite

**URL:** <https://universal-blue.discourse.group/t/issue-updating-bazzite/2675>\
**Category:** Bazzite\
**Created:** [July 2, 2024, 3:16pm UTC](https://universal-blue.discourse.group/t/issue-updating-bazzite/2675 "2024-07-02T15:16:13Z")\
**Posts on this page:** 13\
**Page:** 1

<div class="post-metadata">

**Author:** ![TeamLinux01](https://yyz2.discourse-cdn.com/free1/user_avatar/universal-blue.discourse.group/teamlinux01/32/111_2.png) [@TeamLinux01](https://universal-blue.discourse.group/u/TeamLinux01)\
**Post date:** [July 2, 2024, 3:16pm UTC](https://universal-blue.discourse.group/t/issue-updating-bazzite/2675/1 "2024-07-02T15:16:13Z")

</div>

On both my Steam Deck OLED and LCD, my updates are failing at the moment.

Running `ujust update` has the following error message:

```auto
Pulling manifest: ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-deck:stable
error: Creating importer: Failed to invoke skopeo proxy method OpenImage: remote error: cryptographic signature verification failed: invalid signature when validating ASN.1 encoded signature
System update failed: 
   0: Command failed: `/usr/bin/rpm-ostree upgrade`
   1: `/usr/bin/rpm-ostree` failed: exit status: 1

Location:
   src/steps/os/linux.rs:273

```

Hopefully this is fixed soon if the image didn’t get signed properly. If it is not an upstream issue, I could use some help to figure it out.

---

<div class="post-metadata">

**Author:** ![HenkoHallows](https://yyz2.discourse-cdn.com/free1/user_avatar/universal-blue.discourse.group/henkohallows/32/1924_2.png) [@HenkoHallows](https://universal-blue.discourse.group/u/HenkoHallows)\
**Post date:** [July 2, 2024, 3:43pm UTC](https://universal-blue.discourse.group/t/issue-updating-bazzite/2675/2 "2024-07-02T15:43:39Z")

</div>

Same issue, also Desktop keeps crashing since last update :t  
It looks like it could be because it’s not signed properly as you said, so same thought here.

Went back to see if the crashing would at least be fixed on x11  
I’m on a Desktop PC, and u used the system update button they made.

---

<div class="post-metadata">

**Author:** ![xynydev](https://yyz2.discourse-cdn.com/free1/user_avatar/universal-blue.discourse.group/xynydev/32/131_2.png) [@xynydev](https://universal-blue.discourse.group/u/xynydev)\
**Post date:** [July 2, 2024, 4:05pm UTC](https://universal-blue.discourse.group/t/issue-updating-bazzite/2675/3 "2024-07-02T16:05:22Z")

</div>

Team knows about this. Simply a signing mishap. There will be an announcement soon.

---

<div class="post-metadata">

**Author:** ![HenkoHallows](https://yyz2.discourse-cdn.com/free1/user_avatar/universal-blue.discourse.group/henkohallows/32/1924_2.png) [@HenkoHallows](https://universal-blue.discourse.group/u/HenkoHallows)\
**Post date:** [July 2, 2024, 4:10pm UTC](https://universal-blue.discourse.group/t/issue-updating-bazzite/2675/4 "2024-07-02T16:10:21Z")

</div>

Thank you for your time and work!

---

<div class="post-metadata">

**Author:** ![j0rge](https://yyz2.discourse-cdn.com/free1/user_avatar/universal-blue.discourse.group/j0rge/32/8_2.png) [@j0rge](https://universal-blue.discourse.group/u/j0rge)\
**Post date:** [July 2, 2024, 6:25pm UTC](https://universal-blue.discourse.group/t/issue-updating-bazzite/2675/5 "2024-07-02T18:25:23Z")

</div>

Please stand by, the team is aware of the issue and we’re fixing things and prepping an announcement.

(Discourse outage was unrelated)

---

<div class="post-metadata">

**Author:** ![ramphex](https://avatars.discourse-cdn.com/v4/letter/r/ecccb3/32.png) [@ramphex](https://universal-blue.discourse.group/u/ramphex)\
**Post date:** [July 2, 2024, 7:37pm UTC](https://universal-blue.discourse.group/t/issue-updating-bazzite/2675/6 "2024-07-02T19:37:25Z")

</div>

sub’d for updates, obv same issue here

---

<div class="post-metadata">

**Author:** ![j0rge](https://yyz2.discourse-cdn.com/free1/user_avatar/universal-blue.discourse.group/j0rge/32/8_2.png) [@j0rge](https://universal-blue.discourse.group/u/j0rge)\
**Post date:** [July 3, 2024, 12:18am UTC](https://universal-blue.discourse.group/t/issue-updating-bazzite/2675/7 "2024-07-03T00:18:50Z")

</div>

> [@Important announcement regarding system updates \[Action needed\]](https://universal-blue.discourse.group/t/important-announcement-regarding-system-updates-action-needed/2689):
>
> If you use Bazzite, Bluefin, Aurora, uCore, or any other Universal Blue image (including our toolboxes) then you need to follow the instructions in this announcement in order to ensure that your device is getting updates. We were rotating our cosign keypairs this morning, which is the method that we use to sign our images. During this process I made a critical error which has resulted in forcing you to take manual steps to migrate to our newly signed images. All existing Universal Blue image…

---

<div class="post-metadata">

**Author:** ![Ne0\_0](https://yyz2.discourse-cdn.com/free1/user_avatar/universal-blue.discourse.group/ne0_0/32/4421_2.png) [@Ne0\_0](https://universal-blue.discourse.group/u/Ne0_0)\
**Post date:** [December 7, 2024, 4:33pm UTC](https://universal-blue.discourse.group/t/issue-updating-bazzite/2675/8 "2024-12-07T16:33:24Z")

</div>

Hi, same problem here, I can’t update my system, have someone found a way to solve this problem? 😵‍💫

System update failed:  
0: Command failed: `/usr/bin/rpm-ostree upgrade`  
1: `/usr/bin/rpm-ostree` failed: exit status: 1  
Location:  
src/steps/os/linux.rs:228

---

<div class="post-metadata">

**Author:** ![j0rge](https://yyz2.discourse-cdn.com/free1/user_avatar/universal-blue.discourse.group/j0rge/32/8_2.png) [@j0rge](https://universal-blue.discourse.group/u/j0rge)\
**Post date:** [December 7, 2024, 4:47pm UTC](https://universal-blue.discourse.group/t/issue-updating-bazzite/2675/9 "2024-12-07T16:47:07Z")

</div>

We need to see the whole error not just a fragment.

---

<div class="post-metadata">

**Author:** ![Ne0\_0](https://yyz2.discourse-cdn.com/free1/user_avatar/universal-blue.discourse.group/ne0_0/32/4421_2.png) [@Ne0\_0](https://universal-blue.discourse.group/u/Ne0_0)\
**Post date:** [December 7, 2024, 5:13pm UTC](https://universal-blue.discourse.group/t/issue-updating-bazzite/2675/10 "2024-12-07T17:13:27Z")

</div>

Sorry, I didn’t see the solution before writing the message. I copied the line to the terminal and I think it worked, but does this mean I can no longer use the system update app? I tried to use it because I thought the line didn’t update the system, but every time I try to update it shows me this error:  
Preformatted text── 18:03:34 -  
Updatingthesystem────────────────────────────────────────────────────  
Pulling manifest: ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-gnome-nvidia:stable  
Checking out tree 610008c… done  
Enabled rpm-md repositories: copr:copr.fedorainfracloud.org:matte-schwartz:sunshine copr:copr.fedorainfracloud.org:rodoma92:kde-cdemu-manager copr:copr.fedorainfracloud.org:rodoma92:rmlint copr:copr.fedorainfracloud.org:rok:cdemu updates fedora protonvpn-fedora-stable hardware\_razer updates-archive  
Importing rpm-md… done  
rpm-md repo ‘copr:copr.fedorainfracloud.org:matte-schwartz:sunshine’ (cached); generated: 2024-08-12T15:47:19Z solvables: 2  
rpm-md repo ‘copr:copr.fedorainfracloud.org:rodoma92:kde-cdemu-manager’ (cached); generated: 2024-10-29T12:13:12Z solvables: 16  
rpm-md repo ‘copr:copr.fedorainfracloud.org:rodoma92:rmlint’ (cached); generated: 2024-10-29T12:31:09Z solvables: 4  
rpm-md repo ‘copr:copr.fedorainfracloud.org:rok:cdemu’ (cached); generated: 2024-10-21T13:15:21Z solvables: 23  
rpm-md repo ‘updates’ (cached); generated: 2024-12-07T07:32:49Z solvables: 12568  
rpm-md repo ‘fedora’ (cached); generated: 2024-10-24T13:55:59Z solvables: 76624  
rpm-md repo ‘protonvpn-fedora-stable’ (cached); generated: 2024-12-05T13:31:24Z solvables: 25  
rpm-md repo ‘hardware\_razer’ (cached); generated: 2024-11-10T18:29:43Z solvables: 15  
rpm-md repo ‘updates-archive’ (cached); generated: 2024-12-07T07:49:59Z solvables: 13796  
Resolving dependencies… done  
error: Could not depsolve transaction; 2 problems detected:  
Problem 1: package openrazer-meta-3.9.0-1.1.noarch from hardware\_razer requires python3-openrazer, but none of the providers can be installed

- conflicting requests
- nothing provides python(abi) = 3.12 needed by python3-openrazer-3.9.0-1.1.noarch from hardware\_razer
- nothing provides python3.12dist(dbus-python) \>= 1.2 needed by python3-openrazer-3.9.0-1.1.noarch from hardware\_razer
- nothing provides python3.12dist(numpy) \>= 1.11 needed by python3-openrazer-3.9.0-1.1.noarch from hardware\_razer  
Problem 2: package razergenie-1.2.0-1.1.x86\_64 from hardware\_razer requires openrazer-daemon, but none of the providers can be installed
- conflicting requests
- nothing provides python(abi) = 3.12 needed by openrazer-daemon-3.9.0-1.1.noarch from hardware\_razer
- nothing provides python3.12dist(dbus-python) \>= 1.2 needed by openrazer-daemon-3.9.0-1.1.noarch from hardware\_razer
- nothing provides python3.12dist(pyudev) \>= 0.16.1 needed by openrazer-daemon-3.9.0-1.1.noarch from hardware\_razer
- nothing provides python3.12dist(daemonize) \>= 2.4.7 needed by openrazer-daemon-3.9.0-1.1.noarch from hardware\_razer
- nothing provides python3.12dist(pygobject) \>= 3.20 needed by openrazer-daemon-3.9.0-1.1.noarch from hardware\_razer
- nothing provides python3.12dist(setproctitle) \>= 1.1.8 needed by openrazer-daemon-3.9.0-1.1.noarch from hardware\_razer
- package razergenie-1.2.0-1.1.aarch64 from hardware\_razer does not have a compatible architecture
- nothing provides ld-linux-aarch64.so.1()(64bit) needed by razergenie-1.2.0-1.1.aarch64 from hardware\_razer
- nothing provides ld-linux-aarch64.so.1(GLIBC\_2.17)(64bit) needed by razergenie-1.2.0-1.1.aarch64 from hardware\_razer  
System update failed:  
0: Command failed: `/usr/bin/rpm-ostree upgrade`  
1: `/usr/bin/rpm-ostree` failed: exit status: 1

Location:  
src/steps/os/linux.rs:228

---

<div class="post-metadata">

**Author:** ![nicknamenamenick](https://yyz2.discourse-cdn.com/free1/user_avatar/universal-blue.discourse.group/nicknamenamenick/32/4512_2.png) [@nicknamenamenick](https://universal-blue.discourse.group/u/nicknamenamenick)\
**Post date:** [December 7, 2024, 6:00pm UTC](https://universal-blue.discourse.group/t/issue-updating-bazzite/2675/11 "2024-12-07T18:00:09Z")

</div>

You will lose all your layered packages but:  
`rpm-ostree reset` and rebooting after it’s finished should allow it to update.

---

<div class="post-metadata">

**Author:** ![Plyply](https://avatars.discourse-cdn.com/v4/letter/p/82dd89/32.png) [@Plyply](https://universal-blue.discourse.group/u/Plyply)\
**Post date:** [December 7, 2024, 6:29pm UTC](https://universal-blue.discourse.group/t/issue-updating-bazzite/2675/12 "2024-12-07T18:29:29Z")

</div>

What I do is `rpm-ostree status` and copy the list of layered packages to a text file. Then after a reset and update, add those packages back.

Eight months of using Bazzite and I’ve only had to do that one time. Not bad.

---

<div class="post-metadata">

**Author:** ![Ne0\_0](https://yyz2.discourse-cdn.com/free1/user_avatar/universal-blue.discourse.group/ne0_0/32/4421_2.png) [@Ne0\_0](https://universal-blue.discourse.group/u/Ne0_0)\
**Post date:** [December 7, 2024, 9:52pm UTC](https://universal-blue.discourse.group/t/issue-updating-bazzite/2675/13 "2024-12-07T21:52:15Z")

</div>

ok thanks it worked for me
