https://bugs.winehq.org/show_bug.cgi?id=50867
Bug ID: 50867 Summary: wine start /unix stopped working in 6.5 Product: Wine Version: 6.5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: duck@duckcorp.org Distribution: ---
Quack,
I just upgraded to 6.5 using WineHQ's Debian packages. My computer is using Debian unstable.
When starting my games using start /unix I now get: (leaving out fixme:font:opentype_enum_font_names lines) $ wine start /unix $WINEPREFIX/drive_c/GOG\ Games/Risen\ 3\ -\ Titan\ Lords/LanguageSetup.exe Application could not be started, or no application associated with the specified file. ShellExecuteEx failed: File not found.
If I remove start /unix in this case it works but not all programs will be happy with this unless I manually go into the right workdir, that is why I use this feature as recommended in the user's guide.
6.4 worked fine and many versions before. I did not see anything about this in the news and changelog. Has anything changed?
Regards. _o<
https://bugs.winehq.org/show_bug.cgi?id=50867
--- Comment #1 from Alexandre Julliard julliard@winehq.org --- What has changed is that Wine is more strict about requiring the file to execute to actually be found on disk. By default, start.exe is installed into c:\windows\command, which is not in the standard path, so it isn't found.
We should probably add a workaround for this case. For the time being, copying start.exe into c:\windows\system32 should work.
https://bugs.winehq.org/show_bug.cgi?id=50867
Louis Lenders xerox.xerox2000x@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |xerox.xerox2000x@gmail.com
--- Comment #2 from Louis Lenders xerox.xerox2000x@gmail.com --- (In reply to Alexandre Julliard from comment #1)
What has changed is that Wine is more strict about requiring the file to execute to actually be found on disk. By default, start.exe is installed into c:\windows\command, which is not in the standard path, so it isn't found.
I still have one in system32:
rm -rf ~/ramdisk/.wine
wine winecfg
find . -name start.exe ./drive_c/windows/command/start.exe ./drive_c/windows/system32/start.exe
Then 'wine64 start winecfg' works whereas 'wine start winecfg' fails.
Is this difference intentional? (this is self-compiled wine 6.5)
https://bugs.winehq.org/show_bug.cgi?id=50867
--- Comment #3 from Alexandre Julliard julliard@winehq.org --- We are not supposed to have the 64-bit one either, though apparently it doesn't break anything. Maybe we could simply duplicate the 32-bit one into syswow64 to fix this bug.
https://bugs.winehq.org/show_bug.cgi?id=50867
Robbert van der Helm mail@robbertvanderhelm.nl changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |mail@robbertvanderhelm.nl
https://bugs.winehq.org/show_bug.cgi?id=50867
--- Comment #4 from Robbert van der Helm mail@robbertvanderhelm.nl --- To add to this (from bug 50869), launching applications through Wine from the GUI through file associations with `wine.desktop` also no longer works in Wine 6.5 because that too uses `wine start /unix`.
https://bugs.winehq.org/show_bug.cgi?id=50867
stefan k8auf1947@cometchaser.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |k8auf1947@cometchaser.de
--- Comment #5 from stefan k8auf1947@cometchaser.de --- Hi,
I do have the same issue on Debian 10 stable and the latest Wine development-branch (not self compiled).
https://bugs.winehq.org/show_bug.cgi?id=50867
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Fixed by SHA1| |fcb37c9c123cd841debb17b6821 | |493b8b2f83473 Resolution|--- |FIXED
--- Comment #6 from Alexandre Julliard julliard@winehq.org --- Fixed by fcb37c9c123cd841debb17b6821493b8b2f83473.
https://bugs.winehq.org/show_bug.cgi?id=50867
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |aros@gmx.com
--- Comment #7 from Alexandre Julliard julliard@winehq.org --- *** Bug 50897 has been marked as a duplicate of this bug. ***
https://bugs.winehq.org/show_bug.cgi?id=50867
--- Comment #8 from Artem S. Tashkinov aros@gmx.com --- (In reply to Alexandre Julliard from comment #7)
*** Bug 50897 has been marked as a duplicate of this bug. ***
Thanks,
cp -a ~/.wine/drive_c/windows/command/start.exe ~/.wine/drive_c/windows/
has fixed it for me.
https://bugs.winehq.org/show_bug.cgi?id=50867
André H. nerv@dawncrow.de changed:
What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.winehq.org/sho | |w_bug.cgi?id=50911
https://bugs.winehq.org/show_bug.cgi?id=50867
Jan Havran havran.jan@email.cz changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |havran.jan@email.cz
https://bugs.winehq.org/show_bug.cgi?id=50867
--- Comment #9 from Marc Dequènes (Duck) duck@duckcorp.org --- Thanks Alexandre _o<
https://bugs.winehq.org/show_bug.cgi?id=50867
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #10 from Alexandre Julliard julliard@winehq.org --- Closing bugs fixed in 6.6.
https://bugs.winehq.org/show_bug.cgi?id=50867
--- Comment #11 from Marc Dequènes (Duck) duck@duckcorp.org --- The 6.6 Debian package (in winehq's repo) came out and I just tested and the bug is still there (same message), could you please reopen?
https://bugs.winehq.org/show_bug.cgi?id=50867
--- Comment #12 from Jan Havran havran.jan@email.cz --- (In reply to Marc Dequènes (Duck) from comment #11)
The 6.6 Debian package (in winehq's repo) came out and I just tested and the bug is still there (same message), could you please reopen?
Hi, I had same problem with Wine 6.5, but it is fixed with Wine 6.6 for me.
I run app in FireJail and start it like this: firejail --private="$JAIL" --noprofile wine start /d "$WDIR" /unix "$WDIR"/vietcong.exe
https://bugs.winehq.org/show_bug.cgi?id=50867
--- Comment #13 from Marc Dequènes (Duck) duck@duckcorp.org --- Just in case I was tired and made a mistake I started all over on a prefix I used successfully before this bug:
$ wine --version wine-6.6 $ ls -l "${WINEPREFIX}/drive_c/GOG Games/Cat Quest II/Cat Quest II.exe" -rwxr-x--- 1 duck dc-users 639488 Mar 23 21:58 '/srv/data/Wine/wine-prefixes/cat_quest_ii/drive_c/GOG Games/Cat Quest II/Cat Quest II.exe' $ wine start /unix "${WINEPREFIX}/drive_c/GOG Games/Cat Quest II/Cat Quest II.exe" 0034:fixme:font:opentype_enum_font_names handle name format 1 0034:fixme:font:opentype_enum_font_names handle name format 1 0064:fixme:font:opentype_enum_font_names handle name format 1 0064:fixme:font:opentype_enum_font_names handle name format 1 005c:fixme:font:opentype_enum_font_names handle name format 1 006c:fixme:font:opentype_enum_font_names handle name format 1 005c:fixme:font:opentype_enum_font_names handle name format 1 006c:fixme:font:opentype_enum_font_names handle name format 1 002c:fixme:font:opentype_enum_font_names handle name format 1 002c:fixme:font:opentype_enum_font_names handle name format 1 0024:fixme:font:opentype_enum_font_names handle name format 1 0024:fixme:font:opentype_enum_font_names handle name format 1 010c:fixme:font:opentype_enum_font_names handle name format 1 010c:fixme:font:opentype_enum_font_names handle name format 1 Application could not be started, or no application associated with the specified file. ShellExecuteEx failed: File not found.
https://bugs.winehq.org/show_bug.cgi?id=50867
WinterSnowfall winter.snowfall23@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |winter.snowfall23@gmail.com
--- Comment #14 from WinterSnowfall winter.snowfall23@gmail.com --- (In reply to Robbert van der Helm from comment #4)
To add to this (from bug 50869), launching applications through Wine from the GUI through file associations with `wine.desktop` also no longer works in Wine 6.5 because that too uses `wine start /unix`.
Confirming this is still a problem even in 6.6.
https://bugs.winehq.org/show_bug.cgi?id=50867
--- Comment #15 from WinterSnowfall winter.snowfall23@gmail.com --- (In reply to Alexandre Julliard from comment #3)
We are not supposed to have the 64-bit one either, though apparently it doesn't break anything. Maybe we could simply duplicate the 32-bit one into syswow64 to fix this bug.
I have copied ~/.wine/drive_c/windows/command/start.exe into syswow64 and it works now. Do existing prefixes need to be adjusted as such or is the intended fix supposed to work without moving things around?
https://bugs.winehq.org/show_bug.cgi?id=50867
--- Comment #16 from Alexandre Julliard julliard@winehq.org --- Indeed the fix worked for plain 32-bit but not for Wow64, sorry about that. It should be really fixed by ee13ab0f022f1b89cdc0e6f36ac55a5fb151d6fb.
https://bugs.winehq.org/show_bug.cgi?id=50867
Andre Heider a.heider@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |a.heider@gmail.com
--- Comment #17 from Andre Heider a.heider@gmail.com --- Even with that patch there's a binary backwards compability issue.
An app built with an older winegcc (here v5.6) doesn't run on v6.6+ee13ab0: Application could not be started, or no application associated with the specified file. ShellExecuteEx failed: File not found.
Trying with WINEDEBUG=module yields: libwine.so.1: cannot open shared object file: No such file or directory
Even though that of course exists in the installed wine directory.
Building the app with winegcc from v6.6 fixes the issue as that doesn't link anymore against libwine, but running older winegcc binaries is supposed to work on newer versions, right?
https://bugs.winehq.org/show_bug.cgi?id=50867
--- Comment #18 from Alexandre Julliard julliard@winehq.org --- That's a different issue, please file a new bug.
https://bugs.winehq.org/show_bug.cgi?id=50867
--- Comment #19 from Andre Heider a.heider@gmail.com --- Done: https://bugs.winehq.org/show_bug.cgi?id=51018
https://bugs.winehq.org/show_bug.cgi?id=50867
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |mo78@abv.bg
--- Comment #20 from Alexandre Julliard julliard@winehq.org --- *** Bug 50877 has been marked as a duplicate of this bug. ***
https://bugs.winehq.org/show_bug.cgi?id=50867
--- Comment #21 from Marc Dequènes (Duck) duck@duckcorp.org --- Thanks, it works fine now :-)