Wayland completely ignores .XCompose (and by the looks of it, .Xmodmap too)

[licehunter]

As per the title. I got mislead by the default choice in this Tumbleweed installation and entered a Wayland () session. I was then wondering why on Earth my key mappings were not working.

When I eventually noticed had to log out and restart a session with a real windowing system, aka X11, causing me no small degree of annoyance.

The compose key is one of those things that make Unix systems so incredibly good, productive and pleasant to use.

[hui]

Wayland

[yvs]

I believe it still works unless it’s a pure wayland environment.
Testing it out on Tumbleweed VM by relogin from Plasma(X11) to Plasma(wayland) got env:

  Display: wayland server: X.org v: 1.21.1.12 with: Xwayland v: 24.1.1
    compositor: kwin_wayland driver: X: loaded: modesetting
    unloaded: fbdev,vesa dri: virtio_gpu gpu: virtio-pci
    resolution: 1280x800
  API: EGL v: 1.4,1.5 drivers: swrast,virtio_gpu
    platforms: wayland,x11,surfaceless,device
  API: OpenGL v: 4.5 compat-v: 4.3 vendor: mesa v: 24.1.3 renderer: virgl
    (AMD Radeon Graphics (radeonsi renoir LLVM 17.0.6 ...)
  API: Vulkan Message: No Vulkan data available.

% echo $XDG_SESSION_TYPE $WAYLAND_DISPLAY
wayland wayland-0

and it works at least in Konsole (with user .Xcompose that ‘include “%L” + custom settings’)

p.s. but in general, yeah, all new shiny things (like wayland or vulkan) are supposed to be some kinda tradeoffs for sufficient time. In this case it’s trade-off between functionality and performance. Well-known common things are good enough to not rush with new ones, and so that there’s time to wait until volunteers polish all those rough edges.