September 2020 - Wine-Bugs - list.winehq.org

[Bug 43173] New: Far Cry 4 sound stops
by wine-bugs＠winehq.org July 20, 2021

July 20, 2021

https://bugs.winehq.org/show_bug.cgi?id=43173 Bug ID: 43173 Summary: Far Cry 4 sound stops Product: Wine Version: 2.10 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-dsound Assignee: wine-bugs(a)winehq.org Reporter: noonetinone(a)gmail.com Distribution: --- Created attachment 58436 --> https://bugs.winehq.org/attachment.cgi?id=58436 a run of FC4 with steam logs excised After the cut scenes from Ubisoft, Dunia, and Nvidia the sound cuts out. When this happens you are at the main menu. A few releases ago, I tested a new game and during the 'Stop the Bus' routine as well as the main menu and there was sound. Something happened. There is some information in my console log. DirectSoundDevice_RemoveBuffer is called multiple time until it has no buffers left. At this point you are at the main menu, at line 2102 in the attachment. The following are the last few lines from +dsound,+alsa. _________________________________________________________________________________ warn:dsound:DSOUND_PrimaryDestroy Destroying primary buffer while references held (1 1) trace:alsa:AudioClient_Stop (0x24887040) trace:alsa:alsa_rewind_best_effort rewinding 1015 frames, now held 3404 trace:alsa:AudioClient_Release (0x24887040) Refcount now 2 trace:alsa:AudioClient_Release (0x24887040) Refcount now 1 trace:alsa:AudioClient_Release (0x24887040) Refcount now 0 trace:alsa:AudioClient_Stop (0x24887040) trace:dsound:DirectSoundDevice_Release (0x24888050) released trace:dsound:directsound_destroy (0x2487a8d0) released -- 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.

2 25

[Bug 35921] New: DXVA Checker 3.0.x (.NET 2.0 app) needs IDirectXVideoProcessorService (via DXVA2CreateVideoService)
by wine-bugs＠winehq.org July 20, 2021

July 20, 2021

https://bugs.winehq.org/show_bug.cgi?id=35921 Bug ID: 35921 Summary: DXVA Checker 3.0.x (.NET 2.0 app) needs IDirectXVideoProcessorService (via DXVA2CreateVideoService) Product: Wine Version: 1.7.15 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: focht(a)gmx.net Hello folks, as the summary says. The app calls DXVA2CreateVideoService with the interface identifier IID_IDirectXVideoProcessorService and subsequently crashes while trying to use it. --- snip --- $ WINEDEBUG=+tid,+seh,+relay,+dxva2 wine ./DXVAChecker.exe >>log.txt 2>&1 ... 002a:Call dxva2.DXVA2CreateVideoService(001a3f80,001791e0,0033e574) ret=0393234c 002a:fixme:dxva2:DXVA2CreateVideoService (0x1a3f80, {fc51a552-d5e7-11d9-af55-00054e43ff02}, 0x33e574): stub 002a:Ret dxva2.DXVA2CreateVideoService() retval=80004001 ret=0393234c ... 002a:trace:seh:raise_exception code=c0000005 flags=0 addr=0x790020cf ip=790020cf tid=002a 002a:trace:seh:raise_exception info[0]=00000000 002a:trace:seh:raise_exception info[1]=00000000 002a:trace:seh:raise_exception eax=00000000 ebx=00142e50 ecx=00000000 edx=00000000 esi=0033e458 edi=0033e5ac 002a:trace:seh:raise_exception ebp=0033e440 esp=0033e424 cs=0023 ds=002b es=002b fs=0063 gs=006b flags=00010246 002a:trace:seh:call_stack_handlers calling handler at 0x79fcc4da code=c0000005 flags=0 --- snip --- MSDN: http://msdn.microsoft.com/en-us/library/windows/desktop/ms705631%28v=vs.85%… $ sha1sum DXVAChecker32_3.0.1.zip e7ba2151ae8cc2b9f805cbd1dd046c31f0d45a5b DXVAChecker32_3.0.1.zip $ du -sh DXVAChecker32_3.0.1.zip 564K DXVAChecker32_3.0.1.zip $ wine --version wine-1.7.15-209-g5d173f9 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.

