Window Controls look weird

Issues & Assistance KDE
#1

Hello,
I recently update my system via pacman -Syu and after restarting my windows didn't wobble anymore and when in full screen mode the three former colory dots are just an x a square and a down looking triangle. further when in window mode there is a light blue dot on the upper left side but at least the colory dots are there.
I know i could fix it just by resetting the configs in garuda assisten but id just like to restore this specific part and i don't know which one it is. If someone knows why this happens in general I'd also be keen to know

perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = "en_US:de",
LC_ALL = (unset),
LC_ADDRESS = "de_DE.UTF-8",
LC_NAME = "de_DE.UTF-8",
LC_MONETARY = "de_DE.UTF-8",
LC_PAPER = "de_DE.UTF-8",
LC_IDENTIFICATION = "de_DE.UTF-8",
LC_TELEPHONE = "de_DE.UTF-8",
LC_MEASUREMENT = "de_DE.UTF-8",
LC_TIME = "de_DE.UTF-8",
LC_NUMERIC = "de_DE.UTF-8",
LANG = "de_AT.UTF-8"
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
System:
Kernel: 5.15.13-zen1-1-zen x86_64 bits: 64 compiler: gcc v: 11.1.0
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=f181ffc3-cea3-4242-9c63-210fcfa3609e 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.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: ASUSTeK product: TUF Gaming FX505DV_FX505DV v: 1.0
serial: <superuser required>
Mobo: ASUSTeK model: FX505DV v: 1.0 serial: <superuser required>
UEFI-[Legacy]: American Megatrends v: FX505DV.312 date: 01/28/2021
Battery:
ID-1: BAT0 charge: 8.0 Wh (20.9%) condition: 38.2/48.1 Wh (79.5%)
volts: 12.4 min: 11.7 model: FX50442 type: Li-ion serial: N/A
status: Charging
CPU:
Info: model: AMD Ryzen 5 3550H with Radeon Vega Mobile Gfx bits: 64
type: MT MCP arch: Zen/Zen+ note: check family: 0x17 (23)
model-id: 0x18 (24) stepping: 1 microcode: 0x8108102
Topology: cpus: 1x cores: 4 tpc: 2 threads: 8 smt: enabled cache:
L1: 384 KiB desc: d-4x32 KiB; i-4x64 KiB L2: 2 MiB desc: 4x512 KiB
L3: 4 MiB desc: 1x4 MiB
Speed (MHz): avg: 2267 high: 2772 min/max: 1400/2100 boost: enabled
scaling: driver: acpi-cpufreq governor: performance cores: 1: 1496 2: 1283
3: 2770 4: 2769 5: 2772 6: 2766 7: 1585 8: 2695 bogomips: 33538
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
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: NVIDIA TU106M [GeForce RTX 2060 Mobile] vendor: ASUSTeK
driver: nvidia v: 495.46 alternate: nouveau,nvidia_drm bus-ID: 01:00.0
chip-ID: 10de:1f11 class-ID: 0300
Device-2: AMD Picasso vendor: ASUSTeK driver: amdgpu v: kernel
bus-ID: 05:00.0 chip-ID: 1002:15d8 class-ID: 0300
Device-3: IMC Networks USB2.0 HD UVC WebCam type: USB driver: uvcvideo
bus-ID: 5-1:2 chip-ID: 13d3:56a2 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: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.0x11.2")
s-diag: 582mm (22.9")
Monitor-1: eDP-1-1 res: 1920x1080 hz: 60 dpi: 142
size: 344x194mm (13.5x7.6") diag: 395mm (15.5")
OpenGL: renderer: NVIDIA GeForce RTX 2060/PCIe/SSE2
v: 4.6.0 NVIDIA 495.46 direct render: Yes
Audio:
Device-1: NVIDIA TU106 High Definition Audio vendor: ASUSTeK
driver: snd_hda_intel v: kernel bus-ID: 01:00.1 chip-ID: 10de:10f9
class-ID: 0403
Device-2: AMD Family 17h HD Audio vendor: ASUSTeK driver: snd_hda_intel
v: kernel bus-ID: 05:00.6 chip-ID: 1022:15e3 class-ID: 0403
Sound Server-1: ALSA v: k5.15.13-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.43 running: yes
Network:
Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
vendor: ASUSTeK driver: r8169 v: kernel port: e000 bus-ID: 02:00.0
chip-ID: 10ec:8168 class-ID: 0200
IF: enp2s0 state: down mac: <filter>
Device-2: Realtek RTL8822CE 802.11ac PCIe Wireless Network Adapter
vendor: AzureWave driver: rtw_8822ce v: N/A modules: rtw88_8822ce
port: d000 bus-ID: 04:00.0 chip-ID: 10ec:c822 class-ID: 0280
IF: wlp4s0 state: up mac: <filter>
IF-ID-1: ipv6leakintrf0 state: unknown speed: N/A duplex: N/A
mac: <filter>
IF-ID-2: proton0 state: unknown speed: 10 Mbps duplex: full mac: N/A
Bluetooth:
Device-1: IMC Networks Bluetooth Radio type: USB driver: btusb v: 0.8
bus-ID: 3-4:3 chip-ID: 13d3:3548 class-ID: e001 serial: <filter>
Report: bt-adapter ID: hci0 rfk-id: 0 state: down
bt-service: enabled,running rfk-block: hardware: no software: yes
address: <filter>
Drives:
Local Storage: total: 476.94 GiB used: 243.61 GiB (51.1%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Micron
model: 2200V MTFDHBA512TCK size: 476.94 GiB block-size: physical: 512 B
logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter>
rev: P1MA0V4 temp: 43.9 C scheme: MBR
Partition:
ID-1: / raw-size: 476.93 GiB size: 476.93 GiB (100.00%)
used: 243.61 GiB (51.1%) fs: btrfs dev: /dev/nvme0n1p1 maj-min: 259:1
ID-2: /home raw-size: 476.93 GiB size: 476.93 GiB (100.00%)
used: 243.61 GiB (51.1%) fs: btrfs dev: /dev/nvme0n1p1 maj-min: 259:1
ID-3: /var/log raw-size: 476.93 GiB size: 476.93 GiB (100.00%)
used: 243.61 GiB (51.1%) fs: btrfs dev: /dev/nvme0n1p1 maj-min: 259:1
ID-4: /var/tmp raw-size: 476.93 GiB size: 476.93 GiB (100.00%)
used: 243.61 GiB (51.1%) fs: btrfs dev: /dev/nvme0n1p1 maj-min: 259:1
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: zram size: 7.26 GiB used: 2 MiB (0.0%) priority: 100
dev: /dev/zram0
Sensors:
System Temperatures: cpu: 48.0 C mobo: N/A
Fan Speeds (RPM): cpu: 2800
GPU: device: nvidia screen: :0.0 temp: 44 C device: amdgpu temp: 48.0 C
Info:
Processes: 307 Uptime: 5m wakeups: 1 Memory: 7.26 GiB
used: 2.98 GiB (41.0%) Init: systemd v: 250 tool: systemctl Compilers:
gcc: 11.1.0 clang: 13.0.0 Packages: pacman: 1572 lib: 458 Shell: Bash
v: 5.1.12 running-in: konsole inxi: 3.3.11
1 Like
#2

Open System Settings, go to Desktop Effects, activate "Wobbly Windows"

System Settings, Appearence, Windows Decorations, set "Sweet-Dark"

Since you're there... make sure that:
Global Theme = Sweetified Plasma
Application Style = kvantum-dark
Gnoe/GTK Application Style = Sweet-Dark
Plasma Style = Sweet
Colors = Sweetified
Icons = BeautyLine

Every now and then I change these settings, but I think this should be the default.

2 Likes
#3

Thanks this restored it to 99% of how it was but the weird light blue dot is still there. And do you know why these setting just change sometimes? and if there is a way to set this as the standard?

#4

I keep telling people about the risks of acid flashbacks from dropping too much blue microdot acid, (but nobody ever listens to us old guys).

3 Likes
#5

This is standard: the "On all desktops" button.
You can remove it in Windows Decorations, Titlebar Buttons, drang it down.

This has never happened to me. Only for the GTK Application Style actually (a few times) and I don't remember many threads on this topic.
You are the only one who can administer your system, updates, configurations, etc.
Maybe it's due to the fact that there have been several plasma updates lately (but that's user configurations).
I wouldn't spend time on it, it's just a few clicks (and really shouldn't happen often).

1 Like
#6

Ok thanks, It happend one time before when my whole desktop nuked itself but thanks to timeshift and the garuda assistant reset all i got it all back. Should I make an Update on it when it happens again or is it to niche?

1 Like
#7

As far as I'm concerned, what matters is always the reproducibility of the problem.
Here we have solved the effect.
Working on the causes in my opinion is always more difficult (but obviously more important).
I would suggest you to make a new topic if you still experience a similar "cause" ("my whole desktop nuked itself").

#8

this time that luckly didnt happen but i had a topic on that

#9

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