Librum: Install the E-Book Reader on Linux

Librum: Install the E-Book Reader on Linux

Choosing a Linux app for your e-book library starts with knowing what it does and how to install it. Librum is an open-source reader and library manager that supports formats including PDF, EPUB and CBZ.

I’ll walk through installing Librum with Flatpak and checking whether its Flathub package is marked end-of-life.

TL;DR

Check the Flathub status before installing Librum. Its listed Flatpak ref is marked end-of-life, so do not rely on it for future updates.

  • Confirm Flatpak is available and Flathub is configured.
  • Use the listed ID, com.librumreader.librum, only after checking the maintenance notice.
  • Use flatpak info to confirm the app, and launch it from your desktop menu.

What is Librum?

Librum is an open-source e-book reader and library manager. The project describes an online library that syncs across devices, alongside bookmarks, highlighting and text search. The Flathub package status is a separate question from this feature description.

The project lists PDF, EPUB and CBZ among its supported formats. The current README names Windows, GNU/Linux and macOS for desktop use. Android and iOS remain marked as coming soon.

The project lists collections, tags and metadata editing. The README identifies some reading features as planned rather than released.

How to install Librum on Linux step by step

The package ID is com.librumreader.librum. Check the remote and package metadata before deciding whether this installation route fits your system.

Step 1: Check Flatpak and Flathub

Flatpak installs desktop applications from remotes such as Flathub. Check its availability and the configured source first:

flatpak --version
flatpak remotes

The commands returned Flatpak 1.14.6 and a user-level flathub remote. A terminal screenshot below shows the version command and its output. If Flathub is absent, use our Flatpak and Flathub setup guide before continuing.

Terminal showing Flatpak version 1.14.6
Flatpak version check and its returned version.

Step 2: Install the Flathub application

Use the exact app ID shown by the Librum package listing. The command below requests an installation and can change your system. Review the remote and runtime prompt before accepting it.

Command: flatpak install flathub com.librumreader.librum. No output is shown because running this command installs software and changes system state. Installation output depends on the remote package and runtime resolution.

Step 3: Verify the installed application

Ask Flatpak for the installed metadata rather than relying only on an installer message.

flatpak info com.librumreader.librum

The read-only remote lookup returned an aarch64 stable ref, version 0.12.2, KDE Platform 6.5 and an end-of-life notice. The installed-info command will identify an installed ref, branch and runtime after installation. This package is not installed here.

Step 4: Launch Librum

Open the desktop application menu and search for Librum. If you prefer a terminal, use this command:

flatpak run com.librumreader.librum

The launch command starts the graphical application and needs an active desktop session.

Check the install and handle common limits

Use the official documentation to separate advertised capabilities from released features. A reader should check the currently available package rather than infer release availability from the project overview.

The package metadata identifies an end-of-life ref. Keep that status in mind when deciding whether to use the package.

SymptomWhat to checkNext step
“No remote refs found” or app not foundRemote name and app IDRun flatpak remotes and add or enable Flathub using the setup guide, then retry.
App already installedInstalled app metadataRun flatpak info com.librumreader.librum, then launch it.
Application marked end-of-lifeCurrent Flathub listing and upstream release pageCheck whether the project has a newer supported package before depending on updates.
Window fails to openRun command from a graphical session and note terminal error textRetry from the desktop session and consult upstream issue tracker if it persists.

For an app that depends on an online library, maintenance affects more than desktop updates. Keep book files outside the app if you may change readers.

Our Foliate guide and Bookworm overview cover other EPUB readers for Linux.

The repository mentions an in-app bookstore and AI-assisted explanations. Confirm their availability in the specific release before building a workflow around them.

The official repository documents self-hosting as a separate setup. It requires Librum Server and client configuration that points to that server.

File compatibility is another reason to check the project documentation before importing a large collection. The README lists PDF, EPUB, CBZ, FB2, TIFF, Mobi, XPS and images.

Readers seeking another option can compare our Foliate installation guide with the Bookworm overview. Match the choice to your file formats and library workflow.

Conclusion

For current package details, consult the Flathub Librum listing, the official release notes, and the Librum source repository.

FAQ

These answers cover installation, file support and the cloud library questions that affect a first setup.

Can you upload PDFs into Librum?

The official project lists PDF among its supported formats. The online library workflow is account-based, so consult the current app documentation for upload and storage limits.

Does Librum work on Linux?

The project lists GNU/Linux as a supported desktop platform and provides a Flathub package. Check the live Flathub listing because the metadata inspected for this article marks the current app end-of-life.

Does Librum sync books between devices?

The official site describes an online library that syncs across devices. Sync depends on the service and an account and keep a separate copy of important books.

What is the Flatpak ID for Librum?

The Flathub application ID is com.librumreader.librum. Install it with flatpak install flathub com.librumreader.librum.

For readers who want to compare the desktop app with other options, Librum’s official feature list includes bookmarks and highlighting, while LinuxLinks describes its library organization and PDF tools. Check the release notes rather than assuming every feature listed in an older review is present in the package currently offered.

The Flathub metadata check is also useful before an upgrade. A runtime identifies the shared platform components an app uses, while the application branch identifies the release stream and neither field alone says whether the project is actively maintained. Here the explicit end-of-life label is the relevant signal.

Keep local originals of books that matter to you. An online library can be convenient across devices, but it introduces an account and a service dependency that a reader storing files only on one computer does not have. This distinction also answers the self-hosting question: the client repository documents a separate Librum Server and configuration, so a normal Flathub install should not be described as a self-hosted server setup.

If a package lookup fails, check the spelling of the remote and application ID before changing your system. The official client repository documents Linux build prerequisites such as Qt, CMake, make and a C++ compiler, but building from source is a separate route with more maintenance work. Use that route only when you understand how to update the build and its dependencies.