[Bug 40458] New: Photoshop CC 2015 Amtlib issues
https://bugs.winehq.org/show_bug.cgi?id=40458 Bug ID: 40458 Summary: Photoshop CC 2015 Amtlib issues Product: Wine-staging Version: 1.9.7 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: msnduy(a)hotmail.de CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de, sebastian(a)fds-team.de Distribution: --- Created attachment 54210 --> https://bugs.winehq.org/attachment.cgi?id=54210 logs I have issues with running Photoshop CC 2015 (64bit) in Wine-Staging. It installs fine with both staging and stable (PDApp only works with Staging). But I can't start it in staging without an error although in wine stable it works normally but the user interface of photoshop is somehow not correctly rendered. Wine-Staging (Compiled from git upstream): Photoshop shows an error with the error code 16. By luck I also came across the amtlib.log file which also contained error message with the same error code, saying: 04/12/16 22:38:32:097 | [ERROR] | | | | AMT | | | 57 | Error: Failed to update RW check key ! 04/12/16 22:38:32:097 | [ERROR] | | | | AMT | | | 57 | ERROR: SLCache is not writable, hence exiting. (Errno = 16) I am sure it's the amtlib what is causing the issue as I didn't get these lines with wine-stable. The tricky part is that I don't know what patch from wine-staging is causing this issue. I attached the log files which are interesting. I am not sure now how to debug this further as the wine debug output isn't helpful either (basically the same output as wine stable). What might by broken can be Registry/memory/file access, the problem is that I don't know what api calls amtlib is doing. Well, if someone can give me further instructions how to debug the issue I would be glad. Also if you have enough time or whatsoever you could try install Photoshop CC 2015 :). -- 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=40458 super_man(a)post.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |super_man(a)post.com --- Comment #1 from super_man(a)post.com --- It could be worth to try newer wine-staging version. Also if it doesnt help you should run a regression test to figure out what patch broke the program. -- 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=40458 mrypsilons(a)gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mrypsilons(a)gmail.com --- Comment #2 from mrypsilons(a)gmail.com --- This is still happening with wine-staging 1.9.20. I found the patchset causing the problem, it's "server-Stored_ACLs". When building wine just with the patchsets server-Stored_ACLs depends on, Photoshop CC is working fine, but as soon as server-Stored_ACLs itself is applied, I get the breaking Error 16 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=40458 Sebastian Lackner <sebastian(a)fds-team.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |regression --- Comment #3 from Sebastian Lackner <sebastian(a)fds-team.de> --- (In reply to mrypsilons from comment #2)
This is still happening with wine-staging 1.9.20. I found the patchset causing the problem, it's "server-Stored_ACLs".
When building wine just with the patchsets server-Stored_ACLs depends on, Photoshop CC is working fine, but as soon as server-Stored_ACLs itself is applied, I get the breaking Error 16 message.
Could you try to track down more exactly which patch exactly is responsible? You can also use "git bisect" for that, just apply all patches as separate commits with: /path/to/patches/patchinstall.sh --backend=git --force-autoconf --all Afterwards use: git bisect good origin git bisect bad and proceed with "git bisect good/bad" until the final regression commit is found. Also, is there a demo available somewhere which can be used to reproduce this issue? -- 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=40458 --- Comment #4 from mrypsilons(a)gmail.com --- (In reply to Sebastian Lackner from comment #3)
Could you try to track down more exactly which patch exactly is responsible?
git bisect identified "server: Temporarily store the full security descriptor for file objects." as the first bad patch (patch 0004 in server-Stored_ACLs).
Also, is there a demo available somewhere which can be used to reproduce this issue?
Yes. Steps to install: - winetricks -q msxml3 vcrun2015 win7 - wget https://ccmdls.adobe.com/AdobeProducts/KCCC/1/win32/CreativeCloudSet-Up.exe - wine CreativeCloudSet-Up.exe (Only worked with non-staging for me...) - Create an Adobe account to log in - Click the install button for Photoshop CC After the installation is complete, you can start Photoshop by running Photoshop.exe in C:\Program Files\Adobe\... and start the 7 day trial. If you can see the splash screen, everything is fine, otherwise you will get the little "Error 16" dialog. -- 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=40458 --- Comment #5 from Sebastian Lackner <sebastian(a)fds-team.de> --- Fix issue should be fixed with https://github.com/wine-compholio/wine-staging/commit/8521ab33ad4e4fe84173e4... (which is included in Wine Staging 1.9.21). Could you please retest? -- 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=40458 --- Comment #6 from mrypsilons(a)gmail.com --- Can confirm the issue is fixed in wine-staging 1.9.21. Thanks for fixing this so fast, very nice! -- 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=40458 Bruno Jesus <00cpxxx(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #7 from Bruno Jesus <00cpxxx(a)gmail.com> --- (In reply to Sebastian Lackner from comment #5)
Fix issue should be fixed with https://github.com/wine-compholio/wine-staging/commit/ 8521ab33ad4e4fe84173e4d5db4617b3ec925e0c (which is included in Wine Staging 1.9.21). Could you please retest?
(In reply to mrypsilons from comment #6)
Can confirm the issue is fixed in wine-staging 1.9.21. Thanks for fixing this so fast, very nice!
Resolving fixed. -- 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=40458 Alistair Leslie-Hughes <leslie_alistair(a)hotmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #8 from Alistair Leslie-Hughes <leslie_alistair(a)hotmail.com> --- Closing Fixed Staging 3.14 -- 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)
-
wine-bugs＠winehq.org