Titlebar Buttons Not Behaving Correctly After Suspend

Issues & Assistance
1

I have been using Garuda for about two weeks now and I'm very pleased with it so far.

I'm not sure when this issue began, so I can't correlate it to the installation of any particular software or configuration change.

I'm using the Dr460nized theme, which uses the Sweet-Dark window decorations. The behavior I'm running into is that after waking the system from sleep, the titlebar buttons on active windows that were open when the system suspended will not change color when the window is made active. This behavior is not seen in new windows that I open after waking the computer.

I would attach a screenshot showing this, but it looks like I'm not allowed to upload pictures yet because my account is new.

Please find the output of garuda-inxi below:

System:
Kernel: 6.2.9-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 12.2.1
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=e40f11c7-a9fe-4ac0-a4ce-af0c8cc5e5ab rw [email protected]
quiet quiet splash rd.udev.log_priority=3 vt.global_cursor_default=0
loglevel=3 ibt=off
Desktop: KDE Plasma v: 5.27.3 tk: Qt v: 5.15.8 wm: kwin_x11 dm: SDDM
Distro: Garuda Linux base: Arch Linux
Machine:
Type: Desktop Mobo: ASUSTeK model: PRIME X570-P v: Rev X.0x serial: <filter>
UEFI: American Megatrends v: 4602 date: 02/23/2023
Battery:
Device-1: hidpp_battery_0 model: Logitech G604 Wireless Gaming Mouse
serial: <filter> charge: 100% (should be ignored) rechargeable: yes
status: discharging
CPU:
Info: model: AMD Ryzen 5 3600X socket: AM4 bits: 64 type: MT MCP arch: Zen 2
gen: 3 level: v3 note: check built: 2020-22 process: TSMC n7 (7nm)
family: 0x17 (23) model-id: 0x71 (113) stepping: 0 microcode: 0x8701030
Topology: cpus: 1x cores: 6 tpc: 2 threads: 12 smt: enabled cache:
L1: 384 KiB desc: d-6x32 KiB; i-6x32 KiB L2: 3 MiB desc: 6x512 KiB
L3: 32 MiB desc: 2x16 MiB
Speed (MHz): avg: 3800 min/max: 2200/4409 boost: enabled
base/boost: 3800/4400 scaling: driver: acpi-cpufreq governor: performance
volts: 1.1 V ext-clock: 100 MHz cores: 1: 3800 2: 3800 3: 3800 4: 3800
5: 3800 6: 3800 7: 3800 8: 3800 9: 3800 10: 3800 11: 3800 12: 3800
bogomips: 91201
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Vulnerabilities: <filter>
Graphics:
Device-1: NVIDIA GA102 [GeForce RTX 3080 Lite Hash Rate] vendor: eVga.com.
driver: nvidia v: 530.41.03 alternate: nouveau,nvidia_drm non-free: 530.xx+
status: current (as of 2023-03) arch: Ampere code: GAxxx
process: TSMC n7 (7nm) built: 2020-22 pcie: gen: 4 speed: 16 GT/s
lanes: 16 bus-ID: 0c:00.0 chip-ID: 10de:2216 class-ID: 0300
Display: x11 server: X.Org v: 21.1.8 with: Xwayland v: 23.1.1
compositor: kwin_x11 driver: X: loaded: nvidia unloaded: modesetting,nouveau
alternate: fbdev,nv,vesa gpu: nvidia display-ID: :0 screens: 1
Screen-1: 0 s-res: 5760x1080 s-dpi: 80 s-size: 1829x343mm (72.01x13.50")
s-diag: 1861mm (73.26")
Monitor-1: DP-0 pos: right res: 1920x1080 dpi: 82
size: 598x336mm (23.54x13.23") diag: 686mm (27.01") modes: N/A
Monitor-2: DP-2 pos: left res: 1920x1080 dpi: 82
size: 598x336mm (23.54x13.23") diag: 686mm (27.01") modes: N/A
Monitor-3: DP-4 pos: primary,center res: 1920x1080 dpi: 82
size: 598x336mm (23.54x13.23") diag: 686mm (27.01") modes: N/A
API: OpenGL v: 4.6.0 NVIDIA 530.41.03 renderer: NVIDIA GeForce RTX
3080/PCIe/SSE2 direct-render: Yes
Audio:
Device-1: Creative Labs CA0108/CA10300 [Sound Blaster Audigy Series]
driver: snd_emu10k1 v: kernel bus-ID: 3-4:3 chip-ID: 0909:0018
class-ID: 0102
Device-2: NVIDIA GA102 High Definition Audio vendor: eVga.com.
driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
bus-ID: 0c:00.1 chip-ID: 10de:1aef class-ID: 0403
Device-3: Audio-Technica AT2020 USB type: USB driver: snd-usb-audio
API: ALSA v: k6.2.9-zen1-1-zen status: kernel-api with: aoss
type: oss-emulator tools: N/A
Server-1: PipeWire v: 0.3.67 status: n/a (root, process) 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: Aquantia AQC107 NBase-T/IEEE 802.3bz Ethernet [AQtion]
driver: atlantic v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 4 port: N/A
bus-ID: 05:00.0 chip-ID: 1d6a:07b1 class-ID: 0200
IF: enp5s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Device-2: Intel Wireless-AC 9260 driver: iwlwifi v: kernel pcie: gen: 2
speed: 5 GT/s lanes: 1 bus-ID: 08:00.0 chip-ID: 8086:2526 class-ID: 0280
IF: wlp8s0 state: down mac: <filter>
Bluetooth:
Device-1: Intel Wireless-AC 9260 Bluetooth Adapter type: USB driver: btusb
v: 0.8 bus-ID: 1-6:4 chip-ID: 8087:0025 class-ID: e001
Report: bt-adapter ID: hci0 rfk-id: 3 state: up address: <filter>
Drives:
Local Storage: total: 2.5 TiB used: 490.7 GiB (19.2%)
ID-1: /dev/nvme0n1 maj-min: 259:1 vendor: Western Digital
model: WDS250G2X0C-00L350 size: 232.89 GiB block-size: physical: 512 B
logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter>
rev: 101110WD temp: 53.9 C scheme: GPT
SMART: yes health: PASSED on: 1y 314d 21h cycles: 3,414
read-units: 17,943,083 [9.18 TB] written-units: 15,535,404 [7.95 TB]
ID-2: /dev/nvme1n1 maj-min: 259:0 vendor: Western Digital
model: WDS500G3X0C-00SJG0 size: 465.76 GiB block-size: physical: 512 B
logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter>
rev: 102000WD temp: 52.9 C scheme: GPT
SMART: yes health: PASSED on: 1y 229d 6h cycles: 2,878
read-units: 87,451,540 [44.7 TB] written-units: 74,740,206 [38.2 TB]
ID-3: /dev/sda maj-min: 8:0 vendor: Western Digital model: WDS200T2B0A
family: WD Blue / Red / Green SSDs size: 1.82 TiB block-size:
physical: 512 B logical: 512 B sata: 3.3 speed: 6.0 Gb/s type: SSD
serial: <filter> rev: 90WD temp: 31 C scheme: GPT
SMART: yes state: enabled health: PASSED on: 1y 228d 7h cycles: 2823
Partition:
ID-1: / raw-size: 195.95 GiB size: 195.95 GiB (100.00%)
used: 45.25 GiB (23.1%) fs: btrfs block-size: 4096 B dev: /dev/nvme1n1p5
maj-min: 259:6
ID-2: /boot/efi raw-size: 100 MiB size: 96 MiB (96.00%)
used: 29.4 MiB (30.6%) fs: vfat block-size: 512 B dev: /dev/nvme1n1p1
maj-min: 259:2
ID-3: /home raw-size: 195.95 GiB size: 195.95 GiB (100.00%)
used: 45.25 GiB (23.1%) fs: btrfs block-size: 4096 B dev: /dev/nvme1n1p5
maj-min: 259:6
ID-4: /var/log raw-size: 195.95 GiB size: 195.95 GiB (100.00%)
used: 45.25 GiB (23.1%) fs: btrfs block-size: 4096 B dev: /dev/nvme1n1p5
maj-min: 259:6
ID-5: /var/tmp raw-size: 195.95 GiB size: 195.95 GiB (100.00%)
used: 45.25 GiB (23.1%) fs: btrfs block-size: 4096 B dev: /dev/nvme1n1p5
maj-min: 259:6
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: zram size: 31.26 GiB used: 3.4 MiB (0.0%) priority: 100
dev: /dev/zram0
Sensors:
System Temperatures: cpu: 34.5 C mobo: 43.0 C gpu: nvidia temp: 60 C
Fan Speeds (RPM): fan-1: 940 fan-2: 0 fan-3: 771 fan-4: 0 fan-5: 3417
fan-6: 1147 fan-7: 0 gpu: nvidia fan: 0%
Info:
Processes: 377 Uptime: 16h 55m wakeups: 24 Memory: 31.26 GiB
used: 8.22 GiB (26.3%) Init: systemd v: 253 default: graphical
tool: systemctl Compilers: gcc: 12.2.1 Packages: pm: pacman pkgs: 2001
libs: 556 tools: octopi,paru Shell: garuda-inxi (sudo) default: Bash
v: 5.1.16 running-in: konsole inxi: 3.3.26
Garuda (2.6.16-1):
System install date:     2023-03-31
Last full system update: 2023-04-05
Is partially upgraded:   No
Relevant software:       snapper NetworkManager dracut nvidia-dkms
Windows dual boot:       Yes
Failed units:
2

Welcome to the Fourm!

A very simple way to guide into the troubleshooting would be to change the Sweet-Dark Window theme to another one. You can start with plain default Breeze and see if the issue persists.

This may allow to eliminate the possibility the issue is with Sweet-Dark or to point out to Sweet-Dark specifically (especially if you try other 3rd party Decos and only experience this with Sweet-Dark).

2 Likes
3

Thank you for your reply. Following your advice, I switched to the Breeze theme to see if I could reproduce the issue. I did this by opening some windows, suspending the system, and then waking it. While using Breeze, the same behavior did not occur.

That being said, I don't know if the two themes work the same way because in Breeze the titlebar buttons do not change appearance when they are in the background vs. foreground.

4

Ha! Very good point! Would you be able to test a Window Deco that uses the same behavior as Sweet, then?

At least we know nothing else weird happens with Breeze buttons (disappearing, etc.).

5

I have reproduced the behavior that I described in this post in the Layan theme. While it does not have the same behavior of the titlebar buttons changing to different colors when they are in the background, it is still behaving incorrectly after suspending and resuming. Normally, the titlebar buttons are grey but change to colored buttons for close/restore/minimize/etc. when mousing over. After suspending and resuming the system, the buttons stay grey even when moused over.

I have also found another strange behavior that may be connected. When right-clicking the maximize/restore titlebar button to make the window expand horizontally, the titlebar of the window does not scale properly, so the text and buttons all become stretched out. This behavior is present in Dr460nized, Sweet, and Layan, but does not occur in breeze.

1 Like
6

Ok, that gives a good idea the issue is larger than just 1 Window Deco.
I wonder if this is graphics related...

Do you know exactly when this started?
After an system update?
After changing some Plasma configs?
After a crash?
Changing hardware?
etc.

7

For a few reasons yesterday I ended up doing a full re-install of Garuda Dr460nized gaming. The same behavior is present after the re-install and no changes to any settings. The only thing I did was login and go through the setup assistant.

8

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