https://bugs.winehq.org/show_bug.cgi?id=57653
Bug ID: 57653 Summary: Software-based iLok activation doesn't seem to work in wine, gives some file I/O error Product: Wine Version: 9.17 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: el@horse64.org Distribution: ---
It seems to be the case that software-based iLok DRM ( https://paceap.com/ ) is currently broken in wine, and can't activate any license while spitting out some weird file creation error instead:
Thrift: Fri Jan 10 19:16:52 2025 TPipe::open ::CreateFile errored GLE=: errno = 2 Thrift: Fri Jan 10 19:16:52 2025 \.\pipe\com_paceap_eden_licensed_authorization: errno = 0
This means all professional audio software that uses software iLok doesn't work, and tragically pro audio software is otherwise one of the most well working software categories that I know in wine. Since iLok is so popular, this means a lot of industry standard software doesn't work, making this a potentially high impact issue for audio software.
It would therefore be nice if this could be addressed at some point. Sorry if this is just caused by some mistake on my end, but I've found others on web forums with similar problems with activations, so I believe it's not just me.
https://bugs.winehq.org/show_bug.cgi?id=57653
--- Comment #1 from el@horse64.org --- Created attachment 77806 --> https://bugs.winehq.org/attachment.cgi?id=77806 Wine output with the corresponding iLok activation error
https://bugs.winehq.org/show_bug.cgi?id=57653
--- Comment #2 from Austin English austinenglish@gmail.com ---
06bc:err:winediag:ntlm_check_version ntlm_auth was not found. Make sure that ntlm_auth >= 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution. 06bc:err:ntlm:ntlm_LsaApInitializePackage no NTLM support, expect problems
Does installing winbind make any difference?
https://bugs.winehq.org/show_bug.cgi?id=57653
--- Comment #3 from el@horse64.org --- Created attachment 77813 --> https://bugs.winehq.org/attachment.cgi?id=77813 Wine output with the corresponding iLok activation error, this time with winbind installed
https://bugs.winehq.org/show_bug.cgi?id=57653
--- Comment #4 from el@horse64.org --- Sadly, installing winbind doesn't seem to make any difference, see new log.
When I attempt reactivation the website says: "Activation updated
The activation of Melodyne on your computer has been updated for the new version. You can now close this window and work with Melodyne.
If, contrary to expectations, your Melodyne has not yet switched to the new version, please download the latest installation program from your user account and reinstall Melodyne."
But the plugin then doesn't activate. This all happened in the time span shown in the new log.
From user reports, it seems like this used to work in the past with wine, so it might be either a wine regression or some software iLok update that regressed here.
https://bugs.winehq.org/show_bug.cgi?id=57653
--- Comment #5 from el@horse64.org --- Created attachment 77815 --> https://bugs.winehq.org/attachment.cgi?id=77815 Error message when using "winetricks crypt32" (different error than when not using winetricks)
https://bugs.winehq.org/show_bug.cgi?id=57653
--- Comment #6 from el@horse64.org --- I just tested out "winetricks crypt32" but that results in a different problem where the plugin won't even load. It was worth an attempt, I guess.
https://bugs.winehq.org/show_bug.cgi?id=57653
--- Comment #7 from el@horse64.org --- I tried again copying in crypt32.dll, wintrust.dll, and imagehlp.dll manually and setting them to native, but that got me the "Melodyne has encountered a problem" error again. In any case, after all this poking around it seems to me like the activation not working with builtin wine crypt32 may be related to whatever this means:
04dc:fixme:cryptasn:CryptDecodeObjectEx Unsupported decoder for lpszStructType 1.3.6.1.4.1.311.2.1.4 04dc:fixme:cryptasn:CryptDecodeObjectEx Unsupported decoder for lpszStructType 1.3.6.1.4.1.311.2.1.4 04dc:fixme:ole:CoInitializeSecurity 0000000000000000, -1, 0000000000000000, 0000000000000000, 0, 3, 0000000000000000, 0, 0000000000000000 stub 04dc:fixme:cryptasn:CryptDecodeObjectEx Unsupported decoder for lpszStructType 1.3.6.1.4.1.311.2.1.4 04dc:fixme:cryptasn:CryptDecodeObjectEx Unsupported decoder for lpszStructType 1.3.6.1.4.1.311.2.1.4
So there's probably some sort of crypto that current software iLok wants that wine won't do.
https://bugs.winehq.org/show_bug.cgi?id=57653
--- Comment #8 from el@horse64.org --- All the software to test this is available for testing without purchase, so I thought I'd give you the info on how to test this.
Steps to reproduce:
1. Go to https://reaper.fm and get the free trial version of reaper, https://www.reaper.fm/files/7.x/reaper730_x64-install.exe using a fresh wine prefix
2. Go to https://www.celemony.com/en/trial and get "Melodyne 5 studio for Windows" ( https://www.celemony.com/cgi-bin/WebObjects/LicenseApp.woa/wa/demoRegistrati... ) and install it using the same wine prefix.
3. Launch REAPER. It will nag you since you're using the trial, wait the few seconds until it lets you click the "Buy me" button (you don't need to actually buy it).
4. In REAPER, you should be looking at a new blank project. If that's not the case, use File > New project.
5. In REAPER, add a track into the project using Track > Insert new track.
6. In REAPER, click the "FX" button on the new track, seen on the left. It should be close to the "ROUTE" button and the track number, "1". If you don't see it, resize the left-hand button area horizontally to be large enough to show it, and/or resize the track itself vertically so it's visible.
7. You should now be looking at the "Add Fx To: Track 1" window. Click FX > Scan for new plugins. Once that is completed, click the "VST3" category. You should be seeing "VST3: Melodyne (Celemony)" now. Double-click that entry to add it to the track.
8. You should now be looking at the "FX: Track 1" window. The "VST3: Melodyne" entry should be marked to your left, and in the center you should be seeing the Melodyne plugin area. It should be showing a popup saying "Welcome!" that asks you to "Activate". Most importantly, the top-right of the Melodyne plugin says: "melodyne: player". This is important to notice.
9. Click "Activate" in the melodyne dialog, which should open a website. On the website, sign up for a free trial with an e-mail of your choice.
Now what's supposed to happen at this point is if you go back to the "FX: Track 1" window that is still open, it should no longer show "melodyne: player" in the corner, but it should automatically recognize you just signed up for the trial on the website and it should change to "melodyne: studio". This happens when you're using windows natively or a windows VM, but it doesn't happen with wine 9.17.
My apologies if I forgot a step or if something is unclear.
https://bugs.winehq.org/show_bug.cgi?id=57653
--- Comment #9 from Austin English austinenglish@gmail.com --- It worked for me using wine-10.0-rc6 (Note: I closed the original tab that opened in firefox by mistake, and then used 'Copy URL' in the application and pasted that manually, which may have made the difference).
Retrying a second time and it seems like the site remembers my computer (even in incognito mode, so presumably it's by IP).