Programs freeze and show weird artefacts when tiling to a corner

Hello Garuda users.

I installed Garuda KDE yesterday and I have some problems/ weird glithes when tilling a window to one of the corners.
Image

garuda-inxi output:

System:
Kernel: 6.0.8-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=91bb459f-61ac-475f-9cfc-70a095b52fd1 rw rootflags=subvol=@
quiet quiet splash rd.udev.log_priority=3 vt.global_cursor_default=0
resume=UUID=e9decb81-7e02-40f9-aa54-67f128b1c2b7 loglevel=3
Desktop: KDE Plasma v: 5.26.3 tk: Qt v: 5.15.7 info: latte-dock
wm: kwin_x11 vt: 1 dm: SDDM Distro: Garuda Linux base: Arch Linux
Machine:
Type: Desktop Mobo: ASUSTeK model: PRIME A320M-K v: Rev X.0x
serial: <superuser required> UEFI: American Megatrends v: 5220
date: 09/12/2019
CPU:
Info: model: AMD Ryzen 3 3200G with Radeon Vega Graphics bits: 64 type: MCP
arch: Zen/Zen+ note: check gen: 1 level: v3 note: check built: 2019
process: GF 12nm family: 0x17 (23) model-id: 0x18 (24) stepping: 1
microcode: 0x8108109
Topology: cpus: 1x cores: 4 smt: <unsupported> 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: 1257 high: 1258 min/max: 1400/3600 boost: enabled
scaling: driver: acpi-cpufreq governor: schedutil cores: 1: 1258 2: 1258
3: 1257 4: 1257 bogomips: 28745
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: mmio_stale_data status: Not affected
Type: retbleed mitigation: untrained return thunk; SMT disabled
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: Retpolines, IBPB: conditional, STIBP:
disabled, RSB filling, PBRSB-eIBRS: Not affected
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: AMD Picasso/Raven 2 [Radeon Vega Series / Radeon Mobile Series]
vendor: ASUSTeK driver: amdgpu v: kernel arch: GCN-5 code: Vega
process: GF 14nm built: 2017-20 pcie: gen: 3 speed: 8 GT/s lanes: 16
ports: active: HDMI-A-1 empty: DP-1 bus-ID: 07:00.0 chip-ID: 1002:15d8
class-ID: 0300 temp: 44.0 C
Display: x11 server: X.Org v: 21.1.4 with: Xwayland v: 22.1.5
compositor: kwin_x11 driver: X: loaded: amdgpu unloaded: modesetting
alternate: fbdev,vesa dri: radeonsi gpu: amdgpu display-ID: :0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22")
s-diag: 582mm (22.93")
Monitor-1: HDMI-A-1 mapped: HDMI-A-0 model: LG (GoldStar) FULL HD
serial: <filter> built: 2016 res: 1920x1080 hz: 75 dpi: 102 gamma: 1.2
size: 480x270mm (18.9x10.63") diag: 551mm (21.7") ratio: 16:9 modes:
max: 1920x1080 min: 720x400
API: OpenGL v: 4.6 Mesa 22.2.3 renderer: AMD Radeon Vega 8 Graphics
(raven LLVM 14.0.6 DRM 3.48 6.0.8-zen1-1-zen) direct render: Yes
Audio:
Device-1: AMD Raven/Raven2/Fenghuang HDMI/DP Audio
vendor: ASUSTeK PRIME B450M-A driver: snd_hda_intel v: kernel pcie: gen: 3
speed: 8 GT/s lanes: 16 bus-ID: 07:00.1 chip-ID: 1002:15de class-ID: 0403
Device-2: AMD Family 17h/19h HD Audio vendor: ASUSTeK PRIME B450M-A
driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16
bus-ID: 07:00.6 chip-ID: 1022:15e3 class-ID: 0403
Sound API: ALSA v: k6.0.8-zen1-1-zen running: yes
Sound Server-1: PulseAudio v: 16.1 running: no
Sound Server-2: PipeWire v: 0.3.59 running: yes
Network:
Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
vendor: ASUSTeK PRIME B450M-A driver: r8169 v: kernel pcie: gen: 1
speed: 2.5 GT/s lanes: 1 port: f000 bus-ID: 05:00.0 chip-ID: 10ec:8168
class-ID: 0200
IF: enp5s0 state: down mac: <filter>
Device-2: Realtek RTL8188EUS 802.11n Wireless Network Adapter type: USB
driver: r8188eu bus-ID: 1-8:4 chip-ID: 0bda:8179 class-ID: 0000
serial: <filter>
IF: wlp1s0f0u8 state: up mac: <filter>
Bluetooth:
Device-1: Cambridge Silicon Radio Bluetooth Dongle (HCI mode) type: USB
driver: btusb v: 0.8 bus-ID: 1-3:2 chip-ID: 0a12:0001 class-ID: e001
Report: bt-adapter ID: hci0 rfk-id: 0 state: up address: <filter>
Drives:
Local Storage: total: 1.93 TiB used: 1.23 TiB (63.5%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: Western Digital
model: WD20EZAZ-00GGJB0 size: 1.82 TiB block-size: physical: 4096 B
logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 5400 serial: <filter>
rev: 0A80 scheme: GPT
ID-2: /dev/sdb maj-min: 8:16 vendor: A-Data model: SU650 size: 111.79 GiB
block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD
serial: <filter> rev: 831a scheme: GPT
Partition:
ID-1: / raw-size: 102.69 GiB size: 102.69 GiB (100.00%)
used: 10.27 GiB (10.0%) fs: btrfs dev: /dev/sdb2 maj-min: 8:18
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 576 KiB (0.2%) fs: vfat dev: /dev/sdb1 maj-min: 8:17
ID-3: /home raw-size: 102.69 GiB size: 102.69 GiB (100.00%)
used: 10.27 GiB (10.0%) fs: btrfs dev: /dev/sdb2 maj-min: 8:18
ID-4: /var/log raw-size: 102.69 GiB size: 102.69 GiB (100.00%)
used: 10.27 GiB (10.0%) fs: btrfs dev: /dev/sdb2 maj-min: 8:18
ID-5: /var/tmp raw-size: 102.69 GiB size: 102.69 GiB (100.00%)
used: 10.27 GiB (10.0%) fs: btrfs dev: /dev/sdb2 maj-min: 8:18
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: zram size: 5.71 GiB used: 4.8 MiB (0.1%) priority: 100
dev: /dev/zram0
ID-2: swap-2 type: partition size: 8.8 GiB used: 0 KiB (0.0%) priority: -2
dev: /dev/sdb3 maj-min: 8:19
Sensors:
System Temperatures: cpu: 43.6 C mobo: N/A gpu: amdgpu temp: 43.0 C
Fan Speeds (RPM): N/A
Info:
Processes: 255 Uptime: 48m wakeups: 0 Memory: 5.72 GiB
used: 3.16 GiB (55.4%) Init: systemd v: 252 default: graphical
tool: systemctl Compilers: gcc: 12.2.0 Packages: pm: pacman pkgs: 1295
libs: 348 tools: octopi,paru Shell: fish v: 3.5.1 default: Bash v: 5.1.16
running-in: konsole inxi: 3.3.23
Garuda (2.6.9-1):
System install date:     2022-11-13
Last full system update: 2022-11-14
Is partially upgraded:   No
Relevant software:       NetworkManager
Windows dual boot:       No/Undetected
Snapshots:               Snapper
Failed units:

Try to disable/re-enable the compositor and see if it fixes the glitch.

Alt+Shift+F12

:point_up_2: Once to disable, wait a few seconds, then again to re-enable.

If this seems to fix the issue, I would check in System Settings -> Workspace Behavior -> Desktop Effects to see if you can do without any of the currently enabled graphical effects, to try to ease the burden on the compositor.

3 Likes

It works. When I disable it stops glitching. But when I turn it on returns back to glitching like usual.

I don't want to keep it turned off.

Yeah if you just turn it back on without changing anything you will be right back where you started.

How did you make out with the second part?

Another option would be just switch to Wayland.

sudo pacman -Syu plasma-wayland-session

Reboot, and toggle the session to Wayland on the login screen.

2 Likes

I switched to wayland but now I have a new problem


I dont want my window to go under that dock

That is unfortunately a known bug, reported here: 459755 – 5.26 Wayland windows go below Latte when "always visible" is chosen

I wouldn't hold your breath for a fix on that one, as it seems Latte-Dock is unfortunately going to seed after the lead developer stepped away from the project. I understand there is a new dock experience in the works for Dr460nized, perhaps based on the native KDE dock or perhaps something else. It is not ready yet, but when it is it won't have that bug.

In the meantime, if the bug is really bothering you you can either go back to X11 and disable some graphical effects to take the curse off the compositor, or stick with Wayland, disable Latte-Dock and set up your own dock (right-click on the desktop, add panel, customize) or install another dock.

5 Likes

Ah Okay, I wait for the update to the dock and then switch to Wayland.

Thank you for your help :slight_smile:

That glitch had fixed itself and I didn't have to worry at all. But it has returned again

I reset-ted my latte dock settings and its fine now.

:sweat_smile:


it seems like it freaks out even if I customize my latte panel a little bit.
Can't wait for latte-free dragonized.

Use

3 Likes

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