Some texts of KDE widgets are corrupted, have missing character

Hi,

Probably since last update, some text in KDE widgets, like dock, system-monitor and kde settings are corrupted.

Does anyone have an idea ?

  Kernel: 6.1.4-zen2-1-zen arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
    parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
    root=UUID=0516cc77-cb27-4964-8ac0-ccdb9cfccc68 rw [email protected]
    quiet
    cryptdevice=UUID=a8f9f78c-37f2-44e1-af31-1aaa655af8d6:luks-a8f9f78c-37f2-44e1-af31-1aaa655af8d6
    root=/dev/mapper/luks-a8f9f78c-37f2-44e1-af31-1aaa655af8d6
    resume=/dev/mapper/luks-a8f9f78c-37f2-44e1-af31-1aaa655af8d6
    resume_offset=29140226 quiet splash mem_sleep_default=deep
    rd.udev.log_priority=3 vt.global_cursor_default=0 loglevel=3 ibt=off
  Desktop: KDE Plasma v: 5.26.5 tk: Qt v: 5.15.8 info: latte-dock
    wm: kwin_wayland vt: 2 dm: SDDM Distro: Garuda Linux base: Arch Linux
Machine:
  Type: Laptop System: Framework product: Laptop v: AB
    serial: <superuser required>
  Mobo: Framework model: FRANBMCP0B v: AB serial: <superuser required>
    UEFI: INSYDE v: 03.07 date: 12/14/2021
Battery:
  ID-1: BAT1 charge: 31.9 Wh (60.3%) condition: 52.9/55.0 Wh (96.1%)
    volts: 15.8 min: 15.4 model: NVT Framewo type: Li-ion serial: <filter>
    status: charging
CPU:
  Info: model: 11th Gen Intel Core i7-1165G7 bits: 64 type: MT MCP
    arch: Tiger Lake gen: core 11 level: v4 note: check built: 2020
    process: Intel 10nm family: 6 model-id: 0x8C (140) stepping: 1
    microcode: 0xA6
  Topology: cpus: 1x cores: 4 tpc: 2 threads: 8 smt: enabled cache:
    L1: 320 KiB desc: d-4x48 KiB; i-4x32 KiB L2: 5 MiB desc: 4x1.2 MiB
    L3: 12 MiB desc: 1x12 MiB
  Speed (MHz): avg: 2727 high: 2800 min/max: 400/4700 scaling:
    driver: intel_pstate governor: performance cores: 1: 2222 2: 2800 3: 2800
    4: 2800 5: 2800 6: 2800 7: 2800 8: 2800 bogomips: 44851
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities: <filter>
Graphics:
  Device-1: Intel TigerLake-LP GT2 [Iris Xe Graphics] driver: i915 v: kernel
    arch: Gen-12.1 process: Intel 10nm built: 2020-21 ports: active: DP-3,eDP-1
    empty: DP-1,DP-2,DP-4 bus-ID: 00:02.0 chip-ID: 8086:9a49 class-ID: 0300
  Display: wayland server: X.org v: 1.21.1.6 with: Xwayland v: 22.1.7
    compositor: kwin_wayland driver: X: loaded: modesetting
    alternate: fbdev,intel,vesa dri: iris gpu: i915 d-rect: 3424x2083
    display-ID: 0
  Monitor-1: DP-3 pos: primary,top-left res: 1920x1080 size: N/A modes: N/A
  Monitor-2: eDP-1 pos: bottom-r res: 1504x1003 size: N/A modes: N/A
  API: OpenGL v: 4.6 Mesa 22.3.2 renderer: Mesa Intel Xe Graphics (TGL GT2)
    direct render: Yes
Audio:
  Device-1: Intel Tiger Lake-LP Smart Sound Audio driver: snd_hda_intel
    v: kernel alternate: snd_sof_pci_intel_tgl bus-ID: 00:1f.3
    chip-ID: 8086:a0c8 class-ID: 0403
  Sound API: ALSA v: k6.1.4-zen2-1-zen running: yes
  Sound Server-1: PulseAudio v: 16.1 running: no
  Sound Server-2: PipeWire v: 0.3.63 running: yes
