Koodo Reader

Troubleshooting

Solutions for common Koodo Reader issues on Linux, macOS, Windows, and the web.

TTS is not working on Linux

Chromium-based applications need a speech engine installed on the system. See this answer for the cause and solution: Chromium is not generating voice.

Unable to type on Linux

Add the following flags after the startup command:

--ozone-platform=wayland --enable-wayland-ime --wayland-text-input-version=3

Importing books on Linux fails unexpectedly

Some third-party libraries depend on a specific glibc version. If the required version is missing, the import may fail.

  1. Open the console and check the error message to identify the missing glibc version.
  2. Install the corresponding version. For example, see How can I get glibc 2.35 on Ubuntu 20.04?.

App flickering on Linux with Wayland

This is commonly caused by the Nvidia driver on Wayland. Add the following flags to the startup command:

--enable-features=UseOzonePlatform --ozone-platform=wayland

Unable to run an AppImage package on Linux

Add the --no-sandbox flag after the command:

./Koodo-Reader.AppImage --no-sandbox

Unable to open in Ubuntu or KDE Plasma Wayland

Start Koodo Reader with one of the following commands:

koodo-reader --disable-gpu
koodo-reader --disable-gpu-compositing

macOS says the app cannot be verified

This warning appears because the application is not notarized by Apple. To open it:

Open System Settings > Privacy & Security > Security.

Click Open Anyway next to the blocked application, if the button is available.

Enter your administrator password when prompted.
Try opening the application again.

TXT books appear garbled

Koodo Reader supports most text encodings for TXT files. If the text is still garbled:

  1. Open the file in another text editor and check whether the text is also garbled there.
  2. If it looks correct in another editor, save the file as UTF-8 and import it again.

The reader is blank or does not respond

  • The book file may be damaged. Try opening it in another reader.
  • The book may be too large for the available memory or CPU. Close other applications and try again.

PDF books report "book does not exist" after Google Drive sync

Google Drive may automatically identify PDF files and add a file extension, which prevents Koodo Reader from finding the original file. Remove the added extension manually, then try opening the book again.

Backing up a large library fails or the app crashes

This can happen when the library is very large or the system does not have enough memory. Follow these steps to back up and restore the library:

Click Sync to export your application configuration to the library directory.
Open Settings > Data > Change Storage Location, click Locate, and open the library directory.
Close Koodo Reader. This step is important.

Select the config, book, and cover folders. Compress these three folders into a single ZIP file.

Do not compress the parent folder

Select the three folders themselves, not the directory that contains them. The resulting ZIP file is your library backup. Store it in a safe place.

To restore the backup:

Extract the ZIP file into a new directory.

Open Settings > Data > Switch Library, select the extracted directory, and confirm.

Your library is now restored.

I forgot my protection password or PIN

The password and PIN are stored locally after encryption. There is currently no way to retrieve or reset them directly. You can recover your data by following these steps:

Copy the data folder to a safe location.

Windows:

C:\Users\[Username]\AppData\Roaming\koodo-reader\uploads\data

macOS:

/Users/[Username]/Library/Application Support/koodo-reader/uploads/data

Delete the Koodo Reader application data folder to clear all local data.

Windows:

C:\Users\[Username]\AppData\Roaming\koodo-reader

macOS:

/Users/[Username]/Library/Application Support/koodo-reader
Reopen Koodo Reader, open Settings > Data > Switch Library, and select the folder you copied earlier. Your data will be restored.