Should I reinstall Garuda or trying to fix it in steps

Hello,

since a few months ago my Garuda installation seems to accumulate weird quirks, as I’m still kinda new to the whole Linux as a main driver experience I’m not to sure how to handle things from here.

My windows experience tells me it’s time to get rid of collected bloat and to just reinstall the whole operating system to start fresh.
The same behavior gets me every year with my web server (Debian).

From my understanding of Linux it should be more of a journey to fix what comes up, but quite frankly I’m not to sure what is causing some of my problems, which would range from chromium windows after a restart needing to be maximized again 2 times, cause the first time it will be optically leave out the space of the title bar while still being fully maximized leading to mouse interactions being of by the title bar in contrast to the mouse cursor position over to leaving the system running for 2 days and the system spontaneously freezing over random actions.

I would be interested in fixing the current state and take my learning from it instead of taking the easy way out with a fresh install and in line with that I would be happy for any clues one might have for me to track down these random quirks or whats just best practice in cases like this.

Greetings
Atafh

System:
  Kernel: 6.12.19-1-lts arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
    clocksource: tsc avail: hpet,acpi_pm
    parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-lts
    root=UUID=814b5a44-cc3e-4a96-af5e-86e325473144 rw rootflags=subvol=@
    quiet quiet rd.udev.log_priority=3 vt.global_cursor_default=0 loglevel=3
    ibt=off
  Desktop: KDE Plasma v: 6.3.3 tk: Qt v: N/A info: frameworks v: 6.12.0
    wm: kwin_wayland vt: 1 dm: SDDM Distro: Garuda base: Arch Linux
Machine:
  Type: Desktop Mobo: ASRock model: X570 Taichi serial: <superuser required>
    uuid: <superuser required> UEFI: American Megatrends v: P4.30
    date: 04/14/2021
CPU:
  Info: model: AMD Ryzen 7 5800X bits: 64 type: MT MCP arch: Zen 3+ gen: 3
    level: v3 note: check built: 2022 process: TSMC n6 (7nm) family: 0x19 (25)
    model-id: 0x21 (33) stepping: 0 microcode: 0xA20102D
  Topology: cpus: 1x dies: 1 clusters: 1 cores: 8 threads: 16 tpc: 2
    smt: enabled cache: L1: 512 KiB desc: d-8x32 KiB; i-8x32 KiB L2: 4 MiB
    desc: 8x512 KiB L3: 32 MiB desc: 1x32 MiB
  Speed (MHz): avg: 1752 min/max: 550/4851 boost: enabled scaling:
    driver: amd-pstate-epp governor: powersave cores: 1: 1752 2: 1752 3: 1752
    4: 1752 5: 1752 6: 1752 7: 1752 8: 1752 9: 1752 10: 1752 11: 1752 12: 1752
    13: 1752 14: 1752 15: 1752 16: 1752 bogomips: 121634
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  Vulnerabilities: <filter>
Graphics:
  Device-1: NVIDIA GP104 [GeForce GTX 1060 6GB] vendor: Micro-Star MSI
    driver: nvidia v: 570.124.04 alternate: nouveau,nvidia_drm
    non-free: 550/565.xx+ status: current (as of 2025-01; EOL~2026-12-xx)
    arch: Pascal code: GP10x process: TSMC 16nm built: 2016-2021 pcie: gen: 3
    speed: 8 GT/s lanes: 16 ports: active: none off: DP-1,DP-2,DP-3
    empty: DVI-D-1,HDMI-A-1 bus-ID: 0d:00.0 chip-ID: 10de:1b83 class-ID: 0300
  Device-2: Logitech C920 PRO HD Webcam driver: snd-usb-audio,uvcvideo
    type: USB rev: 2.1 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 3-5:4
    chip-ID: 046d:08e5 class-ID: 0102
  Display: wayland server: X.org v: 1.21.1.16 with: Xwayland v: 24.1.6
    compositor: kwin_wayland driver: X: loaded: nvidia
    unloaded: modesetting,nouveau alternate: fbdev,nv,vesa
    gpu: nvidia,nvidia-nvswitch d-rect: 3840x1080 display-ID: 0
  Monitor-1: DP-1 pos: primary,left model: CTV TV serial: <filter>
    built: 2016 res: mode: 1920x1080 hz: 60 scale: 100% (1) dpi: 42 gamma: 1.2
    size: 708x398mm (27.87x15.67") diag: 1321mm (52") ratio: 16:9 modes:
    max: 1920x1080 min: 640x480
  Monitor-2: DP-2 pos: primary,left model: Philips 227ELH serial: <filter>
    built: 2011 res: mode: 1920x1080 hz: 60 scale: 100% (1) dpi: 102 gamma: 1.2
    size: 480x268mm (18.9x10.55") diag: 550mm (21.6") ratio: 16:9 modes:
    max: 1920x1080 min: 640x480
  Monitor-3: DP-3 pos: right model: VG278 serial: <filter> built: 2019 res:
    mode: 1920x1080 hz: 144 scale: 100% (1) dpi: 82 gamma: 1.2
    size: 598x336mm (23.54x13.23") diag: 686mm (27") ratio: 16:9 modes:
    max: 1920x1080 min: 640x480
  API: EGL v: 1.5 hw: drv: nvidia platforms: device: 0 drv: nvidia gbm:
    drv: nvidia surfaceless: drv: nvidia wayland: drv: nvidia x11: drv: nvidia
  API: OpenGL v: 4.6.0 vendor: nvidia v: 570.124.04 glx-v: 1.4
    direct-render: yes renderer: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2
    memory: 5.86 GiB display-ID: :1.0
  API: Vulkan v: 1.4.304 layers: 14 device: 0 type: discrete-gpu name: NVIDIA
    GeForce GTX 1060 6GB driver: N/A device-ID: 10de:1b83
    surfaces: xcb,xlib,wayland device: 1 type: cpu name: llvmpipe (LLVM
    19.1.7 256 bits) driver: N/A device-ID: 10005:0000
    surfaces: xcb,xlib,wayland
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
    de: kscreen-console,kscreen-doctor gpu: corectrl, nvidia-settings,
    nvidia-smi wl: wayland-info x11: xdpyinfo, xprop, xrandr
