Skip to content

ConsoleRDP 1.0.5

Latest

Choose a tag to compare

@billsecond billsecond released this 04 May 19:41

ConsoleRDP 1.0.5 — defensive .deb install + comprehensive verification

If a fresh Kubuntu 26.04 happens to have a stock krdp or kpipewire* package whose version number is higher than our patched ones, apt-get install on our local .debs would silently keep the stock package, the patches wouldn't apply, and the install would appear successful while mstsc still failed at NLA. This release closes that hole.

Changes

Defensive .deb install. install.sh now uses --allow-downgrades --reinstall -o Dpkg::Options::=--force-overwrite when installing the bundled .debs. apt is forced to replace whatever's on disk with our patched version regardless of version comparison.

Per-package version verification. After the .deb install, install.sh confirms each of the 7 bundled packages is at a version containing +consolerdp (or is the consolerdp orchestrator itself). Hard-fails with the exact wrong package name if not.

Comprehensive final-summary check. Step 6/6 is now per-component:

  • kcm_krdpserver.so present? (System Settings → Remote Desktop)
  • /usr/bin/krdpserver carries the consolerdp build marker?
  • consolerdp.service active?
  • krdpserverrc + TLS cert provisioned for the seat user?
  • tcp/3389 listening?
  • ufw allows 3389/tcp (if active)?

Each gets a separate ✓ / ! line. You can see at a glance what worked and what didn't on the last screenful of install output, instead of having to dig through consolerdp-doctor afterward.

consolerdp-configure step 7/8 race fix. Now waits up to 5s for /run/user/$UID/bus after loginctl enable-linger (was racing systemd before), prefers systemctl --user --machine="$user@.host" (systemd 248+) over sudo+env-vars, and verifies the unit actually came up.

Upgrade

Same recipe — re-run the bootstrap on top of any 1.0.x install:

curl -fsSL https://github.com/billsecond/consolerdp/releases/latest/download/install-remote.sh -o /tmp/install-remote.sh
sudo bash /tmp/install-remote.sh

After install

Watch the last screenful. If you see a row of ✓ lines and no ! warnings, you're done — open mstsc with your Linux user/password and connect. If you see any ! lines, paste them and I'll debug from there.