Everything you know. Linux underneath.
Trier Bridge is a Windows-to-Linux experience layer for Ubuntu Desktop: the places, names, and tools a Windows user already knows, opened onto the real Linux underneath — without a terminal, and without pretending Linux is Windows.
Install • Screenshots • What's inside • Bridge Terminal • How it is built • Security • Docs • Support
If Trier Bridge makes your move to Linux easier, a star on the repository helps others find it.
One Debian package for Ubuntu 24.04 Desktop: trier-bridge_1.0.0_all.deb (about 140 KB). Its runtime dependencies are Python 3, PyGObject, GTK 4, and libadwaita; it also recommends the Ubuntu packages for printer and Files integration. The installer resolves any missing dependencies. Get it from the Releases page.
Without a terminal. Right-click the .deb in Files → Open With → App Center, tick Always use for this file type, then press Install. From then on a double-click installs. (On a stock Ubuntu 24.04 the archive viewer is the default for .deb files, so the first time needs that one choice. Once Trier Bridge is installed, Apps → Default apps → Software installers (.deb) offers the same choice inside the app.)
With a terminal, if you prefer:
sudo apt install ./trier-bridge_1.0.0_all.debTrier Bridge keeps its preferences and operation records in your user configuration and state folders (normally ~/.config/trier-bridge and ~/.local/state/trier-bridge); removing the package leaves those behind, the way a Windows uninstall leaves AppData. File operations affect the files you select, and service or network changes go through the corresponding Linux service. Trier Bridge never installs or removes other software and runs as your signed-in user. Linux decides whether an authorized system change requires a password prompt.
Task Manager → Performance — live graphs for CPU, memory, every disk and every adapter, laid out the way Windows lays them out
| Home | Files |
|---|---|
 |
 |
| Apps | Settings |
|---|---|
 |
 |
| Task Manager — processes | Event Viewer |
|---|---|
 |
 |
| Services | Command Prompt |
|---|---|
 |
 |
Every image above is rendered from the installed 1.0.0 package on an Ubuntu 24.04 desktop, at 1280×800. Full set:
docs/screenshots/.
Everyday
- Home — type what you would look for on Windows (Task Manager, Add or Remove Programs, Control Panel, Downloads) and go straight to the Linux place for it.
- Files — your folders and drives in an in-app browser, with the drive letters you know (
C:,D:) shown as labels next to the real Linux paths. - Apps — every installed program in one list, with where each one came from, plus a Default apps chooser.
- Settings — the familiar names, routed to the matching panel in Linux Settings.
- Printers and Network — printers and scanners; adapters, addresses, and connection changes translated to NetworkManager.
Troubleshooting
- Task Manager — End task for your own programs, and a Performance tab with live graphs for CPU, memory, every disk, and every adapter. System-critical processes are marked and protected.
- Event Viewer, Device Manager, Startup Apps, Disk Management — the tools by the names you know, over the real Linux sources (the journal, sysfs/udev, autostart entries, udisks).
Advanced
- Services — running state and start-at-boot, with Linux controlling permission for system services.
- Command Prompt — Windows commands and PowerShell names, each turned into a typed operation; nothing you type is ever passed to a shell.
- System Information — this computer's hardware and software, and what Trier Bridge can and cannot do here.
Integrations you choose at setup, each reversible — a tray icon, desktop search that understands Windows words, familiar launchers in the app grid, a Files context-menu entry, Ctrl+Shift+Esc.
The shell — a branded sidebar with an adjustable accent color, a zoom control, and a keyboard-navigable layout that follows the desktop theme.
A Windows user types what they know:
C:\Users\You> ipconfig
Nothing is substituted into Bash. Every line goes through a strict parser into a typed Trier Bridge operation, which is validated against the machine's real capabilities and the security rules, carried out by a Linux-native adapter with a fixed argument list, verified, and reported back in familiar form:
Windows-style input
↓
strict parser
↓
typed Trier Bridge operation
↓
capability + security validation
↓
Linux-native adapter
↓
verified result
↓
familiar output
If no safe, faithful Linux equivalent exists, Trier Bridge says so and performs no hidden substitution.
- Typed operations, never shell text. A command becomes a parsed, typed operation with a fixed argument list. Not one line of Trier Bridge hands text to a shell, and the project's own gate refuses any change that tries.
- Linux stays in charge. Trier Bridge runs as your signed-in user. System service and network changes go through Linux's authorization checks; Linux decides when to prompt. Task Manager can end your own eligible programs and protects system and session-critical processes.
- Honest about what it knows. A value it cannot read shows as Unknown, never as zero. An action interrupted mid-way is shown to you afterward, never silently repeated. Where Windows and Linux differ, it says so instead of inventing a match.
- Evidence from a real desktop. Recorded checks include unit and integration tests on the project's Ubuntu 24.04 desktop VM, reproducible package builds, and lintian checks. The 258 invariants in
docs/INVARIANTS.mddefine the requirements.docs/VALIDATION.mdrecords the exact candidates and environments checked, including limitations and checks not run. The measured code-quality score is inCODE-QUALITY-REPORT.md.
Guiding order, always: everyday continuity → familiar troubleshooting → advanced Windows continuity → optional Linux learning. Learning Linux is optional. Productivity is not.
GitHub checks code, a non-destructive unit subset, reproducible Debian builds, and commit history for secrets on every push to main and pull request targeting it. The badge above reports the actual workflow result. Desktop and system-change testing remain separate; see docs/CI.md for coverage and limits.
- No privileged helper or privilege cache in Trier Bridge: system-scope changes use Linux authorization. Polkit may retain a grant according to the system's policy; Trier Bridge does not control that cache.
- Explicit trust boundaries; untrusted input (typed commands, IPC, files) is validated on the trusted side; malformed input performs no operation.
- Fixed executable argument arrays everywhere — no shell interpolation, no dynamic command construction.
- Secrets never enter UI state; records are kept without them.
- Full design:
docs/SECURITY.md. Please report security issues privately rather than in public issues.
- Builds for Linux Mint and Zorin.
- A package repository, so updates arrive the normal Ubuntu way.
- More of the Windows vocabulary in Home search.
Start with docs/README.md, then:
docs/PRODUCT-CONCEPT.md·docs/PRODUCT-NORTH-STAR.md·docs/EXPERIENCE.mddocs/ENGINEERING.md·docs/SECURITY.md·docs/INVARIANTS.md·docs/DECISIONS.mddocs/PLATFORMS.md·docs/PACKAGING.md·docs/VALIDATION.md·docs/CODE-QUALITY.md
Repository-root control documents: CONTRIBUTING.md · AGENTS.md · CONTEXT.md · Engine Spec Tasklist 01.MD · CODE-QUALITY-REPORT.md · LICENSE · NOTICE
Trier Bridge is free and open source. If it makes your move to Linux easier, you can support its continued development through the Sponsor button at the top of the repository, or directly:
Apache License 2.0 — see LICENSE and NOTICE. Copyright 2026 Doug Trier.