The passage provides a concise, step‑by‑step tutorial for installing Beekeeper Studio on Ubuntu 22.04 LTS by adding the official APT repository, importing its GPG signing key, updating package lists, and finally running sudo apt install beekeeper-studio. It explains why using the upstream repo is preferable to Snap or manual .deb files—offering newer features, automatic security updates, and fewer dependency headaches—and warns about common pitfalls such as incorrect key permissions or missing public‑key warnings. An optional verification step (beekeeper-studio --version) and a note on removing any lingering Snap installation are included to ensure the correct version is running. After completing these four commands, users have a ready‑to‑use SQL client for MySQL, PostgreSQL, SQLite, and other databases directly from Ubuntu’s desktop or terminal.

Install Beekeeper Studio on Ubuntu 22.04 LTS – Quick and Clean

You’ll get a fully working copy of Beekeeper Studio without hunting around for random .deb files. We’ll add the official repository, pull in the signing key, and finish with a single apt command. By the end you’ll be ready to open your databases straight from Ubuntu’s terminal or menu.

Add the Beekeeper Studio APT source

The upstream repo ships the newest features and security fixes, something the Snap version lags behind on. Open a terminal and run:

echo "deb [arch=amd64 signed-by=/usr/share/keyrings/beekeeper.gpg] https://repo.beekeeperstudio.io/debian stable main" | sudo tee /etc/apt/sources.list.d/beekeeper.list > /dev/null

Why this matters: the file tells apt where to look for Beekeeper packages and locks it to the 64‑bit builds you actually need on a typical desktop.

Import the repository’s GPG key

Ubuntu refuses to install unsigned packages. Grab the key and store it where we pointed above:

curl -fsSL https://repo.beekeeperstudio.io/keys/beekeeper.gpg | sudo gpg --dearmor -o /usr/share/keyrings/beekeeper.gpg

I’ve seen this step trip people up after a kernel upgrade – the key file ends up with the wrong permissions and apt throws “The following signatures could not be verified”. Running the command as shown creates a proper .gpg file that apt trusts.

Refresh package lists

Now let apt read the new source:

sudo apt update

If you get a warning about “NO_PUBKEY”, double‑check the previous curl command; a truncated download is the usual culprit.

Install Beekeeper Studio

Finally, pull the app in:

sudo apt install beekeeper-studio

Apt will resolve any missing dependencies (usually just libsecret‑tool). When it finishes you’ll see a desktop entry appear automatically.

Optional: Verify the installation

Run:

beekeeper-studio --version

You should see something like Beekeeper Studio 2.3.4. If the version number looks ancient, you probably still have an old Snap lurking; remove it with sudo snap remove beekeeper-studio.

Why not just use a .deb from GitHub?

I’ve tried that route a few times and ended up chasing down missing libssl1.1 on newer Ubuntu releases. The repository method sidesteps those headaches because the maintainers rebuild the package for each Ubuntu LTS cycle.

That’s it – you’re ready to connect to MySQL, PostgreSQL, SQLite or any other supported database without leaving Ubuntu. Happy querying!

— Enjoy your new SQL playground!