# Bazzite will not update, please help

**URL:** <https://universal-blue.discourse.group/t/bazzite-will-not-update-please-help/12424>\
**Category:** Bazzite\
**Created:** [August 27, 2026, 3:05am UTC](https://universal-blue.discourse.group/t/bazzite-will-not-update-please-help/12424 "2026-08-27T03:05:43Z")\
**Posts on this page:** 16\
**Page:** 1

<div class="post-metadata">

**Author:** ![Undying](https://avatars.discourse-cdn.com/v4/letter/u/a9a28c/32.png) [@Undying](https://universal-blue.discourse.group/u/Undying)\
**Post date:** [August 27, 2026, 3:05am UTC](https://universal-blue.discourse.group/t/bazzite-will-not-update-please-help/12424/1 "2026-08-27T03:05:43Z")

</div>

I have been trying to get Bazzite to update for some time now and have been going between posts that I can find but come up short.

I believe the issue has something to do with ostree being labeled as a read-only file, but I might be missing something. I have tried telling the consel to reset ostree, tried using the usroverlay command, even tried looking at making a new sysroot path to try and be able to update, only for every command to be shut down with the file being read-only.

The photo is the majority of what I repeatedly get when trying to update, though this time it actually tried to fetch the update instead of telling me it couldn’t change anything. I also do not know a lot about bazzite or Linux code in general, so I may have severally missed something.

It should also be noted that things have slowly began to stop working. Steam will not launch games and Mozzila says that it is running an instance despite there not being one open, and it is bad enough to where my computer even gives a message before letting me shut it off, and I am fairly certain it is connected to the issue since they appeared when I started trying to update before actually trying to change things.

 ![2300](https://global.discourse-cdn.com/free1/uploads/univeral_blue/original/2X/0/041e3ab73c584089c663dddeb04c17d6da2cfa9d.jpeg)

---

<div class="post-metadata">

**Author:** ![Arkalim](https://avatars.discourse-cdn.com/v4/letter/a/7feea3/32.png) [@Arkalim](https://universal-blue.discourse.group/u/Arkalim)\
**Post date:** [August 27, 2026, 8:25am UTC](https://universal-blue.discourse.group/t/bazzite-will-not-update-please-help/12424/2 "2026-08-27T08:25:30Z")

</div>

It even says in red, ‘upgrade’ components failed. Try running “ujust upgrade” to update Bazzie revision, and then update components to latest versions with ‘ujust update’. And don’t forget the restarts.

---

<div class="post-metadata">

**Author:** ![Undying](https://avatars.discourse-cdn.com/v4/letter/u/a9a28c/32.png) [@Undying](https://universal-blue.discourse.group/u/Undying)\
**Post date:** [August 28, 2026, 12:47am UTC](https://universal-blue.discourse.group/t/bazzite-will-not-update-please-help/12424/3 "2026-08-28T00:47:55Z")

</div>

ujust upgrade gives the same exact error as ujust update

---

<div class="post-metadata">

**Author:** ![GhostOfGaby](https://yyz2.discourse-cdn.com/free1/user_avatar/universal-blue.discourse.group/ghostofgaby/32/9810_2.png) [@GhostOfGaby](https://universal-blue.discourse.group/u/GhostOfGaby)\
**Post date:** [August 28, 2026, 1:07am UTC](https://universal-blue.discourse.group/t/bazzite-will-not-update-please-help/12424/4 "2026-08-28T01:07:24Z")

</div>

Do you have packages layered (installed directly with rpm-ostree)?  
One of the packages could be causing a conflict which blocks the upgrade.

---

<div class="post-metadata">

**Author:** ![Undying](https://avatars.discourse-cdn.com/v4/letter/u/a9a28c/32.png) [@Undying](https://universal-blue.discourse.group/u/Undying)\
**Post date:** [August 28, 2026, 1:26am UTC](https://universal-blue.discourse.group/t/bazzite-will-not-update-please-help/12424/5 "2026-08-28T01:26:58Z")

</div>

From what I can tell, it isnt layered. rpm-ostree search gives the error “bash: syntax error near unexpected token ‘newline’”. The uninstall command gives the same result, but doing rpm-ostree reset gives me the message “No change.”

---

<div class="post-metadata">

**Author:** ![GhostOfGaby](https://yyz2.discourse-cdn.com/free1/user_avatar/universal-blue.discourse.group/ghostofgaby/32/9810_2.png) [@GhostOfGaby](https://universal-blue.discourse.group/u/GhostOfGaby)\
**Post date:** [August 28, 2026, 1:49am UTC](https://universal-blue.discourse.group/t/bazzite-will-not-update-please-help/12424/6 "2026-08-28T01:49:49Z")

</div>

Looked at your picture again, it seems your file system is read-only, it tried to delete a stuck file. Try these command to check what is causing it

```bash
# Find the file
sudo find /sysroot/ostree/deploy/default/deploy/ba9d53eb602f94484e77cd* -name 'yaml-indent-strict.yaml.txt'

# use the file path to check/clear its immutable attribute
sudo lsattr <path-to-file>
sudo chattr -i <path-to-file>

# can also try to clean you deployment and try again. 
sudo rpm-ostree cleanup -p
sudo rpm-ostree upgrade

```

---

<div class="post-metadata">

**Author:** ![Undying](https://avatars.discourse-cdn.com/v4/letter/u/a9a28c/32.png) [@Undying](https://universal-blue.discourse.group/u/Undying)\
**Post date:** [August 28, 2026, 2:20am UTC](https://universal-blue.discourse.group/t/bazzite-will-not-update-please-help/12424/7 "2026-08-28T02:20:32Z")

</div>

sudo lstattr gave me back the same file path from the find command. sudo chattr -i \< path-to-file \> gave me back this:

chatte: Read-only file system while setting flags on \< path-to-file \>

Everything I try seems to always say whatever file is a Read-only file. The cleanup command didn’t work either, giving me this:

error: cleanup: Invoking cleanup: GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark.\_g\_2dio\_2derror\_2dquark.Code13: Remounting /sysroot read-write: Invalid argument

---

<div class="post-metadata">

**Author:** ![GhostOfGaby](https://yyz2.discourse-cdn.com/free1/user_avatar/universal-blue.discourse.group/ghostofgaby/32/9810_2.png) [@GhostOfGaby](https://universal-blue.discourse.group/u/GhostOfGaby)\
**Post date:** [August 28, 2026, 2:35am UTC](https://universal-blue.discourse.group/t/bazzite-will-not-update-please-help/12424/8 "2026-08-28T02:35:43Z")

</div>

```bash
# check if the entire subvolume is set to read only or if btrfs saw an error and locked itself
sudo btrfs property get /sysroot ro
sudo btrfs device stats /sysroot

# if that returns true, set it to false and retry upgrade
sudo btrfs property set -f /sysroot ro false
sudo rpm-ostree upgrade

```

---

<div class="post-metadata">

**Author:** ![Arkalim](https://avatars.discourse-cdn.com/v4/letter/a/7feea3/32.png) [@Arkalim](https://universal-blue.discourse.group/u/Arkalim)\
**Post date:** [August 28, 2026, 4:54am UTC](https://universal-blue.discourse.group/t/bazzite-will-not-update-please-help/12424/9 "2026-08-28T04:54:54Z")

</div>

Oh, I missed that aswell. I thought he just had removed file access for writing.

Just to clarify, you didn’t accidentally install the package/live version of it, right? Cause if it is a new install or a packaged/live one, it would have been easier and faster to just ‘repair’ for a non-packaged/live version of bazzite.

I guess, i’ll add it here. If you get the file system fixed, and want to install custom software. But it either fails completely or gives you the blank screen. Try using Flatseal to give the program rights to some (either system or account) folders. Cause, of course, that is a thing.

---

<div class="post-metadata">

**Author:** ![Undying](https://avatars.discourse-cdn.com/v4/letter/u/a9a28c/32.png) [@Undying](https://universal-blue.discourse.group/u/Undying)\
**Post date:** [August 28, 2026, 11:34pm UTC](https://universal-blue.discourse.group/t/bazzite-will-not-update-please-help/12424/10 "2026-08-28T23:34:13Z")

</div>

ro is already set to false, however the device stats says “[/dev/nvme0n1p3].corruption\_errs 48”

Also something to add, I thought about rolling back the version to maybe be able to update from an older version. It will not let me because its an invalid argument (?) Rebasing also fails, same reason.

More to add, looked in fastfetch, thinking maybe that would give me something, and it says btrfs is set to read-only. Trying to set it to false gets refused for it being read-only file system.

---

<div class="post-metadata">

**Author:** ![Undying](https://avatars.discourse-cdn.com/v4/letter/u/a9a28c/32.png) [@Undying](https://universal-blue.discourse.group/u/Undying)\
**Post date:** [August 28, 2026, 11:35pm UTC](https://universal-blue.discourse.group/t/bazzite-will-not-update-please-help/12424/11 "2026-08-28T23:35:49Z")

</div>

I do not know, but I’ve had the software installed for a while now, at least 3-6 months, if not longer, so it seems weird that it would remove access now of all times. I should also note that it started happening in the middle of using the computer, not upon booting it up, so it would be extra weird if that was the cause.

---

<div class="post-metadata">

**Author:** ![GhostOfGaby](https://yyz2.discourse-cdn.com/free1/user_avatar/universal-blue.discourse.group/ghostofgaby/32/9810_2.png) [@GhostOfGaby](https://universal-blue.discourse.group/u/GhostOfGaby)\
**Post date:** [August 29, 2026, 12:30am UTC](https://universal-blue.discourse.group/t/bazzite-will-not-update-please-help/12424/12 "2026-08-29T00:30:48Z")

</div>

You might have to back up your data if it’s showing corruption errors

```bash
# check ssd health
sudo smartctl -a /dev/nvme0n1p3

```

---

<div class="post-metadata">

**Author:** ![Undying](https://avatars.discourse-cdn.com/v4/letter/u/a9a28c/32.png) [@Undying](https://universal-blue.discourse.group/u/Undying)\
**Post date:** [August 29, 2026, 12:55am UTC](https://universal-blue.discourse.group/t/bazzite-will-not-update-please-help/12424/13 "2026-08-29T00:55:16Z")

</div>

From what I can tell, SSD health is fine. Everything looks correct, no errors or reports, literally everything is in working order as far as hardware goes.

---

<div class="post-metadata">

**Author:** ![GhostOfGaby](https://yyz2.discourse-cdn.com/free1/user_avatar/universal-blue.discourse.group/ghostofgaby/32/9810_2.png) [@GhostOfGaby](https://universal-blue.discourse.group/u/GhostOfGaby)\
**Post date:** [August 29, 2026, 5:46pm UTC](https://universal-blue.discourse.group/t/bazzite-will-not-update-please-help/12424/14 "2026-08-29T17:46:58Z")

</div>

Out of ideas. Try to find which files might causing the error or screen logs for corruption

```bash
sudo dmesg -T | grep -i 'btrfs.*csum\|btrfs.*error' | tail -150

```

---

<div class="post-metadata">

**Author:** ![Undying](https://avatars.discourse-cdn.com/v4/letter/u/a9a28c/32.png) [@Undying](https://universal-blue.discourse.group/u/Undying)\
**Post date:** [August 29, 2026, 6:14pm UTC](https://universal-blue.discourse.group/t/bazzite-will-not-update-please-help/12424/15 "2026-08-29T18:14:24Z")

</div>

All honesty, I just went and saved everything I needed to a Hard Drive and reinstalled Bazzite. Whatever I went and did just completely Fd it over. Thanks for trying, though.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/free1/uploads/univeral_blue/original/2X/e/e39f7d1952979cf23b0f8d634e025fb38da50026.png) [@system](https://universal-blue.discourse.group/u/system)\
**Post date:** [September 1, 2026, 6:14pm UTC](https://universal-blue.discourse.group/t/bazzite-will-not-update-please-help/12424/16 "2026-09-01T18:14:51Z")

</div>

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.
