Repository navigation
Update cua-driver-bin to 0.33.4, which captures multi-monitor Hyprland desktops again - #807
Conversation
…d desktops again Driver 0.28.3 through 0.33.3 refused desktop capture on Hyprland with more than one output or one output away from the origin (trycua/cua#4161), which is why the package was held at 0.28.2; 0.33.4 fixes it (trycua/cua#4305). The plugin sources are unchanged from 0.32.0 through 0.33.4 and speak the same input protocol, so the plugin package stays and only its README names the new pairing.
|
Replayed this on an Omabot Edge worker running Hyprland 0.56.2-4 and cua-hyprland-plugin 0.32.0-3. I built this branch's package, served it as a local repository ahead of
Not covered yet: the same pairing on real hardware with two monitors, one of them away from 0,0. The rig for that is offline. Codex XHigh reviewed the PKGBUILD and README diff and found nothing blocking. CI's build jobs fail before they reach this package. The builder image fetches the repository key from 🤖 Generated by Opus 5.5 in Claude Code. Reviewed by Codex XHigh. |
|
CI builds it now that 🤖 Generated by Opus 5.5 in Claude Code. |
Publish succeeded → livePackages: cua-driver-bin (x86_64, PR artifact); cua-driver-bin (aarch64, PR artifact); cua-hyprland-plugin (x86_64, already published, skipped)
Some planned slots did not run because an earlier slot failed. |

cua-driver-binhas been held at 0.28.2 because Cua Driver 0.28.3 through 0.33.3 refuse desktop capture on Hyprland when more than one output is active, or when the only output is away from 0,0 (trycua/cua#4161). Driver 0.33.4 fixes that (trycua/cua#4305), so this moves the package to it. 0.33.4 also carries the native Hyprland foreground fixes released in 0.33.2 (trycua/cua#4396): page-scroll units, keyboard-first cursor placement, AT-SPI geometry on native Wayland and stale-zoom refusals.The plugin package does not change. Its sources are identical from Driver 0.32.0 through 0.33.4, both sides speak input protocol v3, and the
cua-hyprland-plugin 0.32.0-3already on edge is built from those sources; its README now names this pairing instead of explaining the hold. Cua's own Edge kit for this source records the same compositor and header hashes as #772's profile.The recipe changes only the version and the release's checksums. The vendor installer URL still appears four times in the binary on both architectures and is rewritten to
pm.shas before, and the release'sTHIRD_PARTY_NOTICES.mdis now installed beside the license. Upstream updates stay held ("sync": false), so the driver still moves only through a reviewed bump like this one.