English · العربية · Español · Français · 日本語 · 한국어 · Tiếng Việt · 中文 (简体) · 中文（繁體） · Deutsch · Русский

UU Remote Ubuntu Bridge

Use NetEase UU Remote to view and fully control the Ubuntu GNOME desktop.

_{An Ubuntu GNOME desktop accessed from macOS through UU Remote Ubuntu Bridge.}

An experimental compatibility bridge that runs the official Windows UU client in an isolated Wine prefix, presents the real GNOME desktop through a local RDP relay (or the optional local VNC relay on X11), with mouse, keyboard, semantic phone text and clipboard integration.

What works

Reviewed 2026-10-04. Everyday desktop control, text clipboard and dictation are working on tested or user-confirmed paths. Working describes those paths, not every device, keyboard layout or native Windows UU feature.

Feature	Status	Scope / limits
Existing Ubuntu desktop	Working	Video and reconnect preserve the selected session and open apps.
Mouse	Working	Movement, clicks, buttons, wheel and focus on tested relays.
Physical keyboard / shortcuts	Working; client-dependent	Letters, modifiers and symbols; no universal US/JIS/Mac layout guarantee.
Phone keyboard / Unicode	Working on tested paths	Chinese, punctuation, emoji and multiline text; individual IMEs still need checking.
Continuous dictation	Working in reported use; regression-tested	Composition revisions preserve earlier messages; real-phone coverage varies by release.
Text clipboard, both directions	Working; route-dependent	Text only. X11/VNC return is opt-in, up to 60 KiB; images/files are not covered.
Same UU / RDP / RealVNC desktop	Optional setup	Shared physical X11 backend; separate default sessions are not automatically unified.
Resolution / canvas fitting	Configurable	Fixed size or optional stable X11/VNC size following; not extra virtual displays.
Recovery / boot startup	Conditional	Supervised restart and login retention; usable GNOME login/keyring required. No new reboot test in 4.42 acceptance.
Native UU Terminal → Ubuntu shell	Adapter works; channel conditional	UTF-8 and PTY resize; vendor version/connection failures and native exit-status limitation remain.
uu-shell	Verified with enrolled SSH	Explicit LazyTunnel, mapped SSH or native selection; SSH tests do not prove native UU works.
UU port mapping / SSH / SCP	Conditional	Verified routes exist; takeover or closing the carrier can break them. Not a VPN.
Super Screen / extra virtual displays	Unverified	No accepted Ubuntu-bridge test; ordinary desktop resizing is not proof.
Anti-peep / privacy screen	Unverified	No validated Linux physical-screen blanking/input-lock backend. Do not rely on it for privacy.
Audio / microphone	Limited	Host-dependent; some installations intentionally use silent audio.
Native file transfer, image/file clipboard, other extras	Unverified	Text copy is not file transfer; SCP/SFTP over verified SSH is a separate option.

See feature evidence and limitations, including the separate RDP and X11 acceptance records. The 4.42 Mac-controller run did not validate real-phone continuous dictation. The shared-desktop XRDP 0.9.24 clipboard also has a documented non-BMP emoji limitation.

For an already configured peer named lab:

uu-shell --list
uu-shell lab
uu-shell --lazy lab hostname
uu-shell --native lab

Replace lab with your peer. --lazy requires LazyTunnel enrollment; --native requests UU's own terminal and can fail independently. There is no silent fallback or desktop takeover. See fleet shell details.

This is not a native UU Linux port and is not affiliated with NetEase. The default fresh-install manifest is intentionally locked to UU Remote 4.42.1.2835. A plain reinstall preserves the installed manifest; other releases require an explicit exact-hash manifest.

The 4.42.1.2835 workstation upgrade passed physical-desktop video, mouse, English typing, bidirectional Chinese text clipboard, reconnect, service restart, login preservation, and the 270-second stability gate. The prior working runtime remains tagged and backed up. See that record for test limits and rollback details; this is not a claim that every controller or hardware configuration was tested.

Download UU only from NetEase's official uuyc.163.com domain. Its current product page does not list a Linux host; this bridge uses the official Windows client and verifies the complete installer hash. Do not install an unverified .deb, .rpm, or AppImage from a look-alike download site.

