When the new version is pushed out, you may have to manually restart serviio again. All users of Serviio that has had automatic updates turned on has been affected by this. I have asked for it to be pushed to the Community ASAP. This has now been corrected and I have made a 1.5.2-2 release of serviio. My guess is that within a few days there will be a 1.5.2-2 version released that is built correctly.ĮDIT: OK The fault is found: Something has obviously gone wrong when I uploaded my 1.5.2 build to GitHub and two of the patch files got to have the same content. I have sent a message to Peter Baldwin to see what can be ASAP. I tested the new version in clearos-test earlier and that worked. It is faulty and the result is that serviio will start but crash immediately, since some needed patches has not been included in the build for some reasons. (Apologies for the delay in editing this, really busy at work this morning!!!).May 22nd a new version 1.5.2 of serviio was pushed out to the Community. I followed the link in the notification - did not help. I swapped yesterday to pure AMD, but cannot see that causing this. I wasn’t aware of me actually running any appimages, simplenote is electron (and I killed the process to no effect), cannot see anything else in the ps_mem output that could cause this.
0 Comments
Leave a Reply. |