Color Settings Reverting After Reboot

[NovaCore]

Hi Everyone. Newbie Python/C# dev here making my first ever windows escape attempt, and first I'd just like to say thank you to the Garuda team for creating such an awesome out-of-the-box thing here! Very impressed so far!

I am having an issue with my setting from the "colors" control panel reverting back to the original magenta upon restart. I'll change it to the blue, but after restart it's back to the magenta for the highlight/selection color.

All other customization settings seem to be retained fine from what I can see, it's just that color setting that is reverting.

Few other minor issues but I'm still trying to solve them on my own before starting threads.

Thanks!

> Blockquote
Kernel: 5.16.5-zen1-1-zen x86_64 bits: 64 compiler: gcc v: 11.1.0
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=d5af581e-eff8-4b35-b8db-4838c1055d5d rw rootflags=subvol=@
cryptdevice=UUID=46b8c56b-d7cf-4e46-a6d9-d6ac2ee0a757:luks-46b8c56b-d7cf-4e46-a6d9-d6ac2ee0a757
root=/dev/mapper/luks-46b8c56b-d7cf-4e46-a6d9-d6ac2ee0a757 quiet splash
rd.udev.log_priority=3 vt.global_cursor_default=0 loglevel=3
Desktop: KDE Plasma 5.23.5 tk: Qt 5.15.2 info: latte-dock wm: kwin_x11
vt: 1 dm: SDDM Distro: Garuda Linux base: Arch Linux
Machine:
Type: Laptop System: Razer product: Blade v: 2.04
serial: <superuser required> Chassis: type: 10 serial: <superuser required>
Mobo: Razer model: Razer CH20 serial: <superuser required> UEFI: Razer
v: 1.05 date: 05/16/2019
Battery:
ID-1: BAT0 charge: 82.1 Wh (99.9%) condition: 82.2/80.2 Wh (102.5%)
volts: 17.3 min: 15.4 model: Razer Blade type: Unknown serial: <filter>
status: Full
CPU:
Info: model: Intel Core i7-8750H bits: 64 type: MT MCP arch: Coffee Lake
family: 6 model-id: 0x9E (158) stepping: 0xA (10) microcode: 0xEA
Topology: cpus: 1x cores: 6 tpc: 2 threads: 12 smt: enabled cache:
L1: 384 KiB desc: d-6x32 KiB; i-6x32 KiB L2: 1.5 MiB desc: 6x256 KiB
L3: 9 MiB desc: 1x9 MiB
Speed (MHz): avg: 4048 high: 4101 min/max: 800/4100 scaling:
driver: intel_pstate governor: performance cores: 1: 3907 2: 4059 3: 4052
4: 4097 5: 4071 6: 3977 7: 4050 8: 4100 9: 4036 10: 4038 11: 4099
12: 4101 bogomips: 52799
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities:
Type: itlb_multihit status: KVM: VMX disabled
Type: l1tf
mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable
Type: mds mitigation: Clear CPU buffers; SMT vulnerable
Type: meltdown mitigation: PTI
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 generic retpoline, IBPB: conditional,
IBRS_FW, STIBP: conditional, RSB filling
Type: srbds mitigation: Microcode
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: Intel CoffeeLake-H GT2 [UHD Graphics 630] vendor: Razer USA
driver: i915 v: kernel bus-ID: 00:02.0 chip-ID: 8086:3e9b class-ID: 0300
Device-2: NVIDIA TU104M [GeForce RTX 2080 Mobile] vendor: Razer USA
driver: nvidia v: 510.47.03 alternate: nouveau,nvidia_drm bus-ID: 01:00.0
chip-ID: 10de:1e90 class-ID: 0300
Device-3: Microdia NexiGo HD Webcam type: USB
driver: snd-usb-audio,uvcvideo bus-ID: 1-2.1.4:13 chip-ID: 0c45:2690
class-ID: 0102 serial: <filter>
Device-4: IMC Networks Integrated Camera type: USB driver: uvcvideo
bus-ID: 1-7:7 chip-ID: 13d3:56d5 class-ID: 0e02 serial: <filter>
Display: x11 server: X.Org 1.21.1.3 compositor: kwin_x11 driver:
loaded: modesetting,nvidia display-ID: :0 screens: 1
Screen-1: 0 s-res: 3840x1080 s-dpi: 96 s-size: 1015x285mm (40.0x11.2")
s-diag: 1054mm (41.5")
Monitor-1: HDMI-0 res: 1920x1080 hz: 120 dpi: 30
size: 1600x900mm (63.0x35.4") diag: 1836mm (72.3")
Monitor-2: DP-1 res: 1920x1080 hz: 120 dpi: 30
size: 1600x900mm (63.0x35.4") diag: 1836mm (72.3")
OpenGL: renderer: NVIDIA GeForce RTX 2080 with Max-Q Design/PCIe/SSE2
v: 4.6.0 NVIDIA 510.47.03 direct render: Yes
Audio:
Device-1: Intel Cannon Lake PCH cAVS vendor: Razer USA
driver: snd_hda_intel v: kernel
alternate: snd_soc_skl,snd_sof_pci_intel_cnl bus-ID: 00:1f.3
chip-ID: 8086:a348 class-ID: 0403
Device-2: NVIDIA TU104 HD Audio vendor: Razer USA driver: snd_hda_intel
v: kernel bus-ID: 01:00.1 chip-ID: 10de:10f8 class-ID: 0403
Device-3: XMOS JDS Labs UAC2 DAC (XU208) type: USB driver: snd-usb-audio
bus-ID: 1-2.1.1:10 chip-ID: 20b1:30da class-ID: fe01
Device-4: Microdia NexiGo HD Webcam type: USB
driver: snd-usb-audio,uvcvideo bus-ID: 1-2.1.4:13 chip-ID: 0c45:2690
class-ID: 0102 serial: <filter>
Sound Server-1: ALSA v: k5.16.5-zen1-1-zen running: yes
Sound Server-2: PulseAudio v: 15.0 running: no
Sound Server-3: PipeWire v: 0.3.45 running: yes
Network:
Device-1: Intel Cannon Lake PCH CNVi WiFi driver: iwlwifi v: kernel
bus-ID: 00:14.3 chip-ID: 8086:a370 class-ID: 0280
IF: wlo1 state: up mac: <filter>
IF-ID-1: tun0 state: unknown speed: 10 Mbps duplex: full mac: N/A
Bluetooth:
Device-1: Intel Bluetooth 9460/9560 Jefferson Peak (JfP) type: USB
driver: btusb v: 0.8 bus-ID: 1-14:14 chip-ID: 8087:0aaa class-ID: e001
Report: bt-adapter ID: hci0 rfk-id: 0 state: up address: <filter>
Drives:
Local Storage: total: 11.38 TiB used: 162.57 GiB (1.4%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung
model: MZVLB512HAJQ-00000 size: 476.94 GiB block-size: physical: 512 B
logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter>
rev: EXA7301Q temp: 51.9 C scheme: GPT
ID-2: /dev/sda maj-min: 8:0 type: USB vendor: Western Digital
model: WD20NMVW-11EDZS3 size: 1.82 TiB block-size: physical: 512 B
logical: 512 B type: HDD rpm: 5200 serial: <filter> rev: 1072 scheme: MBR
ID-3: /dev/sdb maj-min: 8:16 type: USB vendor: Western Digital
model: WD Game Drive size: 4.55 TiB block-size: physical: 4096 B
logical: 512 B type: N/A serial: <filter> rev: 5002 scheme: GPT
ID-4: /dev/sdc maj-min: 8:32 type: USB vendor: Western Digital
model: WD Game Drive size: 4.55 TiB block-size: physical: 4096 B
logical: 512 B type: N/A serial: <filter> rev: 5002 scheme: GPT
Partition:
ID-1: / raw-size: 476.64 GiB size: 476.64 GiB (100.00%)
used: 162.57 GiB (34.1%) fs: btrfs dev: /dev/dm-0 maj-min: 254:0
mapped: luks-46b8c56b-d7cf-4e46-a6d9-d6ac2ee0a757
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 720 KiB (0.2%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
ID-3: /home raw-size: 476.64 GiB size: 476.64 GiB (100.00%)
used: 162.57 GiB (34.1%) fs: btrfs dev: /dev/dm-0 maj-min: 254:0
mapped: luks-46b8c56b-d7cf-4e46-a6d9-d6ac2ee0a757
ID-4: /var/log raw-size: 476.64 GiB size: 476.64 GiB (100.00%)
used: 162.57 GiB (34.1%) fs: btrfs dev: /dev/dm-0 maj-min: 254:0
mapped: luks-46b8c56b-d7cf-4e46-a6d9-d6ac2ee0a757
ID-5: /var/tmp raw-size: 476.64 GiB size: 476.64 GiB (100.00%)
used: 162.57 GiB (34.1%) fs: btrfs dev: /dev/dm-0 maj-min: 254:0
mapped: luks-46b8c56b-d7cf-4e46-a6d9-d6ac2ee0a757
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: zram size: 15.52 GiB used: 0 KiB (0.0%) priority: 100
dev: /dev/zram0
Sensors:
System Temperatures: cpu: 65.0 C pch: 70.0 C mobo: N/A gpu: nvidia
temp: 60 C
Fan Speeds (RPM): N/A
Info:
Processes: 356 Uptime: 5m wakeups: 1 Memory: 15.52 GiB
used: 3.08 GiB (19.8%) Init: systemd v: 250 tool: systemctl Compilers:
gcc: 11.1.0 clang: 13.0.0 Packages: pacman: 1916 lib: 562 Shell: fish
v: 3.3.1 default: Bash v: 5.1.16 running-in: konsole inxi: 3.3.12
Garuda (2.5.4-2):
System install date:     2022-02-01
Last full system update: 2022-02-03
Is partially upgraded:   No
Relevant software:       NetworkManager
Windows dual boot:       Probably (Run as root to verify)
Snapshots:               Snapper
Failed units:

[SGS]

Try

Make dragonized more blue

Make dragonized more blue I would like to be able to program And what looks like nothing here has cost me some “time” of my life, because I have zero idea about KDE. Most of the time I was looking for where these pink things come from and where these colours are stored . Then I recoloured the dragonized to my taste. Now all that’s missing is a correct tutorial (if the rest I made is usable ) Would be nice if someone would be intereste…

and welcome to the forum.

I fix your text, use edit to see how I did

[zoeruda]

Note also that Dragonized uses Kvantum as the application style by default, so that theme would not take the plasma colors. Try changing it to "Breeze" and see if that suits you.

[NovaCore]

I really like everything about the sweetified colors in the dragonized theme except I just wanna make the highlight accent color blue. There is already a "Sweetified-blue" color scheme included. I selected that and made a small edit to make the shade of blue slightly darker. Works perfectly until restart, then back to magenta.

I'll try the suggested script and see if that makes a difference, but I don't see why there would be an issue considering the blue option is already there in the color scheme selector.

Also please note that even after the restart, the colors screen still shows the Sweetified-blue as being selected...it's just the highlight box has still reverted back to magenta.

When you refer to "plasma colors" is that the color scheme selector I'm talking about in the system settings? Again they work fine with the Dragonized theme before restarting.

[SGS]

Did you use a live ISO?
IDK that the

@NovaCore

“Sweetified-blue”

is included

[NovaCore]

I'm almost sure I didn't create that, lol
I have a separate one that I did create called "Sweetified-blue[Edit]", but I thought the other sweetified-blue was already there?

Not 100% sure haha