http://bugs.winehq.org/show_bug.cgi?id=58430
Bug ID: 58430 Summary: Clip Studio Paint 4.0 EX Crashes when trying to save or export a project Product: Wine Version: 10.11 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: dalister07@gmail.com Distribution: ---
Created attachment 78852 --> http://bugs.winehq.org/attachment.cgi?id=78852 A Crash Log Created by wine after trying to save the project.
After applying all the needed workarounds to launch the program, trying to save a project or export it with the file menu causes it to hard crash, completely killing the program and triggering the wine debugger. Tried to save the project, export it into 3 different formats, and use save as in the file menu, all of which yielded the same result of hard crashing. Distro is CatchyOS (Arch-based), With the wine version being from wine-git. Log is Attached.
http://bugs.winehq.org/show_bug.cgi?id=58430
Dani dalister07@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Distribution|--- |ArchLinux
http://bugs.winehq.org/show_bug.cgi?id=58430
--- Comment #1 from Dani dalister07@gmail.com --- Also apologies if this bug report seems a bit crude, its my first time trying to report these bugs...
http://bugs.winehq.org/show_bug.cgi?id=58430
Ken Sharp imwellcushtymelike@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- URL| |https://www.clipstudio.net/ | |en/dl/ Severity|major |normal Keywords| |download
--- Comment #2 from Ken Sharp imwellcushtymelike@gmail.com --- It's a good first bug, thank you. Just be aware of the "Importance" (Severity) ratings. This is not major. https://bugs.winehq.org/page.cgi?id=fields.html The link in Bugzilla is incorrect (will fix).
Please remember to link bugs to the AppDB to avoid duplicates in the future. https://appdb.winehq.org/objectManager.php?sClass=version&iId=42586
Did you use any older versions of Wine?
http://bugs.winehq.org/show_bug.cgi?id=58430
--- Comment #3 from Dani dalister07@gmail.com --- Created attachment 78864 --> http://bugs.winehq.org/attachment.cgi?id=78864 The Output of running CSP in terminal and trying to save the project
http://bugs.winehq.org/show_bug.cgi?id=58430
--- Comment #4 from Dani dalister07@gmail.com --- I was using the latest version of wine stable for my distro, 10.9-2, Though to test this and get CSP to originally run in the first place, i changed to the wine-git version on the aur, which is currently running version 10.11. (Because the stable wine was missing a fix that makes csp boot in the first place) I have also provided the output of running csp in the terminal since i seem to have forgot last time.
http://bugs.winehq.org/show_bug.cgi?id=58430
Ignacy Kuchciński ignacykuchcinski@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |ignacykuchcinski@gmail.com
--- Comment #5 from Ignacy Kuchciński ignacykuchcinski@gmail.com --- (In reply to Dani from comment #0)
Created attachment 78852 [details] A Crash Log Created by wine after trying to save the project.
After applying all the needed workarounds to launch the program, trying to save a project or export it with the file menu causes it to hard crash, completely killing the program and triggering the wine debugger. Tried to save the project, export it into 3 different formats, and use save as in the file menu, all of which yielded the same result of hard crashing. Distro is CatchyOS (Arch-based), With the wine version being from wine-git. Log is Attached.
Hi, the first crash log you provided seems to indicate that you're using the Windows 10 compatibility mode, did you not run into the https://bugs.winehq.org/show_bug.cgi?id=58254, which would cause crashing on launching ClipStudioPaint.exe itself? Also, what workarounds did you use?
http://bugs.winehq.org/show_bug.cgi?id=58430
--- Comment #6 from Ignacy Kuchciński ignacykuchcinski@gmail.com --- (In reply to Dani from comment #3)
Created attachment 78864 [details] The Output of running CSP in terminal and trying to save the project
Could you provide the full log since starting in terminal?
http://bugs.winehq.org/show_bug.cgi?id=58430
--- Comment #7 from Dani dalister07@gmail.com --- Sorry for being so late, but the workaround i used to make it launch, based on this appdb report/test results for 4.x https://appdb.winehq.org/objectManager.php?sClass=version&iId=42586 , which involved setting the exe of CSP itself to run in 8.1 mode (any other version would cause it to crash on boot), and anything relating to CLIP STUDIO (its launcher) would have to have edge installed along with webview in order to view the pages and make the launcher function, But that isnt related to CSP itself.
http://bugs.winehq.org/show_bug.cgi?id=58430
--- Comment #8 from Ignacy Kuchciński ignacykuchcinski@gmail.com --- (In reply to Dani from comment #7)
Sorry for being so late, but the workaround i used to make it launch, based on this appdb report/test results for 4.x https://appdb.winehq.org/objectManager.php?sClass=version&iId=42586 , which involved setting the exe of CSP itself to run in 8.1 mode (any other version would cause it to crash on boot), and anything relating to CLIP STUDIO (its launcher) would have to have edge installed along with webview in order to view the pages and make the launcher function, But that isnt related to CSP itself.
No worries, thanks for the clarification.
Based on this information I tried reproducing with following steps:
1. Download CSP from https://www.clipstudio.net/en/purchase/complete_win/ - The version downloaded is CSP_403w_setup.exe with sha1sum 5f065c2a5231862badea072af3d35b3a7ecfc294 2. Install in clean wine 10.12 prefix with default Windows 10 compatibility 3. Change Windows version to 8.1 specifically for ClipStudioPaint.exe in winecfg 4. Run CLIPStudio.exe, login with a license to get EX version, try save and export
I still couldn't reproduce, so additional information on anything different would be appreciated, especially full log, since that will allow me to try to fix this without being able to debug it on my end ;)