After switching to Plasma Wayland Session, Desktop is not usable (looks like zoomed in)

Hello,

I searched a lot for a potential fix but i did not even found someone with the same issue.

I have installed the Nvidia Drivers (550.67-3) during the installer and choose to go for KDE as my Desktop env.
Default it goes with X-Server and i wanted to switch to wayland (i read it has more performance for games etc. and wanted to try it)

After switching from X to wayland, rebooting the desktop is not usable.
It looks like fully Zoomed in. My whole screen is basically covered with the Manjaro welcome screen. The second display is not recognized anymore and copies screen 1.
It does not look like a resolution problem, else right click etc. should at least bring up an oversized context menu or the Taskbar should be visible.
I only see a fully zoomed in welcome bar (and if firefox reopens again an oversized firefox content).
(during typing i remembered it could also be described as a massive overscan)

Switching back to X by modifying the sddm config resolves the issue and it works again.

I read that nvidia and wayland should work fine so i assume the issue is in front of the display.

Thanks in advance
regards

// Edit sorry for posting it first wrong

sudo inxi --admin --verbosity=8 --filter --no-host --width --repos                                           ✔ 
[sudo] Passwort für chris: 
System:
  Kernel: 6.6.25-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 13.2.1
    clocksource: tsc avail: hpet,acpi_pm
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.6-x86_64
    root=UUID=2da6a215-6d4d-4025-8771-08054895d51b rw quiet splash
    udev.log_priority=3 nvidia-drm.modset=1
  Desktop: KDE Plasma v: 5.27.11 tk: Qt v: N/A wm: kwin_wayland dm: SDDM
    Distro: Manjaro base: Arch Linux
Machine:
  Type: Desktop Mobo: ASUSTeK model: MAXIMUS VIII RANGER v: Rev 1.xx
    serial: <filter> part-nu: SKU uuid: 37ad1460-d7db-11dd-91cb-305a3a0269fd
    UEFI: American Megatrends v: 3802 date: 03/15/2018
Battery:
  Device-1: hidpp_battery_0 model: Logitech G305 Lightspeed Wireless Gaming
    Mouse serial: <filter> charge: 100% (should be ignored) rechargeable: yes
    status: discharging
Memory:
  System RAM: total: 32 GiB available: 31.29 GiB used: 3.17 GiB (10.1%)
  Array-1: capacity: 64 GiB slots: 4 modules: 4 EC: None
    max-module-size: 16 GiB note: est.
  Device-1: ChannelA-DIMM1 type: DDR4 detail: synchronous size: 8 GiB
    speed: 2667 MT/s volts: curr: 1.2 width (bits): data: 64 total: 64
    manufacturer: Kingston part-no: KHX2666C15D4/8G serial: <filter>
  Device-2: ChannelA-DIMM2 type: DDR4 detail: synchronous size: 8 GiB
    speed: 2667 MT/s volts: curr: 1.2 width (bits): data: 64 total: 64
    manufacturer: Kingston part-no: KHX2666C15D4/8G serial: <filter>
  Device-3: ChannelB-DIMM1 type: DDR4 detail: synchronous size: 8 GiB
    speed: 2667 MT/s volts: curr: 1.2 width (bits): data: 64 total: 64
    manufacturer: Kingston part-no: KHX2666C15D4/8G serial: <filter>
  Device-4: ChannelB-DIMM2 type: DDR4 detail: synchronous size: 8 GiB
    speed: 2667 MT/s volts: curr: 1.2 width (bits): data: 64 total: 64
    manufacturer: Kingston part-no: KHX2666C15D4/8G serial: <filter>
