INTERACT FORUM

More => Old Versions => JRiver Media Center 24 for Linux => Topic started by: wellywu on June 12, 2018, 10:50:37 am

Title: Please reset my activations
Post by: wellywu on June 12, 2018, 10:50:37 am
Can someone tell me why JRiver Media Center 24 Master License for Ubuntu 18.04.0 64 bit LTS GNU/Linux keeps requiring me to put in my license code after I stop using it but keep it installed on my three Ubuntu powered gaming PCs after a period of time? I constantly have to put in the license key after a few days of not using JRiver. Please reset my license key activations again. Thank you.
Title: Re: Please reset my activations
Post by: Awesome Donkey on June 12, 2018, 12:04:27 pm
Make sure you're using 24.0.28 or 24.0.32-4 beta - there was licensing changes in those builds to help prevent the license is being lost. Keep in mind if you use 24.0.28, it'll still could randomly lose the license (possibly due to kernel updates) and also you will have to re-enter the license again once 24.0.32 (or a higher build number) is released due to additional licensing changes (probably to prevent the license from being lost due to kernel updates, etc.) from builds 24.0.31 and above.
Title: Re: Please reset my activations
Post by: wellywu on June 13, 2018, 11:03:31 am
Ok. Please wait until .31 is released before resetting my licenses again. Thanks.
Title: Re: Please reset my activations
Post by: Awesome Donkey on June 13, 2018, 11:05:33 am
It's up to 24.0.34 now, which is in the beta repo right now. But the license could be lost again due to kernel updates for Ubuntu 18.04 which was released yesterday (it happened to me yesterday) so that might need to be looked into.
Title: Re: Please reset my activations
Post by: bob on June 14, 2018, 10:19:23 am
Ok, it's going to happen again.
PM me if you need activations reset.
You can blame it on intel's buggy cpu's (or my lack of dealing with them properly).
Doesn't affect the arm build.
Title: Re: Please reset my activations
Post by: Awesome Donkey on June 14, 2018, 10:27:35 am
You can blame it on intel's buggy cpu's
I'd say it's this.