Package Details: sonarr-bin 4.0.11.2680-3

Git Clone URL: https://aur.archlinux.org/sonarr-bin.git (read-only, click to copy)
Package Base: sonarr-bin
Description: Smart PVR for newsgroup and torrent users
Upstream URL: https://sonarr.tv
Licenses: GPL-3.0-or-later
Groups: servarr-bin
Conflicts: sonarr
Provides: sonarr
Submitter: txtsd
Maintainer: txtsd (fryfrog)
Last Packager: fryfrog
Votes: 100
Popularity: 2.03
First Submitted: 2024-10-13 20:06 (UTC)
Last Updated: 2024-12-13 01:38 (UTC)

Dependencies (20)

Required by (17)

Sources (8)

Pinned Comments

mkomko commented on 2024-11-15 06:59 (UTC)

PSA: If you receive exceptions like "System.IO.IOException: Read-only file system" when Sonarr is importing files after updating to 4.0.10.2544, and you use your home directory for downloaded files (which is advised against), you can either move file management out of your home directory or do something like the following:

$ sudo systemctl edit sonarr

[Service]
# Allow home directory path to be writable again
ReadWritePaths=/home/user/media

txtsd commented on 2024-10-21 03:56 (UTC) (edited on 2024-10-30 12:50 (UTC) by txtsd)

Alternate versions

sonarr (source version of this package)
sonarr-develop (develop branch)
sonarr-develop-bin (binary version of the develop branch)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 11 .. 16 Next › Last »

shining235 commented on 2018-03-03 16:27 (UTC)

I had mono crashes without legacy setting when updating tv shows. That does not happen any more.... and I don't start sonarr over systemd

fryfrog commented on 2018-02-28 07:09 (UTC)

Anyone know if Environment=MONO_TLS_PROVIDER=legacy can be removed from sonarr.service file yet? I've removed it from mine just now and am keeping an eye on it.

fryfrog commented on 2017-11-06 03:44 (UTC)

2.0.0.5054 is up in the client, but not on github yet. Maybe they forgot? :)

degeberg commented on 2017-08-21 08:41 (UTC)

That is a known bug (https://github.com/Sonarr/Sonarr/issues/1928). I think it depends on the particular SSL/TLS parameters used to establish connections. At least that would explain why some people experience it and others don't.

Denzo commented on 2017-08-21 08:13 (UTC) (edited on 2017-08-21 08:14 (UTC) by Denzo)

With the Environment=MONO_TLS_PROVIDER=legacy line removed, Sonarr crashes whenever it sends a torrent to Transmission. Now that I've re-added the line, it no longer crashes. Anyone else experiencing this?

<deleted-account> commented on 2017-07-28 20:31 (UTC)

@springer Same here, I removed this line and no problems meanwhile.

springer commented on 2017-07-19 11:06 (UTC)

Were there any recent changes that fixed the mono TLS related problem? I just removed the MONO_TLS_PROVIDER line from the startup script and Sonarr seems to be up and running. Can someone else test it as well? This is from my Sonarr > System page """ Health No issues with your configuration About Version 2.0.0.4855 Mono Version 5.0.0 AppData directory /var/lib/sonarr Startup directory /usr/lib/sonarr """

smmalis37 commented on 2017-07-07 18:17 (UTC)

The devs and I have been debugging this issue. For now, legacy is still needed despite the health check (we thought it was fixed but it wasn't). I have filed https://bugs.archlinux.org/task/54738 since this seems to be a bug in mono.

<deleted-account> commented on 2017-07-07 10:57 (UTC)

Hi @degeberg. Is it possible to include the "MONO_TLS_PROVIDER=legacy" as on option in the systemd service file (where it can be easily overriden) instead of in the sonarr.sh file? So adding this to sonarr.service (under the [Service] tag): "Environment=MONO_TLS_PROVIDER=legacy" Just commented out the option in sonarr.sh and it doesn't seem to affect sonarr at all in my install.

degeberg commented on 2017-07-05 04:56 (UTC)

I've switched it back to legacy.

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 11 .. 16 Next › Last »