# Got myself into a bit of trouble (can't update)

**URL:** <https://universal-blue.discourse.group/t/got-myself-into-a-bit-of-trouble-cant-update/1176>\
**Category:** General\
**Created:** [April 20, 2024, 2:41pm UTC](https://universal-blue.discourse.group/t/got-myself-into-a-bit-of-trouble-cant-update/1176 "2024-04-20T14:41:15Z")\
**Posts on this page:** 17\
**Page:** 1

<div class="post-metadata">

**Author:** ![akarypid](https://avatars.discourse-cdn.com/v4/letter/a/b5a626/32.png) [@akarypid](https://universal-blue.discourse.group/u/akarypid)\
**Post date:** [April 20, 2024, 2:41pm UTC](https://universal-blue.discourse.group/t/got-myself-into-a-bit-of-trouble-cant-update/1176/1 "2024-04-20T14:41:15Z")

</div>

I tried to update, but:

```auto
❯ rpm-ostree update
note: automatic updates (stage) are enabled
Pulling manifest: ostree-image-signed:docker://ghcr.io/ublue-os/bluefin-dx:latest
Inactive requests:
  adcli (already provided by adcli-0.9.2-3.fc39.x86_64)
  sssd-ad (already provided by sssd-ad-2.9.4-1.fc39.x86_64)
Checking out tree ccd16de... done
Enabled rpm-md repositories: copr:copr.fedorainfracloud.org:ublue-os:akmods updates fedora rpmfusion-free-updates-testing rpmfusion-free-updates rpmfusion-free rpmfusion-nonfree-updates-testing rpmfusion-nonfree-updates rpmfusion-nonfree google-chrome rpmfusion-nonfree-nvidia-driver rpmfusion-nonfree-steam updates-archive
Importing rpm-md... done
rpm-md repo 'copr:copr.fedorainfracloud.org:ublue-os:akmods' (cached); generated: 2024-03-17T06:02:48Z solvables: 216
rpm-md repo 'updates' (cached); generated: 2024-04-20T00:54:57Z solvables: 26052
rpm-md repo 'fedora' (cached); generated: 2023-11-01T00:12:39Z solvables: 70825
rpm-md repo 'rpmfusion-free-updates-testing' (cached); generated: 2024-04-17T18:47:59Z solvables: 51
rpm-md repo 'rpmfusion-free-updates' (cached); generated: 2024-04-17T18:44:46Z solvables: 177
rpm-md repo 'rpmfusion-free' (cached); generated: 2023-11-04T16:49:08Z solvables: 445
rpm-md repo 'rpmfusion-nonfree-updates-testing' (cached); generated: 2024-04-18T12:10:26Z solvables: 31
rpm-md repo 'rpmfusion-nonfree-updates' (cached); generated: 2024-04-17T19:30:13Z solvables: 75
rpm-md repo 'rpmfusion-nonfree' (cached); generated: 2023-11-04T17:26:32Z solvables: 208
rpm-md repo 'google-chrome' (cached); generated: 2024-04-17T17:16:30Z solvables: 3
rpm-md repo 'rpmfusion-nonfree-nvidia-driver' (cached); generated: 2024-03-24T11:34:40Z solvables: 29
rpm-md repo 'rpmfusion-nonfree-steam' (cached); generated: 2024-03-24T13:27:05Z solvables: 2
rpm-md repo 'updates-archive' (cached); generated: 2024-04-20T01:33:42Z solvables: 42903
Resolving dependencies... done
error: Could not depsolve transaction; 1 problem detected:
 Problem: conflicting requests
  - package glibc-2.38-18.fc39.i686 from updates requires glibc-common = 2.38-18.fc39, but none of the providers can be installed
  - package glibc-2.38-7.fc39.i686 from fedora requires glibc-common = 2.38-7.fc39, but none of the providers can be installed
  - cannot install both glibc-common-2.38-18.fc39.x86_64 from updates and glibc-common-2.38-17.fc39.x86_64 from @System
  - cannot install both glibc-common-2.38-7.fc39.x86_64 from fedora and glibc-common-2.38-17.fc39.x86_64 from @System
  - cannot install both glibc-common-2.38-18.fc39.x86_64 from updates-archive and glibc-common-2.38-17.fc39.x86_64 from @System

~ took 8s 

```

Not sure how I got into this situation, but I suppose it may have to do with [these failed attempts to get my printer to work](https://universal-blue.discourse.group/t/cant-use-printer/1127/2).

I ran `status` and found an error message as well:

```auto
❯ rpm-ostree status
State: idle
AutomaticUpdates: stage; rpm-ostreed-automatic.timer: last run 24h ago
Deployments:
  ostree-image-signed:docker://ghcr.io/ublue-os/bluefin-dx:latest
                   Digest: sha256:0c915556ebdd4ddd95bdcd313d8ff21f36846fb489613623f5f8171fdba66f1f
                  Version: 39.20240419.0 (2024-04-19T19:47:54Z)
            SecAdvisories: 1 moderate
                     Diff: 7 upgraded, 3 added
          LayeredPackages: 'libstdc++.i686' glibc.i686 oddjob-mkhomedir
            LocalPackages: mfcl3770cdwpdrv-1.0.2-0.i386

● ostree-image-signed:docker://ghcr.io/ublue-os/bluefin-dx:latest
                   Digest: sha256:f904a168e9ec6ac3be2079c8abfdad8f4f61dbc8d3e5171cf5efa506505674fd
                  Version: 39.20240418.0 (2024-04-18T20:45:03Z)
          LayeredPackages: 'libstdc++.i686' glibc.i686 oddjob-mkhomedir
            LocalPackages: mfcl3770cdwpdrv-1.0.2-0.i386

  ostree-image-signed:docker://ghcr.io/ublue-os/bluefin-dx:latest
                   Digest: sha256:42f856e95a179a41f6fae7511be19a3508a7ccd0c9c8d4fbd6228e1c6a77ab3b
                  Version: 39.20240418.0 (2024-04-18T18:17:29Z)
          LayeredPackages: 'libstdc++.i686' glibc.i686 oddjob-mkhomedir samba-common-tools
            LocalPackages: mfcl3770cdwpdrv-1.0.2-0.i386

```

Is it possible to revert my system to a “plain” image before whatever the brother “installer” did? I only need `oddjob-mkhomedir samba-common-tools` as extra layered packages.

---

<div class="post-metadata">

**Author:** ![akarypid](https://avatars.discourse-cdn.com/v4/letter/a/b5a626/32.png) [@akarypid](https://universal-blue.discourse.group/u/akarypid)\
**Post date:** [April 20, 2024, 2:59pm UTC](https://universal-blue.discourse.group/t/got-myself-into-a-bit-of-trouble-cant-update/1176/2 "2024-04-20T14:59:44Z")

</div>

I ran `rpm-ostree uninstall mfcl3770cdwpdrv-1.0.2-0.i386` and rebooted.

I still can’t update:

```auto
❯ rpm-ostree status
State: idle
AutomaticUpdates: stage; rpm-ostreed-automatic.timer: no runs since boot
Deployments:
● ostree-image-signed:docker://ghcr.io/ublue-os/bluefin-dx:latest
                   Digest: sha256:0c915556ebdd4ddd95bdcd313d8ff21f36846fb489613623f5f8171fdba66f1f
                  Version: 39.20240419.0 (2024-04-19T19:47:54Z)
          LayeredPackages: 'libstdc++.i686' glibc.i686 oddjob-mkhomedir samba-common-tools

  ostree-image-signed:docker://ghcr.io/ublue-os/bluefin-dx:latest
                   Digest: sha256:f904a168e9ec6ac3be2079c8abfdad8f4f61dbc8d3e5171cf5efa506505674fd
                  Version: 39.20240418.0 (2024-04-18T20:45:03Z)
          LayeredPackages: 'libstdc++.i686' glibc.i686 oddjob-mkhomedir
            LocalPackages: mfcl3770cdwpdrv-1.0.2-0.i386

~ 
❯ rpm-ostree update
note: automatic updates (stage) are enabled
Pulling manifest: ostree-image-signed:docker://ghcr.io/ublue-os/bluefin-dx:latest
Inactive requests:
  adcli (already provided by adcli-0.9.2-3.fc39.x86_64)
  sssd-ad (already provided by sssd-ad-2.9.4-1.fc39.x86_64)
Checking out tree ccd16de... done
Enabled rpm-md repositories: copr:copr.fedorainfracloud.org:ublue-os:akmods updates fedora rpmfusion-free-updates-testing rpmfusion-free-updates rpmfusion-free rpmfusion-nonfree-updates-testing rpmfusion-nonfree-updates rpmfusion-nonfree google-chrome rpmfusion-nonfree-nvidia-driver rpmfusion-nonfree-steam updates-archive
Importing rpm-md... done
rpm-md repo 'copr:copr.fedorainfracloud.org:ublue-os:akmods' (cached); generated: 2024-03-17T06:02:48Z solvables: 216
rpm-md repo 'updates' (cached); generated: 2024-04-20T00:54:57Z solvables: 26052
rpm-md repo 'fedora' (cached); generated: 2023-11-01T00:12:39Z solvables: 70825
rpm-md repo 'rpmfusion-free-updates-testing' (cached); generated: 2024-04-17T18:47:59Z solvables: 51
rpm-md repo 'rpmfusion-free-updates' (cached); generated: 2024-04-17T18:44:46Z solvables: 177
rpm-md repo 'rpmfusion-free' (cached); generated: 2023-11-04T16:49:08Z solvables: 445
rpm-md repo 'rpmfusion-nonfree-updates-testing' (cached); generated: 2024-04-18T12:10:26Z solvables: 31
rpm-md repo 'rpmfusion-nonfree-updates' (cached); generated: 2024-04-17T19:30:13Z solvables: 75
rpm-md repo 'rpmfusion-nonfree' (cached); generated: 2023-11-04T17:26:32Z solvables: 208
rpm-md repo 'google-chrome' (cached); generated: 2024-04-17T17:16:30Z solvables: 3
rpm-md repo 'rpmfusion-nonfree-nvidia-driver' (cached); generated: 2024-03-24T11:34:40Z solvables: 29
rpm-md repo 'rpmfusion-nonfree-steam' (cached); generated: 2024-03-24T13:27:05Z solvables: 2
rpm-md repo 'updates-archive' (cached); generated: 2024-04-20T01:33:42Z solvables: 42903
Resolving dependencies... done
error: Could not depsolve transaction; 1 problem detected:
 Problem: conflicting requests
  - package glibc-2.38-18.fc39.i686 from updates requires glibc-common = 2.38-18.fc39, but none of the providers can be installed
  - package glibc-2.38-7.fc39.i686 from fedora requires glibc-common = 2.38-7.fc39, but none of the providers can be installed
  - cannot install both glibc-common-2.38-18.fc39.x86_64 from updates and glibc-common-2.38-17.fc39.x86_64 from @System
  - cannot install both glibc-common-2.38-7.fc39.x86_64 from fedora and glibc-common-2.38-17.fc39.x86_64 from @System
  - cannot install both glibc-common-2.38-18.fc39.x86_64 from updates-archive and glibc-common-2.38-17.fc39.x86_64 from @System

~ took 10s 

```

---

<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:** [April 20, 2024, 3:23pm UTC](https://universal-blue.discourse.group/t/got-myself-into-a-bit-of-trouble-cant-update/1176/3 "2024-04-20T15:23:13Z")

</div>

> [@akarypid](#):
>
> `'libstdc++.i686' glibc.i686 oddjob-mkhomedir`

This looks like the likely culprit. Do `rpm-ostree reset` to reset your local layers. Looks like you’re pulling in a 32 bit glibc?

---

<div class="post-metadata">

**Author:** ![akarypid](https://avatars.discourse-cdn.com/v4/letter/a/b5a626/32.png) [@akarypid](https://universal-blue.discourse.group/u/akarypid)\
**Post date:** [April 20, 2024, 3:35pm UTC](https://universal-blue.discourse.group/t/got-myself-into-a-bit-of-trouble-cant-update/1176/4 "2024-04-20T15:35:45Z")

</div>

Indeed, this fixed it for me.

These packages got installed by the Brother printer install tool [from the previous post I linked](https://universal-blue.discourse.group/t/cant-use-printer/1127). The command `sudo ./linux-brprinter-installer-2.2.3-1 MFC-L3770CDW` simply pulled these in…

---

<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:** [April 20, 2024, 3:39pm UTC](https://universal-blue.discourse.group/t/got-myself-into-a-bit-of-trouble-cant-update/1176/5 "2024-04-20T15:39:33Z")

</div>

Maybe there’s a way we can support those printers so that nobody has to do this, if you wouldn’t mind filing an issue: [GitHub - ublue-os/bluefin: An interpretation of the Ubuntu spirit built on Fedora technology](https://github.com/ublue-os/bluefin) (I’ll move it to the right repo later)

Whack the printer info there, maybe we can ship some PPDs on disk for the most painful printers so you don’t have to do any of this.

---

<div class="post-metadata">

**Author:** ![arzayus84](https://avatars.discourse-cdn.com/v4/letter/a/ebca7d/32.png) [@arzayus84](https://universal-blue.discourse.group/u/arzayus84)\
**Post date:** [August 27, 2024, 5:49pm UTC](https://universal-blue.discourse.group/t/got-myself-into-a-bit-of-trouble-cant-update/1176/6 "2024-08-27T17:49:08Z")

</div>

I am running in a bit of a problem with the update. It used to update normally , but now it only pulls the same singed docker or same image and it doesn’t run any updates. i did a rebased and that’s when it stop updating to newer versions. Any help will be highly appreciated.

---

<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:** [August 27, 2024, 6:25pm UTC](https://universal-blue.discourse.group/t/got-myself-into-a-bit-of-trouble-cant-update/1176/7 "2024-08-27T18:25:07Z")

</div>

Please post the output of `rpm-ostree status`

---

<div class="post-metadata">

**Author:** ![arzayus84](https://avatars.discourse-cdn.com/v4/letter/a/ebca7d/32.png) [@arzayus84](https://universal-blue.discourse.group/u/arzayus84)\
**Post date:** [August 27, 2024, 6:57pm UTC](https://universal-blue.discourse.group/t/got-myself-into-a-bit-of-trouble-cant-update/1176/8 "2024-08-27T18:57:33Z")

</div>

deck@bazzite:~$ rpm-ostree status  
State: idle  
Deployments:  
● ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-deck:40-stable-20240807  
Digest: sha256:fa9d7c77f4be2d451aa62cc232649afd087a2ea0f539df891ef4bb5cb6ac488a  
Version: 40.20240807.0 (2024-08-07T07:32:24Z)

ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-deck:40-stable-20240807  
Digest: sha256:fa9d7c77f4be2d451aa62cc232649afd087a2ea0f539df891ef4bb5cb6ac488a  
Version: 40.20240807.0 (2024-08-07T07:32:24Z)

---

<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:** [August 27, 2024, 7:37pm UTC](https://universal-blue.discourse.group/t/got-myself-into-a-bit-of-trouble-cant-update/1176/9 "2024-08-27T19:37:18Z")

</div>

Looks like you rebased to a specific day’s image and didn’t move back to the rolling tag:

```
rpm-ostree rebase ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-deck:40-stable

```

Will rebase you to the right image and you’ll get updates from then on.

---

<div class="post-metadata">

**Author:** ![arzayus84](https://avatars.discourse-cdn.com/v4/letter/a/ebca7d/32.png) [@arzayus84](https://universal-blue.discourse.group/u/arzayus84)\
**Post date:** [August 27, 2024, 8:04pm UTC](https://universal-blue.discourse.group/t/got-myself-into-a-bit-of-trouble-cant-update/1176/10 "2024-08-27T20:04:51Z")

</div>

thank you Jorge. Your hard work speaks by itself. This project is amazing and you guys as well

---

<div class="post-metadata">

**Author:** ![arzayus84](https://avatars.discourse-cdn.com/v4/letter/a/ebca7d/32.png) [@arzayus84](https://universal-blue.discourse.group/u/arzayus84)\
**Post date:** [August 27, 2024, 8:48pm UTC](https://universal-blue.discourse.group/t/got-myself-into-a-bit-of-trouble-cant-update/1176/11 "2024-08-27T20:48:42Z")

</div>

Jorge, I put the command and it still stuck in the same date. Is there anything else that I can do?

---

<div class="post-metadata">

**Author:** ![arzayus84](https://avatars.discourse-cdn.com/v4/letter/a/ebca7d/32.png) [@arzayus84](https://universal-blue.discourse.group/u/arzayus84)\
**Post date:** [August 27, 2024, 8:49pm UTC](https://universal-blue.discourse.group/t/got-myself-into-a-bit-of-trouble-cant-update/1176/12 "2024-08-27T20:49:20Z")

</div>

── 16:46:50 - System update ────────────────────────────────────────────────────  
Pulling manifest: ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-deck:40-stable-20240807  
No upgrade available.

---

<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:** [August 27, 2024, 8:55pm UTC](https://universal-blue.discourse.group/t/got-myself-into-a-bit-of-trouble-cant-update/1176/13 "2024-08-27T20:55:55Z")

</div>

Was there an error when you rebased? I’ve been advised to give you this one:

```
rpm-ostree rebase ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-deck:stable

```

---

<div class="post-metadata">

**Author:** ![arzayus84](https://avatars.discourse-cdn.com/v4/letter/a/ebca7d/32.png) [@arzayus84](https://universal-blue.discourse.group/u/arzayus84)\
**Post date:** [August 27, 2024, 8:59pm UTC](https://universal-blue.discourse.group/t/got-myself-into-a-bit-of-trouble-cant-update/1176/14 "2024-08-27T20:59:08Z")

</div>

No there was no error. It worked as normal, but when i looked at the version. It shows that date.

---

<div class="post-metadata">

**Author:** ![arzayus84](https://avatars.discourse-cdn.com/v4/letter/a/ebca7d/32.png) [@arzayus84](https://universal-blue.discourse.group/u/arzayus84)\
**Post date:** [August 27, 2024, 9:06pm UTC](https://universal-blue.discourse.group/t/got-myself-into-a-bit-of-trouble-cant-update/1176/15 "2024-08-27T21:06:55Z")

</div>

Something seems to be corroborating and is just stuck in that version.

---

<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:** [August 28, 2024, 5:53am UTC](https://universal-blue.discourse.group/t/got-myself-into-a-bit-of-trouble-cant-update/1176/16 "2024-08-28T05:53:00Z")

</div>

Please paste in any information you may have when running the recommended commands.

---

<div class="post-metadata">

**Author:** ![arzayus84](https://avatars.discourse-cdn.com/v4/letter/a/ebca7d/32.png) [@arzayus84](https://universal-blue.discourse.group/u/arzayus84)\
**Post date:** [August 28, 2024, 1:11pm UTC](https://universal-blue.discourse.group/t/got-myself-into-a-bit-of-trouble-cant-update/1176/17 "2024-08-28T13:11:13Z")

</div>

I will for sure. Is there a way to unsigned an specific image? or maybe like reset that whole thing?