Space Remaining indicator obscured

Hi again!

My space information text in Dolphin, is obscured as show in photo. This happened a while back after a big issue with brtfs missing space for snapshots that I chose to solve manually, to learn.

I’m still green on Linux in general, so I have no clue how to fix this. This is theme specific, as changing it to any other Breeze default fixes the issue, but I really like the Dragonized theme.

Is there any way I can fully reinstall the default dragonized theme? At this point I don’t care about losing other configurations, I’d just rather have this info back in this easy to reach place.

Thank you in advance!
image

System:
Kernel: 6.10.4-zen2-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=b652edd7-a598-45e7-bbe6-99791107dfbd rw rootflags=subvol=@
quiet loglevel=3 ibt=off
Desktop: KDE Plasma v: 6.1.4 tk: Qt v: N/A info: frameworks v: 6.4.0
wm: kwin_x11 vt: 2 dm: SDDM Distro: Garuda base: Arch Linux
Machine:
Type: Desktop Mobo: Gigabyte model: B550M AORUS ELITE
serial: <superuser required> uuid: <superuser required> UEFI: American
Megatrends LLC. v: F16a date: 11/03/2022
CPU:
Info: model: AMD Ryzen 7 5700X bits: 64 type: MT MCP arch: Zen 3+ gen: 4
level: v3 note: check built: 2022 process: TSMC n6 (7nm) family: 0x19 (25)
model-id: 0x21 (33) stepping: 2 microcode: 0xA20120A
Topology: cpus: 1x cores: 8 tpc: 2 threads: 16 smt: enabled cache:
L1: 512 KiB desc: d-8x32 KiB; i-8x32 KiB L2: 4 MiB desc: 8x512 KiB
L3: 32 MiB desc: 1x32 MiB
Speed (MHz): avg: 2932 high: 3730 min/max: 2200/4662 boost: enabled
scaling: driver: acpi-cpufreq governor: schedutil cores: 1: 2200 2: 3227
3: 3400 4: 3361 5: 2875 6: 2870 7: 2872 8: 2195 9: 2467 10: 3458 11: 3730
12: 2873 13: 2902 14: 2872 15: 2877 16: 2742 bogomips: 108594
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Vulnerabilities: <filter>
Graphics:
Device-1: NVIDIA TU106 [GeForce RTX 2060 SUPER] driver: nvidia v: 555.58.02
alternate: nouveau,nvidia_drm non-free: 550.xx+ status: current (as of
2024-06; EOL~2026-12-xx) arch: Turing code: TUxxx process: TSMC 12nm FF
built: 2018-2022 pcie: gen: 3 speed: 8 GT/s lanes: 16 ports: active: none
off: DVI-D-1,HDMI-A-1 empty: DP-1 bus-ID: 05:00.0 chip-ID: 10de:1f06
class-ID: 0300
Display: x11 server: X.Org v: 21.1.13 with: Xwayland v: 24.1.2
compositor: kwin_x11 driver: X: loaded: nvidia unloaded: modesetting,nouveau
alternate: fbdev,nv,vesa gpu: nvidia,nvidia-nvswitch display-ID: :0
screens: 1
Screen-1: 0 s-res: 3520x1080 s-dpi: 90 s-size: 993x301mm (39.09x11.85")
s-diag: 1038mm (40.85")
Monitor-1: DVI-D-1 mapped: DVI-D-0 note: disabled pos: left
model: LG (GoldStar) E2060 built: 2012 res: 1600x900 hz: 60 dpi: 92
gamma: 1.2 size: 443x249mm (17.44x9.8") diag: 515mm (20.3") ratio: 16:9
modes: max: 1600x900 min: 640x480
Monitor-2: HDMI-A-1 mapped: HDMI-0 note: disabled pos: primary,right
model: Acer V226HQL serial: <filter> built: 2022 res: 1920x1080 hz: 60
dpi: 102 gamma: 1.2 size: 477x268mm (18.78x10.55") diag: 547mm (21.5")
ratio: 16:9 modes: max: 1920x1080 min: 640x480
API: EGL v: 1.5 hw: drv: nvidia platforms: device: 0 drv: nvidia device: 2
drv: swrast gbm: drv: nvidia surfaceless: drv: nvidia x11: drv: nvidia
inactive: wayland,device-1
API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 555.58.02
glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce RTX 2060
SUPER/PCIe/SSE2 memory: 7.81 GiB
API: Vulkan v: 1.3.279 layers: 8 device: 0 type: discrete-gpu name: NVIDIA
GeForce RTX 2060 SUPER driver: nvidia v: 555.58.02 device-ID: 10de:1f06
surfaces: xcb,xlib device: 1 type: cpu name: llvmpipe (LLVM 18.1.8 256
bits) driver: mesa llvmpipe v: 24.1.5-arch1.2 (LLVM 18.1.8)
device-ID: 10005:0000 surfaces: xcb,xlib
Audio:
Device-1: NVIDIA TU106 High Definition Audio driver: snd_hda_intel v: kernel
pcie: gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 05:00.1 chip-ID: 10de:10f9
class-ID: 0403
Device-2: AMD Starship/Matisse HD Audio vendor: Gigabyte
driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
bus-ID: 07:00.4 chip-ID: 1022:1487 class-ID: 0403
API: ALSA v: k6.10.4-zen2-1-zen status: kernel-api with: aoss
type: oss-emulator tools: alsactl,alsamixer,amixer
Server-1: PipeWire v: 1.2.2 status: active with: 1: pipewire-pulse
status: active 2: pipewire-media-session status: active 3: pipewire-alsa
type: plugin 4: pw-jack type: plugin tools: pactl,pw-cat,pw-cli
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: 04:00.0 chip-ID: 10ec:8168 class-ID: 0200
IF: enp4s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
IF-ID-1: br-209a26951ddc state: down mac: <filter>
IF-ID-2: docker0 state: down mac: <filter>
Info: services: NetworkManager, smbd, systemd-timesyncd
Bluetooth:
Device-1: Cambridge Silicon Radio Bluetooth Dongle (HCI mode) driver: btusb
v: 0.8 type: USB rev: 1.1 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-7:9
chip-ID: 0a12:0001 class-ID: e001
Report: btmgmt ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 5.1
lmp-v: 10 status: discoverable: no pairing: no class-ID: 6c0104
Drives:
Local Storage: total: 1.78 TiB used: 1.48 TiB (83.2%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Western Digital
model: WDS480G2G0C-00AJM0 size: 447.13 GiB block-size: physical: 512 B
logical: 512 B speed: 31.6 Gb/s lanes: 4 tech: SSD serial: <filter>
fw-rev: 231800WD temp: 35.9 C scheme: GPT
ID-2: /dev/sda maj-min: 8:0 vendor: Kingston model: SA400S37480G
size: 447.13 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: K1B3 scheme: MBR
ID-3: /dev/sdb maj-min: 8:16 vendor: Seagate model: ST1000VM002-1CT162
size: 931.51 GiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
tech: HDD rpm: 5900 serial: <filter> fw-rev: SC23 scheme: MBR
Partition:
ID-1: / raw-size: 125.59 GiB size: 125.59 GiB (100.00%)
used: 90.62 GiB (72.2%) fs: btrfs dev: /dev/nvme0n1p5 maj-min: 259:5
ID-2: /boot/efi raw-size: 100 MiB size: 96 MiB (96.00%)
used: 27.8 MiB (29.0%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
ID-3: /home raw-size: 125.59 GiB size: 125.59 GiB (100.00%)
used: 90.62 GiB (72.2%) fs: btrfs dev: /dev/nvme0n1p5 maj-min: 259:5
ID-4: /var/log raw-size: 125.59 GiB size: 125.59 GiB (100.00%)
used: 90.62 GiB (72.2%) fs: btrfs dev: /dev/nvme0n1p5 maj-min: 259:5
ID-5: /var/tmp raw-size: 125.59 GiB size: 125.59 GiB (100.00%)
used: 90.62 GiB (72.2%) fs: btrfs dev: /dev/nvme0n1p5 maj-min: 259:5
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: zram size: 31.25 GiB used: 0 KiB (0.0%) priority: 100
comp: zstd avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 16 dev: /dev/zram0
Sensors:
System Temperatures: cpu: 51.4 C mobo: 33.0 C gpu: nvidia temp: 40 C
Fan Speeds (rpm): N/A gpu: nvidia fan: 29%
Info:
Memory: total: 32 GiB available: 31.25 GiB used: 8.48 GiB (27.1%)
Processes: 414 Power: uptime: 10h 39m states: freeze,mem,disk
suspend: deep avail: s2idle wakeups: 0 hibernate: platform avail: shutdown,
reboot, suspend, test_resume image: 12.46 GiB services: org_kde_powerdevil,
power-profiles-daemon, upowerd Init: systemd v: 256 default: graphical
tool: systemctl
Packages: 1830 pm: pacman pkgs: 1802 libs: 470 tools: octopi,pamac,paru
pm: flatpak pkgs: 28 Compilers: clang: 18.1.8 gcc: 14.2.1 Shell: garuda-inxi
default: fish v: 3.7.1 running-in: konsole inxi: 3.3.35
Garuda (2.6.26-1):
System install date:     2023-11-19
Last full system update: 2024-08-14
Is partially upgraded:   No
Relevant software:       snapper NetworkManager dracut nvidia-dkms
Windows dual boot:       Probably (Run as root to verify)
Failed units:

This is a known issue, you should have seen it almost gone when Plasma developers added a feature for the impaired people and it broke this! (oops, see my later comment a bit below)

It’s part of Kvantum engine when using certain themes, like Sweet, which Dr460nized is based on. A few others also cause the issue.

This has been worked around but it is not 100% perfect. However, yours is like it was before the work around being applied.
If you boot from a USB with a recent ISO do you also get that problem?

What is the output of

paru -Qi kvantum garuda-dr460nized plasma5-themes-sweet-full-git
1 Like

Aaaaaaah, that is great to know! I have added all those names to a list of things I need to read up and understand what they do lmao.

Sorry, I don’t have a pendrive available untill monday to test a new ISO. I’ll answer here as soon as I can with that info :smiley:

In regards to the command you specified, here is the output:

Name            : kvantum
Version         : 1.1.2-1
Description     : SVG-based theme engine for Qt6 (including config tool and extra themes)
Architecture    : x86_64
URL             : https://github.com/tsujan/Kvantum
Licenses        : GPL-3.0-or-later
Groups          : None
Provides        : None
Depends On      : gcc-libs  glibc  libx11  kwindowsystem  qt6-base  qt6-svg
Optional Deps   : kvantum-qt5: Qt5 style [installed]
Required By     : garuda-dr460nized  kvantum-qt5  plasma5-themes-sweet-full-git
Optional For    : None
Conflicts With  : None
Replaces        : None
Installed Size  : 8,10 MiB
Packager        : Antonio Rojas <[email protected]>
Build Date      : sáb 01 jun 2024 18:30:59
Install Date    : dom 02 jun 2024 14:05:53
Install Reason  : Explicitly installed
Install Script  : No
Validated By    : Signature

Name            : garuda-dr460nized
Version         : 4.3.6-4
Description     : Dr460nized settings
Architecture    : any
URL             : https://gitlab.com/garuda-linux/themes-and-settings/settings/garuda-dr460nized
Licenses        : GPL
Groups          : None
Provides        : garuda-desktop-settings
Depends On      : beautyline  garuda-common-settings  garuda-fish-config  garuda-icons  garuda-wallpapers
kvantum  kvantum-qt5  plasma-applet-window-buttons  plasma-systemmonitor
plasma5-themes-sweet-full-git  plasma6-applets-window-title
plasma6-wallpapers-blurredwallpaper  ttf-fira-sans  ttf-firacode-nerd
xdg-desktop-portal-gtk
Optional Deps   : None
Required By     : None
Optional For    : None
Conflicts With  : garuda-desktop-settings  plasma5-applets-window-appmenu  plasma5-applets-window-buttons
plasma5-applets-window-title  plasma5-applets-betterinlineclock-git
plasma5-wallpapers-blurredwallpaper
Replaces        : None
Installed Size  : 30,22 MiB
Packager        : Garuda Builder <[email protected]>
Build Date      : seg 03 jun 2024 14:31:52
Install Date    : qua 05 jun 2024 00:11:06
Install Reason  : Explicitly installed
Install Script  : Yes
Validated By    : SHA-256 Sum  Signature

Name            : plasma5-themes-sweet-full-git
Version         : r381.304db38-1
Description     : Sweet KDE Plasma theme
Architecture    : x86_64
URL             : https://github.com/EliverLara/sweet
Licenses        : GPL3
Groups          : None
Provides        : sweet-theme
Depends On      : plasma5-themes-sweet-kde-git  kvantum  candy-icons-git
Optional Deps   : ttf-roboto: primary font face defined (GTK theme)
ttf-ubuntu-font-family: secondary font face defined (GTK theme)
cantarell-fonts: tertiary font face defined (GTK theme) [installed]
sweet-folders-icons-git: sweet folder icons
chaotic-interfere
Required By     : garuda-dr460nized
Optional For    : None
Conflicts With  : sweet-kde  sweet-kde-git  sweet-gtk-theme  sweet-theme-git  sweet-cursor-theme-git
sweet-cursor-theme  sweet-cursors-theme  kvantum-theme-sweet-git  sweet-kvantum-theme-git
sweet-gtk-theme-dark  plasma5-theme-sweet-git  sweet-theme-full-git  sweet-gtk-theme-dark
plasma5-theme-sweet-git  xcursor-sweet
Replaces        : None
Installed Size  : 10,68 MiB
Packager        : Garuda Builder <[email protected]>
Build Date      : ter 13 ago 2024 21:01:18
Install Date    : qua 14 ago 2024 08:54:54
Install Reason  : Installed as a dependency for another package
Install Script  : No
Validated By    : SHA-256 Sum  Signature
~~

You can,

This is good to know in general as some kvantum themes still have this issue.

3 Likes

Hey, appreciate the answer!

Funnily enough, it was already at 4. Setting it back to 9 then 4 again solved the issue though :person_shrugging:

Lmao, another problem fixed by turning it on and off again.

Highly appreciate the answers guys, your work here is awesome!

2 Likes

I suspect something was sort of corrupted and not picked up. This would explain why you still had the issue fully, although your packages are up to date and you just confirmed it had the right value.

Glad it’s fixed, no one wants issues! :rofl:

2 Likes

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