How to restore the default configs of Garuda Top Bar / Panel Colorizer?

arijarman · 26 May 2025 13:10

I did some experiments with the Panel Colorizer tool, and I noticed a few issues. The close, maximize, and minimize buttons appear too small when the window is maximized. Also, when a window is maximized or touches the top bar, the Mokka Carbon theme doesn’t show the stacked effect or borders, unlike the default theme where the borders are visible. So, I want to restore the configuration file to its default settings.

also the background is not showing that in maximised state

enabled those:

here is my garuda-inxi

System:
Kernel: 6.14.7-zen2-1-zen arch: x86_64 bits: 64 compiler: gcc v: 15.1.1
clocksource: tsc avail: acpi_pm
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=8cfa510d-8533-4290-a776-520ee1b846b6 rw rootflags=subvol=@
vt.default_red=30,243,166,249,137,245,148,186,88,243,166,249,137,245,148,166
vt.default_grn=30,139,227,226,180,194,226,194,91,139,227,226,180,194,226,173
vt.default_blu=46,168,161,175,250,231,213,222,112,168,161,175,250,231,213,200
quiet resume=UUID=8b3cc991-5a40-4e12-ad6e-5f4bb09d8645 loglevel=3 ibt=off
Desktop: KDE Plasma v: 6.3.5 tk: Qt v: N/A info: frameworks v: 6.14.0
wm: kwin_wayland vt: 1 dm: SDDM Distro: Garuda base: Arch Linux
Machine:
Type: Laptop System: HP product: HP Laptop 15s-du1xxx
v: Type1ProductConfigId serial: <superuser required> Chassis: type: 10
serial: <superuser required>
Mobo: HP model: 85F1 v: 37.30 serial: <superuser required>
part-nu: 45W89PA#ACJ uuid: <superuser required> UEFI: Insyde v: F.67
date: 08/07/2024
Battery:
ID-1: BAT1 charge: 14.8 Wh (43.7%) condition: 33.9/40.9 Wh (83.0%)
volts: 11.1 min: 11.3 model: Hewlett-Packard PABAS0241231 type: Li-ion
serial: <filter> status: discharging
CPU:
Info: model: Intel Core i3-10110U bits: 64 type: MT MCP
arch: Comet/Whiskey Lake note: check gen: core 10 level: v3 note: check
built: 2018 process: Intel 14nm family: 6 model-id: 0x8E (142)
stepping: 0xC (12) microcode: 0x100
Topology: cpus: 1x dies: 1 clusters: 2 cores: 2 threads: 4 tpc: 2
smt: enabled cache: L1: 128 KiB desc: d-2x32 KiB; i-2x32 KiB L2: 512 KiB
desc: 2x256 KiB L3: 4 MiB desc: 1x4 MiB
Speed (MHz): avg: 800 min/max: 400/4100 scaling: driver: intel_pstate
governor: powersave cores: 1: 800 2: 800 3: 800 4: 800 bogomips: 20799
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities: <filter>
Graphics:
Device-1: Intel CometLake-U GT2 [UHD Graphics] vendor: Hewlett-Packard
driver: i915 v: kernel arch: Gen-9.5 process: Intel 14nm built: 2016-20
ports: active: eDP-1 empty: DP-1,HDMI-A-1,HDMI-A-2 bus-ID: 00:02.0
chip-ID: 8086:9b41 class-ID: 0300
Device-2: Luxvisions Innotech HP TrueVision HD Camera driver: uvcvideo
type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-5:2
chip-ID: 30c9:0035 class-ID: fe01 serial: <filter>
Display: wayland server: X.org v: 1.21.1.16 with: Xwayland v: 24.1.6
compositor: kwin_wayland driver: X: loaded: modesetting
alternate: fbdev,intel,vesa dri: iris gpu: i915 display-ID: 0
Monitor-1: eDP-1 model: ChiMei InnoLux 0x15f5 built: 2017 res:
mode: 1920x1080 hz: 60 scale: 100% (1) dpi: 142 gamma: 1.2
size: 344x193mm (13.54x7.6") diag: 394mm (15.5") ratio: 16:9
modes: 1920x1080
API: EGL v: 1.5 hw: drv: intel iris platforms: device: 0 drv: iris
device: 1 drv: swrast gbm: drv: iris surfaceless: drv: iris wayland:
drv: iris x11: drv: iris
API: OpenGL v: 4.6 compat-v: 4.5 vendor: intel mesa v: 25.1.1-arch1.1
glx-v: 1.4 direct-render: yes renderer: Mesa Intel UHD Graphics (CML GT2)
device-ID: 8086:9b41 memory: 7.38 GiB unified: yes display-ID: :1.0
API: Vulkan v: 1.4.313 layers: 5 device: 0 type: integrated-gpu name: Intel
UHD Graphics (CML GT2) driver: mesa intel v: 25.1.1-arch1.1
device-ID: 8086:9b41 surfaces: N/A device: 1 type: cpu name: llvmpipe
(LLVM 19.1.7 256 bits) driver: mesa llvmpipe v: 25.1.1-arch1.1 (LLVM
19.1.7) device-ID: 10005:0000 surfaces: N/A
Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
de: kscreen-console,kscreen-doctor wl: wayland-info
x11: xdpyinfo, xprop, xrandr
Audio:
Device-1: Intel Comet Lake PCH-LP cAVS vendor: Hewlett-Packard
driver: snd_hda_intel v: kernel alternate: snd_soc_avs,snd_sof_pci_intel_cnl
bus-ID: 00:1f.3 chip-ID: 8086:02c8 class-ID: 0403
API: ALSA v: k6.14.7-zen2-1-zen status: kernel-api tools: N/A
Server-1: sndiod v: N/A status: off tools: aucat,midicat,sndioctl
Server-2: PipeWire v: 1.4.2 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: Hewlett-Packard driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s
lanes: 1 port: 4000 bus-ID: 01:00.0 chip-ID: 10ec:8168 class-ID: 0200
IF: eno1 state: down mac: <filter>
Device-2: Realtek RTL8822CE 802.11ac PCIe Wireless Network Adapter
vendor: Hewlett-Packard driver: rtw_8822ce v: N/A modules: rtw88_8822ce
pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: 3000 bus-ID: 02:00.0
chip-ID: 10ec:c822 class-ID: 0280
IF: wlo1 state: up mac: <filter>
Info: services: NetworkManager, systemd-timesyncd, wpa_supplicant
Bluetooth:
Device-1: Realtek Bluetooth Radio driver: btusb v: 0.8 type: USB rev: 1.0
speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-10:3 chip-ID: 0bda:b00c
class-ID: e001 serial: <filter>
Report: btmgmt ID: hci0 rfk-id: 0 state: down bt-service: enabled,running
rfk-block: hardware: no software: yes address: <filter> bt-v: 5.1 lmp-v: 10
status: discoverable: no pairing: no
RAID:
Hardware-1: Intel 82801 Mobile SATA Controller [RAID mode] driver: ahci
v: 3.0 port: 5060 bus-ID: 00:17.0 chip-ID: 8086:282a rev: class-ID: 0104
Drives:
Local Storage: total: 476.94 GiB used: 67.62 GiB (14.2%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung
model: MZVLQ512HALU-000H1 size: 476.94 GiB block-size: physical: 512 B
logical: 512 B speed: 31.6 Gb/s lanes: 4 tech: SSD serial: <filter>
fw-rev: HPS4NFXV temp: 38.9 C scheme: GPT
Partition:
ID-1: / raw-size: 233.57 GiB size: 233.57 GiB (100.00%)
used: 67.62 GiB (28.9%) fs: btrfs dev: /dev/nvme0n1p8 maj-min: 259:8
ID-2: /boot/efi raw-size: 1.5 GiB size: 1.5 GiB (99.80%)
used: 620 KiB (0.0%) fs: vfat dev: /dev/nvme0n1p6 maj-min: 259:6
ID-3: /home raw-size: 233.57 GiB size: 233.57 GiB (100.00%)
used: 67.62 GiB (28.9%) fs: btrfs dev: /dev/nvme0n1p8 maj-min: 259:8
ID-4: /var/log raw-size: 233.57 GiB size: 233.57 GiB (100.00%)
used: 67.62 GiB (28.9%) fs: btrfs dev: /dev/nvme0n1p8 maj-min: 259:8
ID-5: /var/tmp raw-size: 233.57 GiB size: 233.57 GiB (100.00%)
used: 67.62 GiB (28.9%) fs: btrfs dev: /dev/nvme0n1p8 maj-min: 259:8
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: zram size: 7.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
ID-2: swap-2 type: partition size: 16.76 GiB used: 0 KiB (0.0%)
priority: -2 dev: /dev/nvme0n1p7 maj-min: 259:7
Sensors:
System Temperatures: cpu: 46.0 C pch: 44.0 C mobo: N/A
Fan Speeds (rpm): N/A
Info:
Memory: total: 8 GiB available: 7.56 GiB used: 2.85 GiB (37.8%)
Processes: 244 Power: uptime: 25m states: freeze,mem,disk suspend: deep
avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
suspend, test_resume image: 3 GiB services: org_kde_powerdevil,
power-profiles-daemon, upowerd Init: systemd v: 257 default: graphical
tool: systemctl
Packages: pm: pacman pkgs: 1323 libs: 398 tools: octopi,paru Compilers:
gcc: 15.1.1 Shell: garuda-inxi default: fish v: 4.0.2 running-in: konsole
inxi: 3.3.38
Garuda (2.7.2-1):
System install date:     2025-05-21
Last full system update: 2025-05-26
Is partially upgraded:   No
Relevant software:       snapper NetworkManager dracut
Windows dual boot:       Probably (Run as root to verify)
Failed units:

nepti · 26 May 2025 15:08

Have you tried the “Restore default panel appearance” button?

Have you tried loading the “Mokka Top Panel” preset manually?

You can also try to disable the Panel Colorizer + Apply and then enable it again, this should automatically load the “Mokka Top Panel” preset with the default settings.

arijarman · 26 May 2025 15:20

I tried all of those as you mentioned.
I did those:

Disabled and Enabled colorizer.
Reset from the preset and also enabled Mokka Top Panel preset.
Deleted the current panel and added new garuda top panel.
One telegram user suggested me to take those important configs files from someone who has default one.

This happened after an update.

Another issue is with browsers:
LIke other apps toolbar is in panel like Dolphin file manager’s toolbar as you can see it appears in panel

But in case of my browsers it doesn appear either in browser or in the pannel, it’s missing totally,

Should i reinstall? or other way to reset whole settings?
If in future i face this kind of problems i wanna save the config files after a fresh install which one i will replace if i find any errors so suggest those things or files name with locations (like themes/configs etc)

Apocalypticus · 26 May 2025 15:48

The configuration is located in

/usr/share/plasma/plasmoids/luisbocanegra.panel.colorizer/contents/

I would backup/rename the parent folder and then reinstall panel-colorizer.

nepti · 26 May 2025 16:27

Aaah, I can reproduce the issue with plasma6-applets-panel-colorizer after a system update of the Mokka-VM. The update to version 4.2.0 of plasma6-applets-panel-colorizer shows exactly the same bugs as yours.

dr460nf1r3 · 26 May 2025 16:39

@FGD relevant?

arijarman · 26 May 2025 18:02

im already in 4.2.0 but still those bugs as i mentioned

FGD · 26 May 2025 21:51

Nothing to do with Panel Colorizer.
Right-click those buttons and click Configure Window Buttons to adjust fonts.

Nothing to do with Panel Colorizer. GTK apps are very sketchy to provide their menus to Global Menu widget, or Global Menu has issues retrieving them, either way we tried a lot of workarounds to make this work but we gave up years ago.

Yes, I see it removed all settings and it removed Panel Colorizer on one of my machine, it’s using 4.0.0, does not come back with 4.2.0.
However on another machine, full metal, I have 4.0.0 and everything is fine.

I’ll have to check this out but it won’t be for a couple of days minimum.

It fixes part of it.
The Reset Default Preset button seems to do nothing but when you manually re-apply MOKKA TOP PANEL for Normal windows, it works.
However MOKKA CARBON does not work, which is probably due to the change in preset format. Which I have to take a look later as mentioned above.

FGD · 26 May 2025 22:57

In the meantime you can delete your top panel, recreate using the Garuda Mokka Default Top Panel choice, then in Panel Colorizer change both Mokka Carbon presets to Carbon.

It does not have the fixes for padding inside widgets in some areas but it’s close enough.

FGD · 27 May 2025 00:21

I LIED!!!
It got stuck in my head and couldn’t do anything without looking at this. So I did.
And I pushed a fix garuda-mokka-settings v1.1.0.

There is one caveat, after updating to this new version, anyone still with a problem (probably everyone who had it in the first place) willl need to either

Re-add Panel-Colorizer manually to Top Panel and Dock
Re-add the presets manually in both Top Panel and Dock

OR

Delete the Top Panel and Dock
Re-add them using the default Garuda Mokka choices in the list presented by Plasma

The reason why the package update will not fix everything is cuz widgets often affect files in the userspace. We don’t directly affect those files, a package update will never do that.
But when you load a Panel, it uses a template respecting the Plasma convention and then if affects files in the userspace.

This is why manual intervention is required in this case.

arijarman · 27 May 2025 03:02

Thanks mate. The update work. What the freaking maintainer you just made me thinking of downloading garuda gnome but its ok now, thanks again.

arijarman · 27 May 2025 03:25

Also I wanna mention that similar problem in Dragonised version.
No one can add any widgets to top panel of Dragonised as it seems like the panel is locked and whenever we try to add any elements or widgets to top panel or in dekstop space the screen turn black and again reset to normal so this shit is going on there. I migrated from there and now on mokka so you may keep an eye there.

FGD · 27 May 2025 17:59

Yes I am expecting that since it works the same way. Will fix it as well but probably not as fast as Mokka.

That’s probably different but I will see quickly once I start looking at that Panel-Colorizer fix anyway.

system · 29 May 2025 17:59

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