PCI Slots:
  Slot: 0 type: PCIe lanes: 1 status: available length: short volts: 3.3
    bus-ID: ff:00.0
  Slot: 1 type: PCIe lanes: 16 status: in use length: long volts: 3.3
    bus-ID: 01:00.0
  Slot: 2 type: PCIe lanes: 1 status: available length: short volts: 3.3
    bus-ID: ff:00.0
  Slot: 3 type: PCIe lanes: 8 status: available length: long volts: 3.3
    bus-ID: ff:00.0
  Slot: 4 type: PCIe lanes: 1 status: available length: short volts: 3.3
    bus-ID: ff:00.0
  Slot: 5 type: PCIe lanes: 16 status: available length: long volts: 3.3
    bus-ID: ff:00.0
CPU:
  Info: model: Intel Core i7-6700K socket: LGA1151 bits: 64 type: MT MCP
    arch: Skylake-S gen: core 6 level: v3 note: check built: 2015
    process: Intel 14nm family: 6 model-id: 0x5E (94) stepping: 3
    microcode: 0xF0
  Topology: cpus: 1x cores: 4 tpc: 2 threads: 8 smt: enabled cache:
    L1: 256 KiB desc: d-4x32 KiB; i-4x32 KiB L2: 1024 KiB desc: 4x256 KiB
    L3: 8 MiB desc: 1x8 MiB
  Speed (MHz): avg: 800 min/max: 800/4200 base/boost: 4000/8300 scaling:
    driver: intel_pstate governor: powersave volts: 1.2 V ext-clock: 100 MHz
    cores: 1: 800 2: 800 3: 800 4: 800 5: 800 6: 800 7: 800 8: 800
    bogomips: 64026
  Flags: 3dnowprefetch abm acpi adx aes aperfmperf apic arat
    arch_capabilities arch_perfmon art avx avx2 bmi1 bmi2 bts clflush
    clflushopt cmov constant_tsc cpuid cpuid_fault cx16 cx8 de ds_cpl dtes64
    dtherm dts epb erms est f16c flush_l1d fma fpu fsgsbase fxsr ht hwp
    hwp_act_window hwp_epp hwp_notify ibpb ibrs ida intel_pt invpcid lahf_lm
    lm mca mce md_clear mmx monitor movbe mpx msr mtrr nonstop_tsc nopl nx pae
    pat pbe pcid pclmulqdq pdcm pdpe1gb pebs pge pln pni popcnt pse pse36 pti
    pts rdrand rdseed rdtscp rep_good sdbg sep smap smep ss ssbd sse sse2
    sse4_1 sse4_2 ssse3 stibp syscall tm tm2 tsc tsc_adjust tsc_deadline_timer
    vme x2apic xgetbv1 xsave xsavec xsaveopt xsaves xtopology xtpr
  Vulnerabilities:
  Type: gather_data_sampling status: Vulnerable: No microcode
  Type: itlb_multihit status: KVM: VMX unsupported
  Type: l1tf mitigation: PTE Inversion
  Type: mds mitigation: Clear CPU buffers; SMT vulnerable
  Type: meltdown mitigation: PTI
  Type: mmio_stale_data mitigation: Clear CPU buffers; SMT vulnerable
  Type: reg_file_data_sampling status: Not affected
  Type: retbleed mitigation: IBRS
  Type: spec_rstack_overflow 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: IBRS, IBPB: conditional, STIBP: conditional,
    RSB filling, PBRSB-eIBRS: Not affected
  Type: srbds mitigation: Microcode
  Type: tsx_async_abort mitigation: TSX disabled
