Some Theming issue in Plasma 6

[appu]

I have reinstall the KDE dragonized plasma with last release plasma 6 ISO …

i found some theming issue…

• themeing not applied to root mode : when i open dolphin as root, or in case of garuda apps like (garuda network assistent, garuda boot options, ) … it uses breeze-light or maybe oxygen light theme.
  

  

• garuda apps are not match kavantum theme : the garuda welcome apps or garuda assistent … they seems to be using oxygen theme …not kvantum theme …
  

  

i also changed the kvantum theme …not works …
trying to copy /etc/skel/ to / … still not work …

╰─λ garuda-inxi
System:
Kernel: 6.10.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=b15106c4-d6fc-4f10-9f9e-12d2b1293736 rw rootflags=subvol=@
quiet resume=UUID=46d434b4-5a6a-4b78-8be1-c8e05a25cbb4 loglevel=3 ibt=off
Desktop: KDE Plasma v: 6.1.5 tk: Qt v: N/A info: frameworks v: 6.6.0
wm: kwin_wayland vt: 1 dm: SDDM Distro: Garuda base: Arch Linux
Machine:
Type: Desktop System: Gigabyte product: B450M K v: -CF
serial: <superuser required>
Mobo: Gigabyte model: B450M K-CF v: x.x serial: <superuser required>
uuid: <superuser required> UEFI: American Megatrends LLC. v: FDd
date: 09/02/2024
CPU:
Info: model: AMD Ryzen 5 4600G with Radeon Graphics 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: 0x60 (96) stepping: 1
microcode: 0x860010D
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: 8 MiB desc: 2x4 MiB
Speed (MHz): avg: 400 min/max: 400/4308 scaling: driver: amd-pstate-epp
governor: performance cores: 1: 400 2: 400 3: 400 4: 400 5: 400 6: 400
7: 400 8: 400 9: 400 10: 400 11: 400 12: 400 bogomips: 88635
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] Renoir [Radeon Vega Series /
Radeon Mobile Series] vendor: Gigabyte driver: amdgpu v: kernel
arch: GCN-5 code: Vega process: GF 14nm built: 2017-20 pcie: gen: 3
speed: 8 GT/s lanes: 16 link-max: gen: 4 speed: 16 GT/s ports:
active: DP-1 empty: HDMI-A-1 bus-ID: 09:00.0 chip-ID: 1002:1636
class-ID: 0300 temp: 40.0 C
Display: wayland server: X.org v: 1.21.1.13 with: Xwayland v: 24.1.2
compositor: kwin_wayland driver: X: loaded: amdgpu unloaded: modesetting
alternate: fbdev,vesa dri: radeonsi gpu: amdgpu display-ID: 0
Monitor-1: DP-1 res: 1366x768 size: N/A modes: N/A
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.2.3-arch1.1
glx-v: 1.4 direct-render: yes renderer: AMD Radeon Graphics (radeonsi
renoir LLVM 18.1.8 DRM 3.57 6.10.10-zen1-1-zen) device-ID: 1002:1636
memory: 500 MiB unified: no display-ID: :1.0
API: Vulkan v: 1.3.295 layers: 3 device: 0 type: integrated-gpu name: AMD
Radeon Graphics (RADV RENOIR) driver: mesa radv v: 24.2.3-arch1.1
device-ID: 1002:1636 surfaces: xcb,xlib,wayland device: 1 type: cpu
name: llvmpipe (LLVM 18.1.8 256 bits) driver: mesa llvmpipe
v: 24.2.3-arch1.1 (LLVM 18.1.8) device-ID: 10005:0000
surfaces: xcb,xlib,wayland
Audio:
Device-1: Advanced Micro Devices [AMD/ATI] Renoir Radeon High Definition
Audio driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16
link-max: gen: 4 speed: 16 GT/s bus-ID: 09:00.1 chip-ID: 1002:1637
class-ID: 0403
Device-2: Advanced Micro Devices [AMD] Family 17h/19h HD Audio
vendor: Gigabyte driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s
lanes: 16 link-max: gen: 4 speed: 16 GT/s bus-ID: 09:00.6
chip-ID: 1022:15e3 class-ID: 0403
API: ALSA v: k6.10.10-zen1-1-zen status: kernel-api tools: N/A
Server-1: PipeWire v: 1.2.5 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: Gigabyte driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s
lanes: 1 port: f000 bus-ID: 08:00.0 chip-ID: 10ec:8168 class-ID: 0200
IF: enp8s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Info: services: NetworkManager, smbd, systemd-timesyncd
Drives:
Local Storage: total: 1.58 TiB used: 61.25 GiB (3.8%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: Seagate model: ST3500413AS
size: 465.76 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
tech: HDD rpm: 7200 serial: <filter> fw-rev: JC4B scheme: GPT
ID-2: /dev/sdb maj-min: 8:16 vendor: Crucial model: CT240BX500SSD1
size: 223.57 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: 056 scheme: GPT
ID-3: /dev/sdc maj-min: 8:32 vendor: Western Digital
model: WD10EZEX-60WN4A0 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: MBR
Partition:
ID-1: / raw-size: 100 GiB size: 100 GiB (100.00%) used: 33.52 GiB (33.5%)
fs: btrfs dev: /dev/sdb2 maj-min: 8:18
ID-2: /boot/efi raw-size: 600 MiB size: 598.8 MiB (99.80%)
used: 584 KiB (0.1%) fs: vfat dev: /dev/sdb4 maj-min: 8:20
ID-3: /home raw-size: 100 GiB size: 100 GiB (100.00%)
used: 27.73 GiB (27.7%) fs: btrfs dev: /dev/sdb3 maj-min: 8:19
ID-4: /var/log raw-size: 100 GiB size: 100 GiB (100.00%)
used: 33.52 GiB (33.5%) fs: btrfs dev: /dev/sdb2 maj-min: 8:18
ID-5: /var/tmp raw-size: 100 GiB size: 100 GiB (100.00%)
used: 33.52 GiB (33.5%) fs: btrfs dev: /dev/sdb2 maj-min: 8:18
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: zram size: 15 GiB used: 0 KiB (0.0%) priority: 100
comp: zstd avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 12 dev: /dev/zram0
ID-2: swap-2 type: partition size: 4.03 GiB used: 0 KiB (0.0%)
priority: -2 dev: /dev/sdb1 maj-min: 8:17
Sensors:
System Temperatures: cpu: 45.9 C mobo: 37.0 C gpu: amdgpu temp: 39.0 C
Fan Speeds (rpm): N/A
Info:
Memory: total: 16 GiB note: est. available: 15 GiB used: 4.4 GiB (29.3%)
Processes: 349 Power: uptime: 38m states: freeze,mem,disk suspend: deep
avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
suspend, test_resume image: 5.99 GiB services: org_kde_powerdevil,
power-profiles-daemon, upowerd Init: systemd v: 256 default: graphical
tool: systemctl
Packages: pm: pacman pkgs: 1612 libs: 437 tools: octopi,paru Compilers:
clang: 18.1.8 gcc: 14.2.1 Shell: garuda-inxi default: fish v: 3.7.1
running-in: konsole inxi: 3.3.36
Garuda (2.6.26-1):
System install date:     2024-09-19
Last full system update: 2024-09-30 
Is partially upgraded:   No
Relevant software:       snapper NetworkManager dracut
Windows dual boot:       Probably (Run as root to verify)
Failed units:

[SGS]

@appu

Last full system update: 2024-09-30 ↻

reboot

• After rebooting, post the FULL output of garuda-inxi in the body of the post (not linked externally, or collapsed with the “hide details” feature)

@appu

themeing not applied to root mode

Sure

@appu

when i open dolphin as root

Why?

Just use the terminal if you do not like the light theme like me.

dolphin --sudo
sudo -E garuda-network-assistant

and so on.

[elite]

@appu

themeing not applied to root mode

Because its root. normally you don’t want any theming or anything in root. a quick fix is just to log in as root an log out an never touch it. As it will get the normal dragonized theming.

[FGD]

@elite

normally you don’t want any theming or anything in root.

Precisely! We do not do anything at all theming-wise for root.

[appu]

ok let dolphin out… i just trying root cause i’v to get something from fedora root partition in another disk,

but what about garuda apps …

previously - all the garuda apps uses kvantm theming … + when open as root (or the apps required root password to open) follows dragonized-sweet theme

even when updated from plasma 5 to 6 everything was fine …

but after complete reinstalling this … i got these issues …

[appu]

i think the themeing configurations in /etc/skel/.config/kvantum should be applied globaly …

[FGD]

The /etc/skel/ folder is for storing Garuda’s default files, in case for example anyone needs to revert by manually copying them to the corresponding user’s Home folder.

In your example that would be ~/.config/Kvantum/.
I’m not entirely sure but I think the ISO install process also uses those files to copy them in the corresponding user’s Home folders on 1st install…

What I mean is they are not root files.
I cannot say what changed in your reinstall, on my end I do not do anything for Garuda (and myself) with root theming-wise, won’t touch this with a 100-foot pole.

I’m pretty sure many other people on any distro have found ways to apply theming to root.

[BluishHumility]

@appu

• garuda apps are not match kavantum theme
  […]
  i also changed the kvantum theme …not works …

Double-check that you have kvantum-qt5 installed.

@FGD

The /etc/skel/ folder is for storing Garuda’s default files, in case for example anyone needs to revert by manually copying them to the corresponding user’s Home folder.

In your example that would be ~/.config/Kvantum/.
I’m not entirely sure but I think the ISO install process also uses those files to copy them in the corresponding user’s Home folders on 1st install…

The /etc/skel directory is automatically copied to the home directory of a newly created user. This happens any time a new user is created, including when they are being set up during the installation process.

In the case of Garuda Linux, the files in /etc/skel are also copied over to /root due to this custom Calamares job: calamares-garuda/0001-Apply-garuda-specific-patches.patch · main · Garuda Linux 🦅 / PKGBUILDs · GitLab. On the back of a fresh install, the root user should inherit the same configuration from /etc/skel that a normal user account does.

@FGD

I’m pretty sure many other people on any distro have found ways to apply theming to root.

Yes, there are many ways to do this. The ArchWiki has some suggestions here: Qt - ArchWiki and here: GTK - ArchWiki. What ends up being most practical will depend on the DE in use, and how theming is being applied in general.

For our Sway spin, env_keep is set in a /etc/sudoers.d drop-in to allow root to inherit the QT_STYLE_OVERRIDE environment variable. garuda/sway/desktop-overlay/etc/sudoers.d/sway-env · master · Garuda Linux 🦅 / Tools / iso-profiles · GitLab. I don’t think KDE uses this environment variable, but the point is if another environment variable is used for specifying the theme then that can be passed along in /etc/sudoers the same way.

[FGD]

@BluishHumility

In the case of Garuda Linux, the files in /etc/skel are also copied over to /root due to this custom Calamares job: calamares-garuda/0001-Apply-garuda-specific-patches.patch · main · Garuda Linux / PKGBUILDs · GitLab. On the back of a fresh install, the root user should inherit the same configuration from /etc/skel that a normal user account does.

Ok that’s interesting to know.
Root should have the same theme. It’s not applied via Root theming but rather via a simple copy script during installation.

All that makes better sense now.