Taskbar turns black when application windows maximized

blazeheroic · 8 April 2025 02:33

Hi there,

I am relatively new with Garuda and Dr4gonized, and am having a glitch where when applications are maximized, the majority of the taskbar with the menu, digital clock, and application name as well as any spacers are blacked out. If I hover over the digital clock or the application name, they do still display a floating tooltip, but do not show text as normal. I have tried this with many different applications, including Firefox, LibreOffice Writer, RetroArch, and Discord, and the issue persists with every application. I cannot upload any images (new forum user) or I would do so. Any help you can give me would be appreciated, thanks.

System:
Kernel: 6.13.8-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=febaf9ad-0482-4918-ab5a-fefa9211638a rw rootflags=subvol=@
quiet loglevel=3 ibt=off
Desktop: KDE Plasma v: 6.3.4 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: MSI model: Z97S SLI Krait Edition (MS-7922) v: 2.0
serial: <superuser required> uuid: <superuser required>
UEFI: American Megatrends v: 10.6 date: 08/13/2015
CPU:
Info: model: Intel Core i5-4690K bits: 64 type: MCP arch: Haswell
gen: core 4 level: v3 note: check built: 2013-15 process: Intel 22nm
family: 6 model-id: 0x3C (60) stepping: 3 microcode: 0x28
Topology: cpus: 1x dies: 1 clusters: 4 cores: 4 smt: <unsupported> cache:
L1: 256 KiB desc: d-4x32 KiB; i-4x32 KiB L2: 1024 KiB desc: 4x256 KiB
L3: 6 MiB desc: 1x6 MiB
Speed (MHz): avg: 3900 min/max: 800/3900 scaling: driver: intel_cpufreq
governor: performance cores: 1: 3900 2: 3900 3: 3900 4: 3900 bogomips: 28000
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities: <filter>
Graphics:
Device-1: NVIDIA GM206 [GeForce GTX 960] vendor: ASUSTeK driver: nvidia
v: 570.133.07 alternate: nouveau,nvidia_drm non-free: 550/565.xx+
status: current (as of 2025-01; EOL~2026-12-xx) arch: Maxwell code: GMxxx
process: TSMC 28nm built: 2014-2019 pcie: gen: 3 speed: 8 GT/s lanes: 16
ports: active: none off: HDMI-A-1 empty: DP-1, DP-2, DP-3, DVI-I-1
bus-ID: 01:00.0 chip-ID: 10de:1401 class-ID: 0300
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
alternate: fbdev,nouveau,nv,vesa gpu: nvidia,nvidia-nvswitch display-ID: 0
Monitor-1: HDMI-A-1 model: ASUS VG27V serial: <filter> built: 2020 res:
mode: 1920x1080 hz: 165 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 nouveau drv: nvidia platforms: device: 0
drv: nvidia device: 1 drv: nouveau device: 2 drv: swrast gbm: drv: nvidia
surfaceless: drv: nvidia wayland: drv: nvidia x11: drv: nvidia
API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 570.133.07
glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce GTX 960/PCIe/SSE2
memory: 3.91 GiB display-ID: :1.0
API: Vulkan v: 1.4.309 layers: 9 device: 0 type: discrete-gpu
name: NVIDIA GeForce GTX 960 driver: N/A device-ID: 10de:1401
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: Intel 9 Series Family HD Audio vendor: Micro-Star MSI
driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:8ca0
class-ID: 0403
Device-2: NVIDIA GM206 High Definition Audio vendor: ASUSTeK
driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16
bus-ID: 01:00.1 chip-ID: 10de:0fba class-ID: 0403
API: ALSA v: k6.13.8-zen1-1-zen 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: 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: d000 bus-ID: 05:00.0 chip-ID: 10ec:8168 class-ID: 0200
IF: enp5s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Info: services: NetworkManager, smbd, systemd-timesyncd
Drives:
Local Storage: total: 3.86 TiB used: 169.33 GiB (4.3%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: Silicon Power
model: SPCC Solid State Disk size: 223.57 GiB block-size: physical: 512 B
logical: 512 B speed: 6.0 Gb/s tech: SSD serial: <filter> fw-rev: 4H
scheme: GPT
ID-2: /dev/sdb maj-min: 8:16 vendor: Seagate model: ST2000DX002-2DV164
size: 1.82 TiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
tech: HDD rpm: 7200 serial: <filter> fw-rev: CC41 scheme: GPT
ID-3: /dev/sdc maj-min: 8:32 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: 3B6Q scheme: GPT
ID-4: /dev/sdd maj-min: 8:48 vendor: Western Digital
model: WD10JMVW-11AJGS1 size: 931.48 GiB block-size: physical: 512 B
logical: 512 B type: USB rev: 3.0 spd: 5 Gb/s lanes: 1 mode: 3.2 gen-1x1
tech: HDD rpm: 5400 serial: <filter> fw-rev: 1042 scheme: MBR
Partition:
ID-1: / raw-size: 931.22 GiB size: 931.22 GiB (100.00%)
used: 169.33 GiB (18.2%) fs: btrfs dev: /dev/sdc2 maj-min: 8:34
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 608 KiB (0.2%) fs: vfat dev: /dev/sdc1 maj-min: 8:33
ID-3: /home raw-size: 931.22 GiB size: 931.22 GiB (100.00%)
used: 169.33 GiB (18.2%) fs: btrfs dev: /dev/sdc2 maj-min: 8:34
ID-4: /var/log raw-size: 931.22 GiB size: 931.22 GiB (100.00%)
used: 169.33 GiB (18.2%) fs: btrfs dev: /dev/sdc2 maj-min: 8:34
ID-5: /var/tmp raw-size: 931.22 GiB size: 931.22 GiB (100.00%)
used: 169.33 GiB (18.2%) fs: btrfs dev: /dev/sdc2 maj-min: 8:34
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: zram size: 15.56 GiB used: 0 KiB (0.0%) priority: 100
comp: zstd avail: lzo-rle,lzo,lz4,lz4hc,deflate,842 max-streams: 4
dev: /dev/zram0
Sensors:
System Temperatures: cpu: 42.0 C mobo: N/A
Fan Speeds (rpm): N/A
Info:
Memory: total: 16 GiB available: 15.56 GiB used: 5.56 GiB (35.8%)
Processes: 309 Power: uptime: 1d 6h 24m states: freeze,mem,disk
suspend: deep avail: s2idle wakeups: 0 hibernate: platform avail: shutdown,
reboot, suspend, test_resume image: 6.16 GiB services: org_kde_powerdevil,
power-profiles-daemon, upowerd Init: systemd v: 257 default: graphical
tool: systemctl
Packages: pm: pacman pkgs: 1828 libs: 562 tools: octopi,paru pm: flatpak
pkgs: 0 Compilers: clang: 19.1.7 gcc: 14.2.1 Shell: garuda-inxi
default: fish v: 4.0.1 running-in: konsole inxi: 3.3.37
Garuda (2.7.2-1):
System install date:     2025-03-23
Last full system update: 2025-04-06 ↻
Is partially upgraded:   No
Relevant software:       snapper NetworkManager dracut nvidia-dkms
Windows dual boot:       Probably (Run as root to verify)
Failed units:

Kayo · 8 April 2025 02:43

When did this issue first start?
Check and see if the issue persists after a restart.
( ↻ means there is a pending restart after updates)

blazeheroic · 8 April 2025 02:47

I just tried a restart, and the issue is still there. Here is the updated garuda-inxi

System:
Kernel: 6.13.8-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=febaf9ad-0482-4918-ab5a-fefa9211638a rw rootflags=subvol=@
quiet loglevel=3 ibt=off
Desktop: KDE Plasma v: 6.3.4 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: MSI model: Z97S SLI Krait Edition (MS-7922) v: 2.0
serial: <superuser required> uuid: <superuser required>
UEFI: American Megatrends v: 10.6 date: 08/13/2015
CPU:
Info: model: Intel Core i5-4690K bits: 64 type: MCP arch: Haswell
gen: core 4 level: v3 note: check built: 2013-15 process: Intel 22nm
family: 6 model-id: 0x3C (60) stepping: 3 microcode: 0x28
Topology: cpus: 1x dies: 1 clusters: 4 cores: 4 smt: <unsupported> cache:
L1: 256 KiB desc: d-4x32 KiB; i-4x32 KiB L2: 1024 KiB desc: 4x256 KiB
L3: 6 MiB desc: 1x6 MiB
Speed (MHz): avg: 3900 min/max: 800/3900 scaling: driver: intel_cpufreq
governor: performance cores: 1: 3900 2: 3900 3: 3900 4: 3900 bogomips: 27997
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities: <filter>
Graphics:
Device-1: NVIDIA GM206 [GeForce GTX 960] vendor: ASUSTeK driver: nvidia
v: 570.133.07 alternate: nouveau,nvidia_drm non-free: 550/565.xx+
status: current (as of 2025-01; EOL~2026-12-xx) arch: Maxwell code: GMxxx
process: TSMC 28nm built: 2014-2019 pcie: gen: 3 speed: 8 GT/s lanes: 16
ports: active: none off: HDMI-A-1 empty: DP-1, DP-2, DP-3, DVI-I-1
bus-ID: 01:00.0 chip-ID: 10de:1401 class-ID: 0300
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
alternate: fbdev,nouveau,nv,vesa gpu: nvidia,nvidia-nvswitch display-ID: 0
Monitor-1: HDMI-A-1 model: ASUS VG27V serial: <filter> built: 2020 res:
mode: 1920x1080 hz: 165 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 nouveau drv: nvidia platforms: device: 0
drv: nvidia device: 1 drv: nouveau device: 2 drv: swrast gbm: drv: nvidia
surfaceless: drv: nvidia wayland: drv: nvidia x11: drv: nvidia
API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 570.133.07
glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce GTX 960/PCIe/SSE2
memory: 3.91 GiB display-ID: :1.0
API: Vulkan v: 1.4.309 layers: 9 device: 0 type: discrete-gpu
name: NVIDIA GeForce GTX 960 driver: N/A device-ID: 10de:1401
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: Intel 9 Series Family HD Audio vendor: Micro-Star MSI
driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:8ca0
class-ID: 0403
Device-2: NVIDIA GM206 High Definition Audio vendor: ASUSTeK
driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16
bus-ID: 01:00.1 chip-ID: 10de:0fba class-ID: 0403
API: ALSA v: k6.13.8-zen1-1-zen 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: 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: d000 bus-ID: 05:00.0 chip-ID: 10ec:8168 class-ID: 0200
IF: enp5s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Info: services: NetworkManager, smbd, systemd-timesyncd
Drives:
Local Storage: total: 3.86 TiB used: 169.33 GiB (4.3%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: Silicon Power
model: SPCC Solid State Disk size: 223.57 GiB block-size: physical: 512 B
logical: 512 B speed: 6.0 Gb/s tech: SSD serial: <filter> fw-rev: 4H
scheme: GPT
ID-2: /dev/sdb maj-min: 8:16 vendor: Seagate model: ST2000DX002-2DV164
size: 1.82 TiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
tech: HDD rpm: 7200 serial: <filter> fw-rev: CC41 scheme: GPT
ID-3: /dev/sdc maj-min: 8:32 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: 3B6Q scheme: GPT
ID-4: /dev/sdd maj-min: 8:48 vendor: Western Digital
model: WD10JMVW-11AJGS1 size: 931.48 GiB block-size: physical: 512 B
logical: 512 B type: USB rev: 3.0 spd: 5 Gb/s lanes: 1 mode: 3.2 gen-1x1
tech: HDD rpm: 5400 serial: <filter> fw-rev: 1042 scheme: MBR
Partition:
ID-1: / raw-size: 931.22 GiB size: 931.22 GiB (100.00%)
used: 169.33 GiB (18.2%) fs: btrfs dev: /dev/sdc2 maj-min: 8:34
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 608 KiB (0.2%) fs: vfat dev: /dev/sdc1 maj-min: 8:33
ID-3: /home raw-size: 931.22 GiB size: 931.22 GiB (100.00%)
used: 169.33 GiB (18.2%) fs: btrfs dev: /dev/sdc2 maj-min: 8:34
ID-4: /var/log raw-size: 931.22 GiB size: 931.22 GiB (100.00%)
used: 169.33 GiB (18.2%) fs: btrfs dev: /dev/sdc2 maj-min: 8:34
ID-5: /var/tmp raw-size: 931.22 GiB size: 931.22 GiB (100.00%)
used: 169.33 GiB (18.2%) fs: btrfs dev: /dev/sdc2 maj-min: 8:34
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: zram size: 15.56 GiB used: 0 KiB (0.0%) priority: 100
comp: zstd avail: lzo-rle,lzo,lz4,lz4hc,deflate,842 max-streams: 4
dev: /dev/zram0
Sensors:
System Temperatures: cpu: 51.0 C mobo: N/A
Fan Speeds (rpm): N/A
Info:
Memory: total: 16 GiB available: 15.56 GiB used: 2.85 GiB (18.3%)
Processes: 287 Power: uptime: 1m states: freeze,mem,disk suspend: deep
avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
suspend, test_resume image: 6.16 GiB services: org_kde_powerdevil,
power-profiles-daemon, upowerd Init: systemd v: 257 default: graphical
tool: systemctl
Packages: pm: pacman pkgs: 1828 libs: 562 tools: octopi,paru pm: flatpak
pkgs: 0 Compilers: clang: 19.1.7 gcc: 14.2.1 Shell: garuda-inxi
default: fish v: 4.0.1 running-in: konsole inxi: 3.3.37
Garuda (2.7.2-1):
System install date:     2025-03-23
Last full system update: 2025-04-06
Is partially upgraded:   No
Relevant software:       snapper NetworkManager dracut nvidia-dkms
Windows dual boot:       Probably (Run as root to verify)
Failed units:

Kayo · 8 April 2025 02:50

It sounds like there might be an issue with Panel Colorizer. You could try disabling its effects on maximized windows or disabling it altogether.
(Right click on the panel and select Show Panel Confirguration. hovering over certain areas of the panel lets you see the currently select widget’s options to either Remove or Configure)

blazeheroic · 8 April 2025 02:53

Ok, so disabling the panel colorizer on the full taskbar does work. Do you know of a way to troubleshoot this issue? Like, is there an update or a config change I can make to fix this?

EDIT: the issue appears to be with the “Dr4gonized Top Panel Interaction” preset in the colorizer. I tried other presets and they seemed to work fine.

Kayo · 8 April 2025 03:02

Looks like there is an update that just dropped 24 hours ago to fix color issues with Plasma 6.3.4

The version in the AUR / Chaotic AUR should be up to date as well. (lists version 2.4.2 as well). I would suggest to try updating with garuda-update again (and restarting afterwards), as there is a chance you might of just missed the update last time.

blazeheroic · 8 April 2025 03:04

That looks like it fixed it. Thanks for the help

Locutus · 8 April 2025 08:15

All you had to do was use the forum search to find out there was issue and a update.

yiannisp · 8 April 2025 11:46

Do a garuda-update. The issue has been fixed.

Locutus · 8 April 2025 12:06

Do a forum search and you would know I already know that and that’s why I suggested the forum search in the first place.

nepti · 8 April 2025 12:21

The issue has been fixed and this topic has been resolved.

So everything has been said and there is no need to start a discussion that might escalate.

That’s why I’m closing here.

Kayo · 8 April 2025 17:27

Weird how there isn’t any thread title talking about that specific issue?
Looks like the opening poster followed the template (I really don’t see many first time posters post garuda-inxi without reading it) so I’m pretty sure they searched. I don’t think we should be be making backhanded comments.
Even if they did saw there was an update, the times where it comes available in the Chaotic AUR is a bit different, and that version was only very recently available. That would make it just hours difference most likely since their last update. Though I’m not quite sure if you read the whole thread here before you made a quick no-value-added remark on a solved thread.