The supported host is x86-64 Ubuntu 24.04 with a logged-in GNOME 46 desktop (physical, Wayland, Xorg, or XRDP). The installer checks this boundary and fails before making partial changes on an unsupported OS or architecture. Use ./install.sh --check-host for a read-only OS/CPU check. ARM64 Oracle VPS hosts are not supported; see host compatibility.

Using—or needing—another Ubuntu release, desktop/session, CPU architecture, UU version, or controller platform? Share one compatibility report or request. Filing is free and public and does not promise support. Do not attach or link proprietary binaries, credentials, account or device IDs, raw logs, screenshots, or private configuration.

If you need a vendor-independent route instead, LazyRemote uses the separate open-source LazyTunnel core for self-hosted SSH, terminal, and noVNC access. It is a different tool; this repository remains the compatibility path for the official UU client.

Already have one reachable relay and up to three computers, but want the exposure and key roles checked before changing anything? Read the complete sample first. The optional USD 250 review starts with a free metadata-only fit check and excludes deployment, hardware, and ongoing support.

Releases and behavior tracks

Tag	Purpose	Default input behavior
v0.1.0	Immutable known-good baseline from the original working host	Original unpaced phone text and physical-key path
v0.2.0	Union release with the baseline fallback plus optional host-specific extensions	New installs pace phone text by 8 ms; physical pacing is off, the compatible RDP keyboard route remains selected, and all network adapters remain visible

The v0.1.0 tag is never moved or rewritten. Upgrading an existing v0.1.0 installation preserves its missing text-delay field as 0, so merely installing v0.2.0 does not change the timing of that known-good host. A new installation starts at 8 ms. In both cases, an explicit saved or command-line setting takes precedence.

Use descriptive parallel tags when recording the input path validated on a specific machine:

Behavior tag	Use when
track-rdp-broker-20260724	The compatible Wine broker and RDP keyboard route are already smooth
track-direct-x11-20260724	An X11/XRDP host needs the authenticated direct keyboard route

These aliases do not rank one path above the other and the updater never switches between them automatically. Read the behavior-track handoff.

Quick start

Run from the logged-in Ubuntu GNOME desktop session:

./install.sh

Fresh installs use the accepted 4.42.1.2835 manifest; ordinary reinstalls preserve the installed release. The pinned FreeRDP nightly currently returns 404, so a fresh default RDP install needs an existing exact-hash client. For an X11/XRDP desktop, ./install.sh --desktop-relay vnc avoids that dependency. See download recovery and duplicate-launcher cleanup.

The one installer:

1. installs Ubuntu, WineHQ, build, X11, RDP, and keyring dependencies
2. downloads and verifies the approved UU installer when needed
3. builds all original compatibility DLLs and helpers
4. builds the pinned Windows WinPR runtime used by SDL FreeRDP
5. backs up and applies only approved binary signatures
6. configures GNOME Remote Desktop with a pinned TLS certificate
7. stores the relay password in GNOME Keyring, never in a script
8. installs and starts the supervised user service
9. runs immediate end-to-end verification

The first run prompts for a local relay password without echo and opens the official UU window on the logged-in desktop before starting the private relay. Complete account sign-in and close that window. Re-running the same command is idempotent; unchanged FreeRDP build outputs are checksum-verified and reused.

Port, resolution, optional stable desktop-resolution following, private-display, shared-desktop target, phone-text pacing, optional physical-key pacing, physical-key route, and an optional UU-only network-interface choice are persistent and can be set without editing the service:

./install.sh --rdp-port 3391 --resolution 2560x1440 --display auto \
  --follow-desktop-resolution off \
  --desktop-target auto \
  --desktop-relay rdp \
  --text-key-delay-ms 8 --physical-key-delay-ms 0 \
  --keyboard-route rdp \
  --network-interface all

They are validated and stored in ~/.config/uu-remote-bridge/environment. auto safely chooses the first free private X display from :20 through :99, avoiding existing VNC/Xvfb sessions. A later plain ./install.sh preserves these choices. Requested ports and fixed displays are checked before use. A conflicting non-GNOME listener fails closed, and an installer error restarts a bridge that was active before the attempted upgrade.