Audio:
  Device-1: NVIDIA GP104 High Definition Audio vendor: Micro-Star MSI
    driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16
    bus-ID: 0d:00.1 chip-ID: 10de:10f0 class-ID: 0403
  Device-2: Advanced Micro Devices [AMD] Starship/Matisse HD Audio
    vendor: ASRock driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s
    lanes: 16 bus-ID: 0f:00.4 chip-ID: 1022:1487 class-ID: 0403
  Device-3: Corsair VIRTUOSO Wireless Gaming Headset
    driver: hid-generic,snd-usb-audio,usbhid type: USB rev: 2.0 speed: 12 Mb/s
    lanes: 1 mode: 1.1 bus-ID: 1-4:3 chip-ID: 1b1c:0a42 class-ID: 0300
    serial: <filter>
  Device-4: JMTek LLC. USB Condenser Microphone
    driver: hid-generic,snd-usb-audio,usbhid type: USB rev: 1.1 speed: 12 Mb/s
    lanes: 1 mode: 1.1 bus-ID: 3-4:3 chip-ID: 0c76:1716 class-ID: 0300
  Device-5: Logitech C920 PRO HD Webcam driver: snd-usb-audio,uvcvideo
    type: USB rev: 2.1 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 3-5:4
    chip-ID: 046d:08e5 class-ID: 0102
  API: ALSA v: k6.12.19-1-lts status: kernel-api with: aoss
    type: oss-emulator tools: N/A
  Server-1: PipeWire v: 1.4.1 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
Network:
  Device-1: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel pcie: gen: 2
    speed: 5 GT/s lanes: 1 bus-ID: 05:00.0 chip-ID: 8086:2723 class-ID: 0280
  IF: wlp5s0 state: down mac: <filter>
  Device-2: Intel I211 Gigabit Network vendor: ASRock driver: igb v: kernel
    pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: f000 bus-ID: 07:00.0
    chip-ID: 8086:1539 class-ID: 0200
  IF: enp7s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  IF-ID-1: virbr0 state: down mac: <filter>
  IF-ID-2: vmnet1 state: unknown speed: N/A duplex: N/A mac: <filter>
  IF-ID-3: vmnet8 state: unknown speed: N/A duplex: N/A mac: <filter>
  Info: services: NetworkManager,systemd-timesyncd
Bluetooth:
  Device-1: Intel AX200 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0
    speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 3-2:2 chip-ID: 8087:0029
    class-ID: e001
  Report: btmgmt ID: hci0 rfk-id: 0 state: down bt-service: enabled,running
    rfk-block: hardware: no software: yes address: <filter> bt-v: 5.2 lmp-v: 11
    status: discoverable: no pairing: no
