Topic: mc 24 loses the license (Read 3208 times)

geier22 · « **on:** April 28, 2018, 06:57:08 am »

I wrote a contribution in the German forum, because I can explain it badly in English.
https://yabb.jriver.com/interact/index.php/topic,115659.msg799262.html#msg799262
I posted log files in the german thread.
Conclusion:
I am unable to register MC 24 for more than one day.
I deleted everything from MC (including * ~ / home /.jriver and ~ home / JRiver) this morning. Restored the license. Restart - Updates from Debian Hibernate -.
6 Hours later, the license is disappearing.
I think that is at least 10 times now

mwillems · « **Reply #1 on:** April 28, 2018, 07:42:09 am »

Does the machine connect to the internet using wi-fi and network manager? If so you're probably getting caught by this issue:
https://yabb.jriver.com/interact/index.php/topic,109391.msg757477.html#msg757477

geier22 · « **Reply #2 on:** April 28, 2018, 07:58:59 am »

Only wired

Code: [Select]

ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.0.40  netmask 255.255.255.0  broadcast 192.168.0.255
        inet6 fe80::5680:2019:2ea0:4954  prefixlen 64  scopeid 0x20<link>
        inet6 fd00::270a:23e5:2608:d075  prefixlen 64  scopeid 0x0<global>
        ether d0:50:99:71:41:8f  txqueuelen 1000  (Ethernet)
        RX packets 35026  bytes 34436964 (32.8 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 28676  bytes 3855227 (3.6 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Lokale Schleife)
        RX packets 181  bytes 28685 (28.0 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 181  bytes 28685 (28.0 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

geier22 · « **Reply #3 on:** April 28, 2018, 08:20:15 am »

What happens there? License renewed for the umpteenth time. Mc left open. Suspend to RAM.

JimH · « **Reply #4 on:** April 28, 2018, 09:05:05 am »

Is the MAC address changing? That's what mwillems discovered in the thread he linked to.

geier22 · « **Reply #5 on:** April 28, 2018, 09:19:53 am »

no
first

Code: [Select]

ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.0.40  netmask 255.255.255.0  broadcast 192.168.0.255
        inet6 fe80::5680:2019:2ea0:4954  prefixlen 64  scopeid 0x20<link>
        inet6 fd00::270a:23e5:2608:d075  prefixlen 64  scopeid 0x0<global>
        ether d0:50:99:71:41:8f  txqueuelen 1000  (Ethernet)
        RX packets 35026  bytes 34436964 (32.8 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 28676  bytes 3855227 (3.6 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

after Suspend to RAM

Code: [Select]

ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.0.40  netmask 255.255.255.0  broadcast 192.168.0.255
        inet6 fe80::5680:2019:2ea0:4954  prefixlen 64  scopeid 0x20<link>
        inet6 fd00::270a:23e5:2608:d075  prefixlen 64  scopeid 0x0<global>
        ether d0:50:99:71:41:8f  txqueuelen 1000  (Ethernet)
        RX packets 186812  bytes 206847525 (197.2 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 130441  bytes 12257514 (11.6 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

after reboot

Code: [Select]

ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.0.40  netmask 255.255.255.0  broadcast 192.168.0.255
        inet6 fd00::270a:23e5:2608:d075  prefixlen 64  scopeid 0x0<global>
        inet6 fe80::5680:2019:2ea0:4954  prefixlen 64  scopeid 0x20<link>
        ether d0:50:99:71:41:8f  txqueuelen 1000  (Ethernet)
        RX packets 148  bytes 179871 (175.6 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 134  bytes 13678 (13.3 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

I have a triple boot system (all Debian Buster). Now I have tested this in LXQT. MC 23 + MC 24 are installed there. MC open ----> Suspend to RAM ------> MC has lost the license .

The same with MC 23 on LXQT ----> MC 23 does not lose the license.

geier22 · « **Reply #6 on:** April 28, 2018, 09:44:02 am »

Here is the logfile (I deleted the previous content first) form LXQT
License restored (open with) ----> Suspending to RAM ------> License lost ------> License restored

The same in KDE

geier22 · « **Reply #7 on:** April 28, 2018, 05:00:23 pm »

I have MC23 installed again because I am tired of restoring the license several times a day.
Why does MC 24 nees a constant connection to the internet?
Because that does not happen with MC 23.

Awesome Donkey · « **Reply #8 on:** April 29, 2018, 05:45:42 am »

Odd issue, I haven't encountered this running Arch Linux, Ubuntu 18.04, Linux Mint 18.3 or Debian Stretch. It *could* be one of the side-effects from running Debian Testing (Buster), especially if it's happening to all your Buster installs. Something could've changed in one of the newer packages in Buster, which is causing MC24's licensing to be lost as a result. It's worth mentioning that running MC on Debian Testing or Debian Unstable *may* be considered unsupported since there's too many things that could go wrong, like this.

Personally, I wouldn't recommend using Debian Testing or Debian Unstable if you're intending to run MC on the system. Right now, I'd recommend Debian Stable (Stretch), Ubuntu or Linux Mint.

geier22 · « **Reply #9 on:** April 29, 2018, 06:10:26 am »

At the same time there is support for many Distros here in the forum?

Strangely, MC 23 does not lose the license. So it seems that JRiver made some changes in licensing.

But OK. I then use MC 23.

Thanks for the good support.

For the purchase of the MC 24 Master license, which I no longer need, you do not need to thank you

Awesome Donkey · « **Reply #10 on:** April 29, 2018, 06:49:03 am »

Quote from: geier22 on April 29, 2018, 06:10:26 am

At the same time there is support for many Distros here in the forum?

Unofficial support. The only officially supported distro(s) by JRiver are Debian Jessie (and probably Debian Stretch soon).

Quote from: geier22 on April 29, 2018, 06:10:26 am

So it seems that JRiver made some changes in licensing.

It's possible. Could be other possibilities like incorrect file permissions within the ~/.jriver/Media Center 24 folder (or specific files, e.g. Machine Settings.ini in ~/.jriver/Media Center 24/Settings). But something is definitely causing the licensing to be lost.

If it's an issue that affects all Buster installs in general, I'm sure Bob will probably want to look into it before Buster becomes stable.

geier22 · « **Reply #11 on:** April 29, 2018, 07:32:10 am »

Quote from: Awesome Donkey on April 29, 2018, 06:49:03 am

Unofficial support. The only officially supported distro(s) by JRiver are Debian Jessie (and probably Debian Stretch soon).

That means that there is only official support for Debian old stable?
But then you have to say: MC only supports 3 years old machines. Newer ones are not supported because of kernel 3.16.0-4.
That can not be serious.
What would Windows users say if you do not support Windows 10?

Quote from: Awesome Donkey on April 29, 2018, 06:49:03 am

It's possible. Could be other possibilities like incorrect file permissions within the ~/.jriver/Media Center 24 folder (or specific files, e.g. Machine Settings.ini in ~/.jriver/Media Center 24/Settings). But something is definitely causing the licensing to be lost.

Ok.- Here are all the permissions of directory ~ / .jriver / Media Center 24 /

Hendrik · « **Reply #12 on:** April 29, 2018, 07:40:49 am »

We support released versions of Debian, that is Jessie and Stretch right now. Pre-release versions like unstable or testing are not supported. This is the same rule that applies to all operating systems, we also don't support Windows Insider builds. If you run them, you're on your own.
The reason for that is simple - they are basically a moving target and change too much.

Awesome Donkey · « **Reply #13 on:** April 29, 2018, 07:46:20 am »

Quote from: geier22 on April 29, 2018, 07:32:10 am

That means that there is only official support for Debian old stable?
But then you have to say: MC only supports 3 years old machines. Newer ones are not supported because of kernel 3.16.0-4.

As I said, right now they still mainly support Jessie because that's the distro they target/build MC24 on right now. They did for a short time move to Stretch last summer, but MC23 would no longer run on certain distros running older, incompatible libraries (e.g. Ubuntu 16.04 LTS and Linux Mint 18.x). Ultimately this meant they had stay with targeting and building MC on Jessie for the sake of compatibility (even though they don't officially support those). With the release of Ubuntu 18.04 LTS (and Linux Mint 19 soon) they can finally move on to targeting/building MC on Stretch. This doesn't really have anything to do with the version of the kernel used either - as it stands right now MC24 runs fine in Debian Stretch (even though it's built on Jessie). I'm running it in a Stretch VM right now with no issues.

Quote from: geier22 on April 29, 2018, 07:32:10 am

What would Windows users say if you do not support Windows 10?

Windows is not Linux.

geier22 · « **Reply #14 on:** April 29, 2018, 07:53:16 am »

Again and finally:
Since the first version of MC for Linux I use Debian-Testing.
All versions of MC ran on this system.
MC 23 also runs on all Debian systems without problems.
But MC 24 not.
You have made changes. Not Debian.

Awesome Donkey · « **Reply #15 on:** April 29, 2018, 07:54:54 am »

Even so, Debian Testing is not supported by JRiver, so you're on your own.

JimH · « **Reply #16 on:** April 29, 2018, 07:55:36 am »

Awesome Donkey is a user like you. He doesn't work for JRiver, though he knows a lot more than I do, and I work for JRiver. So does Hendrik.

geier22 · « **Reply #17 on:** April 29, 2018, 07:59:04 am »

Quote from: JimH on April 29, 2018, 07:55:36 am

Awesome Donkey is a user like you. He doesn't work for JRiver, though he knows a lot more than I do, and I work for JRiver. So does Hendrik.

I know it. And I also meant jriver and not Awesome Donkey.
But that does not matter now.

Awesome Donkey · « **Reply #18 on:** April 29, 2018, 07:59:21 am »

Quote from: JimH on April 29, 2018, 07:55:36 am

Awesome Donkey is a user like you. He doesn't work for JRiver, though he knows a lot more than I do, and I work for JRiver.

Correct. I might write up, post and maintain the tutorials (as a normal user) for Ubuntu and Linux Mint, but those distros are not supported by JRiver. As just a normal user, any issues I encounter running MC on Arch Linux, Ubuntu, Linux Mint. etc. I have to either fix myself or simply ignore them. However, if I can reproduce the issue(s) in Debian Stretch, then I'll report them.

One last thing you might try is doing a library backup first, making sure MC24 is closed and deleting the Media Center 24 folder in ~/.jriver and see if that helps any. Also make sure you don't ever run MC as root/su/sudo/admin because that will mess things up.

geier22 · « **Reply #19 on:** April 29, 2018, 08:18:55 am »

Awesome Donkey, I did not expect any solution from you either. I can not imagine that nobody from the developer team installed Mediacenter on Debian Testing.
Rather, I would have thought that the answer would have been the following:
if we can reproduce it we will (maybe) take care of it. But it is not our priority.
But none of it. Only - no support.

Hendrik · « **Reply #20 on:** April 29, 2018, 08:35:24 am »

You should be aware that you started your thread on a Saturday. I do not know what Bob is or is not aware of, but you won't get any answers before the next work-day.

bob · « **Reply #21 on:** April 30, 2018, 01:02:33 pm »

Quote from: geier22 on April 29, 2018, 08:18:55 am

Awesome Donkey, I did not expect any solution from you either. I can not imagine that nobody from the developer team installed Mediacenter on Debian Testing.
Rather, I would have thought that the answer would have been the following:
if we can reproduce it we will (maybe) take care of it. But it is not our priority.
But none of it. Only - no support.

Licensing did change in MC24 for Linux.

Would you please send me a log and a copy/paste of
cat /proc/cpuinfo
from a terminal.

bob (at) jriver (dot) com

Thanks.

geier22 · « **Reply #22 on:** April 30, 2018, 03:34:19 pm »

Thanks for the answer.
I sent you everything you wanted.

Boerd · « **Reply #23 on:** May 09, 2018, 10:56:17 pm »

Quote from: geier22 on April 28, 2018, 06:57:08 am

I wrote a contribution in the German forum, because I can explain it badly in English.
https://yabb.jriver.com/interact/index.php/topic,115659.msg799262.html#msg799262
I posted log files in the german thread.
Conclusion:
I am unable to register MC 24 for more than one day.
I deleted everything from MC (including * ~ / home /.jriver and ~ home / JRiver) this morning. Restored the license. Restart - Updates from Debian Hibernate -.
6 Hours later, the license is disappearing.
I think that is at least 10 times now

Same here - I have to enter the license again and again and again...

Awesome Donkey · « **Reply #24 on:** May 10, 2018, 03:00:25 am »

Make sure you're using 24.0.24.

geier22 · « **Reply #25 on:** May 10, 2018, 04:00:30 am »

Quote from: Awesome Donkey on May 10, 2018, 03:00:25 am

Make sure you're using 24.0.24.

I can confirm: Bob has fixed that. MC 24.0.24 works perfectly with the license - as always

BON0267 · « **Reply #26 on:** May 26, 2018, 04:50:53 am »

Hi there!
I've got more or less the same problem like geier22 - MC24 always looses (master)licence after a couple of days!
I have no multi-installation - just ubuntu 16.04 LTS. i am using MC 24.0.28 - just updated yesterday.

How do I get back to MC 24.0.24 ??

I've spent 3 installation-keys now - so I will go back to MC 23 (latest version) until the problem can be fixed.
I know that im writing on a saturday - hope to get some information next week, thank you

Regrets
Bernhard

geier22 · « **Reply #27 on:** May 26, 2018, 04:55:02 am »

Quote from: BON0267 on May 26, 2018, 04:50:53 am

Hi there!
I've got more or less the same problem like geier22 - MC24 always looses (master)licence after a couple of days!
I have no multi-installation - just ubuntu 16.04 LTS. i am using MC 24 24.24.0.28 - just updated yesterday.

I've spent 3 installation-keys now - so I will go back to MC 23 (latest version) until the problem can be fixed.
I know that im writing on a saturday - hope to get some information next week, thank you

Regrets
Bernhard

See here:
https://yabb.jriver.com/interact/index.php/topic,115942.msg801233.html#msg801233

https://yabb.jriver.com/interact/index.php/topic,115942.msg801233.html#msg801233

BON0267 · « **Reply #28 on:** May 26, 2018, 05:00:57 am »

Danke geier22

durch das gestrige Update sollte mein Problem behoben sein, oder ? ?

geier22 · « **Reply #29 on:** May 26, 2018, 05:04:25 am »

Scheint leider nicht so zu sein

Does not seem to be that way. You have to read the end of the thread

BON0267 · « **Reply #30 on:** May 26, 2018, 05:10:29 am »

I dont understand - I followed your link and with vers. 0.26 they say to do a new registry - I did this yesterday - so am I fine now or shoul I go back to MC 23 ??

By the way - geier22 - can we do this in german (somewhere else maybe)

BON0267 · « **Reply #31 on:** May 26, 2018, 05:40:51 am »

O.K.
now i got it - will wait for bug fix.

THANKS and have a nice weekend.

INTERACT FORUM

Author Topic: mc 24 loses the license (Read 3208 times)