Xwayland not working for some reason

Community
,
1

Hi guys,

I’m on Fedora 44/KDE and usually update daily, but restart each two weeks or something like that - when it is mandatory.

So, a month+ ago or so, xwayland stopped working for me resulting in jetbrains toolbox, discord and android studio emulators not starting (perhaps others). After few more updates it started working again and now it does not work, again. So I’m stuck without X11 bridge.

Some logs I’ve seen - excerpt from journald

abrt-notification[6907]: [🡕] Process 4745 (gmenudbusmenuproxy) crashed in qt_assert(char const*, char const*, int)()
abrt-applet[5164]: g_app_info_should_show: assertion 'G_IS_APP_INFO (appinfo)' failed
abrt-server[5046]: Deleting problem directory ccpp-2026-08-24-16:57:18.378033-4968 (dup of ccpp-2026-08-17-08:26:18.985281-4745)

and crash report

ksmserver killed by SIGABRT
...
User Logs:
ksmserver[4578]: could not connect to display
ksmserver[4578]: From 6.5.0, xcb-cursor0 or libxcb-cursor0 is needed to load the Qt xcb platform plugin.
ksmserver[4578]: Could not load the Qt platform plugin "xcb" in "" even though it was found.

any idea how to fix it or investigate?
ksmserver[4578]: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vkkhrdisplay, vnc, wayland-brcm, wayland-egl, wayland, xcb.

Can anybody suggest a solution or at least how to collect more info and troubleshoot it?

2

Is the Xwayland process running?

Does a simple x11 app like xterm work for you?

3

Process not running. And I suppose no X11 app would run.

4

When you first login it should be running can you confirm this?

Can you install inxi and post the output of inxi -ezxx please?

5

Thanks, will do tomorrow late evening.

6

Here, relevant parts (omitted Audio, Network, Bluetooth and Drives/Partition)

System:
  Kernel: 7.1.10-200.fc44.x86_64 arch: x86_64 bits: 64 compiler: gcc v: 16.2.1
  Desktop: KDE Plasma v: 6.7.4 tk: Qt v: N/A wm: kwin_wayland dm: N/A
    Distro: Fedora Linux 44 (KDE Plasma Desktop Edition)
Machine:
  Type: Desktop System: ASRock product: X870 Riptide WiFi v: N/A
    serial: <superuser required>
  Mobo: ASRock model: X870 Riptide WiFi serial: <superuser required>
    Firmware: UEFI vendor: American Megatrends LLC. v: 3.30 date: 06/16/2025
Battery:
  Device-1: hidpp_battery_0 model: Logitech Wireless Mouse MX Master 3
    serial: <filter> charge: 100% (should be ignored) status: discharging
CPU:
  Info: 12-core model: AMD Ryzen 9 9900X bits: 64 type: MT MCP arch: Zen 5
    rev: 0 cache: L1: 960 KiB L2: 12 MiB L3: 64 MiB
  Speed (MHz): avg: 5337 min/max: 614/5662 boost: enabled cores: 1: 5337
    2: 5337 3: 5337 4: 5337 5: 5337 6: 5337 7: 5337 8: 5337 9: 5337 10: 5337
    11: 5337 12: 5337 13: 5337 14: 5337 15: 5337 16: 5337 17: 5337 18: 5337
    19: 5337 20: 5337 21: 5337 22: 5337 23: 5337 24: 5337 bogomips: 210790
  Flags-basic: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a
    ssse3 svm
Graphics:
  Device-1: Advanced Micro Devices [AMD/ATI] Granite Ridge [Radeon Graphics]
    vendor: ASRock driver: amdgpu v: kernel arch: RDNA-2 pcie: speed: 16 GT/s
    lanes: 16 ports: active: DP-1,DP-2,HDMI-A-1 empty: DP-3,Writeback-1
    bus-ID: 70:00.0 chip-ID: 1002:13c0 temp: 49.0 C
  Device-2: Logitech HD Pro Webcam C920 driver: snd-usb-audio,uvcvideo
    type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 bus-ID: 1-7:8 chip-ID: 046d:082d
  Display: wayland server: Xwayland v: 24.1.13 compositor: kwin_wayland
    driver: gpu: amdgpu d-rect: 11520x4320 display-ID: 0
  Monitor-1: DP-1 pos: bottom-c model: LG (GoldStar) HDR 4K res: 3840x2160
    hz: 60 dpi: 163 diag: 690mm (27.2")
  Monitor-2: DP-2 pos: top-right model: LG (GoldStar) HDR 4K res: 3840x2160
    hz: 60 dpi: 163 diag: 690mm (27.2")
  Monitor-3: HDMI-A-1 pos: bottom-l model: LG (GoldStar) HDR 4K
    res: 3840x2160 hz: 60 dpi: 163 diag: 690mm (27.2")
  API: EGL v: 1.5 platforms: device: 0 drv: radeonsi device: 1 drv: swrast
    gbm: drv: radeonsi surfaceless: drv: radeonsi wayland: drv: radeonsi
    inactive: x11
  API: OpenGL v: 4.6 vendor: mesa v: 26.1.8 note: incomplete (EGL sourced)
    renderer: AMD Ryzen 9 9900X 12-Core Processor (radeonsi raphael_mendocino
    ACO DRM 3.64 7.1.10-200.fc44.x86_64), llvmpipe (LLVM 22.1.8 256 bits)
  API: Vulkan v: 1.4.341 surfaces: N/A device: 0 type: integrated-gpu
    driver: mesa radv device-ID: 1002:13c0 device: 1 type: cpu
    driver: mesa llvmpipe device-ID: 10005:0000
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
    de: kscreen-console,kscreen-doctor gpu: amdgpu_top,radeontop
    wl: wayland-info x11: xdriinfo, xdpyinfo, xprop, xrandr
Info:
  Memory: total: 120 GiB note: est. available: 117.49 GiB
    used: 67.8 GiB (57.7%)
  Processes: 895 Power: uptime: 4d 18h 14m wakeups: 6 Init: systemd v: 259
    default: graphical
  Packages: pm: rpm pkgs: N/A note: see --rpm pm: flatpak pkgs: 47
    Compilers: clang: 22.1.8 gcc: 16.2.1 Shell: fish v: 4.6.0
    running-in: konsole inxi: 3.3.41
7

After today’s Fedora update and restart, it started working again. Go figure. The inxi report above is from when it wasn’t working.

Any idea what can I look into when/if stops working again?

8

Look in the user and system journals for errors. Also the Xorg log may have clues.

Then reproduce the problem step by step.

  1. Login - check Xwayland is running
  2. Start one app - does that crash Xwayland?
  3. Start the next app - does that crash Xwayland

FYI Fedora support is over on https://discussion.fedoraproject.org/ but a number of us Fedora KDE users hang on both sites.

1 Like