Since a recent update ungoogle-chromium-bin
started setting itself as the default browser after each update.
(on KDE Plasma v5.27.10)
Can this behavior be disabled?
It quickly gets very annoying to always go to:
Settings => Applications => Default Applications => Toggle Web browser
back to what I had manually configured
Related Github issue with possible solutions:
https://github.com/ungoogled-software/ungoogled-chromium-archlinux/issues/260
Pinned Comments
networkException commented on 2025-05-02 13:41 (UTC)
Hello everyone, there's always a lot of confusion when ungoogled-chromium doesn't start because of a system dependency it can't find.
This issue is inherent to Arch Linux package management, there's no mechanism that tracks required rebuilds. Maintainers are expected to push manual pkgrel bumps once a rebuild is required. The
chromium
package can somewhat easily handle this, they can also update the package in testing first.People's comments here or on GitHub are how I notice that a rebuild is required, I try to push an update quickly then. Sadly a full rebuild currently takes over 24 hours on GitHub Actions and I'm not exactly maintaining open source software as my dayjob either, so this can take a while.
There's no solution for this really, other than adopting the package into the official repository maybe (I cannot do that). Note that for Manjaro users even a rebuild might not be enough as there can always be mismatches in what system library versions are available.
networkException commented on 2022-09-20 17:36 (UTC)
Please note that normally it's not required to flag this package as out of date. I usually tag releases in the main ungoogled-chromium repository and update the arch packaging right afterwards.
If the package hasn't updated after an ungoogled-chromium release GitHub Actions might still be building or the ungoogled-chromium patchset got updated for non Linux platforms only to match their upstream release cycle