How do I fix this weird KDE glitch?

Issues & Assistance KDE
,
1

So basically, whenever I restart my garuda linux (running KDE Plasma 6 on it), the below app panel glitches. I have to either: enter edit mode, take screenshot or launch some app from application launcher to revert it back to normal. It’s extremely annoying and I have found no solution regarding it. I do not know if it’s a KDE only issue or related to garuda Dr460nized theme, hence I am posting it here. I am a beginner so I apologise if this is a dumb question or shouldn’t be posted here.

Here is the image of my desktop:
After booting: Pasteboard - Uploaded Image
After opening some app or entering edit mode: Pasteboard - Uploaded Image

This issue was faced ever since I installed garuda linux, around maybe a month ago. I had also re-installed garuda for some other reasons but this issue did not seem to stop.

Any help will be appreciated!

P.S. When I am trying to enter edit mode now, “Enter Edit Mode” option no longer works and doesn’t do anything. Also one other thing, whenever I tried to add widgets to my desktop or panel via edit mode, KDE just crashes then restarts itself and it doesn’t work. Is this normal for garuda? I know one issue per post, but I am just asking it, not trying to fix it as I am kinda fine without using widgets, though I’d love to use 'em if I had the option.

Thank you so much in advanced!

garuda-inxi output:
System:
  Kernel: 6.12.10-zen1-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=6d7c48e7-3eb2-4f31-aade-996b49a62496 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: Laptop System: ASUSTeK product: VivoBook_ASUSLaptop X512DA_X512DA
    v: 1.0 serial: <superuser required>
  Mobo: ASUSTeK model: X512DA v: 1.0 serial: <superuser required>
    uuid: <superuser required> UEFI: American Megatrends v: X512DA.318
    date: 09/28/2022
Battery:
  ID-1: BAT0 charge: 21.7 Wh (77.0%) condition: 28.2/37.1 Wh (75.9%)
    power: 6.9 W volts: 7.8 min: 7.8 model: ASUSTeK ASUS Battery type: Li-ion
    serial: N/A status: discharging cycles: 623
CPU:
  Info: model: AMD Ryzen 3 3200U with Radeon Vega Mobile Gfx bits: 64
    type: MT MCP arch: Zen/Zen+ note: check gen: 1 level: v3 note: check
    built: 2019 process: GF 12nm family: 0x17 (23) model-id: 0x18 (24)
    stepping: 1 microcode: 0x8108109
  Topology: cpus: 1x dies: 1 clusters: 1 cores: 2 threads: 4 tpc: 2
    smt: enabled cache: L1: 192 KiB desc: d-2x32 KiB; i-2x64 KiB L2: 1024 KiB
    desc: 2x512 KiB L3: 4 MiB desc: 1x4 MiB
  Speed (MHz): avg: 1400 min/max: 1400/2600 boost: disabled scaling:
    driver: acpi-cpufreq governor: powersave cores: 1: 1400 2: 1400 3: 1400
    4: 1400 bogomips: 20761
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  Vulnerabilities: <filter>
Graphics:
  Device-1: Advanced Micro Devices [AMD/ATI] Picasso/Raven 2 [Radeon Vega
    Series / Radeon Mobile Series] vendor: ASUSTeK 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: eDP-1 empty: HDMI-A-1
    bus-ID: 03:00.0 chip-ID: 1002:15d8 class-ID: 0300 temp: 44.0 C
  Device-2: IMC Networks USB2.0 HD UVC WebCam driver: uvcvideo type: USB
    rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-6.2:6
    chip-ID: 13d3:56dd class-ID: 0e02 serial: <filter>
  Display: wayland server: X.org v: 1.21.1.15 with: Xwayland v: 24.1.4
    compositor: kwin_wayland driver: X: loaded: amdgpu unloaded: modesetting
    alternate: fbdev,vesa dri: radeonsi gpu: amdgpu display-ID: 0
  Monitor-1: eDP-1 model: AU Optronics 0x21ed built: 2021 res:
    mode: 1920x1080 hz: 60 scale: 125% (1.25) to: 1536x864 dpi: 142 gamma: 1.2
    size: 344x193mm (13.54x7.6") diag: 394mm (15.5") ratio: 16:9 modes:
    max: 1920x1080 min: 640x480
  API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi
    device: 1 drv: swrast gbm: drv: kms_swrast surfaceless: drv: radeonsi
    wayland: drv: radeonsi x11: drv: radeonsi
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 24.3.4-arch1.1
    glx-v: 1.4 direct-render: yes renderer: AMD Radeon Vega 3 Graphics
    (radeonsi raven2 LLVM 19.1.7 DRM 3.59 6.12.10-zen1-1-zen)
    device-ID: 1002:15d8 memory: 1.95 GiB unified: no display-ID: :1.0
  API: Vulkan v: 1.4.303 layers: 14 device: 0 type: integrated-gpu name: AMD
    Radeon Vega 3 Graphics (RADV RAVEN2) driver: N/A device-ID: 1002:15d8
    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 wl: wayland-info
    x11: xdpyinfo, xprop, xrandr
