mirror of
https://github.com/debauchee/barrier.git
synced 2026-10-23 08:07:53 -06:00
[GH-ISSUE #2146] Restore Barrier 2.4.0 interoperability for 3.3.0 #1855
Labels
No labels
HiDPI
bounty
bsd/freebsd
bsd/openbsd
bug
bug
build-infra
cantfix
critical
doc
duplicate
enhancement
fix-available
from git
from release
good first issue
help wanted
installer/package
invalid
linux
macOS
meta
needs testing
pull-request
query
question
regression
regression
v2.4.0
windows
wontfix
work-in-progress
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
github-starred/barrier#1855
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @ivypi-cc on GitHub (Aug 29, 2026).
Original GitHub issue: https://github.com/debauchee/barrier/issues/2146
Goal: release Barrier 3.3.0 with the current 3.2.0 feature set while restoring interoperability with widely deployed Barrier 2.4.0 peers.\n\nAcceptance:\n- A 3.x client connecting to a 2.4.0 server negotiates protocol 1.6 behavior and does not send 3.x-only wire messages.\n- A 2.4.0 client connecting to a 3.x server remains supported without requiring display geometry/name messages.\n- Mixed client layouts are supported on a 3.x server: peers with 3.x display geometry use physical display rectangles; peers without geometry use a synthetic single rectangle from DINF.\n- 3.x-to-3.x enhanced display routing remains available.\n- Version and release notes are updated for 3.3.0 without environment-specific deployment details.
@ivypi-cc commented on GitHub (Aug 29, 2026):
Opened on the upstream repository by mistake; this work is being tracked in the maintained fork.