Bizarre Garuda Rani behavior - different experience when executing from terminal vs KDE desktop icon

[shayaknyc]

First off, here’s my garuda-inxi:

System:
  Kernel: 6.15.4-zen2-1-zen arch: x86_64 bits: 64 compiler: gcc v: 15.1.1 clocksource: tsc
    avail: acpi_pm parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
    root=UUID=8dcc0c9c-8fe9-4fc6-b189-a8db2cfa3823 rw rootflags=subvol=@ rd.driver.pre=vfio-pci
    intel_iommu=on i915.enable_guc=3 i915.max_vfs=7 quiet
    resume=UUID=a14a443b-9c6b-47d0-b49a-d9686d767b7c loglevel=3 sysrq_always_enabled=1
    split_lock_detect=off nvidia-drm.modeset=1 pci=disable_acs_redir=pci:12D8:2308
    vt.default_red=30,243,166,249,137,245,148,186,88,243,166,249,137,245,148,166
    vt.default_grn=30,139,227,226,180,194,226,194,91,139,227,226,180,194,226,173
    vt.default_blu=46,168,161,175,250,231,213,222,112,168,161,175,250,231,213,200 ibt=off
  Console: pty pts/1 DM: SDDM Distro: Garuda base: Arch Linux
Machine:
  Type: Desktop System: ASUS product: N/A v: N/A serial: <superuser required>
  Mobo: ASUSTeK model: PRIME Z690-P WIFI v: Rev 1.xx serial: <superuser required> part-nu: SKU
    uuid: <superuser required> UEFI: American Megatrends v: 3601 date: 10/14/2024
CPU:
  Info: model: 12th Gen Intel Core i9-12900K bits: 64 type: MST AMCP arch: Alder Lake gen: core 12
    level: v3 note: check built: 2021+ process: Intel 7 (10nm ESF) family: 6 model-id: 0x97 (151)
    stepping: 2 microcode: 0x3A
  Topology: cpus: 1x dies: 1 clusters: 10 cores: 16 threads: 24 mt: 8 tpc: 2 st: 8 smt: enabled
    cache: L1: 1.4 MiB desc: d-8x32 KiB, 8x48 KiB; i-8x32 KiB, 8x64 KiB L2: 14 MiB
    desc: 8x1.2 MiB, 2x2 MiB L3: 30 MiB desc: 1x30 MiB
  Speed (MHz): avg: 800 min/max: 800/5100:5200:3900 scaling: driver: intel_pstate
    governor: performance cores: 1: 800 2: 800 3: 800 4: 800 5: 800 6: 800 7: 800 8: 800 9: 800
    10: 800 11: 800 12: 800 13: 800 14: 800 15: 800 16: 800 17: 800 18: 800 19: 800 20: 800
    21: 800 22: 800 23: 800 24: 800 bogomips: 152985
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities: <filter>
Graphics:
  Device-1: Intel AlderLake-S GT1 vendor: ASUSTeK driver: i915 v: kernel alternate: xe arch: Xe
    process: Intel 10nm built: 2020-21 ports: active: none empty: DP-1,HDMI-A-1,HDMI-A-2
    bus-ID: 00:02.0 chip-ID: 8086:4680 class-ID: 0300
  Device-2: NVIDIA GA104 [GeForce RTX 3060 Ti Lite Hash Rate] vendor: ASUSTeK driver: nvidia
    v: 575.64 alternate: nouveau,nvidia_drm non-free: 550-570.xx+ status: current (as of 2025-04;
    EOL~2026-12-xx) arch: Ampere code: GAxxx process: TSMC n7 (7nm) built: 2020-2023 pcie: gen: 1
    speed: 2.5 GT/s lanes: 16 link-max: gen: 4 speed: 16 GT/s ports: active: none off: DP-2,DP-4
    empty: DP-3,HDMI-A-3,HDMI-A-4 bus-ID: 01:00.0 chip-ID: 10de:2489 class-ID: 0300
  Device-3: Microsoft LifeCam Studio driver: hid-generic,snd-usb-audio,usbhid,uvcvideo type: USB
    rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-9:3 chip-ID: 045e:0772 class-ID: 0300
  Display: unspecified server: X.org v: 1.21.1.18 with: Xwayland v: 24.1.8
    compositor: kwin_wayland driver: X: loaded: modesetting,nvidia unloaded: nouveau
    alternate: fbdev,intel,nv,vesa dri: iris gpu: nvidia,nvidia-nvswitch tty: 205x30
  Monitor-1: DP-2 model: Samsung SyncMaster serial: <filter> built: 2009 res: 1920x1080 dpi: 92
    gamma: 1.2 size: 531x298mm (20.91x11.73") diag: 609mm (24") ratio: 16:9 modes: max: 1920x1080
    min: 640x480
  Monitor-2: DP-4 model: Dell UZ2715H serial: <filter> built: 2014 res: 1920x1080 dpi: 83
    gamma: 1.2 size: 597x336mm (23.5x13.23") diag: 676mm (26.6") ratio: 16:9 modes: max: 1920x1080
    min: 640x480
  API: EGL v: 1.5 hw: drv: intel iris drv: nvidia platforms: device: 0 drv: nvidia device: 2
    drv: iris device: 3 drv: swrast gbm: drv: nvidia surfaceless: drv: nvidia wayland: drv: nvidia
    inactive: x11,device-1
  API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: mesa v: 25.1.4-arch1.1 note: console (EGL sourced)
    renderer: NVIDIA GeForce RTX 3060 Ti/PCIe/SSE2, Mesa Intel UHD Graphics 770 (ADL-S GT1),
    llvmpipe (LLVM 20.1.6 256 bits)
  API: Vulkan v: 1.4.313 layers: 16 device: 0 type: discrete-gpu name: NVIDIA GeForce RTX 3060
    Ti driver: nvidia v: 575.64 device-ID: 10de:2489 surfaces: N/A device: 1 type: integrated-gpu
    name: Intel UHD Graphics 770 (ADL-S GT1) driver: mesa intel v: 25.1.4-arch1.1
    device-ID: 8086:4680 surfaces: N/A device: 2 type: cpu name: llvmpipe (LLVM 20.1.6 256 bits)
    driver: mesa llvmpipe v: 25.1.4-arch1.1 (LLVM 20.1.6) device-ID: 10005:0000 surfaces: N/A
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo de: kscreen-console,kscreen-doctor
    gpu: corectrl, gputop, intel_gpu_top, lsgpu, nvidia-settings, nvidia-smi
    wl: wayland-info,wlr-randr x11: xdpyinfo, xprop, xrandr
