Problem with applying themes

When I choose to install any theme with the checkboxes for design parameters and widget and window locations enabled, only the open System Settings window remains on the desktop. The theme itself, the desktop, desktop shortcuts, wallpaper, everything disappears, a black screen. If I close the Settings, there will just be a black background. If I set a background image, the system immediately freezes. So with any theme that is installed or downloaded. The applied theme will work after rebooting the computer.
I thought I was the only one with this. So I’m not alone, there are many of us. By the way, this is because of some updates. Because I booted from a bootable USB flash drive and everything was fine. And on the newly installed system, everything was fine too, until the 3GB update arrived after installation.
And it also annoys me that on some themes, and now it’s Breeze, when you open a window to the entire desktop, there are no close or minimize buttons in the corner of the window. But in the Dr460nized theme, if the window is not yet open to the full screen, then the open button is, for example, on the far right, but when the window is open to the full desktop, then the open button is already in the middle. As if they are swapped. Which is a little annoying.
garuda-inxi

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=b78d0f32-bdb0-4fc2-9410-34dbd76a876b rw rootflags=subvol=@
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 tools: avail: lxlock,xtrlock vt: 1 dm: SDDM Distro: Garuda
base: Arch Linux
Machine:
Type: Desktop System: Micro-Star product: MS-7B89 v: 1.0
serial: <superuser required>
Mobo: Micro-Star model: B450M MORTAR MAX (MS-7B89) v: 1.0
serial: <superuser required> uuid: <superuser required> UEFI: American
Megatrends LLC. v: 2.M0 date: 08/22/2024
Battery:
Device-1: apple_mfi_fastcharge model: N/A serial: N/A charge: N/A
status: N/A
CPU:
Info: model: AMD Ryzen 5 3600 bits: 64 type: MT MCP arch: Zen 2 gen: 2
level: v3 note: check built: 2020-22 process: TSMC n7 (7nm)
family: 0x17 (23) model-id: 0x71 (113) stepping: 0 microcode: 0x8701034
Topology: cpus: 1x dies: 1 clusters: 1 cores: 6 threads: 12 tpc: 2
smt: enabled cache: L1: 384 KiB desc: d-6x32 KiB; i-6x32 KiB L2: 3 MiB
desc: 6x512 KiB L3: 32 MiB desc: 2x16 MiB
Speed (MHz): avg: 3603 min/max: 550/4208 boost: enabled scaling:
driver: amd-pstate-epp governor: powersave cores: 1: 3603 2: 3603 3: 3603
4: 3603 5: 3603 6: 3603 7: 3603 8: 3603 9: 3603 10: 3603 11: 3603 12: 3603
bogomips: 86405
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] Navi 21 [Radeon RX 6800/6800 XT
/ 6900 XT] vendor: ASRock driver: amdgpu v: kernel arch: RDNA-2
code: Navi-2x process: TSMC n7 (7nm) built: 2020-22 pcie: gen: 4
speed: 16 GT/s lanes: 16 ports: active: HDMI-A-1 empty: DP-1, DP-2, DP-3,
Writeback-1 bus-ID: 28:00.0 chip-ID: 1002:73bf class-ID: 0300
Display: wayland server: X.org v: 1.21.1.15 with: Xwayland v: 24.1.5
compositor: kwin_wayland driver: X: loaded: amdgpu
unloaded: modesetting,radeon alternate: fbdev,vesa dri: radeonsi
gpu: amdgpu display-ID: 0
Monitor-1: HDMI-A-1 model: Asus ML229 serial: <filter> built: 2012 res:
mode: 1920x1080 hz: 60 scale: 100% (1) dpi: 103 gamma: 1.2
size: 475x267mm (18.7x10.51") diag: 545mm (21.5") ratio: 16:9 modes:
max: 1920x1080 min: 720x400
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 RX 6800 (radeonsi navi21
LLVM 19.1.7 DRM 3.59 6.13.1-zen3-1-zen) device-ID: 1002:73bf
memory: 15.62 GiB unified: no display-ID: :1.0
API: Vulkan v: 1.4.303 layers: 15 device: 0 type: discrete-gpu name: AMD
Radeon RX 6800 (RADV NAVI21) driver: N/A device-ID: 1002:73bf
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] Navi 21/23 HDMI/DP Audio
driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
bus-ID: 28:00.1 chip-ID: 1002:ab28 class-ID: 0403
Device-2: Advanced Micro Devices [AMD] Starship/Matisse HD Audio
vendor: Micro-Star MSI driver: snd_hda_intel v: kernel pcie: gen: 4
speed: 16 GT/s lanes: 16 bus-ID: 2a:00.4 chip-ID: 1022:1487 class-ID: 0403
Device-3: ASUSTek TUF GAMING H5/H7
driver: hid-generic,snd-usb-audio,usbhid type: USB rev: 2.0 speed: 12 Mb/s
lanes: 1 mode: 1.1 bus-ID: 3-4:5 chip-ID: 0b05:189c class-ID: 0300
serial: <filter>
API: ALSA v: k6.13.1-zen3-1-zen status: kernel-api with: aoss
type: oss-emulator 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 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: f000 bus-ID: 22:00.0 chip-ID: 10ec:8168 class-ID: 0200
IF: enp34s0 state: up speed: 100 Mbps duplex: full mac: <filter>
IF-ID-1: enp3s0f0u9c4i2 state: down mac: <filter>
Info: services: NetworkManager,systemd-timesyncd
Bluetooth:
Device-1: Cambridge Silicon Radio Bluetooth Dongle (HCI mode) driver: btusb
v: 0.8 type: USB rev: 2.0 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-7:2
chip-ID: 0a12:0001 class-ID: e001
Report: btmgmt ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 4.0
lmp-v: 6 status: discoverable: no pairing: no class-ID: 7c0104
Drives:
Local Storage: total: 1.47 TiB used: 987.62 GiB (65.4%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: AMD Radeon model: R5MP120G8
size: 111.79 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s
lanes: 4 tech: SSD serial: <filter> fw-rev: T1103F0L temp: 38.9 C
scheme: GPT
ID-2: /dev/nvme1n1 maj-min: 259:3 vendor: Western Digital
model: WD BLACK SN750 SE 500GB size: 465.76 GiB block-size: physical: 512 B
logical: 512 B speed: 63.2 Gb/s lanes: 4 tech: SSD serial: <filter>
fw-rev: 711250WD temp: 34.9 C scheme: GPT
ID-3: /dev/sda maj-min: 8:0 vendor: Western Digital
model: WD10EZEX-75WN4A0 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: 1A01 scheme: GPT
Partition:
ID-1: / raw-size: 111.5 GiB size: 111.5 GiB (100.00%)
used: 15.96 GiB (14.3%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 584 KiB (0.2%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
ID-3: /home raw-size: 465.76 GiB size: 465.76 GiB (100.00%)
used: 430.66 GiB (92.5%) fs: btrfs dev: /dev/nvme1n1p4 maj-min: 259:4
ID-4: /var/log raw-size: 111.5 GiB size: 111.5 GiB (100.00%)
used: 15.96 GiB (14.3%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-5: /var/tmp raw-size: 111.5 GiB size: 111.5 GiB (100.00%)
used: 15.96 GiB (14.3%) fs: btrfs 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: 15.54 GiB used: 0 KiB (0.0%) priority: 100
comp: zstd avail: lzo-rle,lzo,lz4,lz4hc,deflate,842 max-streams: 12
dev: /dev/zram0
Sensors:
System Temperatures: cpu: 36.2 C mobo: N/A gpu: amdgpu temp: 38.0 C
mem: 36.0 C
Fan Speeds (rpm): N/A gpu: amdgpu fan: 0
Info:
Memory: total: 16 GiB available: 15.54 GiB used: 4.28 GiB (27.5%)
Processes: 421 Power: uptime: 26m states: freeze,mem,disk suspend: deep
avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
suspend, test_resume image: 6.21 GiB services: org_kde_powerdevil,
power-profiles-daemon, upowerd Init: systemd v: 257 default: graphical
tool: systemctl
Packages: 1873 pm: pacman pkgs: 1846 libs: 546 tools: octopi,pamac,paru
pm: flatpak pkgs: 27 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:     2025-02-09
Last full system update: 2025-02-09
Is partially upgraded:   No
Relevant software:       snapper NetworkManager dracut
Windows dual boot:       No/Undetected
Failed units:


1 Like

I can confirm it - switch from “Dr460nized” to “Breeze” (no matter which theme and in which direction) - as soon as “Layout settings: Desktop layout” is selected and applied, the whole plasma-desktop is killed.

Tested with garuda-dr460nized-linux-zen-250201.iso (up to date) in a VM:


I can also confirm that. Logging out and back in via terminal or Ctrl + ALt + Del also works.

2 Likes

This is an known issue, but I don’t know if something from the base Garuda packages/configs causes this or if it’s Plasma.
Another reason to wait for Plasma 6.3 and see.

The workaround is immediately after applying a Global Theme, close the Settings window and CTRL-ALT-DEL, then either LOGOUT or REBOOT.
Be patient, it can take a while for Plasma to realize you asked it to close.

2 Likes

Same issue with KDE neon (up to date):

4 Likes

OMG.
Well Plasma has sneaked another one. :rofl:

3 Likes

“The same procedure as every year, KDE!”

4 Likes

Short test with EnOS (VM). Fresh offline installation + reboot → no issues. After system update + reboot → same issue. :upside_down_face:

4 Likes

The bug can bee seen here 498175 – Desktop goes black and panels disappear when changing the global theme with "Desktop and window layout selected", until plasmashell is restarted

6 Likes

Not included in 6.3…
I will add my comment to that bug as well so KDE knows even more people have this issue.
Tnx for digging it up!

4 Likes

I am kind of happy to hear other people have this problem. I was installing a bunch of programs at once and was afraid I had messed it up somehow.

1 Like

The bug is still there in 6.4 dev atm so hopping it comes in a 6.3.1 release.

2 Likes

the bug is fixed in 6.3.2

3 Likes

Yes Nate himself updated this morning. :smile:

3 Likes

6.3.2 is in the repo since yesterday. Is fixed and even works. :smiley:

1 Like

Yes I tested that yesterday, works exactly as it should now!

1 Like

Applying themes works now, but I still can’t add widgets to dragonized

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