Common issues and solutions for Libiry.
Installation issues
Linux specific: make sure the install file is executable (chmod +x)
Windows specific: Python not installed
Problem: Running the Libiry installer shows Python not found.
Solution:
IMPORTANT: If you have Python 3.13 or higher, or if you got Python through the Microsoft Store or the new “Python Install Manager” (py), it may not work correctly with Libiry yet. Install Python 3.12 instead.
- Install Python 3.12 from python.org
- Go to https://www.python.org/downloads/release/python-31210/
- Scroll to “Files” at the bottom of the page
- Download “Windows installer (64-bit)” -> python-3.12.10-amd64.exe
- Run the Python installer
- IMPORTANT: on the first screen, check the box “Add Python 3.12 to PATH” before clicking Install Now
- Click “Install Now” and wait for it to finish
- Click “Close”
- Restart your terminal/command prompt
- Run
python --versionto verify
To verify, you can open a Command Prompt and type: python --version It should print: Python 3.12.x
Kivy installation fails
Problem: pip failed to install Kivy
Solution:
# Try installing with base dependencies only
pip install kivy[base]
# Or install pre-built wheel
pip install kivy --pre --extra-index-url https://kivy.org/downloads/simple/PyMuPDF installation fails
Problem: PyMuPDF (fitz) fails to compile
Solution:
Windows: install Visual Studio Build Tools first
Linux:
sudo apt install libmupdf-dev mupdf-toolsNo module named ‘kivy’
The venv was not set up correctly. Re-install Libiry.
No runtimes are installed / pymanager error
You have the new Python Install Manager, but no Python runtime. Install Python 3.12 from python.org and re-install Libiry.
The app opens, but then crashes immediately
Delete the venv folder and re-install Libiry.
What is installed exactly?
What gets removed exactly?
UNINSTALL INSTRUCTIONS
can you make a list of everything that might have come onto their computer (python, kivy) and how to remove that again, with terminal instructions? also pointing out the dangers?
● An AppImage install leaves nothing system-level behind — Python and Kivy are bundled inside the AppImage file. The footprint is:
Complete AppImage clean uninstall: rm ~/Downloads/Libiry-*.AppImage rm -rf ~/.config/Libiry/ rm -rf ~/.cache/Libiry/ Leave ~/.kivy/ unless you’re certain you have no other Kivy apps.
install.sh install touches system directories and requires sudo to clean up:
| What | Location | How to remove | Danger |
|---|---|---|---|
| The app │ wherever you put the .AppImage │ rm ~/Downloads/Libiry-*.AppImage │ None │ | |||
| Settings │ ~/.config/Libiry/ │ rm -rf ~/.config/Libiry/ │ Irreversible — your folder location and customizations are gone │ ├─────────────┼────────────────────────────────┼──────────────────────────────────┼──────────────────────────────────────────────────────────────────────┤ │ Cover cache │ ~/.cache/Libiry/ │ rm -rf ~/.cache/Libiry/ │ Safe — rebuilds itself │ ├─────────────┼────────────────────────────────┼──────────────────────────────────┼──────────────────────────────────────────────────────────────────────┤ │ Kivy config │ ~/.kivy/ │ rm -rf ~/.kivy/ │ Caution — if you have other Kivy apps, this removes their config too │ └─────────────┴────────────────────────────────┴──────────────────────────────────┴──────────────────────────────────────────────────────────────────────┘ |
| App + Python venv │ /opt/Libiry/ │ sudo rm -rf /opt/Libiry/ │ None beyond losing the app │ |CLI launcher │ /usr/local/bin/libiry │ sudo rm /usr/local/bin/libiry │ None │ |System icon │ /usr/share/pixmaps/libiry.png │ sudo rm /usr/share/pixmaps/libiry.png │ None │ |Desktop entry │ ~/.local/share/applications/Libiry.desktop │ rm ~/.local/share/applications/Libiry.desktop │ None │ |User icon │ ~/.local/share/icons/hicolor/256x256/apps/libiry.png │ rm ~/.local/share/icons/hicolor/256x256/apps/libiry.png │ None │ |Settings │ ~/.config/Libiry/ │ rm -rf ~/.config/Libiry/ │ Irreversible │ |Cover cache │ ~/.cache/Libiry/ │ rm -rf ~/.cache/Libiry/ │ Safe │ |Kivy config │ ~/.kivy/ │ rm -rf ~/.kivy/ │ Caution — other Kivy apps affected │ |System packages │ libsdl2-dev, python3-venv, etc. │ see below │ High danger │ The uninstall.sh script handles everything except system packages and ~/.kivy/.
Do not remove system packages blindly. The packages installed by install.sh (python3-dev, python3-venv, libsdl2-dev, etc.) may be needed by other software. Running: sudo apt-get remove python3-dev python3-venv libsdl2-dev sudo apt-get autoremove could remove dependencies shared with other apps. Only do this if you know these packages were not on your system before installing Libiry.
Application issues
Application won’t start
Problem: Libiry does not start
Solution:
- Check if there any Python processes still running on your computer. Close these or restart your computer
- Run Libiry_debug.bat instead of Libiry.bat to see error messages
- Check if a virtual environment exists in the venv/ folder
- Re-run install.bat
Blank window / no books shown
Problem: Libiry opens but shows nothing
Solutions:
- Check Settings → Location
- Verify the folder contains supported file types
- Check the “Only selected file types” setting
- Press F5 to refresh
Slow startup
Problem: Libiry takes a long time to start
Solutions:
- Large libraries take longer on the first scan
- Check your network connection (cover lookup may timeout for slow connections)
- Move your library to SSD if on HDD
- Reduce your folder depth (fewer nested folders)
- Uncheck the ‘Show tags’ box in Settings
Display issues
Covers not showing
Problem: Books are displayed without covers
Solutions:
- If the cover field is filled with a URL, check your internet connection (for online lookup)
- Verify that your e-books contain embedded covers
- Clear the cache
- If the cover field is filled with a URL, check if the URL is valid
Text too small/large
Problem: UI elements are wrong size
Solution: Change your font size.
High DPI scaling issues
Problem: The UI looks tiny on a high-resolution display.
Solution: Increase the font size under Settings. Kivy may not auto-scale on all systems.
Book doesn’t open
Problem: Double clicking a book in Libiry doesn’t open it in your default reading app
Solutions:
- Check if the book opens correctly in this app outside of Libiry
- Some tools (like Obsidian) require a command line interface. Either enable that or change your default markdown app from Obsidian to another app that can read markdown files, like Notepad or the Calibre Viewer. This will not affect your Obsidian experience
- Replace Calibre with the Calibre Viewer
- Run Libiry in debug mode. It will tell you why it cannot display the file
Tag issues
Calibre tags not displayed in Libiry
Problem: Calibre tags are not visible in Libiry
Solution: There may be a difference in the tags that are shown in Libiry and in Calibre. Calibre stores PDF tags in the subject field, while Libiry uses Keywords.
Tags not saving
Problem: Tags disappear after saving
Solution: Most books require sidecar files. Check if a sidecar file was created next to the book. Ensure write permissions in the folder.
Search issues
Search isn’t finding books
Problem: Books exist, but search doesn’t find them.
Solutions:
- Search is case-insensitive but exact by default
- Enable Fuzzy search in Settings for partial matches
- Search depth is limited to 10 folder levels
- Check if files have correct extensions
Fuzzy search too broad
Problem: Fuzzy search returns too many results.
Solution: Disable fuzzy search for more precise matching:
Fuzzy search y/n: NPerformance issues
High memory usage
Problem: Libiry uses too much RAM.
Solutions:
- Close other applications
- Reduce grid zoom level
- Divide large folders into subfolders
Slow scrolling
Problem: Grid scrolling is laggy
Solutions:
- Reduce the number of visible tiles (zoom out less)
- Make sure that thumbnail cache is working (
~/.libiry/cache/) - Use an SSD for library storage
File issues
Permission denied when saving
Problem: Can’t save tags or move files
Solutions:
- Check folder permissions
- Close files in other applications
- Run as administrator (Windows)
- Check if files are read-only
Deleted files still showing
Problem: Removed files appear in the grid.
Solution: Refresh the view
Moving files fails
Problem: The move operation doesn’t work
Solutions:
- Check if the destination folder exists
- Check the write permissions
- Make sure that the file isn’t open in another program
Getting help
Debug mode
Run with console output to see error messages:
run_debug.batLog files
Check for errors in the console output. No separate log files are created
Reporting issues
When reporting bugs, include:
- Operating system and version
- Python version
- Error message from debug mode
- Steps to reproduce
- Example files
Report issues at GitHub Issues or at Reddit. Please take into account that I am just one person, doing this free of charge. Not all changes that you request will be granted.