Gsettings conflicts due to homebrew installation

Community
1

Hi all,

Yesterday I realized I could not adjust my font scaling via terminal anymore. gsettings set org.gnome.desktop.interface text-scaling-factor appeared to work, as I could get or monitor the values and confirm the input was being registered, but the interface would not react.

I then tried dconf watch / and confirmed that my changes were not being received correctly.

After a bit of digging, I realized homebrew seems to be the source of my problem:

> which gsettings
/home/linuxbrew/.linuxbrew/bin/gsettings

Turns out I have glib installed, which I am pretty sure it came as a dependency of openjdk, which I installed a couple of days ago.

Now, I don’t need openjdk anymore and can solve the problem by removing it. Before doing so, I was wondering if anyone has opinions as to how I would need to tackle this problem if I needed openjdk.

Thanks!

2

This is an upstream homebrew problem. When you eval homebrew’s environment, it prioritizes its binaries and libraries over system libraries. For the most part, this works fine, but can cause issues.

Some distros like Bluefin that preinstall brew do some hacks to prevent this, such as by preventing binaries like systemctl and dbus from going on the path. Also, they make it so that system libraries are prioritized over homebrew ones (so instead of system libraries breaking, the homebrew ones may break instead).

So you can either copy their tweaks to reduce the chances of breakages, or stop using brew until brew comes up with a better system (assuming they ever want to try and address the issue).

3

Thanks for the explanation and the pointers. I guess I’ll take the easy way out and uninstall openjdk then. :stuck_out_tongue: