Arch Linux User Repository

If you are using firefox and it hangs trying to load Kavita, add a /login to the end of the URL

@CountMurphy

I ran into two issues: 1) Upgrading thru yay downloaded 0.7.2.0. manual upgrade worked without issues 2) Same issue with kavita user not having access to /opt/kavita/config/appsettings.json. manually running

# chown kavita:kavita /opt/kavita/config/appsettings.json

allowed me to login after upgrading from 0.7.2 to 0.7.3

Thank you for maintaining this package!

Looks like Kavita 0.7.3 changed how logins work. Personally I cannot log in to update my key and have filed a bug (https://github.com/Kareadita/Kavita/issues/2042). Hopefully I'm just an idiot and there is an easy workaround. Until then I have personally downgraded to 0.7.2

EDIT: Problem was my fault. If you are experiencing a similar issue, I am working on a fix to the PKGFILE

EDIT EDIT:

Issue looks resolved now. If anyone has any problems creating new users or logging in please let me know.

@TalkingHat: Right after you install kavita, the package prints the instructions out on the terminal:

"To run, systemctl start kavita site at localhost:5000"

How do I run the program? I've tried writing kavita on the terminal but it doesn't work and there isn't a launcher in the menu.

Added arm 32. @TheHardew I don't have any devices to test this with, so you'll have to let me know if it worked.

Could you add arm 32 bits (especially armv7 for raspberry pi 4) please?

@rahulmn, just built on my Pi3 just fine. So the tar file downloaded from github always has the same file name, kavita-arm64.tar.gz. There is no version number in the file name. When running an aur helper like yay, it gives you the option for a clean build. You'll have to say yes to that (or delete the old tar.gz file yourself). When makepkg starts to build, it sees the old tar file, and skips downloading the new one (since the file names are the same), hence the hash mismatch

I'm seeing the wrong md5sum for the aarch64 package

Linux is case sensitive. Anything other than whats in the service file, "ExecStart=/opt/kavita/Kavita" will fail. Unless the service file was manually changed to "/opt/Kavita," altering the executable path will cause the service to fail no matter what architecture the OS is on. If its still giving you trouble, I'd uninstall it and then manually delete any left files in /opt and /etc, then reinstall.

Just for shits and giggles, I installed it on my pi3 board and manually changed the case in /opt. As expected the service failed to start with that modification.

I think the difference might be filesystem or some other environment difference. Can you check to see if you run into issues capitalizing Kavita in /opt ?