Package Details: sonarr 2.0.0.5338-1

Git Clone URL: https://aur.archlinux.org/sonarr.git (read-only, click to copy)
Package Base: sonarr
Description: PVR for newsgroup users
Upstream URL: https://sonarr.tv
Licenses: GPL3
Submitter: justin8
Maintainer: degeberg
Last Packager: degeberg
Votes: 80
Popularity: 0.23
First Submitted: 2014-11-10 04:45
Last Updated: 2019-08-17 05:50

Dependencies (9)

Required by (5)

Sources (4)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 ... Next › Last »

Ronin7z commented on 2018-03-19 05:41

Tried installing through AUR today, got this error when trying to run it

[ronin@Ronin ~]$ sonarr
exception inside UnhandledException handler: The type initializer for 'System.Console' threw an exception.

[ERROR] FATAL UNHANDLED EXCEPTION: System.TypeInitializationException: The type initializer for 'System.Console' threw an exception. ---> System.TypeInitializationException: The type initializer for 'System.ConsoleDriver' threw an exception. ---> System.Exception: Magic number is wrong: 542
  at System.TermInfoReader.ReadHeader (System.Byte[] buffer, System.Int32& position) [0x00028] in <a84b655e5e6a49ee96b338ec792f5580>:0 
  at System.TermInfoReader..ctor (System.String term, System.String filename) [0x0005f] in <a84b655e5e6a49ee96b338ec792f5580>:0 
  at System.TermInfoDriver..ctor (System.String term) [0x00055] in <a84b655e5e6a49ee96b338ec792f5580>:0 
  at System.ConsoleDriver.CreateTermInfoDriver (System.String term) [0x00000] in <a84b655e5e6a49ee96b338ec792f5580>:0 
  at System.ConsoleDriver..cctor () [0x0004d] in <a84b655e5e6a49ee96b338ec792f5580>:0 
   --- End of inner exception stack trace ---
  at System.Console.SetupStreams (System.Text.Encoding inputEncoding, System.Text.Encoding outputEncoding) [0x00007] in <a84b655e5e6a49ee96b338ec792f5580>:0 
  at System.Console..cctor () [0x0008e] in <a84b655e5e6a49ee96b338ec792f5580>:0 
   --- End of inner exception stack trace ---
  at NzbDrone.Common.Instrumentation.GlobalExceptionHandlers.HandleAppDomainException (System.Object sender, System.UnhandledExceptionEventArgs e) [0x0007a] in <6d548036160a49ed8e2657c617163f50>:0 

strangebrew commented on 2018-03-18 15:28

I had an issue this morning doing an upgrade through the Sonarr GUI. The ownership of the binary directory should be the sonarr user. Here's a quick patch:

sed -i '/chown/ a \        chown -R sonarr: /usr/lib/sonarr' sonarr.install

Thanks!

shining235 commented on 2018-03-03 16:27

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

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

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

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

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?

Anonymous comment on 2017-07-28 20:31

@springer

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

springer commented on 2017-07-19 11:06

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

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.