Audio:
  Device-1: Intel Alder Lake-S HD Audio vendor: ASUSTeK driver: vfio-pci alternate: snd_hda_intel,
    snd_soc_avs, snd_sof_pci_intel_tgl bus-ID: 00:1f.3 chip-ID: 8086:7ad0 class-ID: 0403
  Device-2: NVIDIA GA104 High Definition Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel
    pcie: gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 01:00.1 chip-ID: 10de:228b class-ID: 0403
  Device-3: Microsoft LifeCam Studio driver: hid-generic,snd-usb-audio,usbhid,uvcvideo type: USB
    rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-9:3 chip-ID: 045e:0772 class-ID: 0300
  API: ALSA v: k6.15.4-zen2-1-zen status: kernel-api with: aoss type: oss-emulator
    tools: alsactl,alsamixer,amixer
  Server-1: PipeWire v: 1.4.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
Network:
  Device-1: Intel Alder Lake-S PCH CNVi WiFi driver: iwlwifi v: kernel bus-ID: 00:14.3
    chip-ID: 8086:7af0 class-ID: 0280
  IF: wlo1 state: down mac: <filter>
  Device-2: Realtek RTL8125 2.5GbE vendor: ASUSTeK driver: r8169 v: kernel pcie: gen: 2
    speed: 5 GT/s lanes: 1 port: 3000 bus-ID: 06:00.0 chip-ID: 10ec:8125 class-ID: 0200
  IF: enp6s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  IF-ID-1: br-1f7862558da6 state: down mac: <filter>
  IF-ID-2: br-7bfc84ea431e state: down mac: <filter>
  IF-ID-3: br-82d31aa0b51e state: up speed: 10000 Mbps duplex: unknown mac: <filter>
  IF-ID-4: br-8cfdb6073e28 state: down mac: <filter>
  IF-ID-5: br-960c3623af4c state: down mac: <filter>
  IF-ID-6: br-b787944b7593 state: up speed: 10000 Mbps duplex: unknown mac: <filter>
  IF-ID-7: br-b90412b2529c state: down mac: <filter>
  IF-ID-8: br-e0cf0c4bc03a state: down mac: <filter>
  IF-ID-9: br-e9c38ec2b98c state: up speed: 10000 Mbps duplex: unknown mac: <filter>
  IF-ID-10: docker0 state: down mac: <filter>
  IF-ID-11: macvtap0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  IF-ID-12: veth63e189f state: up speed: 10000 Mbps duplex: full mac: <filter>
  IF-ID-13: veth6ea2ade state: up speed: 10000 Mbps duplex: full mac: <filter>
  IF-ID-14: vethb55ac9f state: up speed: 10000 Mbps duplex: full mac: <filter>
  IF-ID-15: virbr0 state: down mac: <filter>
  Info: services: NetworkManager, smbd, sshd, systemd-timesyncd
