OPINIONATED OMARCHY
TROUBLESHOOTING CORPUS
790
RECORDS
790
AUDITED
0
UNCHECKED
2388
SOURCES
LIVE
wayland-compat medium common DISPUTE

Fix Chromium freezing when you paste from an XWayland app

omarchyarchhyprlandwaylandxwaylandelectron
CORRECTED An auditor found the fix wrong or incomplete and rewrote it.
AUDIT NOTE

The problem is real and honestly framed: omarchy#2903 exists ('Chromium Freezes When Pasting Clipboard Data From Windows', still open), and the record correctly says no root-cause fix exists rather than inventing one. The mitigations (Ctrl+Shift+V, laundering through wl-clipboard, wl-clip-persist taking ownership) are all sound. The defect is the 0.55+ bind: hl.bind("SUPER SHIFT + V", ...) does not match the documented modifier syntax, which joins every modifier with + (the wiki's examples are "SUPER + SHIFT + Q", "SUPER + XF86AudioNext"), so the bind fails to parse and the user silently gets no key. The recovery command is also oversold: pkill on all renderer processes drops every tab's renderer, not just the hung one.

The cause above was not rewritten and may still contain the error described. The fix below is the corrected version.

Symptom

Copy something in one app, click into Chromium (or Obsidian, or another Electron app) and press Ctrl+V. The app freezes and shows "Application Not Responding". Most often reported copying out of a Windows VM / Docker Windows container, or out of an XWayland app into a native Wayland app. Recovery requires killing the app.

Cause

Under investigation upstream. The clipboard transfer between an XWayland source and a Wayland consumer stalls: Chromium blocks its UI thread waiting for a data-offer read that never completes, typically with rich-text/HTML mime types. Multiple Omarchy users confirm it is specific to XWayland-source -> Wayland-target transfers.

Fix

No root-cause fix exists yet. Practical mitigations:

Paste as plain text, which avoids the rich-text mime negotiation that appears to trigger it:


Ctrl+Shift+V

Or launder the clipboard through wl-clipboard so a local, well-behaved client owns it before you paste:


wl-paste --no-newline | wl-copy

Bind that to a key.

Hyprland <=0.54 / Omarchy 3.x:


bind = SUPER SHIFT, V, exec, wl-paste --no-newline | wl-copy --type text/plain

Hyprland 0.55+ / Omarchy 4.x: every modifier is joined with + . "SUPER SHIFT + V" will not parse:


hl.bind("SUPER + SHIFT + V", hl.dsp.exec_cmd("wl-paste --no-newline | wl-copy --type text/plain"))

(Use hl.dsp.exec_cmd rather than a plain Lua function here. The wiki warns that clipboard tools called inline from a bind callback block the compositor event loop and can freeze the whole desktop.)

Running wl-clip-persist --clipboard regular also helps, because the persist daemon becomes the clipboard owner instead of the dying/remote X client:


sudo pacman -S --needed wl-clip-persist

When it does hang, kill only that browser. Note this drops every tab's renderer in that instance, not just the stuck one, so prefer the plain kill and let Chromium restore:


pkill chromium

Verify

Copy rich text out of the VM/XWayland app and paste with Ctrl+Shift+V. The target app stays responsive.

Sources

chromium-hangs-pasting-from-xwayland-app