[Bug 46112] New: photoshop 5.5 (from 1999, NOT CS5) crashes on startup following Ubuntu automatic upgrade
https://bugs.winehq.org/show_bug.cgi?id=46112 Bug ID: 46112 Summary: photoshop 5.5 (from 1999, NOT CS5) crashes on startup following Ubuntu automatic upgrade Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: blocker Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: gtoal(a)gtoal.com Distribution: --- Created attachment 62746 --> https://bugs.winehq.org/attachment.cgi?id=62746 terminal backtrace output on crash starting photoshop 5.5 (the old one from 1999) which was installed and working OK in August of this year now crashes with a memory write error on startup as soon as the main winow is drawn. This is particularly frustrating as Linux+Wine was the only remaining way to run this software - it no longer installs on Win10. -- 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=46112 --- Comment #1 from Nikolay Sivov <bunglehead(a)gmail.com> --- What's changed since August? Did you install something else in this prefix, did you update wine? -- 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=46112 --- Comment #2 from Graham Toal <gtoal(a)gtoal.com> --- Created attachment 62748 --> https://bugs.winehq.org/attachment.cgi?id=62748 linux automatic updates since initial wine installation in august from script session so may have some extra chars in text -- 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=46112 --- Comment #3 from Graham Toal <gtoal(a)gtoal.com> --- (In reply to Nikolay Sivov from comment #1)
What's changed since August? Did you install something else in this prefix, did you update wine?
I didn't update wine that I'm aware of, but the Nov update was a big one from Ubuntu 16 to Ubuntu 18 and may have included it. I've done my best to include the installation and update logs from august to today. if a wine update snuck in, it should be in that log file. I also took a smaller update immediately prior to the recent attempt to run photoshop that triggered this report. If you know of a better command to list what has been automatically updated, please let me know and I'll run it for you. -- 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=46112 Austin English <austinenglish(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|blocker |normal Version|unspecified |3.0 -- 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=46112 Anastasius Focht <focht(a)gmx.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |focht(a)gmx.net Keywords| |download URL| |ftp://ftp.adobe.com/pub/ado | |be/photoshop/win/5.x/ --- Comment #4 from Anastasius Focht <focht(a)gmx.net> --- Hello folks, I can't reproduce the crash with Photoshop 5.5 commercial and trial version on old Wine 3.0 with Winver 'Windows XP' setting (mimicking the environment from your backtrace). Starts fine here. I even went that far to use Wine 1.6.2 to install it (based on your upgrade logs) --- snip --- 2018-09-15 17:18:57 status installed wine:i386 1:1.6.2-0ubuntu14.2 2018-09-15 17:18:57 remove wine:i386 1:1.6.2-0ubuntu14.2 <none> ... 2018-09-15 18:51:47 status installed wine-stable:all 3.0-1ubuntu1 --- snip --- and use Wine 3.0 to run it (with prefix update). --- snip --- =>0 0x0086e140 in photoshp (+0x46e140) (0x01c9ec40) --- snip --- I placed a breakpoint at this instruction but couldn't trigger any code path to it, trying out various things (loading example pictures, modify ...). The function scope is entered but not that code path. My guess would be you have some "customizations" in that WINEPREFIX (recycled prefix, multiple software installations, additional plugins, additional colour profiles) which just results in a broken WINEPREFIX after the upgrade to a more recent Wine version. If the version jump from the Wine upgrade is very large, Wine sometimes can't seamlessly update the WINEPREFIX on every aspect (folder structures, files, registry). Reinstall the app in a clean (new) WINEPREFIX using the new Wine version. $ sha1sum Adobe\ Photoshop\ 5.5.7z c3edc9730834f32dc614cd646c1316993a4d89fd Adobe Photoshop 5.5.7z $ du -sh Adobe\ Photoshop\ 5.5.7z 100M Adobe Photoshop 5.5.7z $ sha1sum ps55try.exe b46616b781e4a04cc540c4acfc03ae3883d372d7 ps55try.exe $ du -sh ps55try.exe 73M ps55try.exe n550[~/Downloads] wine --version wine-3.0 Regards -- 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=46112 --- Comment #5 from Graham Toal <gtoal(a)gtoal.com> --- Created attachment 62759 --> https://bugs.winehq.org/attachment.cgi?id=62759 how I am invoking photoshop, with 'fixme' line in output This is the first installation of Wine on this system (actually the first time I've used Wine for a program I need - I last looked at it something like 20 years ago and haven't had a need for it since) so there shouldn't be any issues with multiple installations or mangled configurations. I hadn't heard of WINEPREFIX and am not aware of having changed any config parameters. The only thing I've done other than install wine and then install photoshop was to write a small shell wrapper to invoke photoshop under wine in a way that would let me run it easily from the command line when logged in to my unix from a shell over Putty from a Windows10 PC, with XMing running for display. The error occurs whether it is invoked remotely or from the X Console locally. I'll attach a log to show the script and I've executed the contents of the script by hand to show the environment variables it sets up. One interesting thing did show up when I ran it by hand - usually I send stderr to null to hide a couple of non-fatal but annoying messages. This time I did not suppress stderr and I see a line in the output marked 'fixme' - is that perhaps a clue? I'll now uninstall and reinstall Wine (actually I'll just move .wine to .wine.old and create a new installation from scratch) and see if the problem persists. Thank you for putting so much effort into checking this out -- 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=46112 --- Comment #6 from Graham Toal <gtoal(a)gtoal.com> --- Created attachment 62760 --> https://bugs.winehq.org/attachment.cgi?id=62760 attempts at uninstalling -- 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=46112 --- Comment #7 from Graham Toal <gtoal(a)gtoal.com> --- Any hints as to how to remove wine to do a clean reinstallation? There's a problem with it being a virtual package and none of the solutions I've found on the net help or are relevant. -- 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=46112 --- Comment #8 from Graham Toal <gtoal(a)gtoal.com> --- FYI since I haven't yet been able to uninstall wine, I tried just installing the photoshop 5.5 tryout that you linked to which installs into a separate windows directory from the full photoshop cd. The tryout binary crashes in the same way. I guess this confirms that the issue is with my wine installation itself rather than anything messed up in the photoshop installation (although I would have asserted that anyway as I haven't touched the photoshop installation - no extra plugins or other changes) Other .exe's in the wine environment (eg wordpad) do run OK so whatever is causing PhotoShp.exe to crash is not causing all binaries to crash. -- 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=46112 --- Comment #9 from Graham Toal <gtoal(a)gtoal.com> --- Status - have not yet reinstalled wine - the call below is to the same installation that was crashing. All I've done here is move .wine to .wine.ORIG and create a new .wine tree: $ wine wineboot $ winecfg $ ls -lR .wine|more $ cd .wine/drive_c/'Program Files' $ mv ~/.wine.ORIG/drive_c/Program\ Files/Adobe . $ cd Adobe/'Photoshop 5.5' $ wine Photoshp.exe Photoshop now runs without crashing. The rebuilt .wine prefix seems to have fixed the problem so either the problem is in some binary in that tree or in the pseudo-registry file. I did tar a copy of the old .wine before doing anything today so old and new are available for comparison if the cause of this issue is worth tracking down, but since I now have a working solution I'm OK with closing the ticket unless you want to drill down on it further. Thank you for the help. -- 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=46112 Anastasius Focht <focht(a)gmx.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED Summary|photoshop 5.5 (from 1999, |Adobe Photoshop 5.5 (from |NOT CS5) crashes on startup |1999, NOT CS5) crashes on |following Ubuntu automatic |startup following Ubuntu |upgrade |automatic upgrade (broken | |WINEPREFIX) --- Comment #10 from Anastasius Focht <focht(a)gmx.net> --- Hello Graham, --- quote --- Photoshop now runs without crashing. The rebuilt .wine prefix seems to have fixed the problem so either the problem is in some binary in that tree or in the pseudo-registry file. I did tar a copy of the old .wine before doing anything today so old and new are available for comparison if the cause of this issue is worth tracking down, but since I now have a working solution I'm OK with closing the ticket unless you want to drill down on it further. --- quote --- well, diagnosing the reason for the brokenness of the WINEPREFIX could be certainly interesting - not much of a challenge though. Unfortunately, I have way too many other higher priority/more interesting issues in my queue to process :-) Resolving 'invalid' here (broken WINEPREFIX). Regards -- 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=46112 Gijs Vermeulen <gijsvrm(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #11 from Gijs Vermeulen <gijsvrm(a)gmail.com> --- Closing. -- 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