Windows and Linux

QuillArk runs on Windows 10 and 11, and on 64-bit Linux — a Debian package for Linux Mint, Ubuntu and Debian, and a portable archive for anything else.

The application is the same on both. Same features, same file formats, same projects. A Books folder written on one opens on the other without conversion, because it is only folders and Markdown.

What differs

	Windows	Linux
Where settings live	`%APPDATA%\QuillArk`	`~/.config/QuillArk`
Removed backups go to	the Recycle Bin	Trash
“Show in…” opens	Windows Explorer	your file manager
Fonts come from	the Windows font folders	`/usr/share/fonts` and `~/.local/share/fonts`

Your Books folder is wherever you chose it, on both.

Moving between them

Copy the Books folder across. Nothing needs converting and nothing needs exporting first. QuillArk finds the projects the next time it starts.

The search index does not travel — it is rebuilt from your files on first run, and it holds nothing that is not already in them.

On Linux

The .deb installs into /opt/QuillArk and adds a menu entry and a quillark command. Removing it leaves your Books folder and your settings exactly where they are, the same as on Windows.

The portable archive runs from wherever you extract it — ./run.sh — and installs nothing. The same folder holds install.sh, which does what the .deb does, and uninstall.sh, which undoes it.

If QuillArk will not start, the usual cause is a missing system library:

sudo apt install libgtk-3-0 libnotify4 libnss3 libxss1 libxtst6 libatspi2.0-0 libsecret-1-0 xdg-utils

On Ubuntu 24.04 and Linux Mint 22 some of those names end in t64. Your package manager will say so, and the t64 package is the right one.

Running the portable archive without installing means Chromium’s sandbox helper cannot be given the permissions it needs, so run.sh starts QuillArk with the sandbox switched off and prints a line saying so. Installing — with the .deb or with install.sh — restores it.

The Linux packages are built on Windows and cross-packaged. They are genuine Linux builds and the archives carry correct Unix permissions, but they have not been run on a Linux desktop before release. If something is wrong, that is worth reporting rather than working around.