Not wanting to be a party pooper but I for one am running Garuda, RebornOS, BlueStar and in each I’ve been using Garuda Welcome to launch assistant to update keyrings cause if you have 3rd party repos added at least the CachyOS ones it won’t break them like updating keyrings thru RANI will. So it would be nice to have the Garuda Settings Manager back working under Garuda Welcome.
Danke für deinen Post.
Könntest du bitte das Problem mit dem cachyos keyring und Garuda Rani genauer beschreiben?
Leider ist Garuda Settings Manager und Garuda Welcome von Garuda Linux entfernt worden, da sie durch Rani ersetzt wurden. Garuda Settings Manager kann also nicht mehr installiert werden.
3 Likes
Would use Rani to update the Keyrings then run garuda-update and it would tell me no mirrorlist for the Cachy repos. Reinstall the Cachy repos, run garuda-update and all’s good. couple weeks later update the keyrings through Rani, run garuda-update and get the same thing. Couple of weeks later update the keyrings through Garuda-Welcome / Assistant, update via garuda-update and all’s good. This wasn’t a one off two different machines with three separate installs.
On another note including the last boot into the live environment the Randi window that’s suppose to be there is just a purple rectangle with nothing on it, not even the top buttons. On actual install of Garuda and first manual launch of Rani it opens in full screen making one have to resize it and use Window Rules to keep it to a specific size on subiquint launches.
I just built a new system so my roommate can have this one, so later today or tomorrow I will be doing a fresh install. We can see how Rani plays now since it’s been sometime since I’ve used it, before the one update to it that was talked about on here.
Think it would be prudent to move our posts to a new thread so as not to hijack this one. If you create the new thread just leave the language in you first post as is cause I can just hit the translate button if I need to reference it.
Rani does not modify the cachyos mirrorlist files in any way.
This might be one for @dr460nf1r3
1 Like
All I can tell you is what it was doing vS what Garuda-Assistant was doing.
I’m running Garuda, my install is 880 Days old, no issues, no ignores and passes all the new health checks.
CachyOS is very nice, on a separate SSD I built an identical CachyOS system to my Garuda build, the theme was different, liked it, and very nearly unplugged the Garuda SSD. But in the end I’m back to Garuda, there is just something about these purple fonts………
I would though give CachyOS a serious go and I’ve put it on a couple of Laptops with good success.
The Cachy repos are added for those couple of programs that aren’t in Garuda, Chaotic, the standard repos or the AUR. My 3 go to’s are BlueStar, Garuda, and RebornOS.
I’ll look into it at given time.
Though all Rani does is executing Garuda update functionality. Which toggle is it exactly that was used here? Maybe the following one?
(Are there terminal logs @Locutus ?)
1 Like
I just attempted to run the function and I guess now you guys are in the process of adding it back. I really should of reported it shortly after Rani was released. My bad cause I just went back to using Garuda-Assistant instead of reporting. Launching Rani from the terminal I get the below.
INFO [13:07:00.318]: Renderer - Loaded 0 settings from store
INFO [13:07:00.529]: Renderer - Not first boot
INFO [13:07:00.695]: Renderer - Last update: 2025-08-11T10:52:56.000Z
ERROR [13:07:00.695]: Renderer - Failed to get aur updates: bash: line 1: paru: command not found
INFO [13:07:17.393]: Renderer - Refreshing mirrors
INFO [13:07:17.645]: Renderer - Refreshing mirrors
INFO [13:07:17.897]: Renderer - Refreshing mirrors
INFO [13:07:18.111]: Renderer - Refreshing mirrors
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.
I was investigating this again right now. If you click this, then some resetting is definitely expected. Garuda-update remote scripts are basically meant to be a way out when your system is ■■■■ed in one way or another (can even fix broken Pacman), which is also indicated by the tab being named “rescue tools”.
Because this happens:
this.logger.info('Running remote keyring');
return await this.taskManager.executeAndWaitBashTerminal('GARUDA_UPDATE_RANI=1 garuda-update remote keyring');
Which translates to:
if [ "$keyring" = true ]; then
rm -rf /etc/pacman.d/gnupg
rm -rf /var/lib/pacman/sync
pacman-key --init
pacman-key --populate || { echo -e "\033[1;31m\nFailed to populate keyrings\n\033[0m"; }
pacman-key --recv-key 3056513887B78AEB 6D42BDD116E0068F --keyserver keyserver.ubuntu.com && pacman-key --lsign-key 3056513887B78AEB 6D42BDD116E0068F || { echo -e "\033[1;31m\nFailed to install some keys\n\033[0m"; }
pacman-key --keyserver keyserver.ubuntu.com --refresh-keys 67BF8CA6DA181643C9723B4ED6C9442437365605 || { echo -e "\033[1;31m\nFailed to ensure some keys are up to date\n\033[0m"; }
rm /var/cache/pacman/pkg/* || true
fi
if [ "$keyring" = true ]; then
SKIP_AUTOSNAP=1 SNAP_PAC_SKIP=y $pacman -Sy archlinux-keyring chaotic-keyring --noconfirm
fi
After this, CachyOS keyrings are certainly gone. But mirror list should be still available (that’s being reset with another garuda-update remote command).
I’ve adapted the wording to be more specific about this fact, and also added a new “regular” maintenance option which simply runs pacman-key --refresh-keys.
This has also been fixed today.
4 Likes