Hi @czlada,
We knew about it due to you and others, who reported it and really thank you for that, but it was not critical feature for releasing new TOS, that’s why it was not fixed. But it doesn’t mean we will ignore it.
Regarding high load, we need more time to find why it is happening, but for next minor release if you and others will confirm that v3 is fully functional we will downgrade it as temp. solution.
Hi @TomasZak ,
I understand Transmission was not a critical feature that would have prevented TOS 7.0 from deploying.
But on the other side, please consider that Transmission users like me had no way of being notified that some 6.5.2 feature were going to be missing with automatic update to 7.0.
The point is, I just lost 2 hours investigating why on earth Transmission stopped working, with the only result being finding this topic. At last.
I understand and sorry for your troubles. Now we are testing older version and I will disscuss it with @miska. But unfortunately we have no luck, why it’s eat so much cpu…
older version of transmission (version 3) was sent to hbk. So if you want you can test it if it works for you. Now it is building in new HBK so you can try it in the evening.
Might it be an option to add something like this to the “known issues” part of the release notes? That would be really great!
I am currently on 6.5.2 myself as I’m not near my device and I use things like Transmission and OpenVPN a lot. I intend to update in few weeks when I’m near my device again. Looking forward to have clarity on the status of the 7 series!!
Many thanks to everybody looking into problems like this!!
I’m still on 6.5.2 and wondering whether I should already upgrade to 7. I use Transmission quite intensively. Does it seem better to stay on 6.5.2 for now?
I think it does. My 7.0.0 had exactly the same problem with nonfunctioning Transmission, then on 7.0.1 with high CPU load.
I have reverted to 6.5.2. and all quiet on the eastern front.
Maybe someone will actually pay attention to it.