2 11

[Bug 15381] New: CoFreeUnusedLibraries will crash COM server or cause 0x800703E6/I_RpcReceive error 0x3e6
by wine-bugs＠winehq.org July 20, 2021

July 20, 2021

http://bugs.winehq.org/show_bug.cgi?id=15381 Summary: CoFreeUnusedLibraries will crash COM server or cause 0x800703E6/I_RpcReceive error 0x3e6 Product: Wine Version: 1.0.0 Platform: Other OS/Version: other Status: UNCONFIRMED Severity: normal Priority: P2 Component: ole32 AssignedTo: wine-bugs(a)winehq.org ReportedBy: dmda(a)yandex.ru Created an attachment (id=16230) --> (http://bugs.winehq.org/attachment.cgi?id=16230) demo illustrating the problem if CoFreeUnusedLibraries is called by COM server, it will break RPC channcel and lead to the errors Attached is client/server code that demonstrates the problem. If you comment out CoFreeUnusedLibraries call, it will start to work. Steps: -comple all 3 projects in the Workspace (Debug target is the only appropriate for the sake of demo) -make sure server and proxy are registered by running testserver.exe -RegServer, regsvr32 testserverPS.dll -run testproject.exe (the client) Expected behaviour: 1. it will show server's message "CServer is created", click ok 2. it will show client's message "press OK when ready", click ok 3. it will show server's message passed by the client "Hello world!", click ok 4. it will show client's message "call succeeded" and client will exit 5. after roughly 6sec it will show that the server is unloaded/ Actual behaviour: 1. it will show server's message "CServer is created", click ok 2. it will show client's message "press OK when ready", click ok 3. it will show server's message passed by the client "Hello world!", click ok 4. it will dump out trouble in the console and show client's message "call failed" You may call CoFreeUnusedLibraries anywhere in the appartment and it will break RPC on the server side. In some cases it will crash whole the server, like in the demo. Tested environment: Fedora Core 8, 32bit, x86, wine 1.0 installed through the updates -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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.

2 14

[Bug 41703] New: LdrUnloadDll is not suit for musl( musl lacks unload support though it has a dlclose())
by wine-bugs＠winehq.org July 20, 2021

July 20, 2021

https://bugs.winehq.org/show_bug.cgi?id=41703 Bug ID: 41703 Summary: LdrUnloadDll is not suit for musl(musl lacks unload support though it has a dlclose()) Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: xw897002528(a)gmail.com Distribution: --- Created attachment 56111 --> https://bugs.winehq.org/attachment.cgi?id=56111 fix for this problem Hey, sorry for my poor english, and here is the problem: First, musl won't unload module even dlclose(). Check here: http://wiki.musl-libc.org/wiki/Functional_differences_from_glibc#Unloading_… Then, musl won't excute init(__wine_spec_init) function if a module is already loaded. That means load_builtin_dll() thought dll is loaded by the current thread since init function was not called, but actually LdrUnloadDll() destroyed them in another thread and nothing is loaded in the current thread. Load_builtin_dll() try to find wm in InLoadOrderModuleList but nothing. After that, app will crash. And I solved this by making LdrUnloadDll() a stub. Patch is uploaded as a attachment. I hope this could be added in official wine by adding a configure option, thx. Here's my tracking details on this problem if you're intereted in how i found this: https://github.com/xhebox/noname-linux/issues/2#issuecomment-258680745 -- 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.

2 36

[Bug 45807] New: Incorrect toolbar background in MFC apps, when visual theming enabled
by wine-bugs＠winehq.org July 20, 2021

July 20, 2021

