[Bug 50990] New: Photoshop CC 2021 fails to start
https://bugs.winehq.org/show_bug.cgi?id=50990 Bug ID: 50990 Summary: Photoshop CC 2021 fails to start Product: Wine Version: 6.4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: blocker Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: msdobrescu(a)gmail.com Distribution: --- Created attachment 69823 --> https://bugs.winehq.org/attachment.cgi?id=69823 error message popup Trying to run Photoshop 2021 22.3 64 bit, under wine-6.4 (Staging), fails with a message popup appears (attached). This is continuation of https://bugs.winehq.org/show_bug.cgi?id=50925, so happens including the following patches/commits, but not as effect of them: https://source.winehq.org/git/wine.git/commitdiff/c2c7946680b61bfccd4c4f5788... and https://source.winehq.org/git/wine.git/commitdiff/9d1ae850dfd73c60fbe2904c44... The above patches are necessary in order to reach this point. Logs attached. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=50990 msdobrescu(a)gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |msdobrescu(a)gmail.com --- Comment #1 from msdobrescu(a)gmail.com --- Created attachment 69824 --> https://bugs.winehq.org/attachment.cgi?id=69824 Debug log Debug log created using +relay,+seh,+tid,+crypt,+bcrypt wine64-staging -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=50990 --- Comment #2 from msdobrescu(a)gmail.com --- Created attachment 69825 --> https://bugs.winehq.org/attachment.cgi?id=69825 Runtime log -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=50990 Austin English <austinenglish(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|blocker |normal -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=50990 msdobrescu(a)gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.winehq.org/sho | |w_bug.cgi?id=50925 -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=50990 Dmitry Timoshkov <dmitry(a)baikal.ru> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Ever confirmed|0 |1 --- Comment #3 from Dmitry Timoshkov <dmitry(a)baikal.ru> --- According to the log the error you get is "Could not complete your request because Photoshop was unable to parse the PostScript." The following forum post suggests that this can happen with versions of Photoshop up to 22.2 under Windows and Mac OS, and the solution is to reinstall the Adobe Creative Cloud Desktop app, and run Photoshop from it, not directly: https://community.adobe.com/t5/photoshop/could-not-complete-your-request-bec... Does that help? P.S. Photoshop calls RaiseException() after getting error 2 (File not found) from RegOpenKeyExW(HKEY_LOCAL_MACHINE, "SOFTWARE\\Adobe\\Vulcan\\5.0") which leads to the above error message. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=50990 --- Comment #4 from Dmitry Timoshkov <dmitry(a)baikal.ru> --- (In reply to Dmitry Timoshkov from comment #3)
According to the log the error you get is "Could not complete your request because Photoshop was unable to parse the PostScript."
The following forum post suggests that this can happen with versions of Photoshop up to 22.2 under Windows and Mac OS, and the solution is to reinstall the Adobe Creative Cloud Desktop app, and run Photoshop from it, not directly:
https://community.adobe.com/t5/photoshop/could-not-complete-your-request- because-photoshop-was-unable-to-parse-the-postscript/td-p/9479775
Does that help?
P.S. Photoshop calls RaiseException() after getting error 2 (File not found) from RegOpenKeyExW(HKEY_LOCAL_MACHINE, "SOFTWARE\\Adobe\\Vulcan\\5.0") which leads to the above error message.
And one more: https://community.adobe.com/t5/photoshop/unable-to-open-photoshop-2020-photo... -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=50990 --- Comment #5 from msdobrescu(a)gmail.com --- Thank you for investigating! The long standing problem with Photoshop is being unable to install under Wine as long as the installer does not work, so the only way is to copy a successful installation under Windows. For instance, now it throws a message stating that OS is not supported, despite I have set Wine to hide Wine version from the applications. The issue here https://community.adobe.com/t5/photoshop/could-not-complete-your-request-bec... refers to opening a postscript file, but this is not the case unless Photoshop opens a postscript itself, for some reason, as part of the startup process - that being transparent to me. I just try to start an empty instance of Photoshop, not a file with Photoshop. It is not clear the second issue. Reading Wine forums I've found reference that msxml 3 is needed as native, but that does not help either. I wonder if Windows registry entries are needed, but I can't tell that yet. What about trying to troubleshoot the installing process as a new bug? -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=50990 --- Comment #6 from Dmitry Timoshkov <dmitry(a)baikal.ru> --- (In reply to msdobrescu from comment #5)
Thank you for investigating!
The long standing problem with Photoshop is being unable to install under Wine as long as the installer does not work, so the only way is to copy a successful installation under Windows. For instance, now it throws a message stating that OS is not supported, despite I have set Wine to hide Wine version from the applications.
The issue here https://community.adobe.com/t5/photoshop/could-not-complete-your-request- because-photoshop-was-unable-to-parse-the-postscript/td-p/9479775 refers to opening a postscript file, but this is not the case unless Photoshop opens a postscript itself, for some reason, as part of the startup process - that being transparent to me. I just try to start an empty instance of Photoshop, not a file with Photoshop.
It is not clear the second issue.
Both forum posts have user comments mentioning inability to run Photoshop.
Reading Wine forums I've found reference that msxml 3 is needed as native, but that does not help either.
I wonder if Windows registry entries are needed, but I can't tell that yet.
Does copying Windows installation to another Windows machine work? Alternatively, try making a backup, uninstalling, copying Photoshop from the backup, and then run it (all on the same Windows machine).
What about trying to troubleshoot the installing process as a new bug?
Sure, but please search for existing reports first. Also, it looks like Adobe doesn't allow downloading the installer without a registration and providing credit card details. So, I'd personally refrain from requesting a trial. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=50990 --- Comment #7 from msdobrescu(a)gmail.com --- I don't find that registry entry, "HKLM\\Adobe\\Vulcan\\5.0" on the Windows machine. I have copied a legit installation from my Windows machine as I have a subscription. It is strange that Windows registry contains entries for Photoshop that specify the installation path only. I must look for that Vulcan entry further. Note, it is their custom library (it's not Vulkan). -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=50990 --- Comment #8 from msdobrescu(a)gmail.com --- Is there a way to assess the crash cause? Is it possible to have an unhandled return value due to incorrect/unexpected return value or values from the Windows SDK perspective, like a NULL instead an empty string or other? What do we miss in the debug logs? Could that be a different component that also returns the wrong value? -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=50990 --- Comment #9 from msdobrescu(a)gmail.com --- Hi, it seems that fixme:crypt:CryptStringToBinaryW Unimplemented type 4 is fixed in other version/branch. Where can I get a patch for 6.4 to get this implementation? -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=50990 --- Comment #10 from Dmitry Timoshkov <dmitry(a)baikal.ru> --- (In reply to msdobrescu from comment #8)
Is there a way to assess the crash cause? Is it possible to have an unhandled return value due to incorrect/unexpected return value or values from the Windows SDK perspective, like a NULL instead an empty string or other?
What do we miss in the debug logs? Could that be a different component that also returns the wrong value?
Potentially it might be anything. Someone needs to debug this, and remote debugging is not an option. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=50990 --- Comment #11 from msdobrescu(a)gmail.com --- Hi, can it be implemented CRYPT_STRING_HEX in CryptStringToBinaryW? So far CRYPT_STRING_HEX was implemented one way only, in CryptBinaryToStringW, right? I see in the simple log that it fails there: crypt:CryptStringToBinaryW Unimplemented type 4 -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=50990 --- Comment #12 from Gijs Vermeulen <gijsvrm(a)gmail.com> --- (In reply to msdobrescu from comment #11)
Hi, can it be implemented CRYPT_STRING_HEX in CryptStringToBinaryW? So far CRYPT_STRING_HEX was implemented one way only, in CryptBinaryToStringW, right?
I see in the simple log that it fails there:
crypt:CryptStringToBinaryW Unimplemented type 4
You could try these patches: https://www.winehq.org/pipermail/wine-devel/2020-March/163102.html https://www.winehq.org/pipermail/wine-devel/2020-March/163103.html -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=50990 --- Comment #13 from msdobrescu(a)gmail.com --- Thanks! The build fails for missing strchrW definition: base64.c:(.text+0x27d): undefined reference to `strchrW' -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=50990 --- Comment #14 from msdobrescu(a)gmail.com --- What should be referred for strchrW? It is defined in wine/unicode.h, but fails at build time if I add the reference to /dlls/crypt32/base64.c. Note, Gentoo builds wine with gcc, not mingw64. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=50990 --- Comment #15 from msdobrescu(a)gmail.com --- The build error is: In file included from /var/tmp/portage/app-emulation/wine-staging-6.4-r1/work/wine-6.4/dlls/crypt32/base64.c:27: /var/tmp/portage/app-emulation/wine-staging-6.4-r1/work/wine-6.4/include/wine/unicode.h:32:2: error: #error This file should not be used with msvcrt headers Should unicode.h be changed similar to here: https://doxygen.reactos.org/d6/d51/reactos_2wine_2unicode_8h_source.html? -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=50990 --- Comment #16 from Dmitry Timoshkov <dmitry(a)baikal.ru> --- (In reply to msdobrescu from comment #14)
What should be referred for strchrW?
You can replace it with wcschr(). -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=50990 --- Comment #17 from msdobrescu(a)gmail.com --- Created attachment 69847 --> https://bugs.winehq.org/attachment.cgi?id=69847 Logs after CryptStringToBinaryW implementation I have attached trhe logs after adding CryptStringToBinaryW patches. They have changed, but can't tell which one of the two errors triggers the crash handler. log0 is the first run after the new Wine build. log1 is for the next runs. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=50990 --- Comment #18 from msdobrescu(a)gmail.com --- Hello, I moved to Wine Staging 6.6. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=50990 Jonathan <jomarocas(a)outlook.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jomarocas(a)outlook.com --- Comment #19 from Jonathan <jomarocas(a)outlook.com> --- any update of this_ i install prefix 64, and dotnet45, dotnet48, winecfg for windows 10 and still appear same message 002c:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1. 0108:fixme:mshtml:get_listener_container unimplemented event L"dragstart" 0108:fixme:mshtml:OleInPlaceActiveObject_TranslateAccelerator Unsupported message 0200 and no appear nothing, like fonts or html connection no works, thanks for any advice -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=50990 Neko-san <nekoNexus(a)protonmail.ch> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |nekoNexus(a)protonmail.ch -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
participants (1)
-
WineHQ Bugzilla