Page 1 of 1
Mono 5.8 seriously bugged
Posted: Fri Jul 06, 2018 6:22 pm
by dhstsw
Re: Mono 5.8 seriously bugged
Posted: Sat Jul 21, 2018 4:57 pm
by dhstsw
PLS Asustor, fix the bugs afflicting 5.8, as reported in the above thread.
I understand you're busy releasing new NAS models but the best way to sell them is to actually have a working apps echosystem for them, not rushed and untested releases as the above.
Just to say.
Re: Mono 5.8 seriously bugged
Posted: Tue Jul 24, 2018 5:00 am
by ShaMana
Come on, please fix Mono.
Re: Mono 5.8 seriously bugged
Posted: Thu Aug 02, 2018 5:53 am
by ShaMana
The last update made things much worse. Apps are failing
Re: Mono 5.8 seriously bugged
Posted: Sat Dec 01, 2018 7:41 pm
by Ragtag
Please update to latest Mono I can't update apps and they are failing!
Re: Mono 5.8 seriously bugged
Posted: Tue Dec 04, 2018 4:26 pm
by Marco@ASUSTOR
I felt I had to register for this sole purpose. I upgraded mono the other day to a release done this summer and now jackett/sonarr indexers don't work due to:
Jackett.Common.IndexerException: Exception (idopeclone): The authentication or decryption has failed. ---> System.Net.Http.HttpRequestException: An error occurred while sending the request ---> System.Net.WebException: Error: SecureChannelFailure (The authentication or decryption has failed.) ---> System.IO.IOException: The authentication or decryption has failed. ---> System.IO.IOException: The authentication or decryption has failed. ---> Mono.Security.Protocol.Tls.TlsException: The authentication or decryption has failed.
at Mono.Security.Protocol.Tls.RecordProtocol.EndReceiveRecord (System.IAsyncResult asyncResult) [0x00049] in /root/asustor/trunk/trunk_g3/source/mono-5.8.1.0/mcs/class/Mono.Security/Mono.Security.Protocol.Tls/RecordProtocol.cs:434
at Mono.Security.Protocol.Tls.SslClientStream.SafeEndReceiveRecord (System.IAsyncResult ar, System.Boolean ignoreEmpty) [0x00000] in /root/asustor/trunk/trunk_g3/source/mono-5.8.1.0/mcs/class/Mono.Security/Mono.Security.Protocol.Tls/SslClientStream.cs:256
at Mono.Security.Protocol.Tls.SslClientStream.NegotiateAsyncWorker (System.IAsyncResult result) [0x00071] in /root/asustor/trunk/trunk_g3/source/mono-5.8.1.0/mcs/class/Mono.Security/Mono.Security.Protocol.Tls/SslClientStream.cs:418
--- End of inner exception stack trace ---
at Mono.Security.Protocol.Tls.SslClientStream.EndNegotiateHandshake (System.IAsyncResult result) [0x00033] in /root/asustor/trunk/trunk_g3/source/mono-5.8.1.0/mcs/class/Mono.Security/Mono.Security.Protocol.Tls/SslClientStream.cs:397
at Mono.Security.Protocol.Tls.SslStreamBase.AsyncHandshakeCallback (System.IAsyncResult asyncResult) [0x0000c] in /root/asustor/trunk/trunk_g3/source/mono-5.8.1.0/mcs/class/Mono.Security/Mono.Security.Protocol.Tls/SslStreamBase.cs:101
Is this getting updated any time soon or do I need to switch to a NAS that is actually being maintained?
Is mono going to get updated soon?
Hi everyone. Mono was updated already. It's in Beta Apps because we are having difficulties with a third party app, namely Zappiti server. Putting it in Beta Apps allows us to have two simultaneous versions while we figure out how to deal with this third party app. I already said this.