Themes (global) not applying right

Good afternoon,
I am experiencing a problem i never had on my previous runs with garuda. I am using the gaming version. Currently, I am unable to download new themes from the global theme section of system settings. After clicking download it sits for a while and the system settings crash.
When I then download from the online site (store.kde.org) they install but do not apply correctly at all. the basic color applies but no transparency nor other global effects. Any ideas?

Post you inxi -Faz , please.

2 Likes

Maybe it could be this KDE bug (fixed in 5.23.5), although it is strange that it occurred to you only after a certain update (if I understand correctly)
https://bugs.kde.org/show_bug.cgi?id=439797

1 Like

Im sorry, im assuming it's a log file, where would I find this? My apoligies for not knowing...

Sorry i did not clarify, This is a fresh install on a new system. out of the gate it won't take themes. 112921 is the iso im using.

From the template you deleted to post your problem.


Hello.

Post your terminal/konsole in- and output as text (no pictures) from:

inxi -Faz

Without it, you will not receive any help from the Garuda team or your topic is likely to be closed without notice.

Before you open a new help request, read relevant sections of the Arch and Garuda wiki.
Thoroughly search your issue and any error messages in the forum and on the web.

Report everything you have already attempted to solve your problem.

1 Like

My apologies, I was posting on my phone and didn't carefully read the section. I am not home but when I get home I will post the info requested.

Sorry for the late reply...Here is the output:

