http://bugs.winehq.org/show_bug.cgi?id=23321
François Gouget fgouget@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Ever Confirmed|0 |1
--- Comment #13 from François Gouget fgouget@codeweavers.com 2013-03-05 07:35:13 CST --- I can confirm this bug. Here is a simpler way reproduce it with both the 32 and 64-bit builds of Wine:
$ mkdir "~/.wine/drive_c/one space" $ echo Works >"~/.wine/drive_c/one space/file.txt" $ ./wine start "c:\one space\file.txt"
-> This opens the file in notepad and you should see "Works".
$ mkdir "~/.wine/drive_c/one" $ ./wine start "c:\one space\file.txt"
-> Now you get explorer.exe browsing the "One" directory. This is clearly not what you want and this is caused by this bug.
A WINEDEBUG=+exec shows:
trace:exec:SHELL_execute mask=0x00008500 hwnd=(nil) verb=L"open" file=L"C:\One Space\File.txt" parm=L"" dir=(null) show=0x00000001 class=not used fixme:exec:SHELL_execute flags ignored: 0x00000100 trace:exec:ShellExecute_FromContextMenu L"C:\One Space\File.txt" trace:exec:ShellExecute_GetClassKey ext = L".txt" trace:exec:ShellExecute_GetClassKey class = L"txtfile" trace:exec:SHELL_execute execute:L"C:\One Space\File.txt",L"",L"" trace:exec:SHELL_ExecuteW Execute L"C:\One Space\File.txt" from directory L"" trace:exec:SHELL_ExecuteW returning 5 trace:exec:SHELL_FindExecutable L"C:\One" trace:exec:SHELL_FindExecutable SearchPathW returned non-zero trace:exec:SHELL_FindExecutable returning L"" trace:exec:SHELL_FindExecutable L"explorer" ...