--desktop-target auto preserves normal discovery. On a workstation whose real working desktop is an existing XRDP session, use --desktop-target xrdp; the bridge follows the active xrdp-sesman session even if its X display number changes after reboot. physical selects the seat-attached GDM desktop, while :N selects one exact X display. An explicit target waits when unavailable and never falls back to a different desktop, so UU cannot silently open an empty physical desktop while XRDP windows remain elsewhere.

The private canvas normally uses the proven nested GNOME RDP path. If an X11/XRDP host is registered and accepts a controller but the canvas remains uniform black or white, select the loopback-only VNC fallback:

./install.sh --skip-packages --skip-account-login \
  --desktop-target xrdp --desktop-relay vnc \
  --vnc-grab-keyboard on

This does not expose VNC to the LAN: x11vnc binds IPv4 loopback only, and a native full-screen viewer runs on UU's private X display. Mouse events cross that local viewer, while the existing direct-X11 keyboard option remains available. The compatibility default stays rdp, so upgrades never switch a working host automatically. The VNC fallback requires an X11 target and fails closed instead of creating a different desktop for Wayland. The dedicated viewer grabs the keyboard by default so nested Shift/Ctrl state reaches the target, while x11vnc performs layout-aware keysym handling. This does not change the target desktop's XKB layout. See Adaptive keyboard relays for the exact symbol/CJK acceptance test and the opt-out for a non-dedicated viewer.

Windows RDP clients can resize an existing XRDP desktop after UU has already started. On a host that deliberately shares that same X11 desktop through the VNC fallback, opt into stable size following:

./install.sh --skip-packages --skip-account-login \
  --follow-desktop-resolution on

At startup the private UU canvas follows the selected desktop immediately. Later changes must remain unchanged across three five-second observations, after a one-minute startup grace period, before the bridge saves the new size and restarts only itself. XRDP, GNOME, applications, and the controller's keyboard layout are not changed. Sizes below 1024x720 are ignored so a temporarily tiny RDP window cannot shrink the unattended canvas. Fixed mode remains the default for already-working hosts.

On a host where UU opens physical audio devices or stalls during Windows Core Audio discovery, do not force PULSE_SINK or PULSE_SOURCE to duplicated XRDP endpoint names. UURB_UU_AUDIO=off prevents UU from reaching PipeWire, but some controllers still require a valid playout/capture backend before ICE can start. For that case, use the documented dedicated-prefix ALSA null fallback. It satisfies UU's media negotiation without opening a physical speaker or microphone and does not alter Ubuntu, XRDP, browsers, or another Wine prefix. See Troubleshooting.

The process-local cursor guard is a host-specific extension and defaults to off. Enable it only when the controller loses the cursor, renders it too small, or the UU server reports an invalid cross-process cursor handle:

./install.sh --skip-packages --skip-account-login \
  --cursor-guard on --cursor-size auto

auto reads the physical desktop's Xcursor size before Wine starts. A fixed value such as --cursor-size 64 changes only the guard's fallback arrow; it does not change Wine DPI or desktop geometry. Disable the extension with --cursor-guard off if the host does not need it.

Local desktop app

Open UU Remote from GNOME's application list or the desktop shortcut, or run:

uu-remote open

This opens a native TigerVNC window containing only the installed Wine application. UU's client, host server, input broker, and Ubuntu-Desktop-Relay remain together on the private X display; a loopback-only, single-window VNC sidecar carries the management window to GNOME. It does not mirror the complete private desktop, so it cannot produce the recursive desktop view. It also avoids starting a second Wine prefix or splitting one Wine prefix across two X displays. Closing the window minimizes the UU client and restores relay focus automatically.

The localhost-only noVNC view remains available for bridge diagnostics:

uu-remote console

Its endpoint is http://127.0.0.1:6080/vnc.html?autoconnect=1&resize=scale&reconnect=1. Both noVNC and its VNC backend listen on loopback only, so the VNC side needs no separate password and is not reachable from the LAN. Override occupied local ports during installation with --console-web-port and --console-vnc-port.

For a Mac that must control the current physical Ubuntu desktop while this bridge owns GNOME's desktop-sharing RDP session, use the included scripts/macos-connect-7090.applescript launcher. Its default action opens an authenticated, loopback-only VNC view through passwordless SSH; it does not start a second RDP session or expose VNC to the LAN. See macOS current-desktop access.

On the compatible rdp route, the default 8 ms text-key delay prevents UU's phone keyboard from overwhelming the Wine-to-FreeRDP input boundary. An upgrade from v0.1.0 preserves that release's unpaced behavior as 0. The broker confirms that the relay window has focus before acknowledging an input request and sends translated text one character chord at a time. Values from 0 through 50 ms are accepted; change the delay only when a controlled test supports it. The opt-in x11 route bypasses this RDP pacing boundary after it has normalized the complete representable phone-text request.

Physical-key pacing defaults to 0, preserving the ordinary path on hosts that already work. If slow typing succeeds but fast physical-key input omits events, --physical-key-delay-ms 8 adds bounded back-pressure after each accepted broker segment. It never retries or synthesizes a key. See the validated recovery note before changing this host-specific setting.

If broker metadata shows accepted physical-key or normalized phone-text calls but the nested Wine/FreeRDP route still loses fast keys on an Xorg or XRDP desktop, the opt-in direct route removes only that final keyboard hop:

./install.sh --skip-packages --skip-account-login \
  --keyboard-route x11 --physical-key-delay-ms 0

Video and clipboard continue through the selected local desktop relay. Physical keys, layout-representable phone text, and mouse movement/buttons/ wheel go through an authenticated loopback helper and XTEST into the selected X11 desktop. With the default UURB_PHONE_TEXT_MODE=auto, representable text stays on that fast key route, while newline, tab, CJK, emoji, and other non-representable Unicode become a real clipboard paste. On the default RDP track, routine keys and mouse input stay on RDP; only semantic text uses a split helper that owns the physical Xwayland clipboard and sends the paste chord through UU's private FreeRDP window. The helper confirms that new xclip processes own both CLIPBOARD and PRIMARY before emitting the paste, so VTE and non-terminal applications consume the same text; a timeout fails closed without pasting stale clipboard data. This preserves multiline dictation instead of turning each newline into a prompt-submitting Enter key. The global keyboard default remains rdp; auto selects the direct route only for an X11 target. If preflight cannot verify the target display or helper before injection, the request safely uses the compatible RDP route. No event is replayed after an ambiguous partial injection. Extended navigation keys are resolved from keysyms on the active display rather than a fixed X11 keycode table, so the mapping follows the host layout.

The VNC desktop relay explicitly permits clipboard updates from UU's private desktop to Ubuntu while blocking the reverse target-to-private direction. SendPrimary=0 avoids stale selected text, and the receive-only server plus ServerCutText=0 prevent semantic target text from feeding back into the VNC viewer and being pasted again.

Some UU controllers publish received desktop text only to GameViewer's Win32 clipboard under Wine, without creating an X11 selection on the private display. A separate one-way companion accepts only new CF_UNICODETEXT changes whose clipboard owner remains exactly GameViewer.exe throughout the locked read. Existing clipboard content is baselined at companion startup and is not replayed. The companion sends the bounded UTF-8 value over an authenticated loopback socket to a native helper. The helper acknowledges only after foreground xclip children are confirmed as the new owners of both CLIPBOARD and PRIMARY on the selected physical X11/Xwayland desktop. It never reads the host clipboard or emits a paste key. Images, rich text, and files are deliberately ignored. Socket operations have bounded deadlines, and either helper exiting causes the service to clean up and restart. This preserves ServerCutText=0 and the receive-only VNC boundary while allowing controller-to-Ubuntu text paste. The companion also runs with the RDP relay when the selected desktop exposes an authorized X11 or Xwayland display; it is not limited to the VNC/X11 track. See semantic phone text and clipboard relay.

On the validated XRDP workstation, the first live direct-UU run produced 256 content-free sampled physical-key calls on route=x11; every sampled call returned its requested single event with error=0. The operator reported that typing became very smooth and that almost all prior omissions were resolved. This is strong practical acceptance, while deliberately not claiming that an upstream controller can never omit an event under every network condition. Post-v0.2.0 source also includes an isolated phone-text acceptance test. A fixed 26-letter Unicode batch crossed the Wine broker on route=x11-text and arrived as all 52 ordered X11 press/release transitions. Run it without touching the live desktop:

./scripts/test-rdp-semantic-text.sh
./scripts/test-x11-phone-text.sh
./scripts/test-x11-clipboard-text.sh
./scripts/test-controller-clipboard.sh

The companion mouse acceptance sends absolute movement and a complete click through the same broker. It verifies the exact X11 pointer position, ordered button transitions, route=x11-mouse, and error=0:

./scripts/test-x11-mouse.sh

After live deployment, the operator confirmed that normal phone-keyboard typing was fixed. The first 72 bounded phone-text calls all used route=x11-text, returned their complete requested counts with error=0, and completed in 0-2 ms. The logs contained no character values or typed content.

If individual keys lag or disappear while direct RDP remains responsive, check the transport before changing input code:

uu-remote network

The report shows only aggregate path, delay, P2P, and key-watchdog metadata. It never prints addresses, device IDs, account data, or typed text. It includes the completion time and labels reports older than five minutes as stale, so an old session is not mistaken for the current idle bridge. It also reports only whether controller and host relay geography matched, without printing either location. A forced relay near UU's key-watchdog threshold is an upstream network problem; host-side retries can duplicate keys that arrive late.

On a host with several active adapters, UU under Wine can choose the first enumerated adapter even when Ubuntu routes through a different, faster one. If uu-remote network and a direct-RDP comparison point to that condition, select Ubuntu's preferred default route at each bridge start:

./install.sh --skip-packages --skip-account-login \
  --network-interface default

This loads a fail-open adapter view only into UU's Wine service tree. It does not edit routes, NetworkManager, firewall rules, Docker, or system libraries. The repository and installer default remains all, preserving existing hosts. While default is active, the existing bridge supervisor checks the preferred interface every ten seconds. If it changes, the whole relay is rebuilt once on the new route; no additional watcher or service is installed. Use --network-interface all to remove the restriction.

Ubuntu 24.04's libei 1.2.1 leaks the received keyboard-keymap descriptor after duplicating it. The installer builds the exact upstream one-line fix from a hash-verified 1.2.1 archive and loads that library only into this bridge's GNOME RDP child. A raised child limit and persistent 4096-descriptor relay guard remain as defense in depth:

./install.sh --skip-packages --skip-account-login \
  --grd-fd-restart-threshold 4096

Set the threshold to 0 only when deliberately disabling that guard. The launcher also restores the 65536 soft limit itself because a runuser/PAM boundary in an optional system application-profile wrapper can replace the unit's inherited soft limit. Verification recognizes that wrapper and inspects the relay listener in its network namespace without exposing the port on the host.

Update an existing installation

Use the latest supported tag without deleting UU account state or changing the saved relay settings:

cd ~/Projects/uu-remote-ubuntu-bridge
git status --short
git fetch --tags origin
git switch --detach v0.2.0
./install.sh --skip-packages --skip-account-login
./scripts/verify.sh --quick

Stop if the status command reports local changes. Installation briefly restarts the relay. Read the v0.2.0 release notes, use the public GitHub release, and send the copy-ready operator handoff when updating another authorized machine.

For a maintained main checkout with automatic maintenance already configured, use the reusable guarded workflow:

uu-remote upgrade status
uu-remote upgrade check
uu-remote upgrade apply

An operator who deliberately accepts an immediate short UU disconnect can use uu-remote upgrade apply --now. That option bypasses only the activity-idle delay; binary acceptance, complete-prefix snapshot, login preservation, verification, and rollback remain mandatory. Read the reusable upgrade procedure.

Use an already downloaded installer or a future approved release manifest:

./install.sh \
  --uu-installer ~/Downloads/UU-Remote/uuyc_4.33.0.exe \
  --release-manifest patches/uu-remote-4.33.0.8907.json

Unattended reboot startup

To make UU available after reboot without first logging in locally or through RDP, enable the opt-in TPM-backed boot path:

./install.sh --unattended

For an existing installation, run ./scripts/configure-unattended.sh enable. This enables GDM automatic login, so anyone with physical access can use the desktop after boot. The keyring password remains encrypted against this machine's TPM and is never stored in a script or process argument.

Read setup, verification, password-change, and rollback details.

Daily update checks and repair resume

Opt into zero-downtime daily release checks, relay health monitoring, and a reboot-resumable Codex repair workspace:

./scripts/configure-updater.sh enable \
  --track track-rdp-broker-20260724 \
  --model codex-auto-review --reasoning-effort medium

Use track-direct-x11-20260724 only on a host already validated with the direct X11 route. Checks never restart a healthy relay. Unknown installers are downloaded and statically staged outside the Wine prefix; Codex can prepare a reviewable repair but cannot approve or deploy its own binary patch. Interrupted work persists its thread ID and resumes after reboot with bounded backoff. Before an automatic Codex run, the updater verifies that included usage is at most 20%. It fails closed when usage is unavailable and never considers or consumes purchased credits.

Read the complete automatic-maintenance and handoff procedure.

Architecture

Phone / Windows / macOS UU controller
                  |
                  | UU signaling, video, and input
                  v
       GameViewerServer.exe in Wine
             |                 |
       captures window    SendInput IAT hook
             |                 |
             v                 v
   Ubuntu-Desktop-Relay   bounded named-pipe broker
       SDL FreeRDP          |             |
             |              | RDP         | optional physical keys
             |              |             | + normalized phone text
             +--------------+             v
                    |             native X11/XTEST helper
             RDP on 127.0.0.1              |
                    |                      |
                    v                      |
         GNOME Remote Desktop              |
                    |                      |
                    +----------+-----------+
                               v
                    logged-in GNOME desktop
                     (Wayland or Xorg/XRDP)

UU sees one ordinary Windows desktop window. SDL FreeRDP relays that window to GNOME Remote Desktop, which owns supported GNOME capture and input. The launcher discovers the D-Bus of the selected live GNOME Shell, including XRDP sessions that use a private session bus, and keeps the RDP hop local to the host. Automatic selection remains the default; a persistent xrdp, physical, or exact-display target can prevent multi-session hosts from switching desktops after reboot. When Wine denies SendInput from UU's service token, so a bounded broker repeats the same input request from a normal user Wine process. On an explicitly selected X11 target, physical keys, normalized layout-representable phone text, and mouse input bypass the nested desktop-relay input conversion. Video, clipboard, and all other channels keep the selected local relay.

Read the complete architecture. The debugging journey records the failed hypotheses, decisive evidence, Unicode keyboard correction, deployment-drift check, descriptor protection, and unattended boot dependency chain.

Daily commands

uu-remote status
uu-remote restart
uu-remote stop        # quit completely: stops UU and frees its memory (until the next `uu-remote open`)
uu-remote autostart status  # use on or off to change start-at-login behavior
uu-remote logs
uu-remote login       # one-time sign-in or account recovery on this desktop
uu-remote repair-registry  # bounded repair for a “finding routes” cold-start stall
scripts/verify.sh --quick
scripts/verify.sh

Closing the UU Remote window only closes the viewer; UU keeps running in the background. uu-remote stop quits it completely and frees its memory, and uu-remote autostart on|off|status chooses whether it starts at login. Both are also in the launcher's right-click menu. A reinstall keeps an earlier uu-remote autostart off.

autostart status preserves systemctl's exit status (zero when enabled, nonzero when disabled or unavailable). Installation checks the old choice before stopping the bridge: a failed manager query or a masked/unrecognized unit aborts rather than silently enabling it. Runtime-only enablement remains runtime-only. See the contribution review for the launcher tests and the separate, unmerged popup-viewer proposal.

The full verifier waits 270 seconds and proves the same server PID crosses UU's former four-minute failure interval. It also confirms that the installed runtime was built from the current checkout, the current cold start completed device initialization and signaling, and GNOME RDP remains below its guarded descriptor threshold. The registry repair is idempotent and affects only the dedicated UU Wine prefix; see Troubleshooting.

Updating for a new UU release

Unknown binaries are never patched automatically. The maintenance toolkit turns an update into a reproducible review:

# Stage the installer without touching the live Wine prefix.
scripts/stage-uu-release.sh \
  --installer ~/Downloads/UU-Remote/uuyc_NEW.exe \
  --sandbox-install

