Latte crashing after switch to wayland

Hey there,
trying to fix the Wayland boot issue, @dejv78 and I have decided to reinstall our systems.
After that finished for me, I was finally able to boot into wayland, but now there is a new problem: Latte dock won't start.
It always spits out this error: interface 'kde_output_device_v2' has no event 14
Note: I am using the kde git packages.
Why is that?
Thanks!

Inxi:

System:
  Kernel: 5.15.11-zen1-1-zen x86_64 bits: 64 compiler: gcc v: 11.1.0
    parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
    root=UUID=6e6211b4-cfb4-44c0-8970-5e4a826e0c5e 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.4 tk: Qt 5.15.2 wm: kwin_wayland vt: 2 dm: Ly
    Distro: Garuda Linux base: Arch Linux
Machine:
  Type: Desktop System: Gigabyte product: AX370-Gaming 3 v: N/A
    serial: <superuser required>
  Mobo: Gigabyte model: AX370-Gaming 3-CF v: x.x
    serial: <superuser required> UEFI: American Megatrends v: F50a
    date: 11/27/2019
CPU:
  Info: model: AMD Ryzen 5 2600X bits: 64 type: MT MCP arch: Zen+
    family: 0x17 (23) model-id: 8 stepping: 2 microcode: 0x800820D
  Topology: cpus: 1x cores: 6 tpc: 2 threads: 12 smt: enabled cache:
    L1: 576 KiB desc: d-6x32 KiB; i-6x64 KiB L2: 3 MiB desc: 6x512 KiB
    L3: 16 MiB desc: 2x8 MiB
  Speed (MHz): avg: 3029 high: 4239 min/max: 2200/3600 boost: enabled
    scaling: driver: acpi-cpufreq governor: performance cores: 1: 2572 2: 2795
    3: 2438 4: 2432 5: 2717 6: 4239 7: 3220 8: 2848 9: 2424 10: 2604 11: 3827
    12: 4236 bogomips: 86224
  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: AMD Baffin [Radeon RX 550 640SP / RX 560/560X] vendor: ASUSTeK
    driver: amdgpu v: kernel bus-ID: 08:00.0 chip-ID: 1002:67ff class-ID: 0300
  Device-2: Logitech Webcam C270 type: USB driver: snd-usb-audio,uvcvideo
    bus-ID: 3-3:5 chip-ID: 046d:0825 class-ID: 0102 serial: <filter>
  Display: wayland server: X.Org 1.21.1.4 compositor: kwin_wayland driver:
    loaded: amdgpu,ati unloaded: modesetting,radeon alternate: fbdev,vesa
    display-ID: :0 screens: 1
  Screen-1: 0 s-res: 3600x1200 s-dpi: 96 s-size: 953x318mm (37.5x12.5")
    s-diag: 1005mm (39.6")
  Monitor-1: XWAYLAND0 res: 1680x1050 hz: 60 dpi: 91
    size: 470x300mm (18.5x11.8") diag: 558mm (22")
  Monitor-2: XWAYLAND1 res: 1920x1200 hz: 60 dpi: 100
    size: 490x310mm (19.3x12.2") diag: 580mm (22.8")
  OpenGL: renderer: AMD Radeon RX 560 Series (POLARIS11 DRM 3.42.0
    5.15.11-zen1-1-zen LLVM 13.0.0)
    v: 4.6 Mesa 21.3.2 direct render: Yes
Audio:
  Device-1: AMD Baffin HDMI/DP Audio [Radeon RX 550 640SP / RX 560/560X]
    vendor: ASUSTeK driver: snd_hda_intel v: kernel bus-ID: 08:00.1
    chip-ID: 1002:aae0 class-ID: 0403
  Device-2: AMD Family 17h HD Audio vendor: Gigabyte driver: snd_hda_intel
    v: kernel bus-ID: 0a:00.3 chip-ID: 1022:1457 class-ID: 0403
  Device-3: C-Media USB Microphone type: USB
    driver: hid-generic,snd-usb-audio,usbhid bus-ID: 3-1.4:6 chip-ID: 0d8c:9700
    class-ID: 0300 serial: <filter>
  Device-4: Logitech Webcam C270 type: USB driver: snd-usb-audio,uvcvideo
    bus-ID: 3-3:5 chip-ID: 046d:0825 class-ID: 0102 serial: <filter>
  Sound Server-1: ALSA v: k5.15.11-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.42 running: yes
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
    vendor: Gigabyte driver: r8169 v: kernel port: f000 bus-ID: 03:00.0
    chip-ID: 10ec:8168 class-ID: 0200
  IF: eno1 state: up speed: 1000 Mbps duplex: full mac: <filter>
Bluetooth:
  Device-1: Broadcom BCM20702A0 Bluetooth 4.0 type: USB driver: btusb v: 0.8
    bus-ID: 3-1.1:4 chip-ID: 0a5c:21e8 class-ID: fe01 serial: <filter>
  Report: bt-adapter ID: hci0 rfk-id: 0 state: down
    bt-service: enabled,running rfk-block: hardware: no software: no
    address: <filter>
Drives:
  Local Storage: total: 2.96 TiB used: 1.02 TiB (34.3%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 860 EVO 1TB
    size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
    type: SSD serial: <filter> rev: 4B6Q scheme: GPT
  ID-2: /dev/sdb maj-min: 8:16 vendor: Samsung model: SSD 860 EVO 250GB
    size: 232.89 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
    type: SSD serial: <filter> rev: 1B6Q scheme: GPT
  ID-3: /dev/sdc maj-min: 8:32 vendor: Western Digital
    model: WD20EFRX-68EUZN0 size: 1.82 TiB block-size: physical: 4096 B
    logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 5400 serial: <filter>
    rev: 0A82 scheme: GPT
Partition:
  ID-1: / raw-size: 195.03 GiB size: 195.03 GiB (100.00%)
    used: 28.62 GiB (14.7%) fs: btrfs dev: /dev/sda1 maj-min: 8:1
  ID-2: /boot/efi raw-size: 301 MiB size: 300.4 MiB (99.79%)
    used: 576 KiB (0.2%) fs: vfat dev: /dev/sda2 maj-min: 8:2
  ID-3: /home raw-size: 736.18 GiB size: 736.18 GiB (100.00%)
    used: 136.83 GiB (18.6%) fs: btrfs dev: /dev/sda3 maj-min: 8:3
  ID-4: /var/log raw-size: 195.03 GiB size: 195.03 GiB (100.00%)
    used: 28.62 GiB (14.7%) fs: btrfs dev: /dev/sda1 maj-min: 8:1
  ID-5: /var/tmp raw-size: 195.03 GiB size: 195.03 GiB (100.00%)
    used: 28.62 GiB (14.7%) fs: btrfs dev: /dev/sda1 maj-min: 8:1
Swap:
  Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: zram size: 31.36 GiB used: 2.8 MiB (0.0%)
    priority: 100 dev: /dev/zram0
Sensors:
  System Temperatures: cpu: N/A mobo: N/A gpu: amdgpu temp: 32.0 C
  Fan Speeds (RPM): N/A gpu: amdgpu fan: 1410
Info:
  Processes: 406 Uptime: 15m wakeups: 0 Memory: 31.36 GiB
  used: 6.14 GiB (19.6%) Init: systemd v: 250 tool: systemctl Compilers:
  gcc: 11.1.0 clang: 13.0.0 Packages: apt: 0 pacman: 2018 lib: 481
  Shell: fish v: 3.3.1 default: Bash v: 5.1.12 running-in: alacritty
  inxi: 3.3.11

An internet search turns up many hits on this topic. These are just a couple returned:

https://www.mail-archive.com/[email protected]/msg597323.html

1 Like

I couldn't find any of that :confused:
Anyways, it's "not a bug": 441718 – Latte dock crashes instantly on wayland sessions.

So, this is after a fresh install and a full update?

No extra software from the AUR installed?

Just a virginal freshly updated install?

I just installed this (And updated), yes.
I installed some of the software which is important to me, so no no-AUR-installation.

Latte works on x11 lol

Have you tested Latte with all widgets disabled. Widgets are one of the most common reasons for latte crashes.

Latte crashes even with latte-dock --default-layout

Have you thought about trying a KDE barebones install? A bit more effort, but you seem like a very competent user.

Yikes. I am a fan of the garuda configs and I just went the extra mile to reinstall garuda just to get wayland to work... I am not a fan.

It was just a thought to see if we could pin down where the issue originates. I fully understand your hesitancy to go that route.

It may simply be another case of KDE Wayland not quite being ready for prime time yet.

2 Likes

Did you start on zero?

With one monitor?

Latte crash maybe from your 3 monitor configuration?

I sure hope this is the problem.
Reinstalling from time to time isn't too bad though. Keeps the system clean and instandly de-bloats :wink:

(Unless you reinstall all the old packages you had installed, as I did xD)

Huh? I only have two screens

I think Screen-1 is all of the screens added together or something like that.

Like what the other person saw when one shared their screen with discord about a year ago

OOPs

You have two monitors in one screen, ok.

Again, do you try with one monitor in one screen with same size/dimension?

I think so too, with my one monitor :smiley:

2 Likes

Okay I have tried this with only one monitor, which didn't work, but I have something else that I completely forgot about:
Latte "works" for a short while (It just shows the config gui and warns about an error in the garuda config - An orphaned subcontainment or something like that - And when trying to switch configs, latte crashes and only returns the above error

EDIT: Oh the LOGS! 0bin - encrypted pastebin

Did somebody say it was? Hmm, I guess this guy did. :slight_smile:

1 Like

My experience with Wayland has been horrible, it crashes and is very buggy. KDE refused to work right when I used Wayland. IMHO Wayland is not ready for prime time.

1 Like

What is the crash report?

3 Likes

There is no crash report. I had journalctl -xf open and even checked coredumpctl

Close latte, add a default plasma panel, start latte

If it crashes, KCrash will give you a report

2 Likes