Drives:
  Local Storage: total: 4.09 TiB used: 2.09 TiB (51.1%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung
    model: SSD 970 EVO Plus 1TB size: 931.51 GiB block-size: physical: 512 B
    logical: 512 B speed: 31.6 Gb/s lanes: 4 tech: SSD serial: <filter>
    fw-rev: 2B2QEXM7 temp: 43.9 C scheme: GPT
  ID-2: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 870 EVO 1TB
    size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
    tech: SSD serial: <filter> fw-rev: 2B6Q scheme: GPT
  ID-3: /dev/sdb maj-min: 8:16 vendor: Samsung model: SSD 860 EVO 1TB
    size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
    tech: SSD serial: <filter> fw-rev: 4B6Q scheme: GPT
  ID-4: /dev/sdc maj-min: 8:32 vendor: Western Digital
    model: WD10JPLX-00MBPT0 size: 931.51 GiB block-size: physical: 4096 B
    logical: 512 B speed: 6.0 Gb/s tech: HDD rpm: 7200 serial: <filter>
    fw-rev: 1H01 scheme: MBR
  ID-5: /dev/sdd maj-min: 8:48 vendor: Crucial model: CT500MX500SSD1
    size: 465.76 GiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
    tech: SSD serial: <filter> fw-rev: 023 scheme: GPT
Partition:
  ID-1: / raw-size: 465.46 GiB size: 465.46 GiB (100.00%)
    used: 427.76 GiB (91.9%) fs: btrfs dev: /dev/sdd2 maj-min: 8:50
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
    used: 608 KiB (0.2%) fs: vfat dev: /dev/sdd1 maj-min: 8:49
  ID-3: /home raw-size: 465.46 GiB size: 465.46 GiB (100.00%)
    used: 427.76 GiB (91.9%) fs: btrfs dev: /dev/sdd2 maj-min: 8:50
  ID-4: /var/log raw-size: 465.46 GiB size: 465.46 GiB (100.00%)
    used: 427.76 GiB (91.9%) fs: btrfs dev: /dev/sdd2 maj-min: 8:50
  ID-5: /var/tmp raw-size: 465.46 GiB size: 465.46 GiB (100.00%)
    used: 427.76 GiB (91.9%) fs: btrfs dev: /dev/sdd2 maj-min: 8:50
Swap:
  Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
  ID-1: swap-1 type: zram size: 31.27 GiB used: 6.9 MiB (0.0%) priority: 100
    comp: zstd avail: lzo-rle,lzo,lz4,lz4hc,deflate,842 max-streams: 16
    dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 39.9 C mobo: 37.5 C
  Fan Speeds (rpm): fan-6: 1116
Info:
  Memory: total: 32 GiB available: 31.27 GiB used: 7.04 GiB (22.5%)
  Processes: 403 Power: uptime: 7m states: freeze,mem,disk suspend: deep
    avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
    suspend, test_resume image: 12.43 GiB services: org_kde_powerdevil,
    power-profiles-daemon, upowerd Init: systemd v: 257 default: graphical
    tool: systemctl
  Packages: pm: dpkg pkgs: 0 pm: pacman pkgs: 2078 libs: 590
    tools: octopi,paru Compilers: clang: 19.1.7 gcc: 14.2.1 Shell: garuda-inxi
    default: Bash v: 5.2.37 running-in: konsole inxi: 3.3.37
Garuda (2.7.2-1):
  System install date:     2023-08-16
  Last full system update: 2025-03-20
  Is partially upgraded:   No
  Relevant software:       snapper NetworkManager dracut nvidia-dkms
  Windows dual boot:       Probably (Run as root to verify)
  Failed units:            

Hi.
I’m quite new to Linux too. I would try creating new user and see if your known problems persists there.
Also I would try Garuda Assistant or the new Garuda Rani for maintenance like Remove orphans, Clear package cache or Reinstall all packages options alongside Reset Configs section.
If anything would go wrong, make a snapshot with Snapper Tools before these tasks so you could go back. It works perfectly.

7 Likes

The first step should always be, if you have an issue that you can’t fix yourself, then open a topic as soon as possible. The idea of waiting forever and then collecting several issues until the system becomes unstable is not a good idea. Finding the cause after such a long time is usually very difficult.

Linux is not windows. If you maintain your OS regularly, install only the applications you need and fix issues promptly, then you will have very few issues and no bloat. :wink:

Just go through @gacuxz’s suggestions and see if it helps. If not, then either reinstall or open a new topic for each individual issue. It’s your decision.

btw: Breaking a debian server within a year is quite difficult. :slightly_smiling_face:
My debian server has been running for years w/o issues. :smiley:

4 Likes

My Garuda Home-Server too :smiley:

7 Likes

Well, it’s not that I really break it or anything, it’s just setting it up letting it run and neglect it and kinda switching to the newest vps version of the server every year.

But yeah, one bloated up all disk space with logs cause my settings where crap, and another one had some hiccups when it came to ssl certificate renewal, in that sense I’m probably doing something wrong but most of the time I fixed it myself.

And waiting some time for package updates and see if problems go away or consist sounded not to bad to me, if one isn’t to interested in reading through the repos and see if there are similar problems.
Did that though with the kde upgrade where I had a lot of seemingly related instabilities, they resolved themself all by themself within some updates and manual fixes.

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