# Produce PE maps, semantic landmarks, candidate signatures,
# targeted disassembly, and a deliberately non-runnable draft manifest.
scripts/audit-gameviewer.py inspect \
  --server build/upstream/NEW/GameViewerServer.exe \
  --healthd build/upstream/NEW/GameViewerHealthd.exe \
  --installer ~/Downloads/UU-Remote/uuyc_NEW.exe \
  --baseline patches/uu-remote-4.33.0.8907.json \
  --version NEW_VERSION

After manual semantic review, audit-gameviewer.py finalize derives the full patched hash and creates an approved manifest. The generic patch engine then handles patch, verify, and byte-identical restore without source changes.

Learn the complete upstream workflow.

Binary safety model

The patch engine verifies:

• approved manifest status
• complete original SHA-256 and file size
• one long original signature at every exact file offset
• equal-length, non-overlapping replacements
• complete patched SHA-256
• matching audited backup before restore

An update with one changed byte outside the approved result fails closed. A draft manifest cannot be used by the installer or patcher.

The bridge does not edit OS account databases, bypass a login, install a kernel input driver, expose X11 over TCP, or add a new remote-control protocol. The RDP hop targets loopback and pins GNOME's certificate fingerprint.

Review all trust boundaries and residual risk.

Repository map

Path	Purpose
patches/	Versioned approved UU identities and patch signatures
CHANGELOG.md	Tagged bridge release history and upgrade entry points
src/	Input hook, broker, injector, service helper, adapter filter, and SSPI shim
scripts/gameviewer_patchlib.py	Generic release-manifest engine
scripts/patch-gameviewer.py	Patch, verify, status, field, and restore CLI
scripts/stage-uu-release.sh	Private installer staging sandbox
scripts/audit-gameviewer.py	New-release evidence and approval workflow
scripts/uu_update_manager.py	Daily checks, health recovery, and resumable Codex repair state machine
scripts/configure-updater.sh	Install, select a behavior track, and remove maintenance timers
scripts/uu-remote-bridge	Supervised UU/Xvfb/FreeRDP orchestration
scripts/uu-remote-console	Single-window desktop launcher and explicit noVNC diagnostic console
scripts/macos-connect-7090.applescript	Mac launcher for current-desktop VNC over passwordless SSH
scripts/uu-agent	Runtime-discovered UU controller CLI and private-display diagnostics
scripts/upgrade-uu-remote.sh	Fast-forward, guarded product promotion, runtime refresh, verification, and rollback
scripts/uu_connection_status.py	Privacy-safe transport and key-watchdog diagnosis
scripts/configure-unattended.sh	TPM-backed GDM autologin setup and rollback
scripts/uu-keyring-unlock.py	Secret Service unlock before GNOME RDP
install.sh / uninstall.sh	Idempotent setup and reversible removal
tests/	Proprietary-binary-free manifest unit tests

No NetEase executable, FreeRDP artifact, Wine prefix, password, token, device ID, raw production log, screenshot, or private desktop content is committed.

Documentation

• Architecture
• Changelog
• v0.2.0 union release notes
• v0.1.0 release notes
• Update handoff for another operator
• Input behavior tracks
• Automatic checks and resumable repair
• Reusable login-preserving upgrade
• Automated repair agent handoff
• UU controller CLI and remote agent
• Native Ubuntu terminal
• SSH aliases and two-host port mapping
• Mobile-keyboard parity handoff
• Adaptive keyboard relays across UU, RDP, and VNC
• macOS current-desktop access
• XRDP client stall and UU keyboard recovery
• Unattended startup after reboot
• Methodology and tool inventory
• Reverse-engineering record with exact xxd and objdump evidence
• Maintaining the bridge across upstream updates
• Windows reference comparison
• Troubleshooting
• Security
• Contributing

Removal

Restore the audited upstream files and remove bridge components while keeping the dedicated UU account state:

./uninstall.sh --dry-run
./uninstall.sh

The dry run verifies both rollback backups without changing the service or any file. ./uninstall.sh --purge also deletes the dedicated Wine prefix, bridge credential, and GNOME RDP enablement.

Support

Support continued maintenance, upstream release audits, and reusable documentation through any of these channels:

Project

Created as part of The Art of Lazying: automate the tedious parts, preserve the reasoning, and make the result reusable.

Original source is MIT licensed. UU Remote, Wine, FreeRDP, GNOME, OpenSSL, and other third-party components retain their own licenses and trademarks.