How to keep Garuda up to date and rolling?

So initially I had an issue with fastfetch where the fastfetch info was not showing in konsole. It was showing error that it could not find the dr460nized config file. I have resolved it now thanks to octopi package manager and some old posts in the forum. But that process made me realize another possible issue.

Basically the Garuda on this machine(desktop) is multiple years old. Maybe ~2020. I have ran the updates regularly using garuda-update. So I assumed everything was kept up-to-date and rolling except for things that I explicitly excluded in pacman.conf. Then in December 2023 I freshly installed Garuda on my laptop (second device). That fastfetch issue was not present on my laptop. So I checked the fastfetch version on both devices and the laptop has 2.12 (extra) while the desktop had 1.55 from AUR and updates are done. I uninstalled that and installed 2.12 which solved my fastfetch issue.

But since I had all updates done, why was fastfetch not moved from AUR to extra or whatever the Garuda devs have chosen? Am I missing some step to keep my computers updated? I used Arco Linux before and Eric Dubois used to mention running an alias command skel to keep all configs updated. Is there an extra step like that in Garuda? Or is “garuda-update” enough for everything? Do you have any recommendations for me to ensure complete update?

  Kernel: 6.8.9-zen1-2-zen arch: x86_64 bits: 64 compiler: gcc v: 14.1.1 clocksource: hpet
    avail: acpi_pm parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
    root=UUID=bb017815-b349-4750-bd98-a9b9f9b0382e rw rootflags=subvol=@ quiet quiet
    rd.udev.log_priority=3 vt.global_cursor_default=0 loglevel=3 ibt=off
  Desktop: KDE Plasma v: 6.0.4 tk: Qt v: N/A info: frameworks v: 6.2.0 wm: kwin_wayland vt: 1
    dm: SDDM Distro: Garuda base: Arch Linux
  Type: Desktop Mobo: Micro-Star model: B350M PRO-VDH (MS-7A38) v: 2.0 serial: <superuser required>
    uuid: <superuser required> UEFI: American Megatrends LLC. v: A.L4 date: 05/17/2023
  Info: model: AMD Ryzen 3 2200G with Radeon Vega Graphics bits: 64 type: MCP arch: Zen level: v3
    note: check built: 2017-19 process: GF 14nm family: 0x17 (23) model-id: 0x11 (17) stepping: 0
    microcode: 0x8101016
  Topology: cpus: 1x cores: 4 smt: <unsupported> cache: L1: 384 KiB desc: d-4x32 KiB; i-4x64 KiB
    L2: 2 MiB desc: 4x512 KiB L3: 4 MiB desc: 1x4 MiB
  Speed (MHz): avg: 3014 high: 3500 min/max: 1600/3500 boost: enabled scaling:
    driver: acpi-cpufreq governor: performance cores: 1: 3500 2: 3500 3: 3500 4: 1558 bogomips: 27947
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  Vulnerabilities: <filter>
  Device-1: AMD Raven Ridge [Radeon Vega Series / Radeon Mobile Series] driver: amdgpu v: kernel
    arch: GCN-5 code: Vega process: GF 14nm built: 2017-20 pcie: gen: 3 speed: 8 GT/s lanes: 16
    ports: active: HDMI-A-1 empty: DP-1,DVI-D-1,DVI-D-2 bus-ID: 30:00.0 chip-ID: 1002:15dd
    class-ID: 0300 temp: 48.0 C
  Display: wayland server: v: with: Xwayland v: 23.2.7 compositor: kwin_wayland
    driver: X: loaded: amdgpu unloaded: modesetting alternate: fbdev,vesa dri: radeonsi gpu: amdgpu
    display-ID: 0
  Monitor-1: HDMI-A-1 res: 1920x1080 size: N/A modes: N/A
  API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi device: 1 drv: swrast
    surfaceless: drv: radeonsi wayland: drv: radeonsi x11: drv: radeonsi inactive: gbm
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 24.0.7-arch1.3 glx-v: 1.4
    direct-render: yes renderer: AMD Radeon Vega 8 Graphics (radeonsi raven LLVM 17.0.6 DRM 3.57
    6.8.9-zen1-2-zen) device-ID: 1002:15dd memory: 1.95 GiB unified: no display-ID: :1.0
  API: Vulkan v: 1.3.279 layers: 9 device: 0 type: integrated-gpu name: AMD Radeon Vega 8
    Graphics (RADV RAVEN) driver: mesa radv v: 24.0.7-arch1.3 device-ID: 1002:15dd
    surfaces: xcb,xlib,wayland device: 1 type: cpu name: llvmpipe (LLVM 17.0.6 256 bits)
    driver: mesa llvmpipe v: 24.0.7-arch1.3 (LLVM 17.0.6) device-ID: 10005:0000
    surfaces: xcb,xlib,wayland
  Device-1: AMD Raven/Raven2/Fenghuang HDMI/DP Audio vendor: Micro-Star MSI driver: snd_hda_intel
    v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 30:00.1 chip-ID: 1002:15de class-ID: 0403
  Device-2: AMD Family 17h/19h HD Audio vendor: Micro-Star MSI driver: snd_hda_intel v: kernel
    pcie: gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 30:00.6 chip-ID: 1022:15e3 class-ID: 0403
  API: ALSA v: k6.8.9-zen1-2-zen status: kernel-api with: aoss type: oss-emulator tools: N/A
  Server-1: PipeWire v: 1.0.6 status: active with: 1: pipewire-pulse status: active
    2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
  Device-1: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet vendor: Micro-Star MSI
    driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: f000 bus-ID: 25:00.0
    chip-ID: 10ec:8168 class-ID: 0200
  IF: enp37s0 state: up speed: 100 Mbps duplex: full mac: <filter>
  IF-ID-1: outline-tun0 state: down mac: N/A
  Info: services: NetworkManager, smbd, systemd-timesyncd
  Local Storage: total: 1.58 TiB used: 220.95 GiB (13.6%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung model: SSD 980 500GB size: 465.76 GiB
    block-size: physical: 512 B
 logical: 512 B speed: 31.6 Gb/s lanes: 4 tech: SSD serial: <filter>
    fw-rev: 1B4QFXO7 temp: 39.9 C scheme: GPT
  ID-2: /dev/sda maj-min: 8:0 vendor: Western Digital model: WD5000AAKX-753CA0 size: 465.76 GiB
    block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s tech: N/A serial: <filter>
    fw-rev: 1H15 scheme: GPT
  ID-3: /dev/sdb maj-min: 8:16 vendor: Toshiba model: MK5076GSX size: 465.76 GiB block-size:
    physical: 512 B logical: 512 B speed: 3.0 Gb/s tech: HDD rpm: 5400 serial: <filter> fw-rev: 2D
    scheme: GPT
  ID-4: /dev/sdc maj-min: 8:32 vendor: Crucial model: CT240BX500SSD1 size: 223.57 GiB block-size:
    physical: 512 B logical: 512 B speed: 6.0 Gb/s tech: SSD serial: <filter> fw-rev: 056 scheme: GPT
  ID-1: / raw-size: 465.46 GiB size: 465.46 GiB (100.00%) used: 114.74 GiB (24.7%) fs: btrfs
    dev: /dev/nvme0n1p2 maj-min: 259:2
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%) used: 6.4 MiB (2.1%) fs: vfat
    dev: /dev/nvme0n1p1 maj-min: 259:1
  ID-3: /home raw-size: 465.46 GiB size: 465.46 GiB (100.00%) used: 114.74 GiB (24.7%) fs: btrfs
    dev: /dev/nvme0n1p2 maj-min: 259:2
  ID-4: /var/log raw-size: 465.46 GiB size: 465.46 GiB (100.00%) used: 114.74 GiB (24.7%)
    fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
  ID-5: /var/tmp raw-size: 465.46 GiB size: 465.46 GiB (100.00%) used: 114.74 GiB (24.7%)
    fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
  Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
  ID-1: swap-1 type: zram size: 5.7 GiB used: 354.5 MiB (6.1%) priority: 100 comp: zstd
    avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 4 dev: /dev/zram0
  System Temperatures: cpu: 39.0 C mobo: 42.0 C gpu: amdgpu temp: 47.0 C
  Fan Speeds (rpm): fan-1: 0 fan-2: 975 fan-3: 1200 fan-4: 0 fan-5: 0
  Power: 12v: N/A 5v: N/A 3.3v: 3.38 vbat: 3.28
  Memory: total: 6 GiB available: 5.7 GiB used: 2.46 GiB (43.1%)
  Processes: 241 Power: uptime: 14m states: freeze,mem,disk suspend: deep avail: s2idle
    wakeups: 0 hibernate: platform avail: shutdown, reboot, suspend, test_resume image: 2.26 GiB
    services: org_kde_powerdevil,upowerd Init: systemd v: 255 default: graphical tool: systemctl
  Packages: pm: pacman pkgs: 2230 libs: 592 tools: octopi,pamac,paru,yay Compilers: gcc: 14.1.1
    Client: shell wrapper v: 5.2.26-release inxi: 3.3.34
