Arch Linux User Repository

@PatoPan Thanks for reporting. Logs would have been much more helpful.

A weird bug. On a complete fresh arch install, that only has radarr, sonarr, jellyfin, prowlarr, qbittorrent, and moonlight-qt installed, the jellyseer service was failing to start. I noticed that there was a config *file* inside /usr/lib/jellyseer. I fixed it by deleting the file, because it's supposed to be a directory.

Everything including Arch was installed yesterday

While the current versions of the package have the symlink problem fixed. They might still exist on your system. You will have to back up your data and delete them manually.

Detected unsafe path transition /var/lib/jellyseerr (owned by jellyseerr) → /var/lib/jellyseerr/cache (owned by root) during canonicalization of usr/lib/jellyseerr/config/cache/images.
Detected unsafe path transition /var/lib/jellyseerr (owned by jellyseerr) → /var/lib/jellyseerr/cache (owned by root) during canonicalization of usr/lib/jellyseerr/config/cache/images.
error: command failed to execute correctly

Yep, I also see these warnings currently. That's a packaging bug, not an issue with your system.

@jkhsjdhjs Ok thanks so much for picking that out, that has done the trick! I was pretty stumped by this bug lol!

After installing without libvips (picked it up when I was testing out photoprism), it worked pretty much flawlessly after I restarted the jellyseerr with systemctl.

It gives me this

'''Detected unsafe path transition /var/lib/jellyseerr (owned by jellyseerr) → /var/lib/jellyseerr/cache (owned by root) during canonicalization of usr/lib/jellyseerr/config/cache/images. Detected unsafe path transition /var/lib/jellyseerr (owned by jellyseerr) → /var/lib/jellyseerr/cache (owned by root) during canonicalization of usr/lib/jellyseerr/config/cache/images. error: command failed to execute correctly'''

during install, but it seems to have installed correctly and reports 2.0.1 in the about page, and I tested requesting a movie and all the things work fine, so I think it's fine for now.

Appreciate everyone's help!

@gatorpatch1 That error is probably because you have libvips installed, which the nodejs sharp package tries to link against. Check with pacman -Q libvips, but you can see it in the logs here:

│ sharp: Detected globally-installed libvips v8.16.0

Try removing libvips and building the package again. If that works, we found the issue. It would be cool to use the system libvips instead of having the jellyseerr package include its own version, but seeing that it doesn't work, there's probably no way around it. If removing libvips fixes your issue, @txtsd can set the environment variable SHARP_IGNORE_GLOBAL_LIBVIPS in the PKGBUILD to have sharp ignore the globally installed libvips.

See also: https://github.com/lovell/sharp/issues/4253

PS: pastebin.com has ads and captchas, is blocked for some users due to malware and injects CRLF line-endings. It is recommended to use alternative paste services like https://bpaste.net or https://paste.rs/web instead.

@Gilrain Apologies, this is my first time troubleshooting through the AUR. I'm building in a clean chroot now.

It seems to work fully when building it in a clean chroot, which I've attached the logs to here. Right now I guess I'm stumped on how best to get my custom installation up to date, as I have very little idea why it's broken. Might try to uninstall the program and reinstall the newest version, see where that gets me.

Edit: building after uninstalling does not fix the issue.

@gatorpatch1: you should not build AUR packages with your custom installation but instead use a clean/pristine environnement to do so: https://wiki.archlinux.org/title/DeveloperWiki:Building_in_a_clean_chroot

@txtsd If I have nodejs-23.1.0-1, it uninstalls that and installs nodejs-lts-iron-20.18.0-1, which then tries to build jellyseerr, failing after a bit on the same error mentioned before. I grabbed my logs in pastebin here, which I've linked for debug purposes. LMK if they'res any other thing you want me to try!

@picokan I was testing a few things. With 2.0.1-7, I managed to get the size down to the lowest it's been on 2.x.x.