https://bugs.winehq.org/show_bug.cgi?id=47790
Bug ID: 47790 Summary: wine does not work with accented characters Product: Wine Version: 3.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: borneater@yopmail.com Distribution: ---
I'm a french user so don't kill me for ma poor english :)
Wine don't operate when target contain accented characters in path. I'm a french user so i installed a french version of centos. I followed the step by step tuto here https://tecadmin.net/steps-install-wine-centos-rhel-fedora-systems/ and i downloaded putty into ~/Téléchargements.
While executing "wine64 putty.exe" i have a message box "unable to open connection to léchargement\putty.exe Host does not exist
Terminal says $ wine64 putty.exe 0009:fixme:shell:SetCurrentProcessExplicitAppUserModelID L"SimonTatham.PuTTY": stub 0009:fixme:imm:ImmReleaseContext (0x2005e, 0x9e380): stub
if putty is moved into .. with no accented characters in path, it works.
thanks.
https://bugs.winehq.org/show_bug.cgi?id=47790
Olivier F. R. Dierick o.dierick@piezo-forte.be changed:
What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Status|UNCONFIRMED |NEW CC| |o.dierick@piezo-forte.be Keywords| |download URL| |https://www.chiark.greenend | |.org.uk/~sgtatham/putty/lat | |est.html Summary|wine does not work with |putty.exe displays an error |accented characters |at startup when placed in a | |path with accented | |characters.
--- Comment #1 from Olivier F. R. Dierick o.dierick@piezo-forte.be --- Hello,
Wine 3.0 is obsolete, use a recent wine-devel (current is 4.16).
I can confirm the issue with wine 4.15.
I tried several different UTF-8 characters and I could not discern a pattern. The issue seems to happens with displayable accented characters that are below U+0100 code point. When the issue doesn't happen, the imm fixme is not printed in the output.
Same result with both 32 and 64 bit versions of putty.exe.
Here are details for the current 64 bit version from the download URL.
$ du -b putty.exe 1181568 putty.exe
$ sha1sum putty.exe 159634f187e42b19971f8ea323c91e561ab5f39a putty.exe
Wine has no issue running other application from the same path, so I'll make the summary more specific.
Regards.
https://bugs.winehq.org/show_bug.cgi?id=47790
Jeff Smith whydoubt@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |whydoubt@gmail.com
--- Comment #2 from Jeff Smith whydoubt@gmail.com --- This seems to result from the intersection of two issues.
1st is how the raw command line is altered by the wine loader If 'putty.exe' is entered at the command line (or 'wine64 putty.exe' for wine), GetCommandLineA() returns... - Windows cmd: 'putty.exe' - Windows powershell: '"C:\Users\Jeff\Téléchargements\putty.exe"' - wine: 'Z:\home\jeff\Téléchargements\putty.exe'
2nd is how the first argument of the command line is stripped out and passed into WinMain. I am not sure if mingw is used to compile putty for release, but the behaviour does match mingw in that characters >0x7f (along with characters <= 0x20) not contained in quotes are treated as the end of the first arg. What gets delivered to WinMain: Windows cmd: '' Windows powershell: '' wine: 'léchargements\putty.exe'
So when run with wine, putty is effectively passed 'léchargements\putty.exe' as a command-line argument. Then putty attempts to treat it as a host name, leading to the warning message box.
Note that with #2, an offending character _anywhere_ in the command name provided to Windows cmd will cause essentially the same failure.
https://bugs.winehq.org/show_bug.cgi?id=47790
--- Comment #3 from Jeff Smith whydoubt@gmail.com --- This should be fixed by commit ceb32f668360ef51b932fa6350858a6b8d2d26ec , available in release 4.19. The fix makes wine behave more like Windows PowerShell as described in the previous comment.
https://bugs.winehq.org/show_bug.cgi?id=47790
Olivier F. R. Dierick o.dierick@piezo-forte.be changed:
What |Removed |Added ---------------------------------------------------------------------------- Fixed by SHA1| |ceb32f668360ef51b932fa63508 | |58a6b8d2d26ec Status|NEW |RESOLVED Component|-unknown |kernel32 Resolution|--- |FIXED
--- Comment #4 from Olivier F. R. Dierick o.dierick@piezo-forte.be --- (In reply to Jeff Smith from comment #3)
This should be fixed by commit ceb32f668360ef51b932fa6350858a6b8d2d26ec , available in release 4.19. The fix makes wine behave more like Windows PowerShell as described in the previous comment.
Hello,
I can't reproduce the issue with Wine 4.19. → Confirming fixed.
Regards.
https://bugs.winehq.org/show_bug.cgi?id=47790
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #5 from Alexandre Julliard julliard@winehq.org --- Closing bugs fixed in 4.21.
https://bugs.winehq.org/show_bug.cgi?id=47790
Michael Stefaniuc mstefani@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|--- |4.0.x
https://bugs.winehq.org/show_bug.cgi?id=47790
Michael Stefaniuc mstefani@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|4.0.x |---
--- Comment #6 from Michael Stefaniuc mstefani@winehq.org --- Removing the 4.0.x milestone from bug fixes included in 4.0.4.
-
WineHQ Bugzilla