System Failed: Brew Update
After some update the message of 'Some System Updates Failed Systems Failed: Brew Update' started appearing. I ran ujust update and it all went fine, no errors or anything. Funny thing though - it didn't even try updating brew, that section just did not appear. I noticed I have
bash: /home/linuxbrew/.linuxbrew/bin/brew: No such file or directory on top of my terminal. I tried rebasing to 41 but I got:
error: Updating rpm-md repo 'rpmfusion-free-updates': Failed to download gpg key for repo 'rpmfusion-free-updates': Curl error (37): Could not read a file:// file for file:///etc/pki/rpm-gpg/RPM-GPG-KEY-rpmfusion-free-fedora-41 [Couldn't open file /etc/pki/rpm-gpg/RPM-GPG-KEY-rpmfusion-free-fedora-41]
So that's about the extent of my knowledge. So did brew somehow get wiped...? Any way to fix this? I suspect this happened with update to 42. Seems like it's not the answer to life, universe and everything.
Also this is the rpm-ostree status:
State: idle Deployments: ● ostree-image-signed:docker://ghcr.io/ublue-os/bazzite:stable Digest: sha256:20faa2b23b1d415f9182d38fc8c039114e11059511a4c189ffd5997d5f34b517 Version: 42.20250513 (2025-05-13T16:14:14Z) LayeredPackages: coolercontrol liquidctl ostree-image-signed:docker://ghcr.io/ublue-os/bazzite:stable Digest: sha256:1ef5fa460cf052572aa831ffb4ad1142af2f53e20910f867d99b8cf74cf8d6c0 Version: 42.20250511 (2025-05-12T03:51:29Z) LayeredPackages: coolercontrol liquidctl
Solution:
Jump to solution
So I sudo these 2 lines proposed by @tulip to reinstall brew and it seems to have worked so far. ujust update also does its thing properly now and updates brew. No more pop up.
Sorry for the @ just wanted to let you know this issue is still present. I'm guessing it's more popular but people that don't use brew like me just don't notice it till that pop up starts showing up....
24 Replies
Try
brew doctor to see if that fixes your issuebash: brew: command not found seems like there's no brew in my bazzite:huh:
🤔 what do you get from
systemctl brew-setup.service ?
the cavalry is here 😄What happens when you type
which brewIn red
Unknown command verb 'brew-setup.service'.
/usr/bin/which: no brew in (/home/Ares/.local/bin:/home/Ares/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin)
I'm not an expert but that one looks pretty damn funkyoops my bad
systemctl status brew-setup.service○ brew-setup.service - Setup Brew Loaded: loaded (/usr/lib/systemd/system/brew-setup.service; enabled; preset: enabled) Drop-In: /usr/lib/systemd/system/service.d └─10-timeout-abort.conf Active: inactive (dead) Condition: start condition unmet at Wed 2025-05-14 16:11:14 CEST; 2h 24min ago └─ ConditionPathExists=!/var/home/linuxbrew/.linuxbrew was not met May 14 16:11:14 bazzite systemd[1]: brew-setup.service - Setup Brew was skipped because of an unmet condition > lines 1-9/9 (END)
I'm going to leave this to the experts.
I've been getting something similar for a few weeks now.
What is strange I have no issue running ujust update, brew update, brew doctor; however, I continue to receive popup notifications that it uupd Brew update failed.
systemctl status brew-setup.service
○ brew-setup.service - Setup Brew
Loaded: loaded (/usr/lib/systemd/system/brew-setup.service; enabled; preset: enabled)
Drop-In: /usr/lib/systemd/system/service.d
└─10-timeout-abort.conf
Active: inactive (dead)
Condition: start condition unmet at Tue 2025-05-13 17:17:09 EDT; 1 day 14h ago
└─ ConditionPathExists=!/var/home/linuxbrew/.linuxbrew was not met
May 13 17:17:09 epoch systemd[1]: brew-setup.service - Setup Brew was skipped because of an unmet condition check (ConditionPathExists=!/var/home/linuxbrew/.linuxbrew).is it normal to have two linuxbrew folder structures? One is hidden inside linuxbrew folder with the exact same folders and files
I do not use brew often enough to know for sure, but I can tell you that my
/home/linuxbrew folder only contains the .linuxbrew folder which as the contents of yours
I don't know why yours has the contents of .linuxbrew in the /home/linuxbrew folderLet me check where brew itself is installed on the image. Maybe if you directly point to the binary and then do doctor it might help?
I've never seen this issue before
looks like its not actually on the image, its just pushed to the home folder
at install
When did you guys install Bazzite?
I don't have all of the contents inside /home/linuxbrew either
its under /home/linuxbrew/.linuxbrew
Can you guys go to terminal and do this command:
/var/home/linuxbrew/.linuxbrew/brew doctorbash: /var/home/linuxbrew/.linuxbrew/brew: No such file or directory That's what the structure looks like in my case. I've installed either last year of beginning of this year. Looking at some files, January 2025
try it without .linuxbrew
/var/home/linuxbrew/bin/brew doctor
I honestly don't know how your homebrew files got all garbled up like that
this is definitely all wrong
let's hope
/var/home/linuxbrew/bin/brew doctor does something
oh sorry it was supposed to be /var/home/linuxbrew/.linuxbrew/bin/brew doctor I forgot /bin/
otherwise just try and find where the brew executable is and launch it from terminal with doctor argumentspitballing some ideas -- the main brew installer only installs to
/home/linuxbrew, so that might be a nuclear option to manually reinstall itthat's an idea too
Yeah, no idea what got fucked during some update. That's fun. I'll be honest, I half expect that I'll install brew and few updates later end up with 2 brews
same I've had bazzite installed for well over a year, a recent update changed something
or maybe I installed a brew for testing at some point, this is what I get when I print out the list
/var/home/linuxbrew$ brew list
==> Formulae
berkeley-db@5 expat f3 gdbm libxcrypt perl wakeonlan
==> CasksSeems like this issue existed for a while https://github.com/ublue-os/bazzite/issues/2132
Seems like relevant bluefin threads:
https://universal-blue.discourse.group/t/brew-command-not-found-on-blufin/6890
https://universal-blue.discourse.group/t/homebrew-not-installed/6797
https://github.com/ublue-os/bluefin/issues/2154#issuecomment-2611488708
GitHub
homebrew install broken · Issue #2132 · ublue-os/bazzite
Describe the bug Grabbed gnome-stable from bazzite.gg on 12 Jan CET and did a fresh install on bare metal from the bootable image. .linuxbrew/bin/brew was missing and ownerships were screwy. .linux...
Universal Blue
Brew: command not found on Blufin
Brew was working fine yesterday on my Blufin. Yesterday I have poweroff laptop and today I have turned it on. Executing command: brew I get: “bash: brew: command not found”. which brew returns: “/usr/bin/which: no brew in (/var/home/user1/.local/bin:/var/home/user1/bin:/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin)” It looks like ...
Universal Blue
Homebrew not installed
Hello, I thought bluefin would come with homebrew installed. However I get the error message: pbeccard@rubicon:~$ brew bash: brew: Kommando nicht gefunden. Am I doing something wrong? pbeccard@rubicon:~$ cat /etc/os-release NAME="Bluefin" VERSION="41.20250209.1 (Silverblue)" RELEASE_TYPE=stable ID=bluefin ID_LIKE="fedora" VERSION_ID=41 VERS...
GitHub
Brew broke · Issue #2154 · ublue-os/bluefin
Describe the bug All brew commands, besides brew info, fail. What did you expect to happen? I expected brew to work properly, as per usual. Output of bootc status No staged image present Current bo...
Solution
So I sudo these 2 lines proposed by @tulip to reinstall brew and it seems to have worked so far. ujust update also does its thing properly now and updates brew. No more pop up.
Sorry for the @ just wanted to let you know this issue is still present. I'm guessing it's more popular but people that don't use brew like me just don't notice it till that pop up starts showing up.
https://github.com/ublue-os/bazzite/commit/223dc7147591aa4d560b6433dbc831aa6b7ff520
Do you guys happen to update using a desktop shortcut of System Update?
Okay never mind it seems unrelated? We need to figure out how to reproduce it, because I just can't
I run ujust update or use the system update option in the start menu (KDE)
Any time I manually update I use
ujust update