https://bugs.winehq.org/show_bug.cgi?id=45807 Bug ID: 45807 Summary: Incorrect toolbar background in MFC apps, when visual theming enabled Product: Wine Version: 3.15 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: jimbo1qaz(a)gmail.com Distribution: --- Created attachment 62266 --> https://bugs.winehq.org/attachment.cgi?id=62266 Screenshot of bug When visual theming is enabled, MFC toolbar button backgrounds are rendered as "grab handles", and space between buttons is black. (Also visible in screenshot, in 0CC and j0CC, the instrument editor piano is invisible when theming is enabled. Should I file a separate bug?) Tested with ReactOS.iso Lautus theme, and Zune theme (via .msi). Tested with j0CC-Famitracker and OpenMPT (both use MFC), on dirty WINEPREFIX. Also tested with Lautus and j0CC on clean WINEPREFIX with Lautus theme. -- 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.

2 4

[Bug 35611] New: A lot of user32:msg tests fail in the Japanese locale
by wine-bugs＠winehq.org July 20, 2021

July 20, 2021

https://bugs.winehq.org/show_bug.cgi?id=35611 Bug ID: 35611 Summary: A lot of user32:msg tests fail in the Japanese locale Product: Wine Version: 1.7.12 Hardware: x86 OS: Windows Status: NEW Severity: normal Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Classification: Unclassified The WineTestBot's w7u VM runs the tests in the Japanese locale. This results in 49 test failures instead of the background of 6 test failures. This can also be seen in the fg-win7u64-ja VM which gets 55 failures. See: http://test.winehq.org/data/tests/user32:msg.html The failures happen in test_dbcs_wm_char() and test_unicode_wm_char(). msg.c:11812: Test failed: got message 31f msg.c:11817: Test failed: bad wparam 81/2260 msg.c:11819: Test failed: got message 102 msg.c:11829: Test failed: bad wparam 201a/2260 msg.c:11836: Test failed: no messages: 0: the msg sequence is not complete: expected 0000 - actual 0102 msg.c:11836: Failed sequence no messages: msg.c:11836: 0: expected: nothing - actual: MsgCheckProc: 00080390 0102 wp 00000081 lp 00000000 (flags 19) msg.c:11838: Test failed: Unicode WM_CHAR: 0: in msg 0x0102 expecting wParam 0x2260 got 0x201a msg.c:11838: Failed sequence Unicode WM_CHAR: msg.c:11838: 0: expected: msg 0102 - actual: MsgCheckProc: 00080390 0102 wp 0000201a lp 00000000 (flags 19) msg.c:11845: Test failed: no messages: 0: the msg sequence is not complete: expected 0000 - actual 0102 msg.c:11845: Failed sequence no messages: msg.c:11845: 0: expected: nothing - actual: MsgCheckProc: 00080390 0102 wp 00000081 lp 00000000 (flags 19) msg.c:11847: Test failed: Unicode WM_CHAR: 0: in msg 0x0102 expecting wParam 0x2260 got 0x201a msg.c:11847: Failed sequence Unicode WM_CHAR: msg.c:11847: 0: expected: msg 0102 - actual: MsgCheckProc: 00080390 0102 wp 0000201a lp 00000000 (flags 19) msg.c:11854: Test failed: no messages: 0: the msg sequence is not complete: expected 0000 - actual 0102 msg.c:11854: Failed sequence no messages: msg.c:11854: 0: expected: nothing - actual: MsgCheckProc: 00080390 0102 wp 00000081 lp 00000000 (flags 19) msg.c:11856: Test failed: Unicode WM_CHAR: 0: in msg 0x0102 expecting wParam 0x2260 got 0x201a msg.c:11856: Failed sequence Unicode WM_CHAR: msg.c:11856: 0: expected: msg 0102 - actual: MsgCheckProc: 00080390 0102 wp 0000201a lp 00000000 (flags 19) msg.c:11863: Test failed: no messages: 0: the msg sequence is not complete: expected 0000 - actual 0102 msg.c:11863: Failed sequence no messages: msg.c:11863: 0: expected: nothing - actual: MsgCheckProc: 00080390 0102 wp 00000081 lp 00000000 (flags 19) msg.c:11865: Test failed: Unicode WM_CHAR: 0: in msg 0x0102 expecting wParam 0x2260 got 0x201a msg.c:11865: Failed sequence Unicode WM_CHAR: msg.c:11865: 0: expected: msg 0102 - actual: MsgCheckProc: 00080390 0102 wp 0000201a lp 00000000 (flags 19) msg.c:11872: Test failed: no messages: 0: the msg sequence is not complete: expected 0000 - actual 0102 msg.c:11872: Failed sequence no messages: msg.c:11872: 0: expected: nothing - actual: MsgCheckProc: 00080390 0102 wp 00000081 lp 00000000 (flags 19) msg.c:11874: Test failed: Unicode WM_CHAR: 0: in msg 0x0102 expecting wParam 0x2260 got 0x201a msg.c:11874: Failed sequence Unicode WM_CHAR: msg.c:11874: 0: expected: msg 0102 - actual: MsgCheckProc: 00080390 0102 wp 0000201a lp 00000000 (flags 19) msg.c:11882: Test failed: no messages: 0: the msg sequence is not complete: expected 0000 - actual 0102 msg.c:11882: Failed sequence no messages: msg.c:11882: 0: expected: nothing - actual: MsgCheckProc: 00080390 0102 wp 00000081 lp 00000000 (flags 19) msg.c:11885: Test failed: Unicode WM_CHAR: 0: in msg 0x0102 expecting wParam 0x2260 got 0x201a msg.c:11885: Failed sequence Unicode WM_CHAR: msg.c:11885: 0: expected: msg 0102 - actual: MsgCheckProc: 00080390 0102 wp 0000201a lp 00000000 (flags 19) msg.c:11890: Test failed: no messages: 0: the msg sequence is not complete: expected 0000 - actual 0102 msg.c:11890: Failed sequence no messages: msg.c:11890: 0: expected: nothing - actual: MsgCheckProc: 003C03CE 0102 wp 00000081 lp 00000000 (flags 19) msg.c:11892: Test failed: Unicode WM_CHAR: 0: in msg 0x0102 expecting wParam 0x2260 got 0x201a msg.c:11892: Failed sequence Unicode WM_CHAR: msg.c:11892: 0: expected: msg 0102 - actual: MsgCheckProc: 00080390 0102 wp 0000201a lp 00000000 (flags 19) msg.c:11900: Test failed: no messages: 0: the msg sequence is not complete: expected 0000 - actual 0102 msg.c:11900: Failed sequence no messages: msg.c:11900: 0: expected: nothing - actual: MsgCheckProc: 003C03CE 0102 wp 00000081 lp 00000000 (flags 19) msg.c:11908: Test failed: bad wparam 201a/2260 msg.c:11912: Test failed: Unicode WM_CHAR: 0: in msg 0x0102 expecting wParam 0x2260 got 0x201a msg.c:11912: Failed sequence Unicode WM_CHAR: msg.c:11912: 0: expected: msg 0102 - actual: MsgCheckProc: 00080390 0102 wp 0000201a lp 00000000 (flags 19) msg.c:11920: Test failed: no messages: 0: the msg sequence is not complete: expected 0000 - actual 0102 msg.c:11920: Failed sequence no messages: msg.c:11920: 0: expected: nothing - actual: MsgCheckProc: 00080390 0102 wp 00000081 lp 00000000 (flags 19) msg.c:11920: 1: expected: nothing - actual: MsgCheckProc: 00080390 0102 wp 00000081 lp 00000000 (flags 19) msg.c:11922: Test failed: Unicode WM_CHAR: 0: in msg 0x0102 expecting wParam 0x2260 got 0x201a msg.c:11922: Failed sequence Unicode WM_CHAR: msg.c:11922: 0: expected: msg 0102 - actual: MsgCheckProc: 00080390 0102 wp 0000201a lp 00000000 (flags 19) msg.c:11924: Test failed: Unicode WM_CHAR: 0: in msg 0x0102 expecting wParam 0x2260 got 0x201a msg.c:11924: Failed sequence Unicode WM_CHAR: msg.c:11924: 0: expected: msg 0102 - actual: MsgCheckProc: 00080390 0102 wp 0000201a lp 00000000 (flags 19) msg.c:11933: Test failed: no messages: 0: the msg sequence is not complete: expected 0000 - actual 0102 msg.c:11933: Failed sequence no messages: msg.c:11933: 0: expected: nothing - actual: MsgCheckProc: 00080390 0102 wp 00000081 lp 00000000 (flags 19) msg.c:11933: 1: expected: nothing - actual: MsgCheckProc: 00080390 0102 wp 00000081 lp 00000000 (flags 19) msg.c:11936: Test failed: Unicode WM_CHAR: 0: in msg 0x0102 expecting wParam 0x2260 got 0x201a msg.c:11936: Failed sequence Unicode WM_CHAR: msg.c:11936: 0: expected: msg 0102 - actual: MsgCheckProc: 00080390 0102 wp 0000201a lp 00000000 (flags 19) msg.c:11938: Test failed: Unicode WM_CHAR: 0: in msg 0x0102 expecting wParam 0x2260 got 0x201a msg.c:11938: Failed sequence Unicode WM_CHAR: msg.c:11938: 0: expected: msg 0102 - actual: MsgCheckProc: 00080390 0102 wp 0000201a lp 00000000 (flags 19) msg.c:11944: Test failed: no messages: 0: the msg sequence is not complete: expected 0000 - actual 0102 msg.c:11944: Failed sequence no messages: msg.c:11944: 0: expected: nothing - actual: MsgCheckProc: 00080390 0102 wp 00000081 lp 00000000 (flags 19) msg.c:11944: 1: expected: nothing - actual: MsgCheckProc: 00080390 0102 wp 00000081 lp 00000000 (flags 19) msg.c:11946: Test failed: Unicode WM_CHAR: 0: in msg 0x0102 expecting wParam 0x2260 got 0x201a msg.c:11946: Failed sequence Unicode WM_CHAR: msg.c:11946: 0: expected: msg 0102 - actual: MsgCheckProc: 00080390 0102 wp 0000201a lp 00000000 (flags 19) msg.c:11948: Test failed: Unicode WM_CHAR: 0: in msg 0x0102 expecting wParam 0x2260 got 0x201a msg.c:11948: Failed sequence Unicode WM_CHAR: msg.c:11948: 0: expected: msg 0102 - actual: MsgCheckProc: 00080390 0102 wp 0000201a lp 00000000 (flags 19) msg.c:11953: Test failed: Unicode WM_CHAR: 0: in msg 0x0102 expecting wParam 0x2260 got 0x201a0081 msg.c:11953: Failed sequence Unicode WM_CHAR: msg.c:11953: 0: expected: msg 0102 - actual: MsgCheckProc: 003C03CE 0102 wp 201a0081 lp 00000000 (flags 19) msg.c:11962: Test failed: bad wparam 81/30fb msg.c:11969: Test failed: bad wparam 81/30fb msg.c:11980: Test failed: bad wparam 3f/81 msg.c:11982: Test failed: no message msg.c:11985: Test failed: bad wparam 3f/81 msg.c:11995: Test failed: bad wparam 3f/81 msg.c:12001: Test failed: unexpected hwnd 003C03CE msg.c:12002: Test failed: unexpected message 31f msg.c:12003: Test failed: bad wparam 1/81 msg.c:12012: Test failed: bad wparam 3f/81 msg.c:12019: Test failed: unexpected hwnd 00000000 msg.c:12021: Test failed: bad wparam 81/81 msg.c:12022: Test failed: bad lparam 0 msg.c:12023: Test failed: bad time 1b0e62/1b0e90 msg.c:12032: Test failed: unexpected hwnd 003C03CE msg.c:12037: Test failed: unexpected hwnd 003C03CE msg.c:12044: Test failed: bad wparam 3f/81 msg.c:12049: Test failed: bad wparam 3f/81 -- 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.