Audio:
  Device-1: Advanced Micro Devices [AMD/ATI] Raven/Raven2/Fenghuang HDMI/DP
    Audio driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16
    bus-ID: 03:00.1 chip-ID: 1002:15de class-ID: 0403
  Device-2: Advanced Micro Devices [AMD] ACP/ACP3X/ACP6x Audio Coprocessor
    driver: snd_pci_acp3x v: kernel alternate: snd_rn_pci_acp3x, snd_pci_acp5x,
    snd_pci_acp6x, snd_acp_pci, snd_rpl_pci_acp6x, snd_pci_ps,
    snd_sof_amd_renoir, snd_sof_amd_rembrandt, snd_sof_amd_vangogh,
    snd_sof_amd_acp63, snd_sof_amd_acp70 pcie: gen: 3 speed: 8 GT/s lanes: 16
    bus-ID: 03:00.5 chip-ID: 1022:15e2 class-ID: 0480
  Device-3: Advanced Micro Devices [AMD] Family 17h/19h/1ah HD Audio
    vendor: ASUSTeK driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s
    lanes: 16 bus-ID: 03:00.6 chip-ID: 1022:15e3 class-ID: 0403
  API: ALSA v: k6.12.10-zen1-1-zen status: kernel-api with: aoss
    type: oss-emulator tools: N/A
  Server-1: sndiod v: N/A status: off tools: aucat,midicat,sndioctl
  Server-2: 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: Intel Wireless 8265 / 8275 driver: iwlwifi v: kernel pcie: gen: 1
    speed: 2.5 GT/s lanes: 1 bus-ID: 01:00.0 chip-ID: 8086:24fd class-ID: 0280
  IF: wlp1s0 state: up mac: <filter>
  Info: services: NetworkManager, systemd-timesyncd, wpa_supplicant
Bluetooth:
  Device-1: Intel Bluetooth wireless interface driver: btusb v: 0.8 type: USB
    rev: 2.0 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-6.1:5
    chip-ID: 8087:0a2b class-ID: e001
  Report: btmgmt ID: hci0 rfk-id: 2 state: up address: <filter> bt-v: 4.2
    lmp-v: 8 status: discoverable: no pairing: no class-ID: 6c010c
Drives:
  Local Storage: total: 238.47 GiB used: 45.08 GiB (18.9%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Western Digital model: PC SN530
    SDBPNPZ-256G-1002 size: 238.47 GiB block-size: physical: 512 B
    logical: 512 B speed: 31.6 Gb/s lanes: 4 tech: SSD serial: <filter>
    fw-rev: 21106000 temp: 41.9 C scheme: GPT
Partition:
  ID-1: / raw-size: 205.64 GiB size: 205.64 GiB (100.00%)
    used: 45.06 GiB (21.9%) fs: btrfs dev: /dev/nvme0n1p4 maj-min: 259:4
  ID-2: /boot/efi raw-size: 600 MiB size: 598.8 MiB (99.80%)
    used: 19 MiB (3.2%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
  ID-3: /home raw-size: 205.64 GiB size: 205.64 GiB (100.00%)
    used: 45.06 GiB (21.9%) fs: btrfs dev: /dev/nvme0n1p4 maj-min: 259:4
  ID-4: /var/log raw-size: 205.64 GiB size: 205.64 GiB (100.00%)
    used: 45.06 GiB (21.9%) fs: btrfs dev: /dev/nvme0n1p4 maj-min: 259:4
  ID-5: /var/tmp raw-size: 205.64 GiB size: 205.64 GiB (100.00%)
    used: 45.06 GiB (21.9%) fs: btrfs dev: /dev/nvme0n1p4 maj-min: 259:4
Swap:
  Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
  ID-1: swap-1 type: zram size: 5.74 GiB used: 282.2 MiB (4.8%)
    priority: 100 comp: zstd avail: lzo-rle,lzo,lz4,lz4hc,deflate,842
    max-streams: 4 dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 44.1 C mobo: N/A gpu: amdgpu temp: 44.0 C
  Fan Speeds (rpm): cpu: 2400
Info:
  Memory: total: 6 GiB available: 5.74 GiB used: 3.83 GiB (66.8%)
  Processes: 278 Power: uptime: 2m states: freeze,mem,disk suspend: deep
    avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
    suspend, test_resume image: 2.28 GiB services: org_kde_powerdevil,upowerd
    Init: systemd v: 257 default: graphical tool: systemctl
  Packages: pm: pacman pkgs: 2321 libs: 562 tools: octopi,paru,yay
    pm: flatpak pkgs: 0 Compilers: clang: 19.1.7 gcc: 14.2.1 Shell: garuda-inxi
    default: fish v: 3.7.1 running-in: kitty inxi: 3.3.37
Garuda (2.6.26-1.1):
  System install date:     2025-01-15
  Last full system update: 2025-01-27
  Is partially upgraded:   No
  Relevant software:       snapper NetworkManager dracut grub-customizer
  Windows dual boot:       No/Undetected
  Failed units:
2

Do you use virtual desktops?
I use to face a similar bug, where if I hover over an Icon in task bar, wait for the help popup and then use shortcut keys to switch to a different virtual desktop, the popup would stuck around.

3

Unfortunately no real solution…
I have had this problem for months. At first I did the same as you. At some point I realized that pressing the Meta/Windows button was enough on my system to return to the normal state.

4

Funny I had similar issues, but when using X11.

Since I am using Wayland the bottom panel stopped to glitch lol.

5

This bug should be fixed when KDE Plasma 6.3 is out (or if we are lucky, a point release prior to that) 489086 – When system is under heavy load, panel in Fit Content mode is too small at startup until something causes it to re-evaluate its size (e.g. entering edit mode)

Edit:
Plasma 6.3 is planned to come out February 11th:
https://phabricator.kde.org/calendar/query/month/2025/02/11/
So, it will be available to everybody at a time around then. (Depends on how long it needs to be in Arch Testing branch)

8 Likes
6

It’s funny, it happens to me just the opposite, in X11 it works perfectly, but in Wayland sometimes it glitches. :rofl:

7

Nope, I don’t use virtual desktops.

8

Hm. I see. So there is no way then. Hope it gets fixed somewhere in the future.

9

Oh. I see. Thanks. Lets see how it goes.

10

It happens with me in both X11 and wayland lol.

11

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