Bluetooth:
  Device-1: Intel AX201 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0 speed: 12 Mb/s lanes: 1
    mode: 1.1 bus-ID: 1-14:7 chip-ID: 8087:0026 class-ID: e001
  Report: btmgmt ID: hci0 rfk-id: 0 state: up address: N/A
RAID:
  Hardware-1: Intel Volume Management Device NVMe RAID Controller driver: vmd v: 0.6 port: N/A
    bus-ID: 00:0e.0 chip-ID: 8086:467f rev: class-ID: 0104
Drives:
  Local Storage: total: 6.37 TiB used: 2.85 TiB (44.7%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung model: SSD 990 PRO with Heatsink 2TB
    size: 1.82 TiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s lanes: 4 tech: SSD
    serial: <filter> fw-rev: 4B2QJXD7 temp: 53.9 C scheme: GPT
  ID-2: /dev/nvme1n1 maj-min: 259:4 vendor: Samsung model: SSD 980 PRO 1TB size: 931.51 GiB
    block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s lanes: 4 tech: SSD serial: <filter>
    fw-rev: 5B2QGXA7 temp: 47.9 C scheme: GPT
  ID-3: /dev/sda maj-min: 8:0 vendor: Seagate model: ST4000NE001-2MA101 size: 3.64 TiB
    block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s tech: HDD rpm: 7200 serial: <filter>
    fw-rev: EN01 scheme: GPT
  SMART Message: Unknown smartctl error. Unable to generate data.
Partition:
  ID-1: / raw-size: 1.79 TiB size: 1.79 TiB (100.00%) used: 572.54 GiB (31.3%) fs: btrfs
    block-size: 4096 B dev: /dev/nvme0n1p2 maj-min: 259:2
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%) used: 620 KiB (0.2%) fs: vfat
    block-size: 512 B dev: /dev/nvme0n1p1 maj-min: 259:1
  ID-3: /home raw-size: 1.79 TiB size: 1.79 TiB (100.00%) used: 572.54 GiB (31.3%) fs: btrfs
    block-size: 4096 B dev: /dev/nvme0n1p2 maj-min: 259:2
  ID-4: /var/log raw-size: 1.79 TiB size: 1.79 TiB (100.00%) used: 572.54 GiB (31.3%) fs: btrfs
    block-size: 4096 B dev: /dev/nvme0n1p2 maj-min: 259:2
  ID-5: /var/tmp raw-size: 1.79 TiB size: 1.79 TiB (100.00%) used: 572.54 GiB (31.3%) fs: btrfs
    block-size: 4096 B dev: /dev/nvme0n1p2 maj-min: 259:2
Swap:
  Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
  ID-1: swap-1 type: zram size: 31.08 GiB used: 8.31 GiB (26.7%) priority: 100 comp: zstd
    avail: lzo-rle,lzo,lz4,lz4hc,deflate,842 dev: /dev/zram0
  ID-2: swap-2 type: partition size: 34.2 GiB used: 0 KiB (0.0%) priority: -2
    dev: /dev/nvme0n1p3 maj-min: 259:3
Sensors:
  System Temperatures: cpu: 50.0 C mobo: N/A gpu: nvidia temp: 53 C
  Fan Speeds (rpm): N/A