2 6

[Bug 34966] New: Academagia (WPF game) dialog windows are invisible until alt-tabed out
by wine-bugs＠winehq.org July 20, 2021

July 20, 2021

http://bugs.winehq.org/show_bug.cgi?id=34966 Bug #: 34966 Summary: Academagia (WPF game) dialog windows are invisible until alt-tabed out Product: Wine Version: 1.7.6 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: i30817(a)gmail.com Classification: Unclassified installed dotnet51sp1 from the latest winetricks on a 32 bits prefix installed windowscodecs from the latest winetricks the same 32 bits prefix installed the game on the same 32 bits prefix then; started notpad: WINEPREFIX='/home/i30817/wine32bits' WINEARCH='win32' notepad started the game with these options: WINEPREFIX='/home/i30817/wine32bits' WINEARCH='win32' WINEDEBUG=+tid,+seh,+relay wine ./Academagia.exe >>log.txt 2>&1 And waited until the first dialog window i was able to activate, alt-tabed out (that was when i noticed it became visible) and killed the corresponding wineserver with: WINEPREFIX='/home/i30817/wine32bits' WINEARCH='win32' wineserver -k The log is quite large uncompressed (1.5 GB), but actually 30mb compressed. Still too large to upload here; but it can go to my google drive: https://drive.google.com/file/d/0BzxkBmaf1EiWTmhiQjJ1YkllZWc/edit?usp=shari… -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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.

