https://bugs.winehq.org/show_bug.cgi?id=47967
Bug ID: 47967 Summary: Adobe Photoshop 7.0 cannot start Product: Wine Version: 4.18 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: wineserver Assignee: wine-bugs@winehq.org Reporter: aros@gmx.com Distribution: ---
There's a new regression in Wine. It fails to find DLLs in a program directory:
$ pwd /home/birdie
$ wine "C:\Program Files\Adobe\Photoshop 7.0\Photoshop.exe" 0009:err:module:import_dll Library ACE.dll (which is needed by L"C:\Program Files\Adobe\Photoshop 7.0\Photoshop.exe") not found 0009:err:module:import_dll Library AGM.dll (which is needed by L"C:\Program Files\Adobe\Photoshop 7.0\Photoshop.exe") not found 0009:err:module:import_dll Library BIB.dll (which is needed by L"C:\Program Files\Adobe\Photoshop 7.0\Photoshop.exe") not found 0009:err:module:import_dll Library CoolType.dll (which is needed by L"C:\Program Files\Adobe\Photoshop 7.0\Photoshop.exe") not found 0009:err:module:import_dll Library asn.er.dll (which is needed by L"C:\Program Files\Adobe\Photoshop 7.0\Photoshop.exe") not found 0009:err:module:LdrInitializeThunk Importing dlls for L"C:\Program Files\Adobe\Photoshop 7.0\Photoshop.exe" failed, status c0000135
However if I do:
$ cd "/home/birdie/.wine/drive_c/Program Files/Adobe/Photoshop 7.0" $ wine "C:\Program Files\Adobe\Photoshop 7.0\Photoshop.exe"
Everything works.
https://bugs.winehq.org/show_bug.cgi?id=47967
Artem S. Tashkinov aros@gmx.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|Adobe Photoshop 7.0 cannot |Wine fails to find |start |application DLLs when the | |working directory is not | |the application directory Keywords| |regression
https://bugs.winehq.org/show_bug.cgi?id=47967
Artem S. Tashkinov aros@gmx.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Priority|P2 |P1
--- Comment #1 from Artem S. Tashkinov aros@gmx.com --- The same applies to Adobe Photoshop CS2.
It looks like it's a major regression.
https://bugs.winehq.org/show_bug.cgi?id=47967
Artem S. Tashkinov aros@gmx.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |download URL| |https://www.techspot.com/do | |wnloads/3689-adobe-photosho | |p-cs2.html
https://bugs.winehq.org/show_bug.cgi?id=47967
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Severity|critical |normal
--- Comment #2 from Austin English austinenglish@gmail.com --- (In reply to Artem S. Tashkinov from comment #1)
The same applies to Adobe Photoshop CS2.
It looks like it's a major regression.
Can you run a regression test?
https://bugs.winehq.org/show_bug.cgi?id=47967
Fabian Maurer dark.shadow4@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |dark.shadow4@web.de
https://bugs.winehq.org/show_bug.cgi?id=47967
juliansperling@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |juliansperling@gmail.com
--- Comment #3 from juliansperling@gmail.com --- Hi,
I ran a Regression test and get 619bd16e7a7486ca72cde1df01791629efb61341 as the first bad commit.
https://bugs.winehq.org/show_bug.cgi?id=47967
juliansperling@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |julliard@winehq.org
https://bugs.winehq.org/show_bug.cgi?id=47967
--- Comment #4 from juliansperling@gmail.com --- It looks like the new way of finding the dll directory has an issue...
https://bugs.winehq.org/show_bug.cgi?id=47967
Artem S. Tashkinov aros@gmx.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Regression SHA1| |619bd16e7a7486ca72cde1df017 | |91629efb61341
https://bugs.winehq.org/show_bug.cgi?id=47967
Andreas Zuber a.zuber@gmx.ch changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |a.zuber@gmx.ch
--- Comment #5 from Andreas Zuber a.zuber@gmx.ch --- Magic the Gathering Arena does not start anymore with 4.18 and a regression test pointed to this commit.
https://bugs.winehq.org/show_bug.cgi?id=47967
Artem S. Tashkinov aros@gmx.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Severity|normal |critical
--- Comment #6 from Artem S. Tashkinov aros@gmx.com --- Lots of applications are affected, so I don't understand why this bug is just "normal".
https://bugs.winehq.org/show_bug.cgi?id=47967
Olivier F. R. Dierick o.dierick@piezo-forte.be changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |o.dierick@piezo-forte.be Severity|critical |normal
--- Comment #7 from Olivier F. R. Dierick o.dierick@piezo-forte.be --- Hello,
--- wine user guide --- Because Windows programs will often look for files in the location they were started from, when using the command line you should start them in a very specific way: "change directory" to the folder where the program is located and run the .exe file using only its filename. --- end of quote --- https://wiki.winehq.org/Wine_User%27s_Guide#How_to_run_Windows_programs_from...
Unless there were changes that I'm unaware of, this has always been the way to start windows applications from the command line (and scripts).
You can find an explanation there: https://forum.winehq.org/viewtopic.php?t=14623
If the issue only affects non-standard wine usage, then it can't be major or critical.
Please try to change to the application directory before running the command and report what happens.
Regards.
https://bugs.winehq.org/show_bug.cgi?id=47967
--- Comment #8 from Olivier F. R. Dierick o.dierick@piezo-forte.be --- Hello,
Please try to change to the application directory before running the command and report what happens.
Ignore that. You already stated that it worked. sorry.
This makes the bug normal as it affects only users that don't follow the wine user guide.
Regards.
https://bugs.winehq.org/show_bug.cgi?id=47967
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |austinenglish@gmail.com Status|UNCONFIRMED |NEW Ever confirmed|0 |1
--- Comment #9 from Austin English austinenglish@gmail.com --- I can also reproduce this with vlc: 0043:err:module:import_dll Library libvlc.dll (which is needed by L"C:\Program Files\VideoLAN\VLC\vlc.exe") not found 0043:err:module:LdrInitializeThunk Importing dlls for L"C:\Program Files\VideoLAN\VLC\vlc.exe" failed, status c0000135
Using 'wine start "C:\Program Files\VideoLAN\VLC\vlc.exe"' works, however.
https://bugs.winehq.org/show_bug.cgi?id=47967
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |russ.herman@gmail.com
--- Comment #10 from Alexandre Julliard julliard@winehq.org --- *** Bug 47976 has been marked as a duplicate of this bug. ***
https://bugs.winehq.org/show_bug.cgi?id=47967
--- Comment #11 from russ.herman@gmail.com --- @ Olivier F. R. Dierick
Unsatisfactory response. May be documented as requirement, but worked unti 3.18. Much breakage has resulted.
https://bugs.winehq.org/show_bug.cgi?id=47967
--- Comment #12 from Artem S. Tashkinov aros@gmx.com --- Just to be super annoying I've verified that Windows (at least) XP works differently.
1. I've installed VLC 3.0.8 and I've successfully run it this way:
C:\Documents and Settings\User>"c:\Program Files\VideoLAN\VLC\vlc.exe"
OK, maybe that's not enough and CMD or Windows is smart enough to change the current directory to c:\Program Files\VideoLAN\VLC (behind the scenes even though it sounds unlikely).
2. I've now modified the shortcut on the desktop, VLC.lnk, and changed "Start In" to C:\
VLC still works.
3. OK, maybe VLC has some registry entries which point to c:\Program Files\VideoLAN\VLC ?
I've now deleted everything containing VLC (regedit -> Find -> VLC -> nothing found) in registry and C:\Documents and Settings\User.
I can still successfully run VLC both from the broken LNK file and using CMD from the wrong CMD line.
I'm deeply sorry, guys, but Windows DLLs loader (ntdll?) works even when an app is run from the _wrong_ working path.
If we're talking about Windows conformance, Wine 4.18 has stopped being conformant. Please revert the old behavior.
https://bugs.winehq.org/show_bug.cgi?id=47967
--- Comment #13 from Olivier F. R. Dierick o.dierick@piezo-forte.be --- Hello,
(In reply to russ.herman from comment #11)
@ Olivier F. R. Dierick
Unsatisfactory response. May be documented as requirement, but worked unti 3.18. Much breakage has resulted.
I'm simply saying that the issue doesn't prevent the applications from running at all (they run fine when started as described in the manual). That's why the bug severity should not be 'major' or 'critical'.
I make no statement about the undocumented behavior that worked for you until 4.18. I'm following the manual since years and change the directory before starting applications in all my wrapper scripts. In this case, following the manual did prevent 'much breakage' for me.
(In reply to Artem S. Tashkinov from comment #12)
I'm deeply sorry, guys, but Windows DLLs loader (ntdll?) works even when an app is run from the _wrong_ working path.
If we're talking about Windows conformance, Wine 4.18 has stopped being conformant. Please revert the old behavior.
--- quote from the linked forum topic --- (...) Windows uses different conventions: - the loader starts by setting the current working directory to the directory that contains the program and starts it running. (...) --- end quote ---
The difference in behavior is well known and that's why there is a specific entry in the wine user's guide explaining how to achieve that with Wine.
--- quote from wine user's guide --- You need to use wine start if you specify a full path to the .exe, because that allows Wine to set the working directory for the program if it needs it. --- end quote ---
You get Windows loader conformance by using "wine start C:\fullpath\to.exe" instead of simply "wine C:\fullpath\to.exe".
Regards.
https://bugs.winehq.org/show_bug.cgi?id=47967
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |benshalom@gmail.com
--- Comment #14 from Alexandre Julliard julliard@winehq.org --- *** Bug 47984 has been marked as a duplicate of this bug. ***
https://bugs.winehq.org/show_bug.cgi?id=47967
--- Comment #15 from Artem S. Tashkinov aros@gmx.com --- It looks like Alexander has fixed this bug in git:
https://source.winehq.org/git/wine.git/commit/c258b5ef1100c8c238aab0a17ca743...
https://bugs.winehq.org/show_bug.cgi?id=47967
--- Comment #16 from juliansperling@gmail.com --- Can Confirm, Regression is resolved in current main branch of wine
https://bugs.winehq.org/show_bug.cgi?id=47967
Olivier F. R. Dierick o.dierick@piezo-forte.be changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Fixed by SHA1| |c258b5ef1100c8c238aab0a17ca | |743a326829aac Resolution|--- |FIXED
--- Comment #17 from Olivier F. R. Dierick o.dierick@piezo-forte.be --- (In reply to Artem S. Tashkinov from comment #15)
It looks like Alexander has fixed this bug in git:
https://source.winehq.org/git/wine.git/commit/ c258b5ef1100c8c238aab0a17ca743a326829aac
Hello,
Thanks for the feedback.
Marking fixed.
Regards.
https://bugs.winehq.org/show_bug.cgi?id=47967
--- Comment #18 from Artem S. Tashkinov aros@gmx.com --- Please mark bug 47964 as a dupe of this one.
https://bugs.winehq.org/show_bug.cgi?id=47967
Olivier F. R. Dierick o.dierick@piezo-forte.be changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |dav75uk@yahoo.co.uk
--- Comment #19 from Olivier F. R. Dierick o.dierick@piezo-forte.be --- *** Bug 47964 has been marked as a duplicate of this bug. ***
https://bugs.winehq.org/show_bug.cgi?id=47967
sub.drom@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |sub.drom@gmail.com
--- Comment #20 from sub.drom@gmail.com --- Would this fix be part of the new release any time soon?
https://bugs.winehq.org/show_bug.cgi?id=47967
--- Comment #21 from Austin English austinenglish@gmail.com --- (In reply to sub.drom from comment #20)
Would this fix be part of the new release any time soon?
It will be in the next release (4.19) which should be out this Friday.
https://bugs.winehq.org/show_bug.cgi?id=47967
--- Comment #22 from Alexandre Julliard julliard@winehq.org --- *** Bug 48002 has been marked as a duplicate of this bug. ***
https://bugs.winehq.org/show_bug.cgi?id=47967
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |sebastian.miele@gmail.com
--- Comment #23 from Austin English austinenglish@gmail.com --- *** Bug 48022 has been marked as a duplicate of this bug. ***
https://bugs.winehq.org/show_bug.cgi?id=47967
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #24 from Alexandre Julliard julliard@winehq.org --- Closing bugs fixed in 4.19.