Skip to content

Installation

Jump to bottom
dnaidoo621 edited this page Jun 15, 2026 · 2 revisions

Installation

All packages are on the Releases page. Pick the right one for your OS.

OS Package How
Debian / Ubuntu / Pop!_OS .deb sudo apt install ./htpc-remote_*.deb
Fedora / RHEL / AlmaLinux .rpm sudo dnf install ./htpc-remote-*.rpm
Arch / openSUSE / other Linux .tar.gz Run install.sh inside the archive
Windows 10 / 11 .zip Run install-windows.ps1 in PowerShell

Linux — .deb (Debian / Ubuntu / Pop!_OS)

Requirements: Python 3.9+, X11 or Wayland display server.

# Download the .deb from Releases, then:
sudo apt install ./htpc-remote_1.0.2_all.deb

The post-install script automatically:

  1. Creates /opt/htpc-remote/venv with all pip dependencies
  2. Installs a udev rule so the Wayland backend can write to /dev/uinput
  3. Enables the systemd user service (htpc-remote.service) for auto-start on login
  4. Starts the service immediately

Log out and back in once — the QR popup appears within a few seconds.

Uninstall:

sudo apt remove htpc-remote

Upgrade: install the new .deb over the old one — the post-install script handles the venv update and service restart.

Linux — .rpm (Fedora / RHEL / AlmaLinux / openSUSE)

sudo dnf install ./htpc-remote-1.0.2-1.noarch.rpm
# or on openSUSE:
sudo zypper install ./htpc-remote-1.0.2-1.noarch.rpm

Same post-install behaviour as the .deb — venv, udev rule, systemd service.

Uninstall:

sudo dnf remove htpc-remote

Linux — .tar.gz (Arch / other distros)

tar -xf htpc-remote-1.0.2-linux.tar.gz
cd htpc-remote-1.0.2
sudo bash install.sh

The installer detects your package manager (pacman, zypper, dnf, or apt) and installs the required system packages (Python, GTK3 bindings), then sets up the venv and systemd service.

Windows — .zip

Requirements: Windows 10 or 11, PowerShell 5.1+. No admin rights needed.

# Extract the zip, then in PowerShell:
Set-ExecutionPolicy -Scope Process -ExecutionPolicy Bypass
.\install-windows.ps1

The installer:

  1. Checks for Python 3.9+ (installs via winget if missing)
  2. Installs to %LOCALAPPDATA%\htpc-remote
  3. Creates a venv and pip installs all dependencies
  4. Registers a Task Scheduler task to start Glide at login (no console window)
  5. Starts the server immediately

The QR window appears on screen once the server is running. Close it with the X button — it hides but the server keeps running.

Managing the Windows service:

# Stop
Stop-ScheduledTask -TaskName "htpc-remote"

# Start
Start-ScheduledTask -TaskName "htpc-remote"

# Remove completely
Unregister-ScheduledTask -TaskName "htpc-remote" -Confirm:$false

Logs: %LOCALAPPDATA%\htpc-remote\htpc-remote.log

Build from source

See Building from Source to build any of the packages yourself using Docker.

After installing

Glide Remote

Home

Getting started

Using Glide

Reference

Help

Clone this wiki locally