2 4

[Bug 12968] New: MS Visual Studio V6 setup error 258 since 0.9.58
by wine-bugs＠winehq.org July 19, 2021

July 19, 2021

http://bugs.winehq.org/show_bug.cgi?id=12968 Summary: MS Visual Studio V6 setup error 258 since 0.9.58 Product: Wine Version: 0.9.61. Platform: All OS/Version: Linux Status: UNCONFIRMED Severity: critical Priority: P1 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: k.king177(a)ntlworld.com trying to install Visual Studio v6 get MS Msgbox headed "Setup Error 258" with text Your setup files may be damaged. Try restarting the setup program from where you originally ran it. this is probably related or from same issue causing bug# 12967 for Office 97 see that bug for environment details. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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.

2 5

[Bug 15948] New: Error generated when trying to install visual studio 6.0 into centos5 via wine
by wine-bugs＠winehq.org July 19, 2021

July 19, 2021

http://bugs.winehq.org/show_bug.cgi?id=15948 Summary: Error generated when trying to install visual studio 6.0 into centos5 via wine Product: Wine Version: 1.1.7 Platform: PC-x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: enhancement Priority: P4 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: boniemx(a)gmail.com Created an attachment (id=17135) --> (http://bugs.winehq.org/attachment.cgi?id=17135) error-log for installation of visual studio 6.0 via wine into centos5 Hi, am trying to install Visual studio 6.0, but it produces the error that I have attached. Please I need to do this urgently. Please help -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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.

2 6

[Bug 37902] New: CreateDirectoryW creates a directory with the permissions set to 000
by wine-bugs＠winehq.org July 19, 2021

July 19, 2021

https://bugs.winehq.org/show_bug.cgi?id=37902 Bug ID: 37902 Summary: CreateDirectoryW creates a directory with the permissions set to 000 Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: ehsan.akhgari(a)gmail.com Distribution: --- Created attachment 50480 --> https://bugs.winehq.org/attachment.cgi?id=50480 file trace from the installer I am trying to install Visual Studio 2013 Update 4 from its full SDK under wine in Ubuntu Trusty. The installation fails because a directory created by the installer through CreateDirectoryW ends up with the permission bits set to 0. I am attaching a file trace from the relevant failure to the bug. The directory in question is: "C:\users\Public\Application Data\Package Cache\{b8a9dbc1-1fd4-4103-a83b-a2896f193ea0}". -- 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.

2 3