Package Details: codemeter-runtime 6.50.2631.502-2

Git Clone URL: (read-only)
Package Base: codemeter-runtime
Description: codemeter runtime (server and cli tools, no GUI)
Upstream URL:
Licenses: custom
Submitter: de-vries
Maintainer: de-vries
Last Packager: de-vries
Votes: 1
Popularity: 0.003316
First Submitted: 2017-09-10 15:00
Last Updated: 2017-09-19 07:03

Latest Comments

nairolfflo commented on 2018-04-06 14:15

I figured out what my Problem was. I had to change the user in the .INSTALL before the actual install from 'codemeter' to my actual local user name so that all permissions are set correctly.

After the installation, I also had to change the declared Username in the /usr/lib/systemd/system/codemeter.service

Afterwards, I was able to start the service with $ sudo systemctl enable codemeter.service

Everything works fine now. The online-activation on the respective program publisher's works impeccable.

de-vries commented on 2018-04-05 21:26

Getting this to work reliably was absolute hell. Turned out my trying to figure out why it wasn't working by stracing it was actually part of the reason why it didn't work. Apparently it detects that and stops running after 17 seconds or so. It did work for those 17 seconds...

It also insisted on running as root, but I refuse to run some binary DRM blob as root, so I used fakeroot instead. Funnily enough it doesn't detect that. Maybe that is causing issues for you. Can't really tell with binary blobs whose main purpose is to take away control over a PC away from the owner of that PC.

I also feel pretty bad about supporting DRM by packaging this. I did it out of necessity, but the reason why I needed it (ensenso-sdk [1]) thankfully stopped using codemeter. I was actually considering orphaning this and even requesting a deletion.


All that being said, in principle the command center doesn't allow anything more than the CLI tools to. Most command line tools actually give better error details than matching GUI tools, though I don't know about codemeter specifically.

I also had some strange issues at first that turned out to be due to missing folders or wrong folder permissions (specifically /var/spool/ctmp). That's what the install script attempts to fix.

If you did a manual install at some point it is possible that left overs from the manual installation are causing problems. If possible, I would try installing on a clean system and see if it works there.

nairolfflo commented on 2018-04-05 20:13

I am trying to use this package to run Bruker's Topspin4 NMR Suite but am having the Problem that i cannot import the relevant LicenseContainer due to some errors. Would it be possible to include the CodeMeterCC from the full version? I would be very grateful since i struggled to do it myself