The guide takes you step‑by‑step through installing Sublime Merge on Ubuntu 22.04 LTS, starting with a system update and then downloading the official Debian package from Sublime’s download page. It shows how to install that .deb file with dpkg, run “apt‑get install –f” if dependencies are missing, and then confirm the binary is in /usr/bin/sublime_merge. After verifying the executable you can set Sublime Text as Git’s default editor, create a test repository, and launch Merge to see the commit history pop up instantly. The article rounds out with a handy troubleshooting table for common Qt plugin or library errors on minimal installs, highlighting why avoiding Snap’s bundled approach is worthwhile.

Install Sublime Merge on Ubuntu 22.04 LTS – Quick Start Guide

If you’re looking for a slick Git GUI that doesn’t turn your terminal into a circus act, this guide will get Sublime Merge up and running on Ubuntu 22.04 LTS in a few minutes.

We’ll cover the official Debian package, why you shouldn’t use Snap, and how to fix that annoying dependency error I ran into after a bad driver update.

Make sure your system is ready

Before pulling down anything we need the usual suspects:

sudo apt-get update && sudo apt-get upgrade -y

That refreshes package lists and bumps any stale libraries. If you skip it, you’ll be fighting broken dependencies later.

Grab the latest Debian build

Head over to Sublime’s download page or just fire up your browser:

wget https://download.sublimemerge.com/linux/sublimemerge-3.4.1-linux-x86_64.deb

(Replace the URL with the newest release if it has changed.)

The file is a single `.deb` that bundles everything you need – no extra PPAs or complicated repos.

Install with dpkg and fix missing libs

sudo dpkg -i sublimemerge-*.deb || true

If `dpkg` complains about unmet dependencies, run:

sudo apt-get install -f

That pulls in the missing pieces. I remember one time when a fresh 22.04 install threw an error about `libgconf2-4`. The quick fix was exactly this command.

Verify the binary is where it belongs

which sublime_merge
# /usr/bin/sublime_merge

You can also launch it from Activities or run:

sublime_merge &

If it pops up, you’re good. If not, double‑check that the file exists and has execute permissions.

Hook it into Git (optional but handy)

Sublime Merge will automatically detect your global Git config, but if you want to set a default editor:

git config --global core.editor "subl -n -w"

That tells Git to open Sublime Text instead of the console. No need for `merge.tool` settings unless you’re using Merge as an external merge driver.

Quick sanity test

Create a test repo:

mkdir ~/test_merge && cd ~/test_merge
git init
echo hello > file.txt
git add .
git commit -m "first commit"

Now open Sublime Merge and point it at `~/test_merge`. The history should appear instantly. If you don’t see any commits, make sure the folder is a proper Git repo.

Trouble shooting common hiccups

Symptom	Fix
“Failed to load Qt plugin ‘xcb’”	Install `libxkbcommon-x11-0` and `libxcb-icccm4`: `sudo apt-get install libxkbcommon-x11-0 libxcb-icccm4`
“Missing dependency: libqt5widgets5”	`sudo apt-get install qt5-default`

These usually surface if you’re on a minimal install or have removed some Qt packages.

That’s it. Sublime Merge is now ready to give your Git workflow that extra polish, and you avoided the Snap store’s “everything in one jar” mess.