Graphics:
  Device-1: NVIDIA GP104 [GeForce GTX 1080] driver: nvidia v: 550.67
    alternate: nouveau,nvidia_drm non-free: 545.xx+ status: current (as of
    2024-02; EOL~2026-12-xx) arch: Pascal code: GP10x process: TSMC 16nm
    built: 2016-2021 pcie: gen: 3 speed: 8 GT/s lanes: 16 ports: active: none
    off: DP-2,DP-3 empty: DP-1,DVI-D-1,HDMI-A-1 bus-ID: 01:00.0
    chip-ID: 10de:1b80 class-ID: 0300
  Display: server: X.Org v: 23.2.5 with: Xwayland v: 23.2.5
    compositor: kwin_wayland driver: X: loaded: nvidia
    gpu: nvidia,nvidia-nvswitch display-ID: :1 screens: 1
  Screen-1: 0 s-res: 5120x1440 s-dpi: 96 s-size: 1355x381mm (53.35x15.00")
    s-diag: 1408mm (55.42") monitors: <missing: xrandr>
  Monitor-1: DP-2 model: BenQ EW2780Q serial: <filter> built: 2020
    res: 2560x1440 dpi: 109 gamma: 1.2 chroma: red: x: 0.663 y: 0.333 green:
    x: 0.302 y: 0.616 blue: x: 0.149 y: 0.059 white: x: 0.314 y: 0.329
    size: 597x336mm (23.5x13.23") diag: 685mm (27") ratio: 16:9
    modes: 2560x1440, 1920x1080, 1680x1050, 1600x900, 1280x1024, 1280x800,
    1280x720, 1024x768, 800x600, 720x576, 720x480, 640x480
  Monitor-2: DP-3 model: Asus ROG PG279Q serial: <filter> built: 2015
    res: 2560x1440 dpi: 109 gamma: 1.2 chroma: red: x: 0.639 y: 0.329 green:
    x: 0.298 y: 0.600 blue: x: 0.149 y: 0.059 white: x: 0.314 y: 0.329
    size: 598x336mm (23.54x13.23") diag: 686mm (27") ratio: 16:9
    modes: 2560x1440, 1024x768, 800x600, 640x480
  API: EGL v: 1.5 hw: drv: nvidia platforms: device: 0 drv: nvidia device: 2
    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: 550.67 glx-v: 1.4
    direct-render: yes renderer: NVIDIA GeForce GTX 1080/PCIe/SSE2
    memory: 7.81 GiB
  API: Vulkan v: 1.3.279 layers: 1 device: 0 type: discrete-gpu
    name: NVIDIA GeForce GTX 1080 driver: nvidia v: 550.67 device-ID: 10de:1b80
    surfaces: xcb,xlib
Audio:
  Device-1: Intel 100 Series/C230 Series Family HD Audio vendor: ASUSTeK
    driver: snd_hda_intel v: kernel alternate: snd_soc_avs bus-ID: 00:1f.3
    chip-ID: 8086:a170 class-ID: 0403
  Device-2: NVIDIA GP104 High Definition Audio driver: snd_hda_intel
    v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 01:00.1
    chip-ID: 10de:10f0 class-ID: 0403
  Device-3: C-Media USB Advanced Audio Device
    driver: hid-generic,snd-usb-audio,usbhid type: USB rev: 1.1 speed: 12 Mb/s
    lanes: 1 mode: 1.1 bus-ID: 3-2.2:4 chip-ID: 0d8c:016c class-ID: 0300
  API: ALSA v: k6.6.25-1-MANJARO status: kernel-api with: aoss
    type: oss-emulator tools: alsactl,alsamixer,amixer
  Server-1: JACK v: 1.9.22 status: off tools: N/A
  Server-2: 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 tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Intel Ethernet I219-V vendor: ASUSTeK driver: e1000e v: kernel
    port: N/A bus-ID: 00:1f.6 chip-ID: 8086:15b8 class-ID: 0200
  IF: enp0s31f6 state: up speed: 1000 Mbps duplex: full mac: <filter>
  IP v4: <filter> type: dynamic noprefixroute scope: global
    broadcast: <filter>
  IP v6: <filter> type: dynamic noprefixroute scope: global
  IP v6: <filter> type: noprefixroute scope: link
  Info: services: NetworkManager
  WAN IP: <filter>
Bluetooth:
  Device-1: ASUSTek ASUS USB-BT500 driver: btusb v: 0.8 type: USB rev: 1.1
    speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-2:2 chip-ID: 0b05:190e
    class-ID: e001 serial: <filter>
  Report: rfkill ID: hci0 rfk-id: 0 state: up address: see --recommends
Logical:
  Message: No logical block device data found.
RAID:
  Message: No RAID data found.
Drives:
  Local Storage: total: 4.55 TiB used: 33.27 GiB (0.7%)
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung model: SSD 970 EVO 1TB
    size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s
    lanes: 4 tech: SSD serial: <filter> fw-rev: 2B2QEXE7 temp: 34.9 C
    scheme: MBR
  SMART: yes health: PASSED on: 142d 11h cycles: 2,714
    read-units: 71,895,172 [36.8 TB] written-units: 37,838,358 [19.3 TB]
  ID-2: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 870 EVO 2TB
    family: based SSDs size: 1.82 TiB block-size: physical: 512 B logical: 512 B
    sata: 3.3 speed: 6.0 Gb/s tech: SSD serial: <filter> fw-rev: 1B6Q
    temp: 27 C scheme: MBR
  SMART: yes state: enabled health: PASSED on: 209d 16h cycles: 757
    written: 4.28 TiB Pre-Fail: reallocated sector: 83 threshold: 10
  ID-3: /dev/sdb maj-min: 8:16 vendor: Samsung model: SSD 870 EVO 2TB
    family: based SSDs size: 1.82 TiB block-size: physical: 512 B logical: 512 B
    sata: 3.3 speed: 6.0 Gb/s tech: SSD serial: <filter> fw-rev: 1B6Q
    temp: 28 C scheme: MBR
  SMART: yes state: enabled health: PASSED on: 209d 23h cycles: 772
    written: 1.53 TiB Pre-Fail: reallocated sector: 91 threshold: 10
  Message: No optical or floppy data found.
Partition:
  ID-1: / raw-size: 791.77 GiB size: 778.27 GiB (98.30%) used: 33.27 GiB (4.3%)
    fs: ext4 block-size: 4096 B dev: /dev/sdb2 maj-min: 8:18 label: N/A
    uuid: 2da6a215-6d4d-4025-8771-08054895d51b
  ID-2: /boot/efi raw-size: 1 GiB size: 1022.1 MiB (99.80%)
    used: 448 KiB (0.0%) fs: vfat block-size: 512 B dev: /dev/sdb3 maj-min: 8:19
    label: N/A uuid: 0829-FEEE
Swap:
  Alert: No swap data was found.
Unmounted:
  ID-1: /dev/nvme0n1p1 maj-min: 259:1 size: 50 MiB fs: ntfs
    label: System-reserviert uuid: A82ED1F62ED1BD8E
  ID-2: /dev/nvme0n1p2 maj-min: 259:2 size: 930.95 GiB fs: ntfs label: N/A
    uuid: 9EFED548FED518FB
  ID-3: /dev/nvme0n1p3 maj-min: 259:3 size: 525 MiB fs: ntfs label: N/A
    uuid: 20F820B8F8208E5A
  ID-4: /dev/sda1 maj-min: 8:1 size: 1.82 TiB fs: ntfs label: Daten
    uuid: 52EC7497EC747757
  ID-5: /dev/sdb1 maj-min: 8:17 size: 1.05 TiB fs: ntfs label: Daten
    uuid: 7A2A13FA2A13B1DD
USB:
  Hub-1: 1-0:1 info: hi-speed hub with single TT ports: 16 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Device-1: 1-2:2 info: ASUSTek ASUS USB-BT500 type: bluetooth driver: btusb
    interfaces: 2 rev: 1.1 speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1
    power: 500mA chip-ID: 0b05:190e class-ID: e001 serial: <filter>
  Device-2: 1-6:3 info: MCT Elektronikladen VISION type: HID,keyboard
    driver: hid-generic,usbhid interfaces: 3 rev: 2.0 speed: 12 Mb/s (1.4 MiB/s)
    lanes: 1 mode: 1.1 power: 40mA chip-ID: 0c70:f00c class-ID: 0300
    serial: <filter>
  Hub-2: 1-13:4 info: Terminus FE 2.1 7-port Hub ports: 7 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 power: 100mA
    chip-ID: 1a40:0201 class-ID: 0900
  Device-1: 1-13.1:6 info: MCT Elektronikladen QUADRO type: HID
    driver: aquacomputer_d5next,usbhid interfaces: 2 rev: 2.1
    speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1 power: 2mA chip-ID: 0c70:f00d
    class-ID: 0300 serial: <filter>
  Device-2: 1-13.5:7 info: MCT Elektronikladen high flow NEXT type: HID
    driver: aquacomputer_d5next,usbhid interfaces: 2 rev: 2.1
    speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1 power: 2mA chip-ID: 0c70:f012
    class-ID: 0300 serial: <filter>
  Device-3: 1-14:5 info: MCT Elektronikladen aquaero type: keyboard,HID
    driver: aquacomputer_d5next,usbhid interfaces: 3 rev: 2.0
    speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1 power: 100mA
    chip-ID: 0c70:f001 class-ID: 0300 serial: <filter>
  Hub-3: 2-0:1 info: super-speed hub ports: 10 rev: 3.0
    speed: 5 Gb/s (596.0 MiB/s) lanes: 1 mode: 3.2 gen-1x1 chip-ID: 1d6b:0003
    class-ID: 0900
  Hub-4: 3-0:1 info: hi-speed hub with single TT ports: 2 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Hub-5: 3-2:2 info: Genesys Logic Hub ports: 4 rev: 2.1
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 power: 100mA
    chip-ID: 05e3:0610 class-ID: 0900
  Device-1: 3-2.1:3 info: Keychron Q0 type: keyboard,HID
    driver: hid-generic,usbhid interfaces: 3 rev: 2.0 speed: 12 Mb/s (1.4 MiB/s)
    lanes: 1 mode: 1.1 power: 500mA chip-ID: 3434:0130 class-ID: 0300
  Device-2: 3-2.2:4 info: C-Media USB Advanced Audio Device type: audio,HID
    driver: hid-generic,snd-usb-audio,usbhid interfaces: 4 rev: 1.1
    speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1 power: 100mA
    chip-ID: 0d8c:016c class-ID: 0300
  Device-3: 3-2.3:5 info: Logitech USB Receiver type: keyboard,mouse,HID
    driver: logitech-djreceiver,usbhid interfaces: 3 rev: 2.0
    speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1 power: 98mA
    chip-ID: 046d:c53f class-ID: 0300
  Device-4: 3-2.4:6 info: SHARKOON GmbH 87 TKL type: keyboard,HID
    driver: hid-generic,usbhid interfaces: 3 rev: 1.1 speed: 12 Mb/s (1.4 MiB/s)
    lanes: 1 mode: 1.1 power: 500mA chip-ID: 1ea7:7777 class-ID: 0300
    serial: <filter>
  Hub-6: 4-0:1 info: super-speed hub ports: 2 rev: 3.1
    speed: 10 Gb/s (1.16 GiB/s) lanes: 1 mode: 3.2 gen-2x1 chip-ID: 1d6b:0003
    class-ID: 0900
  Hub-7: 4-2:2 info: Genesys Logic Hub ports: 4 rev: 3.2
    speed: 5 Gb/s (596.0 MiB/s) lanes: 1 mode: 3.2 gen-1x1 chip-ID: 05e3:0626
    class-ID: 0900
Sensors:
  System Temperatures: cpu: 21.0 C mobo: N/A
  Fan Speeds (rpm): N/A
Repos:
  Packages: 1148 pm: pacman pkgs: 1133 libs: 329 tools: pamac pm: flatpak
    pkgs: 15
  Active pacman repo servers in: /etc/pacman.d/mirrorlist
    1: https://ct.mirror.garr.it/mirrors/manjaro/stable/$repo/$arch
    2: https://forksystems.mm.fcix.net/manjaro/stable/$repo/$arch
    3: http://mirror.is.co.za/mirrors/manjaro.org/stable/$repo/$arch
Processes:
  CPU top: 5 of 246
  1: cpu: 23.5% command: firefox pid: 1567 mem: 611.0 MiB (1.9%)
  2: cpu: 20.3% command: kwin_wayland pid: 1094 mem: 265.1 MiB (0.8%)
  3: cpu: 7.5% command: plasmashell pid: 1176 mem: 449.0 MiB (1.4%)
  4: cpu: 4.4% command: firefox pid: 2170 mem: 225.4 MiB (0.7%)
  5: cpu: 4.2% command: firefox pid: 1990 mem: 224.1 MiB (0.6%)
  Memory top: 5 of 246
  1: mem: 611.0 MiB (1.9%) command: firefox pid: 1567 cpu: 23.5%
  2: mem: 449.0 MiB (1.4%) command: plasmashell pid: 1176 cpu: 7.5%
  3: mem: 331.9 MiB (1.0%) command: manjaro-hello started-by: python3
    pid: 1110 cpu: 0.6%
  4: mem: 265.1 MiB (0.8%) command: kwin_wayland pid: 1094 cpu: 20.3%
  5: mem: 225.4 MiB (0.7%) command: firefox pid: 2170 cpu: 4.4%
Info:
  Processes: 246 Power: uptime: 6m states: freeze,mem,disk suspend: deep
    avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
    suspend, test_resume image: 12.46 GiB services: org_kde_powerdevil,
    power-profiles-daemon, upowerd Init: systemd v: 255 default: graphical
    tool: systemctl
  Compilers: clang: 16.0.6 gcc: 13.2.1 Shell: Sudo (sudo) v: 1.9.15p5
    default: Bash v: 5.2.26 running-in: konsole inxi: 3.3.33```

Welcome to Manjaro! :smiling_face_with_three_hearts:

  1. Please read the information behind this link. It will help you to post necessary information.
  1. Please press the three dots below your post and then press the :pencil2:
  • If you give us information about your system, we can see what we’re talking about and make better suggestions.
  • You can do this by using inxi in a terminal or in console.
sudo inxi --admin --verbosity=8 --filter --no-host --width --repos
  • Personally identifiable information such as serial numbers and MAC addresses are filtered out by this command
  • Presenting the information in this way allows everyone to be familiar with the format and quickly find the items they need without missing anything.
  1. Copy the output from inxi (including the command) and paste it into your post.
  • To make it more readable, add 3 backticks ``` on an extra line before and after the pasted text.

Have you already :mag: for your problem in the forum ? (Wisdom lies in asking → listening → reading :wink: )

Hello
Thanks sorry for the wrong initial post. I added the information

I actually now got one big step further following this webpage:

Now i have a working KDE with wayland. (need to verify full functionality but it looks good so far)

echo $XDG_SESSION_TYPE                                                                                       ✔ 
wayland

I falsely assumed that if i install the nvidia Driver and wayland from the beginning, that all relevant settings are done.

Now i only have a “lag” (curser stops) if i go in the taskbar about an active program. But not sure if that is a feature or a bug. Did not have this behavior under X

Thanks
regards

You’re making problems for yourself. KDE5 + Wayland + Nvidia is just about the worse possible combination you could choose. Apart from any Nvidia+Wayland issues there are also KDE5+Wayland issues (most of which are supposedly fixed in KDE6). It might work, it might not. There is a reason why X11 is the default for KDE5.

KDE6 is currently available on Manjaro testing and unstable branches.

I very much doubt that, especially on Nvidia. Benchmarks or it didn’t happen.

1 Like

Thanks for the info.

Yeah i learn that step by step that this is one of the worst potential setups right now.
I went back to X11 for the day and i encountered 1 bug after another. After hybernate the Screen was just full of a colorfull rectangles → reboot required. Random crashes.
And i literally did nothing special except Browing and checking some settings and trying to understand what flatpak is (that was not a thing in 2008)

I will reinstall the system to ensure that i did not fundamentaly destroyed something with my wayland adventure but right now i have to say: That setup is not stable