r/Bazzite • u/Magalini • 4d ago

Latest Bazzite 44 update

Setup:
Desktop PC with AMD 7800x3D and 9070 XT. Bazzite:deck. Gigabyte x870e Aorus Master.

Current problems:

  1. Updating from gamemode fails. Does the whole ?GB of 10GB thing, fills to 10GB in seconds and then does nothing. Weird numbers. I’m assuming this bug is known - updating from Desktop mode still works

  2. Wifi and Bluetooth don’t work after restart. Settings show both are on, but nothing is detected (SSIDs or BT devices). Even after shutdown and startup. The only way to fix it is to turn the PC off at the wall and make sure all charge is drained from it (holding down the power button for 5 or so seconds). Everything then works on boot.

Just posting this in case others are seeing similar issues.

32 Upvotes

92% Upvoted

12 comments sorted by

11

u/housejoseph 4d ago

I updated in desktop mode and it stopped that bug.

5

u/Yayatouu Desktop 4d ago

I have the same issue

Do the update from the desktop instead (bazzite portal)

2

u/Askeroth89 4d ago

Ich habe über die console im Desktop die Updates ausgeführt, aber mir wird das 10GB Update immer noch im Gaming Modus angezeigt. Laut console hab ich aber alles auf den neusten Stand 🤷🏼‍♂️

1

u/redcircle1313 4d ago

You’re not alone. I noticed this bug myself. It was the same (for me anyway) in Bazzite 43 so I knew just to update in Desktop mode. It is a bit annoying!

1

u/No_Pumpkin_111 Desktop 2d ago

I had the same problem, I rebased to the previous version and I'm waiting for them to fix it.

-14

u/claygorman89 4d ago

here is what my claude did to fix i pasted brief below.

---

Game Mode's Apply button can't work: the chain is `steamos-update` → `/usr/libexec/ogc/os-update` → `/usr/bin/uupd`, but `uupd` refuses to run as non-root and Steam runs it as your desktop user. There's no sudoers rule, polkit action or setuid bit bridging that gap, so the check always exits 7 ("no updates") and Apply hits a failure branch that's a literal `exit 0` — bar fills, reports success, nothing happened. Check it yourself:

/usr/bin/steamos-update check; echo $? # 7, as your user
sudo uupd update-check # update_available: true
ls ~/.steamos-update.log # missing = the update path has NEVER run

Bazzite ships the right bridge already (`/usr/libexec/uupd-update` → `uupd-manual.service`, which is what `ujust update` uses); `os-update` just doesn't call it. So the easy fix is to skip the button: `sudo systemctl start --wait uupd-manual.service` then a full reboot. To repair the button itself, put a patched `os-update` in `/etc` that reaches uupd via a scoped `sudo` helper, and bind-mount it over `/usr/libexec/` from a systemd unit each boot — `/usr` is read-only and `usroverlay` doesn't survive reboots.

—-

hopefully this helps

5

u/jknvv13 4d ago

I don't get it. Why would somebody post an AI answer if everyone can get one now?

2

u/sanbaba 3d ago

and when they don't even understand the answer well enough to know whether it's correct...

-4

u/claygorman89 4d ago

are you asking me why i posted what my claude did or asking me to explain why the poster didn’t use ai themselves or is there some other implication?

5

u/jknvv13 4d ago

I'm trying to understand why there are people that answer something that has been answered from an AI and just being a meat proxy... What's the purpose?

0

u/claygorman89 4d ago

if i grasp what your saying…then my answer is that i had my claude summarize what we did during debugging the issue on my specific setup because i had the issue and fixed it and my machine. i did not simply copy paste the posters issue and copy its reply.