Bug report on Garuda Maintenance

Hi guys, Just wanted to point out that when opening Clear caches in Garuda Assistant, the root request window fades into the background behind the main window.
Thanks.

System:
Kernel: 6.13.1-zen3-1-zen arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
clocksource: tsc avail: hpet,acpi_pm
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=142516ae-d002-447e-a9a5-0939a0cf79fa rw rootflags=subvol=@
quiet loglevel=3 ibt=off
Desktop: KDE Plasma v: 6.2.5 tk: Qt v: N/A info: frameworks v: 6.10.0
wm: kwin_wayland vt: 1 dm: SDDM Distro: Garuda base: Arch Linux
Machine:
Type: Desktop Mobo: Micro-Star model: X670E GAMING PLUS WIFI (MS-7E16)
v: 1.0 serial: <superuser required> uuid: <superuser required> UEFI: American
Megatrends LLC. v: 1.90 date: 12/31/2024
CPU:
Info: model: AMD Ryzen 9 9950X bits: 64 type: MT MCP arch: N/A level: v4
note: check family: 0x1A (26) model-id: 0x44 (68) stepping: 0
microcode: 0xB404023
Topology: cpus: 1x dies: 2 clusters: 2x1 cores: 16 threads: 32 tpc: 2
smt: enabled cache: L1: 1.2 MiB desc: d-16x48 KiB; i-16x32 KiB L2: 16 MiB
desc: 16x1024 KiB L3: 64 MiB desc: 2x32 MiB
Speed (MHz): avg: 2981 min/max: 600/5752 boost: enabled scaling:
driver: amd-pstate-epp governor: performance cores: 1: 2981 2: 2981 3: 2981
4: 2981 5: 2981 6: 2981 7: 2981 8: 2981 9: 2981 10: 2981 11: 2981 12: 2981
13: 2981 14: 2981 15: 2981 16: 2981 17: 2981 18: 2981 19: 2981 20: 2981
21: 2981 22: 2981 23: 2981 24: 2981 25: 2981 26: 2981 27: 2981 28: 2981
29: 2981 30: 2981 31: 2981 32: 2981 bogomips: 275199
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Vulnerabilities: <filter>
Graphics:
Device-1: NVIDIA AD104 [GeForce RTX 4070 Ti] vendor: ZOTAC driver: nvidia
v: 570.86.16 alternate: nouveau,nvidia_drm non-free: 550/565.xx+
status: current (as of 2025-01) arch: Lovelace code: AD1xx
process: TSMC n4 (5nm) built: 2022+ pcie: gen: 4 speed: 16 GT/s lanes: 16
ports: active: none off: DP-1,HDMI-A-1 empty: DP-2,DP-3 bus-ID: 01:00.0
chip-ID: 10de:2782 class-ID: 0300
Device-2: Advanced Micro Devices [AMD/ATI] Granite Ridge [Radeon Graphics]
vendor: Micro-Star MSI driver: amdgpu v: kernel pcie: gen: 4 speed: 16 GT/s
lanes: 16 ports: active: none empty: DP-4,HDMI-A-2,Writeback-1
bus-ID: 16:00.0 chip-ID: 1002:13c0 class-ID: 0300 temp: 38.0 C
Device-3: Sunplus Innovation Aukey-PC-LM1E Camera
driver: snd-usb-audio,uvcvideo type: USB rev: 2.0 speed: 480 Mb/s lanes: 1
mode: 2.0 bus-ID: 3-3:2 chip-ID: 1bcf:0215 class-ID: 0102
Device-4: Microdia Dual Mode Camera (8006 VGA) driver: hid-generic,usbhid
type: USB rev: 2.0 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 7-2:2
chip-ID: 0c45:8006 class-ID: 0301
Display: wayland server: X.org v: 1.21.1.15 with: Xwayland v: 24.1.5
compositor: kwin_wayland driver: X: loaded: modesetting,nvidia
alternate: fbdev,nouveau,nv,vesa dri: radeonsi gpu: nvidia,nvidia-nvswitch
d-rect: 4480x2520 display-ID: 0
Monitor-1: DP-1 pos: top-right model: MSI G273Q serial: <filter>
built: 2020 res: mode: 2560x1440 hz: 165 scale: 100% (1) dpi: 109 gamma: 1.2
size: 597x336mm (23.5x13.23") diag: 685mm (27") ratio: 16:9 modes:
max: 2560x1440 min: 640x480
Monitor-2: HDMI-A-1 pos: bottom-l model: MSI MAG272C serial: <filter>
built: 2020 res: mode: 1920x1080 hz: 120 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 drv: amd radeonsi platforms: device: 0
drv: nvidia device: 1 drv: radeonsi gbm: drv: radeonsi surfaceless:
drv: nvidia wayland: drv: nvidia x11: drv: nvidia
API: OpenGL v: 4.6.0 compat-v: 4.6 vendor: nvidia mesa v: 570.86.16
glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce RTX 4070 Ti/PCIe/SSE2
memory: 11.71 GiB display-ID: :1.0
API: Vulkan v: 1.4.303 layers: 9 device: 0 type: discrete-gpu name: NVIDIA
GeForce RTX 4070 Ti driver: N/A device-ID: 10de:2782
surfaces: xcb,xlib,wayland
Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
de: kscreen-console,kscreen-doctor gpu: nvidia-settings,nvidia-smi
wl: wayland-info x11: xdpyinfo, xprop, xrandr
Audio:
Device-1: NVIDIA AD104 High Definition Audio vendor: ZOTAC
driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
bus-ID: 01:00.1 chip-ID: 10de:22bc class-ID: 0403
Device-2: Advanced Micro Devices [AMD/ATI] Rembrandt Radeon High
Definition Audio vendor: Micro-Star MSI driver: snd_hda_intel v: kernel
pcie: gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 16:00.1 chip-ID: 1002:1640
class-ID: 0403
Device-3: Advanced Micro Devices [AMD] Family 17h/19h/1ah HD Audio
vendor: Micro-Star MSI driver: snd_hda_intel v: kernel pcie: gen: 4
speed: 16 GT/s lanes: 16 bus-ID: 16:00.6 chip-ID: 1022:15e3 class-ID: 0403
Device-4: Sunplus Innovation Aukey-PC-LM1E Camera
driver: snd-usb-audio,uvcvideo type: USB rev: 2.0 speed: 480 Mb/s lanes: 1
mode: 2.0 bus-ID: 3-3:2 chip-ID: 1bcf:0215 class-ID: 0102
API: ALSA v: k6.13.1-zen3-1-zen status: kernel-api tools: N/A
Server-1: PipeWire v: 1.2.7 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: Realtek RTL8125 2.5GbE vendor: Micro-Star MSI driver: r8169
v: kernel pcie: gen: 2 speed: 5 GT/s lanes: 1 port: e000 bus-ID: 0e:00.0
chip-ID: 10ec:8125 class-ID: 0200
IF: enp14s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Device-2: MEDIATEK MT7922 802.11ax PCI Express Wireless Network Adapter
driver: mt7921e v: kernel pcie: gen: 2 speed: 5 GT/s lanes: 1
bus-ID: 0f:00.0 chip-ID: 14c3:0616 class-ID: 0280
IF: wlp15s0 state: down mac: <filter>
Info: services: NetworkManager, systemd-timesyncd, wpa_supplicant
Bluetooth:
Device-1: MediaTek Wireless_Device driver: btusb v: 0.8 type: USB rev: 2.1
speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 3-6:4 chip-ID: 0e8d:0616
class-ID: e001 serial: <filter>
Report: btmgmt ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 5.2
lmp-v: 11 status: discoverable: no pairing: no class-ID: 6c0104
Drives:
Local Storage: total: 10.01 TiB used: 2.43 TiB (24.3%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:4 vendor: Sabrent model: Rocket Q
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: RKT30Q.2 temp: 31.9 C
scheme: GPT
ID-2: /dev/nvme1n1 maj-min: 259:0 vendor: Smart Modular Tech.
model: SHPP41-1000GM 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: 51060A20 temp: 37.9 C scheme: GPT
ID-3: /dev/sda maj-min: 8:0 vendor: Western Digital
model: WD40EFRX-68WT0N0 size: 3.64 TiB block-size: physical: 4096 B
logical: 512 B speed: 6.0 Gb/s tech: HDD rpm: 5400 serial: <filter>
fw-rev: 0A82 scheme: GPT
ID-4: /dev/sdb maj-min: 8:16 vendor: Seagate model: ST4000DM004-2CV104
size: 3.64 TiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
tech: HDD rpm: 5425 serial: <filter> fw-rev: 0001 scheme: GPT
ID-5: /dev/sdc maj-min: 8:32 vendor: SanDisk model: SSD PLUS 1000GB
size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: 04RL scheme: GPT
Partition:
ID-1: / raw-size: 931.22 GiB size: 931.22 GiB (100.00%)
used: 674.33 GiB (72.4%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:6
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 588 KiB (0.2%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:5
ID-3: /home raw-size: 931.22 GiB size: 931.22 GiB (100.00%)
used: 674.33 GiB (72.4%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:6
ID-4: /var/log raw-size: 931.22 GiB size: 931.22 GiB (100.00%)
used: 674.33 GiB (72.4%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:6
ID-5: /var/tmp raw-size: 931.22 GiB size: 931.22 GiB (100.00%)
used: 674.33 GiB (72.4%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:6
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: zram size: 30.45 GiB used: 208.2 MiB (0.7%)
priority: 100 comp: zstd avail: lzo-rle,lzo,lz4,lz4hc,deflate,842
max-streams: 32 dev: /dev/zram0
Sensors:
System Temperatures: cpu: 48.6 C mobo: 34.0 C gpu: amdgpu temp: 38.0 C
Fan Speeds (rpm): N/A
Info:
Memory: total: 32 GiB note: est. available: 30.45 GiB used: 4.85 GiB (15.9%)
Processes: 572 Power: uptime: 31m states: freeze,mem,disk suspend: deep
avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
suspend, test_resume image: 12.11 GiB services: org_kde_powerdevil,
power-profiles-daemon, upowerd Init: systemd v: 257 default: graphical
tool: systemctl
Packages: 1616 pm: pacman pkgs: 1608 libs: 430 tools: paru pm: flatpak
pkgs: 8 Compilers: clang: 19.1.7 gcc: 14.2.1 Shell: garuda-inxi
default: fish v: 3.7.1 running-in: konsole inxi: 3.3.37
Garuda (2.6.26-1.1):
System install date:     2024-12-03
Last full system update: 2025-02-08
Is partially upgraded:   No
Relevant software:       snapper NetworkManager dracut nvidia-dkms
Windows dual boot:       Probably (Run as root to verify)
Failed units:
1 Like

Restart system, for me, it solved the problem.

Pretty sure this is a Plasma issue cause I’ve noticed it on other apps that aren’t Garuda’s.

4 Likes

yes, by the way it’s random and it doesn’t always do it

ps: your avatar reminds me of someone from the PS4 scene…

Might want to watch some Stat Trek TNG, specifically the episodes dealing with the Borg.

yes I had guessed this, but a user on X has your same avatar (@Prb29327239) as if it were not said.
I close OT.

Hi, I want to report a bug when running functions in Garuda Assistant that require administrative credentials. The window where you have to enter the password is displayed below the terminal window. Maybe they should open in reverse order, if it’s possibile?

1 Like

Welcome @Voltrob :slight_smile: .

As this was already known, I have moved your post here.

There is a Plasma 6.3 issue/bug with using ICC profiles and Wayland. It will result in a black screen after logging into Wayland session, doesn’t seem to affect X11 since it uses another color profile system.

For a quick fix, you can remove '/.config/kwinoutputconfig.json\ and reboot, however you won’t be able to assign a color profile until this is fixed. It apparently has been fixed and is in the testing repos now according to this bug report.

4 Likes

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