Hi,
I've been using DCP-o-matic KDM creator 2.16.99 (Ubuntu Full GUI version) on a VM running Lubuntu 18.04.5 without any issues.
Tried upgrading to 2.18.18 but the system refuses saying a later version is already installed. Uninstalled the 2.16.99 and installed the 2.18.18. Ran the DCP-o-matic 2 program and imported the old keys for the decrypting and signing DCPs to the 2.18.18 and then selected the previous config.xml. Was unable to select the cinemas.xml file as the default filter is set to *.sqlite3. So how do I select the cinemas.xml from my previous installation?
Also, when trying to run DCP-o-matic KDM creator, program crashes with error "DCP-o-matic KDM Creator could not start. Bad_function_call".
Upgrading from 2.16.99
-
carl
- Site Admin
- Posts: 2777
- Joined: Thu Nov 14, 2013 2:53 pm
Re: Upgrading from 2.16.99
Hi,
If the 2.16.99 config files were still there, they should have been found automatically and converted. Or did you remove them first?
Is there no more detail on the "Bad_function_call" error?
If the 2.16.99 config files were still there, they should have been found automatically and converted. Or did you remove them first?
Is there no more detail on the "Bad_function_call" error?
-
Carsten
- Posts: 2947
- Joined: Tue Apr 15, 2014 9:11 pm
- Location: Germany
Re: Upgrading from 2.16.99
Normally, when uninstalling existing versions, settings should stay in place and get updated if necessary upon first start of a newer version.
Nonetheless, it is usually a good idea to back up your config files before updating - especially when you deal with encrypted DCPs and KDMs.
https://dcpomatic.com/faq/23
Nonetheless, it is usually a good idea to back up your config files before updating - especially when you deal with encrypted DCPs and KDMs.
https://dcpomatic.com/faq/23
-
kcsim99
- Posts: 7
- Joined: Sun Dec 01, 2019 12:56 pm
Re: Upgrading from 2.16.99
Ok so I did some tinkering and managed to get it working.
My config.xml and cinemas.xml are stored in a mounted smb shared folder. So I think when uninstalled my old 2.16.99 and installed the new 2.18 version, the paths for the config and cinemas defaulted back to the original paths. So it couldn’t find the old files.
Copied my old config and cinemas.xml to the default location, and edited the config.xml to point to the default paths for the cinemas.xml before starting the program. It found the old cinemas.xml and started converting automatically.
Can I suggest allowing the selection of old cinemas.xml in the settings and prompting the user to convert to the new sqlite3.
But the bug that 2.18.x didn’t allow me to install over 2.16.99 still there.
My config.xml and cinemas.xml are stored in a mounted smb shared folder. So I think when uninstalled my old 2.16.99 and installed the new 2.18 version, the paths for the config and cinemas defaulted back to the original paths. So it couldn’t find the old files.
Copied my old config and cinemas.xml to the default location, and edited the config.xml to point to the default paths for the cinemas.xml before starting the program. It found the old cinemas.xml and started converting automatically.
Can I suggest allowing the selection of old cinemas.xml in the settings and prompting the user to convert to the new sqlite3.
But the bug that 2.18.x didn’t allow me to install over 2.16.99 still there.