Garuda (2.6.26-1):
  System install date:     2021-02-28
  Last full system update: 2024-05-18
  Is partially upgraded:   No
  Relevant software:       snapper NetworkManager dracut
  Windows dual boot:       Probably (Run as root to verify)
  Failed units:            fancontrol.service nfs-server.service 

Garuda Linux does not install any AUR packages, during the installation process or at any time afterward. It must have been a package you installed on your own.

My guess is the reason it became so out of date is you weren’t updating it. By default, AUR packages are not updated with the rest of the system.

If you choose to install AUR packages and wish to update them along with the rest of your system, you can accomplish this by adding the -a flag to the garuda-update command.

garuda-update -a

You can also accomplish this without passing a flag by setting the UPDATE_AUR=1 environment variable in /etc/garuda/garuda-update/config. See also this article: Garuda Update | Garuda Linux wiki

Garuda Assistant has a few configs that can be reset this way (it just copies the latest version from /etc/skel and overwrites the version in your home directory). This will pull in the latest changes–however, be warned you will lose any changes you have made to those configs.

A slightly less automatic way to pull the latest updates out of the files in /etc/skel would be to use Meld. For example:

meld /etc/skel/.config/fish/ ~/.config/fish/

This would allow you to see what changes are in /etc/skel that you don’t have, and decide piecemeal if you want to bring anything over.

In general though, you don’t need to worry about it too much unless something isn’t working. Simply keeping your system up to date is far more crucial than topping off every little config file, and it sounds like you are already doing a good job with that.

Kudos on keeping your original install going, that’s one of the oldest ones around! :partying_face:


This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.