Skip to main content
The Linux app is in beta: only 0.1.0-beta.N builds exist until 0.1.0 ships. It runs on amd64 and arm64, as an app of its own beside the Mac one, with the engines on Connect. Use the repository for your distribution: apt or dnf then installs every update, and so do Software Updater and GNOME Software. Take a file from GitHub Releases for another distribution, through the Flatpak bundle, or to try one exact build.

Install the beta

Enable both the stable and beta repositories, then install tablepro:
apt and dnf install the highest version the two hold, so a release replaces its betas and the next beta replaces that release. Without the stable repository, the last beta stays installed until the next beta.

Install a stable release

From 0.1.0 on, the stable repository alone gets releases and no betas:
To stop testing betas, remove the beta repository. The installed beta stays until the stable repository has a newer version.

Packages on GitHub Releases

Each release and beta on GitHub Releases carries packages and their SHA256SUMS. A beta is a pre-release there. A standalone .deb, .rpm or .flatpak bundle gets no app updates unless you install the next file or enable the PPA or COPR for native packages. New Linux betas and their fixes are announced on that releases page. Subscribe to its Atom feed and filter entries for tags starting with linux-v. The feed also includes other platforms. PPA and COPR installs get updates through apt or dnf. Check the download, then install the file for your system:
The Flatpak bundle fetches the GNOME 51 runtime from Flathub, and the next bundle installs over it. Flathub does not carry TablePro itself. The bundle keeps its files under ~/.var/app/app.tablepro.TablePro/; Troubleshooting lists them. Other distributions build from source with the Quickstart in the app repository.

Move between native packages and Flatpak

The two formats use different data folders and secret storage. An empty connection list after switching does not mean the old data was deleted.
1

Back up saved work

Quit the app and back up its files, including query history, saved queries and drafts, before changing formats.
2

Export connections

Reopen the current installation. Choose Export Connections… from the main menu and save the file outside its app data folder. Quit it before starting the other installation.
3

Import in the other installation

Install the other format and choose Import Connections… from its main menu. Select the exported file and review the import. This transfers connection settings, not history, drafts or passwords.
4

Sign in again

Re-enter database and SSH passwords and key passphrases. Set up cloud AI keys and MCP clients again if you use them. Keep the backup until you have checked your connections and saved work.

Uninstall

Quit the app first. Package removal keeps your connections, history, drafts, preferences and saved secrets. Use the command for your installation:
The Flatpak commands here assume the --user installation in this guide. Use --system for a system-wide installation. For a full reset, follow the optional steps next while the app is still installed.

Optional full reset

Resetting deletes saved work and credentials. Back up saved work first. The steps affect this desktop account, not your server databases or SQLite and DuckDB files stored elsewhere.
1

Reset preferences before uninstalling

Quit the app. Reset GSettings while the installed package still provides its schema:
2

Remove saved work and secrets

For native packages, remove these folders. The commands respect custom XDG locations and delete connections, history, saved queries, tabs, drafts, snippets and crash reports:
In Passwords and Keys (Seahorse) or KWallet Manager, delete only the TablePro secret entries. Removing the folders does not remove those keyring items. Then remove the native package with the uninstall command.For Flatpak, use this instead of the keep-data uninstall command:
The delete-data option removes the sandbox’s data and permissions, including its encrypted secret file. If the desktop keyring still lists a Secret portal item for this app, remove that item too. Native-installation keyring entries remain separate.
3

Remove repository configuration if no longer needed

For native packages, remove both repositories if you enabled both:
For Flatpak, run flatpak remotes --user. Remove an unused bundle-origin remote with flatpak remote-delete --user REPOSITORY, replacing REPOSITORY with its listed name. Keep Flathub if other apps or runtimes use it.