Network:
  Device-1: Intel Wi-Fi 6 AX210/AX211/AX411 160MHz driver: iwlwifi v: kernel
    pcie: gen: 2 speed: 5 GT/s lanes: 1 bus-ID: aa:00.0 chip-ID: 8086:2725
    class-ID: 0280
  IF: wlp170s0 state: up mac: <filter>
Bluetooth:
  Device-1: Intel AX210 Bluetooth type: USB driver: btusb v: 0.8
    bus-ID: 3-10:7 chip-ID: 8087:0032 class-ID: e001
  Report: bt-adapter ID: hci0 rfk-id: 0 state: up address: <filter>
Drives:
  Local Storage: total: 465.76 GiB used: 194.92 GiB (41.8%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Western Digital
    model: WDS500G1X0E-00AFY0 size: 465.76 GiB block-size: physical: 512 B
    logical: 512 B speed: 63.2 Gb/s lanes: 4 type: SSD serial: <filter>
    rev: 614600WD temp: 37.9 C scheme: GPT
Partition:
  ID-1: / raw-size: 465.46 GiB size: 465.46 GiB (100.00%)
    used: 194.92 GiB (41.9%) fs: btrfs dev: /dev/dm-0 maj-min: 254:0
    mapped: luks-a8f9f78c-37f2-44e1-af31-1aaa655af8d6
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
    used: 752 KiB (0.2%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
  ID-3: /home raw-size: 465.46 GiB size: 465.46 GiB (100.00%)
    used: 194.92 GiB (41.9%) fs: btrfs dev: /dev/dm-0 maj-min: 254:0
    mapped: luks-a8f9f78c-37f2-44e1-af31-1aaa655af8d6
  ID-4: /var/log raw-size: 465.46 GiB size: 465.46 GiB (100.00%)
    used: 194.92 GiB (41.9%) fs: btrfs dev: /dev/dm-0 maj-min: 254:0
    mapped: luks-a8f9f78c-37f2-44e1-af31-1aaa655af8d6
  ID-5: /var/tmp raw-size: 465.46 GiB size: 465.46 GiB (100.00%)
    used: 194.92 GiB (41.9%) fs: btrfs dev: /dev/dm-0 maj-min: 254:0
    mapped: luks-a8f9f78c-37f2-44e1-af31-1aaa655af8d6
Swap:
  Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: file size: 32 GiB used: 0 KiB (0.0%) priority: -2
    file: /var/swap/swapfile
  ID-2: swap-2 type: zram size: 31.14 GiB used: 0 KiB (0.0%) priority: 100
    dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 43.0 C mobo: N/A
  Fan Speeds (RPM): N/A
Info:
  Processes: 306 Uptime: 29m wakeups: 1 Memory: 31.14 GiB
  used: 7.64 GiB (24.5%) Init: systemd v: 252 default: graphical
  tool: systemctl Compilers: gcc: 12.2.0 clang: 14.0.6 Packages: pm: pacman
  pkgs: 1463 libs: 331 tools: octopi,paru Shell: fish v: 3.5.1 default: Bash
  v: 5.1.16 running-in: kitty inxi: 3.3.24
Garuda (2.6.14-1):
  System install date:     2022-06-19
  Last full system update: 2023-01-10
  Is partially upgraded:   No
  Relevant software:       snapper NetworkManager mkinitcpio
  Windows dual boot:       No/Undetected
  Failed units:            

I see you're on Wayland.
Does it happen also in a x11 session?

So, I have not though about that and made a few tries. I have a multi screen configuration.
The bug does not appear on X11, only on wayland IF and only IF I have scaling on one monitor, even if I unglug my second monitor. I have to logout/login to resolve the corruption after settings everything to 100%, but not always...

So yet another wayland bug ?

Yes, most definitely.
I have a laptop (which I don't use, but up-to-date) with Arch and KDE Wayland and could reproduce the issue (with only laptop screen, no external monitor).
The KDE bug list including Wayland is so long that I gave up checking if the issue already exists...

2 Likes

Thank you for taking your time reproducing it. At least I'm not alone.

Let's wait for a fix then.

1 Like

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