Troubleshooting
Install
Install the package that matches your distribution:
-
.deb (Debian, Ubuntu and derivatives):
sudo dpkg -i openkm-liveedit_<version>-1_amd64.deb
-
.rpm (Fedora, RHEL)
:
sudo dnf install ./openkm-liveedit-<version>-1.x86_64.rpm
-
.rpm (openSUSE)
:
sudo zypper install ./openkm-liveedit-<version>-1.x86_64.rpm
-
AppImage (any distribution, no administrator privileges required): make the file executable and run it directly, e.g.
chmod +x OKM_LiveEdit-<version>-x86_64.AppImage && ./OKM_LiveEdit-<version>-x86_64.AppImage
The first run registers the liveedit:// protocol handler and autostart entry automatically for the current user.
The .rpm package is signed. See the "RPM: signature public key is not available" section below if the package manager reports a signature warning.
Unlike the Windows version, restarting the operating system is not required after installation.
Uninstall
Steps to uninstall the application correctly:
-
.deb:
sudo dpkg -r openkm-liveedit
-
.rpm (Fedora, RHEL)
:
sudo dnf remove openkm-liveedit
-
.rpm (openSUSE):
sudo zypper remove openkm-liveedit
-
AppImage: there is nothing to uninstall at the system level — stop the running process and delete the desktop/autostart entries created on first run:
pkill -9 -f liveedit-daemon
rm ~/.local/share/applications/openkm-liveedit.desktop
rm ~/.config/autostart/openkm-liveedit.desktop
rm ~/.local/share/icons/hicolor/32x32/apps/openkm-liveedit.png
Uninstalling does not remove the user's configuration, downloaded documents or logs. Delete ~/.config/openkm-liveedit, ~/OpenKM/liveedit and ~/.local/state/openkm-liveedit manually if a completely clean removal is needed.
RPM: "signature public key is not available"
The .rpm package is signed with OpenKM's own GPG key. On a machine where that key has never been used before, dnf/zypper report the package's signature as present but from an unknown key, for example:
Header V4 RSA/SHA512 Signature, key ID c35bf0c24119a96f: NOKEY
Signature verification failed [4-Signatures public key is not available]
This is expected the first time the package is installed on a given machine — it means the signature itself is valid, but the public key used to create it has not been imported into that machine's trust store yet. To fix it:
-
Obtain OpenKM's public key file, openkm-liveedit-linux-public.asc , from an official OpenKM source.
-
Import it into the system's RPM keyring (only needed once per machine):
sudo rpm --import openkm-liveedit-linux-public.asc -
Install the package again with
dnf install/zypper installas usual — it should now proceed without any signature warning.
If the package manager reports the package as unsigned (no signature at all, not just an unknown key), this is unexpected — verify you downloaded the package from an official OpenKM source before proceeding.
System tray icon not visible on GNOME
On GNOME desktop environments without any extension (Fedora Workstation, for example), the system tray icon is not shown after starting the application. This is a known limitation of GNOME itself, not an application error: the background process keeps running normally (protocol handling, autosave, check-in) even though no icon is visible.
To make the tray icon appear:
-
Install the AppIndicator and KStatusNotifierItem Support extension:
sudo dnf install gnome-shell-extension-appindicator # Fedora/RHEL
sudo zypper install gnome-shell-extension-appindicator # openSUSE, if applicable -
Enable it:
gnome-extensions enable appindicatorsupport@rgcjonas.gmail.com
Verify it is active with
gnome-extensions list --enabled(it should listappindicatorsupport@rgcjonas.gmail.com). -
Restart the application after enabling the extension. Enabling the extension while the application is already running is not enough — the icon will not appear until the application is stopped and started again:
pkill -9 -f liveedit-daemon
Then open the application again (or log out and back in if it is set to start automatically).
Desktop environments with native tray icon support — such as Cinnamon (Linux Mint) and KDE Plasma (openSUSE) — do not require this extension.