Info:
  Memory: total: 32 GiB note: est. available: 31.08 GiB used: 16.64 GiB (53.5%)
  Processes: 635 Power: uptime: 22h 32m states: freeze,mem,disk suspend: deep avail: s2idle
    wakeups: 0 hibernate: platform avail: shutdown, reboot, suspend, test_resume image: 12.35 GiB
    services: org_kde_powerdevil, power-profiles-daemon, upowerd Init: systemd v: 257
    default: graphical tool: systemctl
  Packages: 2483 pm: pacman pkgs: 2476 libs: 603 tools: octopi,pacseek,paru pm: flatpak pkgs: 7
    Compilers: clang: 20.1.6 gcc: 15.1.1 alt: 13/14 Shell: garuda-inxi default: fish v: 4.0.2
    running-in: pty pts/1 (SSH) inxi: 3.3.38
Garuda (2.7.3-1):
  System install date:     2024-10-16
  Last full system update: 2025-06-30
  Is partially upgraded:   No
  Relevant software:       snapper NetworkManager dracut nvidia-dkms
  Windows dual boot:       Probably (Run as root to verify)
  Failed units:

When I run Rani directly from the Application Launcher (or from the pinned taskbar icon) Rani loads like this:

The loading animation goes on forever, I have these two alerts, one of which insists I have to merge pacdiff files, and when I go into system settings, everything is deselected. See here:

However, if I close it, and then re-run Rani in terminal via garuda-rani, things appear to be working as they’re supposed to:

No forever loading animation, no complaints about needing to merge diff files. I even uninstalled and re-installed Rani. Nothing. Any ideas?

Thanks in advance to all you amazing folks!

[Duke187]

Hi @shayaknyc ,

wired behavior my one is working fine i had some other issues. There is another Topic were all people telling their issues take a look here. Did you used the -Rdd or just -R command ? Which Version do you have installed?

Garuda Rani - preview releases and testing

It seems like I forgot reimplementing that functionality I mean, the switch is there and all that, but after porting it to electron I didn’t add back the logic for responding to toggling it. Absolutely my bad, I’ll be adding it back very soon. I wonder what a use case would be, given the app refreshes whenever a relevant thing was executed. But yes, that’s one of the easiest things do. I’d call a full refresh however (there is more state other than packages only). Nic…

[shayaknyc]

@Duke187

There is another Topic were all people telling their issues take a look here.

Very cursory search, wasn’t sure if I could identify someone’s post as close to or relevant to the experience I’m having. Perhaps a deeper dive would be necessary. I’ll follow-up once I’ve reviewed the latest 285 posts (as of this writing LOL).

@Duke187

Did you used the -Rdd or just -R

Actually, I used -Rns when uninstalling it.

@Duke187

Which Version do you have installed?

Seems I have v3.0.2-1 installed.

All that said and done, I did just run paru -Rdd garuda-rani then rebooted and reinstalled via paru -S garuda-rani and I’m still having the exact same behavior.

[Duke187]

Yes i know you can handle commands so thats why i didnt wrote much about it

I use normally pacman for the stuff and paru only for AUR installs. I dont know if this would do a big different . Only i know with paru sometimes can be used for unstable packages .

Hope our Nico will see it and give you a hint or solution for it. Thumps pressed

[shayaknyc]

I’ve tried again with pacman instead and still having the same issue when loaded via icon-only vs terminal. It’s like it knows it’s being watched, and behaves correctly when scrutinized. LOL

[dr460nf1r3]

@Duke187

Hope our Nico will see it and give you a hint or solution for it. Thumps pressed

There’s rarely a thread I don’t see, especially when it has certain keywords

No idea what this could possibly be right now. An idea could be to try and alter the .desktop starting it to redirect the console output to a log file and gain logs this way. Also add --enable-logging (redirects renderer console logs to stout, very useful). Of course, considering it doesn’t behave correctly this way…

[shayaknyc]

@dr460nf1r3

An idea could be to try and alter the .desktop starting it to redirect the console output to a log file

I’d love to, but I’m not sure what command-line options I should use in order to do so? Should I modify the .desktop file to include this in the command-line arguments: --enable-logging > ~/garuda-rani.log ?

[dr460nf1r3]

That’s exactly what I would’ve done, yes. The .desktop is usually in /usr/share/applications, so sudo micro /usr/share/applications/garuda-rani.desktop should do the trick (I think that was the right one. Otherwise search for rani in that directory). Might also add 2>&1 at the end to also catch stderr streams.

[shayaknyc]

