Spotify UI Flickering

Issues & Assistance Unsupported Software (AUR & Other)
, ,
1

I’ve noticed on wayland spotify has an issue where it will start to flicker and parts of the UI will start to disappear such as the playlists panel on the side having it’s playlist icons disappear.
Anyone got a clue as to what’s going on? The result of garuda-inxi is below

System:
Kernel: 6.7.4-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 13.2.1
clocksource: tsc available: hpet,acpi_pm
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=bdce2a21-901c-4746-8585-0768c91ee180 rw rootflags=subvol=@
quiet loglevel=3 ibt=off
Desktop: KDE Plasma v: 5.27.10 tk: Qt v: 5.15.12 wm: kwin_wayland dm: SDDM
Distro: Garuda Linux base: Arch Linux
Machine:
Type: Desktop Mobo: ASRock model: B650M Pro RS WiFi serial: N/A
UEFI: American Megatrends LLC. v: 2.02 date: 11/17/2023
CPU:
Info: model: AMD Ryzen 7 7800X3D socket: AM5 bits: 64 type: MT MCP
arch: Zen 4 gen: 5 level: v4 note: check built: 2022+ process: TSMC n5 (5nm)
family: 0x19 (25) model-id: 0x61 (97) stepping: 2 microcode: 0xA601206
Topology: cpus: 1x cores: 8 tpc: 2 threads: 16 smt: enabled cache:
L1: 512 KiB desc: d-8x32 KiB; i-8x32 KiB L2: 8 MiB desc: 8x1024 KiB
L3: 96 MiB desc: 1x96 MiB
Speed (MHz): avg: 2844 high: 4392 min/max: 400/5050 base/boost: 4200/5050
scaling: driver: amd-pstate-epp governor: powersave volts: 1.3 V
ext-clock: 100 MHz cores: 1: 400 2: 4388 3: 3563 4: 3525 5: 400 6: 4389
7: 3298 8: 3611 9: 3960 10: 4392 11: 4378 12: 4380 13: 3622 14: 400
15: 400 16: 400 bogomips: 134159
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Vulnerabilities: <filter>
Graphics:
Device-1: NVIDIA TU116 [GeForce GTX 1660 SUPER] vendor: Micro-Star MSI
driver: nvidia v: 545.29.06 alternate: nouveau,nvidia_drm non-free: 545.xx+
status: current (as of 2023-10; EOL~2026-12-xx) arch: Turing code: TUxxx
process: TSMC 12nm FF built: 2018-2022 pcie: gen: 3 speed: 8 GT/s
lanes: 16 ports: active: none off: DP-1,HDMI-A-1 empty: DP-2,DP-3
bus-ID: 01:00.0 chip-ID: 10de:21c4 class-ID: 0300
Device-2: AMD Raphael driver: amdgpu v: kernel arch: RDNA-2 code: Navi-2x
process: TSMC n7 (7nm) built: 2020-22 pcie: gen: 4 speed: 16 GT/s lanes: 16
ports: active: none empty: DP-4, DP-5, DP-6, HDMI-A-2 bus-ID: 0e:00.0
chip-ID: 1002:164e class-ID: 0300 temp: 43.0 C
Display: server: X.Org v: 23.2.4 with: Xwayland v: 23.2.4
compositor: kwin_wayland driver: X: loaded: amdgpu,nvidia
unloaded: modesetting,nouveau alternate: fbdev,nv,vesa dri: radeonsi
gpu: nvidia,nvidia-nvswitch display-ID: :1 screens: 1
Screen-1: 0 s-res: 3840x1392 s-dpi: 96 s-size: 1016x368mm (40.00x14.49")
s-diag: 1081mm (42.54")
Monitor-1: DP-1 note: disabled pos: primary,top-right model: E321VL
serial: <filter> built: 2008 res: 1920x1080 hz: 60 dpi: 70 gamma: 1.2
size: 700x390mm (27.56x15.35") diag: 801mm (31.5") ratio: 16:9 modes:
max: 1920x1080 min: 640x480
Monitor-2: HDMI-A-1 note: disabled pos: bottom-l
model: BOE Display RT1971-AC built: 2017 res: 1920x1080 hz: 60 gamma: 1.2
size: N/A modes: max: 1366x768 min: 640x480
API: EGL v: 1.5 hw: drv: nvidia drv: amd radeonsi platforms: device: 0
drv: nvidia device: 2 drv: radeonsi device: 3 drv: swrast gbm: drv: nvidia
surfaceless: drv: nvidia x11: drv: zink inactive: wayland,device-1
API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 545.29.06
glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce GTX 1660
SUPER/PCIe/SSE2 memory: 5.86 GiB
API: Vulkan v: 1.3.276 layers: 10 device: 0 type: discrete-gpu name: NVIDIA
GeForce GTX 1660 SUPER driver: nvidia v: 545.29.06 device-ID: 10de:21c4
surfaces: xcb,xlib device: 1 type: integrated-gpu name: AMD Radeon
Graphics (RADV RAPHAEL_MENDOCINO) driver: mesa radv v: 23.3.5-arch1.1
device-ID: 1002:164e surfaces: xcb,xlib device: 2 type: cpu name: llvmpipe
(LLVM 16.0.6 256 bits) driver: mesa llvmpipe v: 23.3.5-arch1.1 (LLVM
16.0.6) device-ID: 10005:0000 surfaces: xcb,xlib
Audio:
Device-1: NVIDIA TU116 High Definition Audio vendor: Micro-Star MSI
driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16
bus-ID: 01:00.1 chip-ID: 10de:1aeb class-ID: 0403
Device-2: AMD Rembrandt Radeon High Definition Audio driver: snd_hda_intel
v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 0e:00.1
chip-ID: 1002:1640 class-ID: 0403
Device-3: AMD Family 17h/19h HD Audio vendor: ASRock driver: snd_hda_intel
v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 0e:00.6
chip-ID: 1022:15e3 class-ID: 0403
Device-4: Kingston HyperX 7.1 Audio
driver: hid-generic,snd-usb-audio,usbhid type: USB rev: 2.0 speed: 12 Mb/s
lanes: 1 mode: 1.1 bus-ID: 3-4:3 chip-ID: 0951:16a4 class-ID: 0300
serial: <filter>
API: ALSA v: k6.7.4-zen1-1-zen status: kernel-api with: aoss
type: oss-emulator tools: N/A
Server-1: PipeWire v: 1.0.3 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: MEDIATEK MT7922 802.11ax PCI Express Wireless Network Adapter
driver: mt7921e v: kernel pcie: gen: 2 speed: 5 GT/s lanes: 1
bus-ID: 05:00.0 chip-ID: 14c3:0616 class-ID: 0280
IF: wlp5s0 state: down mac: <filter>
Device-2: Realtek RTL8125 2.5GbE vendor: ASRock driver: r8169 v: kernel
pcie: gen: 2 speed: 5 GT/s lanes: 1 port: e000 bus-ID: 06:00.0
chip-ID: 10ec:8125 class-ID: 0200
IF: enp6s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Bluetooth:
Device-1: MediaTek Wireless_Device driver: btusb v: 0.8 type: USB rev: 2.1
speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 3-8:5 chip-ID: 0e8d:0616
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.2 lmp-v: 11
status: discoverable: no pairing: no
Drives:
Local Storage: total: 2.96 TiB used: 526.47 GiB (17.4%)
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: TeamGroup model: TM8FP6256G
size: 238.47 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s
lanes: 4 tech: SSD serial: <filter> fw-rev: VC2S038C temp: 45.9 C
scheme: GPT
SMART: yes health: PASSED on: 45d 23h cycles: 328
read-units: 3,828,242 [1.96 TB] written-units: 4,428,529 [2.26 TB]
ID-2: /dev/sda maj-min: 8:0 vendor: HGST (Hitachi) model: HTS721010A9E630
family: Travelstar 7K1000 size: 931.51 GiB block-size: physical: 4096 B
logical: 512 B sata: 3.0 speed: 6.0 Gb/s tech: HDD rpm: 7200
serial: <filter> fw-rev: A3U0 temp: 34 C scheme: GPT
SMART: yes state: enabled health: PASSED on: 1y 26d 16h cycles: 2292
ID-3: /dev/sdb maj-min: 8:16 vendor: Samsung model: SSD 870 EVO 1TB
family: based SSDs size: 931.51 GiB block-size: physical: 512 B
logical: 512 B sata: 3.3 speed: 6.0 Gb/s tech: SSD serial: <filter>
fw-rev: 3B6Q temp: 31 C scheme: GPT
SMART: yes state: enabled health: PASSED on: 53d 19h cycles: 456
written: 2.89 TiB
ID-4: /dev/sdc maj-min: 8:32 vendor: Western Digital
model: WD10EZEX-75WN4A1 family: Blue size: 931.51 GiB block-size:
physical: 4096 B logical: 512 B sata: 3.1 speed: 6.0 Gb/s tech: HDD
rpm: 7200 serial: <filter> fw-rev: 7113 temp: 32 C scheme: GPT
SMART: yes state: enabled health: PASSED on: 1y 75d 20h cycles: 1287
read: 7.26 TiB written: 9.09 TiB
Partition:
ID-1: / raw-size: 238.17 GiB size: 238.17 GiB (100.00%)
used: 85.72 GiB (36.0%) fs: btrfs block-size: 4096 B dev: /dev/nvme0n1p2
maj-min: 259:2
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 584 KiB (0.2%) fs: vfat block-size: 512 B dev: /dev/nvme0n1p1
maj-min: 259:1
ID-3: /home raw-size: 238.17 GiB size: 238.17 GiB (100.00%)
used: 85.72 GiB (36.0%) fs: btrfs block-size: 4096 B dev: /dev/nvme0n1p2
maj-min: 259:2
ID-4: /var/log raw-size: 238.17 GiB size: 238.17 GiB (100.00%)
used: 85.72 GiB (36.0%) fs: btrfs block-size: 4096 B dev: /dev/nvme0n1p2
maj-min: 259:2
ID-5: /var/tmp raw-size: 238.17 GiB size: 238.17 GiB (100.00%)
used: 85.72 GiB (36.0%) fs: btrfs block-size: 4096 B dev: /dev/nvme0n1p2
maj-min: 259:2
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: zram size: 30.47 GiB used: 4 MiB (0.0%) priority: 100
comp: zstd avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 16 dev: /dev/zram0
Sensors:
System Temperatures: cpu: 49.8 C mobo: 34.0 C gpu: amdgpu temp: 43.0 C
Fan Speeds (rpm): N/A
Info:
Processes: 427 Uptime: 2m wakeups: 0 Memory: total: 32 GiB note: est.
available: 30.47 GiB used: 5.61 GiB (18.4%) Init: systemd v: 255
default: graphical tool: systemctl Compilers: gcc: 13.2.1 Packages:
pm: pacman pkgs: 1880 libs: 549 tools: octopi,paru pm: appimage pkgs: 0
Shell: garuda-inxi (sudo) default: Bash v: 5.2.26 running-in: konsole
inxi: 3.3.31
Garuda (2.6.23-1):
System install date:     2024-01-25
Last full system update: 2024-02-07
Is partially upgraded:   No
Relevant software:       snapper NetworkManager dracut nvidia-dkms
Windows dual boot:       Yes
Failed units:
2

Wayland is still very much a work-in-progress with KDE. Expect it to be flawed. You can report any bugs to the Wayland & KDE developers.

But until Wayland goes stable in Arch + KDE, expect glitches. And use x11. :smiley:

2 Likes
3

I would but x11 gives me awful screen tearing on things like games or youtube videos

4

You are missing kernel parameters for Nvidia on Wayland:

2 Likes
5

I would say “use wayland, report bugs”

Since switching to garuda 2 Months ago and having wayland by default I have seen little problems and that it is improving rapidly.

Also expecting big things with plasma 6 really focusing on wayland.

I am on a rolling release distro so I think that means living on the bleeding edge.

Also to go back to OT no problems with spotify in the last 2 Months with AMD graphics.

6

I have this internal instinct where if something does not work correctly on wayland/xorg e.g kstars from the package manager I opt to install a version from either flatpak/snap

Not a worthwile solution but can be a temporary save—> :eyes:
P.s… You should probably follow the advice above this comment, you can try this comment as and adventure ride.

7

“A little knowledge is a dangerous thing.”

I’m a slow learner. It’s taken me 20+ years of daily use to learn the little bit about Linux I’ve acquired to date. I must like living dangerously. :rofl:

4 Likes
8

I had to sudo nano and add the nvidia part because the command given would not change grub for whatever reason and even then it still happens

9

Went the flatpak version of spotify and the flickering persists

10

Not sure if that will work for Spotify but I got rid of some graphical glitches after disabling Blur in Desktop Effects

11

Flickers seem to be almost minimal but I don’t know if something changed since last time I used wayland when making this post but turning off blur did fix an issue I had where the terminal and other semi transparent windows left a weird trail behind the cursor

12

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