INTERACT FORUM
More => Old Versions => JRiver Media Center 22 for Linux => Topic started by: ReinaldoRauch on July 08, 2017, 09:20:02 am
-
Hi, first post here.
My Media Center 22/23 does not keep activated on my Manjaro machine and I need to keep restoring my license on that.
As the page on the wiki says https://wiki.jriver.com/index.php/Restoring_a_License, I checked everything and it's all right even the clock so I don't know what's the problem.
My licence is a master license mc 23 upgraded from 22.
Thanks for your attention and pacience.
-
Likely this issue (and there's this fix):
https://yabb.jriver.com/interact/index.php/topic,109391.msg757477.html#msg757477
-
Thanks a lot for the reply, that resolved my issue. Sorry, could not find that thread before.
-
I'm starting to notice this again on straight Arch Linux every day. I believe there was a Network Manager update not too long ago. I wonder if they broke the workaround?
-
This issue has been an ongoing pain for me as I use my computer tethered to my phone half the time. When I tether, I immediately lose my license, I hypothesize because the computer shows my phone's mac address as its mac address, which breaks the registration. I need to be able to use that computer both on wifi and tethered, so I've just given up keeping MC registered on that machine, and keep using the trial period and re-registering every month or so (or use other players if I get caught out).
I know product registration is a "close hold" issue, but it would be nice if the strict MAC address checking could be relaxed as it's going to be a less and less reliable indicator going forward (as MAC randomization is already standard in GNU/Linux, is coming to android, and may follow to other OSs).
-
Just to let you know we are looking for a solution for this...
-
For the last couple days it's been holding, so I'm hopeful.
-
Same here on Manjaro with KDE Plasma. Applied the fix as sugessted, w/o any success.
:'(
-
Sorry for the late reply but don't know if that fix really worked or actually something else broken it. Kinda pain in the a*** :(.
Unfortunally I'm not too deep into Arch/Manjaro or debugging these kind of issues to help find out what's going on.
-
Build 23.0.25 in the beta repo attempts to fix this.
You will need to register your MC one more time, then the Mac address randomization should be OK.
Feedback desired.
-
22.108. worked for a few days w/o complaining. After a system update from Manjaro today again "not registered, 1 day remaining"
Don't want to update to v23 to get this fixed.
-
23.0.25 beta been holding well for the last couple days on Arch Linux without issue (I reversed the NetworkManager.conf fix to test this).
Not sure if this is going to be backported to MC22 as development has ceased. Though, I do agree this would be a major issue with MC 22 (even 20 and 21 too).
-
Build 23.0.25 in the beta repo attempts to fix this.
You will need to register your MC one more time, then the Mac address randomization should be OK.
Feedback desired.
How do I download the new beta version throught pacman?
Edit: I already upgraded to the 23 version license. Should I open another thread on MC23 version subforum?
-
Oh, that takes a lot of wizardry as the MC package on AUR doesn't update for betas. Personally I manually make my own PKGBUILD and used that to install to the beta. I guess I really should do a Arch Linux tutorial, but I just don't have the time to do it.
IMO, I'd wait for the next release on the latest channel (so the AUR package can be updated). Then use a AUR helper like Pacaur to install/update it.
-
Nah, that's okay for me, I use my manjaro machine most for work and then I don't use MC a lot that would worth change the PKGBUILD.
Anyways, thanks for fixing that issue. <3
-
Unfortunately issue is still existing. Need to re-active nearly every time when I restart my PC (fixed LAN).
Solution would be highly appreciated, if you don't want to provide new .mjr-files every week ;)
-
The issue has only been fixed in MC23 in build 23.0.28 and above.
There *may* not be an update for MC22 or older builds, as development has officially ended. It's up to the dev team whether or not they want to issue a MC22 update with the changes to the registration system which combats this issue. But honestly, I wouldn't hold my breath for an update to MC22, but you never know, this *is* a special sort of issue.