Ok, ssssooooo…something very weird. There is only one garuda-rani.desktop file and it’s in /usr/share/applications/. Instead of editing the file directly, I right-clicked on its application launcher entry and selected Edit Application from the context-menu, and then it loaded KDE Menu Editor which currently displays the command-line arguments:

(home path, redacted)

However, when editing the file in terminal, the arguments are nowhere to be found. So, I modified the Exec line as follows:
Exec=garuda-rani --enable-logging > /home/USER/garuda-rani.log 2>&1

Saved, and then executed xdg-desktop-menu forceupdate. Then, loaded Rani via the icon and same behavior, but…here’s the kicker… NO LOG FILE GENERATED!

Then, just for funsies, I decided to inspect the menu listing with KDE Menu editor, and the new exec line is not at all reflected in the entry.

I even ran locate garuda-rani after running sudo updatedb and here’re the locations that it found (removed all the snapshot locations):

/usr/bin/garuda-rani
/usr/lib/garuda-rani
/usr/lib/garuda-rani/app.asar
/usr/share/applications/garuda-rani.desktop
/usr/share/icons/garuda-rani.svg
/usr/share/icons/hicolor/scalable/apps/garuda-rani.svg
/usr/share/licenses/garuda-rani
/usr/share/licenses/garuda-rani/LICENSE

At this point, I’m not really sure how to proceed… I’m questioning the efficacy of the KDE Menu Editor and where that’s being saved. And why the .desktop entry doesn’t seem to be synced to the Menu listing…

[shayaknyc]

Ok, new update. Added the command-line arguments directly to the “Program” field in KDE Menu Editor and with --enable-logging > /home/USER/garuda-rani.log 2>&1 appended, Rani works exactly as it should, and outputs everything to the log file. However, when I remove the options from the “Program” field, it reverts to that bizarre behavior where nothing loads. Seriously, it’s only behaving when it’s being scrutinized, otherwise it’s a big to me.

Here’s a copy of the log: Garuda's PrivateBin

[dr460nf1r3]

Big what the ■■■■ indeed.

I can’t think of a reason why this would happen. Maybe the best thing would be to enable logging to a file without explicitly having to enable it.

As for how the KDE menu editor works, it should generate a new file in ~/.local/share/applications to my knowledge.

Anyone else had a situation like this before with another app maybe?

[shayaknyc]

@dr460nf1r3

Maybe the best thing would be to enable logging to a file without explicitly having to enable it.

I don’t know what this means without having --enable-logging explicitly set in the shortcut.

@dr460nf1r3

As for how the KDE menu editor works, it should generate a new file in ~/.local/share/applications to my knowledge.

It does, and it has the same Exec line as the file in /usr/share/applications/. Either way, it doesn’t appear to load correctly. If I click on the icon in the menu, it loads all borked. If I run it in terminal, it loads correctly with logging enabled to the con.

Truly have no idea what would cause it to behave this way…

Edit: Tried something, added just --enable-logging in the Exec line, and then had it set to “open in terminal” - and it shows all the logging to the terminal in the background, but the APP IS STILL BORKED! So, now that it’s being scrutinized, it’s still “broken” - but this ONLY happens when launched from the menu/.desktop entry - NOT when run from terminal directly. Not sure if this is useful: Garuda Rani Output Log

[wizzard8]

I have an issue (im not sure if its related or not), my rani icon on the desktop has changed to white paper icon with a ? on it for no apparent reason, the tooltip is org.garudalinux.rani.desktop and it no longer runs the assistant when clicked on. (unknown application folder). I can run it from the application launcher menu though.

[shayaknyc]

@wizzard8

I have an issue (im not sure if its related or not), my rani icon on the desktop has changed to white paper icon with a ? on it for no apparent reason

That happened to me after a recent update. If you have a proper Rani entry in your menu, you can just unpin the paper icon, and then re-add the Rani icon from the menu. Should work.

[dr460nf1r3]

@shayaknyc

I don’t know what this means without having --enable-logging explicitly set in the shortcut.

Basically logging to a file without setting the param. I’ll need to code this however, and I’ll likely not be able to very soon. I’ll keep you updated however!

[shayaknyc]

@dr460nf1r3

Basically logging to a file without setting the param. I’ll need to code this however, and I’ll likely not be able to very soon. I’ll keep you updated however!

Oh! Ok. I thought I needed to do something specifically to make this work. For now, I seem to have a work-around. Happy to be kept abreast of things as they progress.