System:    Kernel: 5.15.7-zen1-1-zen x86_64 bits: 64 compiler: gcc v: 11.1.0
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen root=UUID=61771b1b-121d-4222-a19d-570cce02866f
rw [email protected] quiet splash rd.udev.log_priority=3 vt.global_cursor_default=0
systemd.unified_cgroup_hierarchy=1 loglevel=3
Desktop: KDE Plasma 5.23.4 tk: Qt 5.15.2 info: latte-dock wm: kwin_x11 vt: 1 dm: SDDM
Distro: Garuda Linux base: Arch Linux
Machine:   Type: Desktop System: HP product: HP Pavilion Gaming Desktop 690-00xx v: N/A
serial: <superuser required> Chassis: type: 3 serial: <superuser required>
Mobo: HP model: 8433 v: 11 serial: <superuser required> UEFI: AMI v: F.21 date: 12/12/2018
CPU:       Info: 8-Core model: AMD Ryzen 7 2700 bits: 64 type: MT MCP arch: Zen+ family: 17 (23)
model-id: 8 stepping: 2 microcode: 800820D cache: L1: 768 KiB L2: 4 MiB L3: 16 MiB
flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 102211
Speed: 2615 MHz min/max: 1550/3200 MHz boost: enabled Core speeds (MHz): 1: 2615 2: 3075
3: 2807 4: 2515 5: 2732 6: 2850 7: 3578 8: 3663 9: 2715 10: 2415 11: 3009 12: 3326 13: 2354
14: 2782 15: 2778 16: 2338
Vulnerabilities: Type: itlb_multihit status: Not affected
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2
mitigation: Full AMD retpoline, IBPB: conditional, STIBP: disabled, RSB filling
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics:  Device-1: AMD Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] vendor: Hewlett-Packard
driver: amdgpu v: kernel bus-ID: 1d:00.0 chip-ID: 1002:67df class-ID: 0300
Display: x11 server: X.Org 1.21.1.1 compositor: kwin_x11 driver: loaded: amdgpu,ati
unloaded: modesetting alternate: fbdev,vesa display-ID: :0 screens: 1
Screen-1: 0 s-res: 5326x1920 s-dpi: 96 s-size: 1405x506mm (55.3x19.9") s-diag: 1493mm (58.8")
Monitor-1: DisplayPort-0 res: 1920x1080 hz: 60 dpi: 93 size: 527x296mm (20.7x11.7")
diag: 604mm (23.8")
Monitor-2: DisplayPort-1 res: 1920x1080 hz: 60 dpi: 82 size: 598x336mm (23.5x13.2")
diag: 686mm (27")
Monitor-3: HDMI-A-0 res: 1080x1920 hz: 60
Message: Unable to show advanced data. Required tool glxinfo missing.
Audio:     Device-1: AMD Ellesmere HDMI Audio [Radeon RX 470/480 / 570/580/590] vendor: Hewlett-Packard
driver: snd_hda_intel v: kernel bus-ID: 1d:00.1 chip-ID: 1002:aaf0 class-ID: 0403
Device-2: AMD Family 17h HD Audio vendor: Hewlett-Packard driver: snd_hda_intel v: kernel
bus-ID: 1f:00.3 chip-ID: 1022:1457 class-ID: 0403
Sound Server-1: ALSA v: k5.15.7-zen1-1-zen running: yes
Sound Server-2: JACK v: 1.9.19 running: no
Sound Server-3: PulseAudio v: 15.0 running: no
Sound Server-4: PipeWire v: 0.3.40 running: yes
Network:   Device-1: Realtek RTL8821CE 802.11ac PCIe Wireless Network Adapter vendor: Hewlett-Packard
driver: rtw_8821ce v: N/A modules: rtw88_8821ce port: f000 bus-ID: 17:00.0 chip-ID: 10ec:c821
class-ID: 0280
IF: wlo1 state: up mac: <filter>
Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Hewlett-Packard
driver: r8169 v: kernel port: e000 bus-ID: 1c:00.0 chip-ID: 10ec:8168 class-ID: 0200
IF: enp28s0 state: down mac: <filter>
Bluetooth: Device-1: Realtek Realtek Bluetooth 4.2 Adapter type: USB driver: btusb v: 0.8 bus-ID: 1-10:4
chip-ID: 0bda:b00a class-ID: e001 serial: <filter>
Report: bt-adapter ID: hci0 rfk-id: 0 state: up address: <filter>
Drives:    Local Storage: total: 4.66 TiB used: 32 GiB (0.7%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /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 type: HDD rpm: 5400
serial: <filter> rev: 0A82 scheme: GPT
ID-2: /dev/sdb maj-min: 8:16 vendor: Samsung model: MZNLN128HAHQ-000H1 size: 119.24 GiB
block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter>
rev: 4H3Q scheme: GPT
ID-3: /dev/sdc maj-min: 8:32 vendor: Seagate model: ST1000DM003-1SB102 size: 931.51 GiB
block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 7200
serial: <filter> rev: HPH4 scheme: GPT
Partition: ID-1: / raw-size: 118.95 GiB size: 118.95 GiB (100.00%) used: 32 GiB (26.9%) fs: btrfs
dev: /dev/sdb2 maj-min: 8:18
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%) used: 576 KiB (0.2%) fs: vfat
dev: /dev/sdb1 maj-min: 8:17
ID-3: /home raw-size: 118.95 GiB size: 118.95 GiB (100.00%) used: 32 GiB (26.9%) fs: btrfs
dev: /dev/sdb2 maj-min: 8:18
ID-4: /var/log raw-size: 118.95 GiB size: 118.95 GiB (100.00%) used: 32 GiB (26.9%) fs: btrfs
dev: /dev/sdb2 maj-min: 8:18
ID-5: /var/tmp raw-size: 118.95 GiB size: 118.95 GiB (100.00%) used: 32 GiB (26.9%) fs: btrfs
dev: /dev/sdb2 maj-min: 8:18
Swap:      Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: zram size: 15.6 GiB used: 33.2 MiB (0.2%) priority: 100 dev: /dev/zram0
Sensors:   System Temperatures: cpu: 58.0 C mobo: N/A gpu: amdgpu temp: 51.0 C
Fan Speeds (RPM): N/A gpu: amdgpu fan: 1331
Info:      Processes: 370 Uptime: 2h 0m wakeups: 0 Memory: 15.6 GiB used: 3.26 GiB (20.9%) Init: systemd
v: 249 tool: systemctl Compilers: gcc: 11.1.0 clang: 13.0.0 Packages: pacman: 1795 lib: 329
Shell: fish v: 3.3.1 default: Bash v: 5.1.12 running-in: konsole inxi: 3.3.09
McFly: Importing shell history for the first time. This may take a minute or two...done.

i did just notice, i am on .4 of kde, not ,5 which supposedly fixed the crashing, is this correct?

That bug is fixed but pending to be released with the next KDE release 5.23.5, whenever this will occur...
I edited your post to format the inxi part properly :blush:
Yesterday, I fired up a KDE barebones VM, updated it, and tried to switch to a completely different global theme, and system settings actually crashed.
Of course this is not proving/repeating the bug, because in my opinion global themes are quite "delicate" and complex, changing a lot of things in cascade, so I guess they are more "error" prone, meaning that you should be careful when selecting and testing them.

2 Likes

Hello,
Thank you for formatting that for me :slight_smile: much appriciated. I do realize global themes are very error prone, i was just confused because the release I was using before redoing my machine (from back in august) the same theme worked perfectly, and the november version had crashes when trying ot get the same theme applied. Thanks for testing that for me, at least its not me skrewing up :slight_smile:

1 Like

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