TROUBLESHOOTING
•
LINUX DESKTOP
•
KEYBOARD/MOUSE SHARING
Barrier GUI Stuck on “Starting” in Linux: The Fix That Actually Works
Barrier 2.4.0 can work perfectly on Linux even when the GUI never flips to “Running”. This guide shows how to confirm the connection, run the stable backend client, and auto-start it on login—privacy-safe placeholders included.
The Symptom
On some Linux desktops (commonly Cinnamon/Xorg), Barrier’s GUI can get stuck showing Barrier is starting forever—without any useful error. The important detail is that this can be a GUI-only state bug, not a connection problem.
Key idea
If the backend client (barrierc) connects and your mouse crosses screens,
Barrier is already working. The fix is to run the backend reliably and auto-start it on login.
Step 1: Prove the Connection (CLI Test)
Run the Barrier client in the foreground with SSL/crypto disabled (recommended for LAN stability):
Terminal
barrierc -f --disable-crypto --name CLIENT_SCREEN_NAME SERVER_IP_ADDRESSExpected output looks like this:
Expected output
NOTE: started client
NOTE: connecting to 'SERVER_IP_ADDRESS': SERVER_IP_ADDRESS:24800
connected to server
Result
Seeing connected to server confirms your network and Barrier config are correct.
If input sharing works, the GUI “Starting” label is cosmetic.
Step 2: Create a One-Click Client Script
Create a local scripts folder:
Terminal
mkdir -p ~/binCreate the script file:
Terminal
nano ~/bin/barrier-client.shPaste this into the file (placeholders shown):
barrier-client.sh
#!/bin/bash
barrierc --disable-crypto --name CLIENT_SCREEN_NAME SERVER_IP_ADDRESSMake it executable:
Terminal
chmod +x ~/bin/barrier-client.shTest it once:
Terminal
~/bin/barrier-client.shStep 3: Auto-Start on Login (No Broken GUI Needed)
Add the working client script in Startup Applications so it connects automatically after you log in. Use these fields:
Name
Barrier Client
Command
bash -c "sleep 8 && /home/USERNAME/bin/barrier-client.sh"
Comment
Auto-start Barrier client
The sleep 8 delay prevents “starts too early” issues before networking is fully ready.
Optional: Why It Won’t Work at the Linux Login Screen
Barrier (and similar software KVM tools) typically cannot inject input at the Linux login screen. They start after your user session loads. If you need hands-free boot-to-control, enable Automatic Login so Barrier can start immediately after boot.
Tip
Automatic login is the clean approach when you don’t want a physical keyboard connected.
Placeholder Reference
| Placeholder | Replace with | |
|---|---|---|
| CLIENT_SCREEN_NAME | Your Linux client hostname (example: LINUX-PC) | |
| SERVER_IP_ADDRESS | Your Barrier server IP (example: 192.168.1.50 or your LAN IP) | |
| USERNAME | Your Linux username (example: user) |
