December 2018 - Wine-Bugs - list.winehq.org

[Bug 36628] New: Multiple GFWL (Games For Windows Live) 2.0.0687.0 games fail on startup, reporting 'E_INVALIDARG : XLiveInitialize(&xii)' (Resident Evil 5)
by wine-bugs＠winehq.org July 9, 2024

July 9, 2024

https://bugs.winehq.org/show_bug.cgi?id=36628 Bug ID: 36628 Summary: Multiple GFWL (Games For Windows Live) 2.0.0687.0 games fail on startup, reporting 'E_INVALIDARG : XLiveInitialize(&xii)' (Resident Evil 5) Product: Wine Version: 1.7.19 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, split off from bug 23914 I'm copying my analysis verbatim here. To come this far you have to work around some bugs... The first issue is bug 36627 --- snip --- $ pwd /home/focht/.wine/drive_c/Program Files/CAPCOM/RESIDENT EVIL 5 $ wine ./Launcher.exe err:module:import_dll Library MSASN1.dll (which is needed by L"C:\\windows\\system32\\xlive.dll") not found err:module:import_dll Library xlive.dll (which is needed by L"C:\\Program Files\\CAPCOM\\RESIDENT EVIL 5\\RE5DX9.EXE") not found err:module:LdrInitializeThunk Main exe initialization for L"C:\\Program Files\\CAPCOM\\RESIDENT EVIL 5\\RE5DX9.EXE" failed, status c0000135 --- snip --- The game bundles 'Games For Windows Live 2.0.0687.0' which hard-binds to 'MSASN1.dll'. This can be worked around with: 'winetricks -q msasn1' The next issue is bug 17195 (SetNamedPipeHandleState implementation, support for named pipe message mode) as indicated by comment #22 The launcher uses named pipe in message mode for IPC with main game process. --- snip --- $ pwd /home/focht/.wine/drive_c/Program Files/CAPCOM/RESIDENT EVIL 5 $ WINEDEBUG=+tid,+seh,+relay,+snoop,+msvcrt wine ./Launcher.exe >>log.txt 2>&1 ... 002b:Call KERNEL32.CreateNamedPipeW(00dbe080 L"\\\\.\\pipe\\0000002a",40080003,00000006,00000001,00000400,00000400,00001388,00dbe054) ret=00403d54 002b:Ret KERNEL32.CreateNamedPipeW() retval=0000006c ret=00403d54 ... 002c:Starting thread proc 0x401490 (arg=0x2413b8) ... 002c:Call KERNEL32.ConnectNamedPipe(0000006c,002413fc) ret=004033ed 002c:Ret KERNEL32.ConnectNamedPipe() retval=00000000 ret=004033ed 002c:Call KERNEL32.GetLastError() ret=004033fa 002c:Ret KERNEL32.GetLastError() retval=000003e5 ret=004033fa 002c:Call KERNEL32.WaitForMultipleObjects(00000002,00241414,00000000,ffffffff) ret=00403a88 ... 002b:Call KERNEL32.CreateProcessW(00000000,00dbcd58 L"RE5DX9.exe -dx9",00000000,00000000,00000000,00000410,00000000,0013ba40 L"C:\\Program Files\\CAPCOM\\RESIDENT EVIL 5\\",00dbc410,00dbc400) ret=7e56607a ... 002e:Call KERNEL32.__wine_kernel_init() ret=7bc5a4b2 002b:Ret KERNEL32.CreateProcessW() retval=00000001 ret=7e56607a ... 002e:Call KERNEL32.CreateFileW(0033d78c L"\\\\.\\pipe\\0000002a",c0000000,00000000,00000000,00000003,40000000,00000000) ret=00e26522 002e:Ret KERNEL32.CreateFileW() retval=000000b4 ret=00e26522 002e:Call KERNEL32.SetNamedPipeHandleState(000000b4,0033d784,00000000,00000000) ret=00e26547 002e:Ret KERNEL32.SetNamedPipeHandleState() retval=00000000 ret=00e26547 002e:Call KERNEL32.GetLastError() ret=00e26450 002e:Ret KERNEL32.GetLastError() retval=00000000 ret=00e26450 ... 002e:Ret KERNEL32.CloseHandle() retval=00000001 ret=00e265a0 ... 002c:Ret KERNEL32.WaitForMultipleObjects() retval=00000000 ret=00403a88 ... 002e:Call user32.MessageBoxA(00000000,01273d08 "Errorcode:80070507",00f64bfc "InitRpl Failed",00041010) ret=00721f07 --- snip --- The child closes the other end of pipe after failure to bring the pipe in message mode which also wakes the parent with broken pipe error. Faking "success" is obviously not a good solution hence I ran the game with a Wine version that carries Adam Martinson's patchset (branch rebased to tip). This brings the game further - only to run into GFWL init problem: --- snip --- ... 002e:CALL xlive.5297(<unknown, check return>) ret=0044eb72 002e:Call advapi32.RegisterTraceGuidsA(015e39d7,00000000,01495c5c,00000003,01ab8744,00000000,00000000,01ac85b0) ret=015e3a5c 002e:fixme:advapi:RegisterTraceGuidsA (0x15e39d7, (nil), {d5b9ac76-d546-4891-bb8c-bfd865e5c7d5}, 3, 0x1ab8744, (null), (null), 0x1ac85b0): stub 002e:Ret advapi32.RegisterTraceGuidsA() retval=00000000 ret=015e3a5c ... 002e:Call KERNEL32.LoadLibraryW(0033c0c8 L"C:\\Program Files\\CAPCOM\\RESIDENT EVIL 5\\RE5DX9.EXE") ret=01573fd8 002e:Ret KERNEL32.LoadLibraryW() retval=00400000 ret=01573fd8 ... 002e:Call KERNEL32.lstrcmpiW(001ed71c L"xlive.dll",01492e70 L"shimeng.dll") ret=015738f6 002e:Ret KERNEL32.lstrcmpiW() retval=00000001 ret=015738f6 002e:Call KERNEL32.K32GetModuleInformation(ffffffff,00400000,0033c0b0,0000000c) ret=01571ca9 002e:Ret KERNEL32.K32GetModuleInformation() retval=00000001 ret=01571ca9 002e:Call KERNEL32.FreeLibrary(00400000) ret=01573e42 002e:Ret KERNEL32.FreeLibrary() retval=00000001 ret=01573e42 002e:Call KERNEL32.UnmapViewOfFile(13360000) ret=01574ab9 002e:Ret KERNEL32.UnmapViewOfFile() retval=00000001 ret=01574ab9 002e:Call KERNEL32.CloseHandle(00000104) ret=01574ade 002e:Ret KERNEL32.CloseHandle() retval=00000001 ret=01574ade 002e:Call KERNEL32.CloseHandle(00000100) ret=01574afc ... 002e:Call advapi32.RegisterEventSourceW(00000000,01495a2c) ret=015eccbf 002e:fixme:advapi:RegisterEventSourceW ((null),L"XLive"): stub 002e:Ret advapi32.RegisterEventSourceW() retval=cafe4242 ret=015eccbf 002e:Call advapi32.ReportEventW(cafe4242,00000002,00000000,80000002,00000000,00000004,00000000,0033bb24,00000000) ret=015eccff 002e:fixme:advapi:ReportEventW (0xcafe4242,0x0002,0x0000,0x80000002,(nil),0x0004,0x00000000,0x33bb24,(nil)): stub 002e:Ret advapi32.ReportEventW() retval=00000001 ret=015eccff 002e:Call advapi32.DeregisterEventSource(cafe4242) ret=015ecd1f 002e:fixme:advapi:DeregisterEventSource (0xcafe4242) stub 002e:Ret advapi32.DeregisterEventSource() retval=00000001 ret=015ecd1f ... 002e:Call advapi32.UnregisterTraceGuids(00000000,00000000) ret=015e3a6f 002e:fixme:advapi:UnregisterTraceGuids 0: stub 002e:Ret advapi32.UnregisterTraceGuids() retval=00000078 ret=015e3a6f 002e:RET xlive.5297(0033d330,2002af00) retval=80004005 ret=0044eb72 002e:Call KERNEL32.GetLastError() ret=00e31b72 002e:Ret KERNEL32.GetLastError() retval=00000000 ret=00e31b72 002e:Call KERNEL32.FatalAppExitA(00000000,0033cec8 "E_FAIL : XLiveInitialize(&xii)") ret=0042eb7d 002e:warn:seh:FatalAppExitA AppExit 002e:Call user32.MessageBoxA(00000000,0033cec8 "E_FAIL : XLiveInitialize(&xii)",00000000,00001000) ret=7b83bee7 --- snip --- xlive.5297 API entry = XLiveInitializeEx() This is bug 33034 After merging my fix on top of named pipe branch it fares better but still fails in the end: --- snip --- 002e:CALL xlive.5297(<unknown, check return>) ret=0044eb72 ... 002e:CALL sqmapi.SqmStartUpload(<unknown, check return>) ret=015e368f ... 002e:RET sqmapi.SqmStartUpload(0033c9c0,0033c5b0,00000000,00000002,015e2de0) retval=00000000 ret=015e368f ... 002e:CALL sqmapi.SqmGetSession(<unknown, check return>) ret=015e3243 ... 002e:RET sqmapi.SqmGetSession(01495a2c,00008000,00000001) retval=00000001 ret=015e3243 ... 002e:CALL sqmapi.SqmSetAppVersion(<unknown, check return>) ret=015e347a ... 002e:RET sqmapi.SqmSetAppVersion(00000001,00020000,02af0000) retval=00000001 ret=015e347a 002e:CALL sqmapi.SqmReadSharedMachineId(<unknown, check return>) ret=015e348c ... 002e:RET sqmapi.SqmReadSharedMachineId(0033cba4) retval=00000001 ret=015e348c 002e:CALL sqmapi.SqmSetMachineId(<unknown, check return>) ret=015e34b7 ... 002e:RET sqmapi.SqmSetMachineId(00000001,0033cba4) retval=00000001 ret=015e34b7 002e:CALL sqmapi.SqmReadSharedUserId(<unknown, check return>) ret=015e34c5 ... 002e:RET sqmapi.SqmReadSharedUserId(0033cbb4) retval=00000001 ret=015e34c5 002e:CALL sqmapi.SqmSetUserId(<unknown, check return>) ret=015e34f0 ... 002e:RET sqmapi.SqmSetUserId(00000001,0033cbb4) retval=00000001 ret=015e34f0 ... 002e:CALL sqmapi.SqmSetEnabled(<unknown, check return>) ret=015e3087 ... 002e:RET sqmapi.SqmSetEnabled(00000001,00000000) retval=00000001 ret=015e3087 ... 002e:CALL sqmapi.SqmSet(<unknown, check return>) ret=015e2e4a ... 002e:RET sqmapi.SqmSet(00000001,000000c1,0001b5e7) retval=00000000 ret=015e2e4a ... 002e:CALL sqmapi.SqmTimerStart(<unknown, check return>) ret=015e2fcd ... 002e:RET sqmapi.SqmTimerStart(00000001,00000035) retval=00000000 ret=015e2fcd ... 002e:CALL sqmapi.SqmSetBits(<unknown, check return>) ret=015e2eaa ... 002e:RET sqmapi.SqmSetBits(00000001,0000002e,0000000c) retval=00000000 ret=015e2eaa ... <lots of DRM checks/anti-debugging> ... 002e:Call advapi32.RegisterEventSourceW(00000000,01495a2c) ret=015eccbf 002e:fixme:advapi:RegisterEventSourceW ((null),L"XLive"): stub 002e:Ret advapi32.RegisterEventSourceW() retval=cafe4242 ret=015eccbf 002e:Call advapi32.ReportEventW(cafe4242,00000002,00000000,80000002,00000000,00000004,00000000,0033bb24,00000000) ret=015eccff 002e:fixme:advapi:ReportEventW (0xcafe4242,0x0002,0x0000,0x80000002,(nil),0x0004,0x00000000,0x33bb24,(nil)): stub 002e:Ret advapi32.ReportEventW() retval=00000001 ret=015eccff 002e:Call advapi32.DeregisterEventSource(cafe4242) ret=015ecd1f 002e:fixme:advapi:DeregisterEventSource (0xcafe4242) stub 002e:Ret advapi32.DeregisterEventSource() retval=00000001 ret=015ecd1f ... 002e:RET xlive.5297(0033d330,2002af00) retval=80070057 ret=0044eb72 ... 002e:Call KERNEL32.FatalAppExitA(00000000,0033cec8 "E_INVALIDARG : XLiveInitialize(&xii)") ret=0042eb7d 002e:warn:seh:FatalAppExitA AppExit 002e:Call user32.MessageBoxA(00000000,0033cec8 "E_INVALIDARG : XLiveInitialize(&xii)",00000000,00001000) ret=7b83bee7 --- snip --- $ wine --version wine-1.7.19-70-gd6a59f7 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 12

[Bug 44740] New: "A Hat in Time" any x360 joystick' s sticks seems to be stuck in upper right corner.
by wine-bugs＠winehq.org July 9, 2024

July 9, 2024

https://bugs.winehq.org/show_bug.cgi?id=44740 Bug ID: 44740 Summary: "A Hat in Time" any x360 joystick's sticks seems to be stuck in upper right corner. Product: Wine Version: 3.3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: xinput Assignee: wine-bugs(a)winehq.org Reporter: spam(a)hjkos.com Distribution: --- Game: https://appdb.winehq.org/objectManager.php?sClass=version&iId=36033 Game recognizes joystick correctly, buttons work as expected, however game sees analog stick as if it's stuck in some corner, making character run in circles. Jiggling the joystick makes it slightly change direction, but game is still unplayable this way. Joystick appears to be working correctly - it works fine in Linux games, and joystick control panel also shows correct positions. I tried two joysticks: Logitech F710 (XInput mode) Steam Controller (sc-controller x360 joystick emulation) both yield same result. dumbxinputemu makes game see two controllers, one real and one emulated by dumbxinputemu, and seems this time around emulated one works normally, but the real one keeps overriding it, so character just changes directions frequently and in with drastic direction changes. Also, Logitech F710 has DirectInput mode, which has working sticks, however it has weird bindings and i am unable to rebind it in-game. -- 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 44856] New: DOOM 2016 is no longer working
by wine-bugs＠winehq.org July 9, 2024

July 9, 2024

https://bugs.winehq.org/show_bug.cgi?id=44856 Bug ID: 44856 Summary: DOOM 2016 is no longer working Product: Wine Version: 3.4 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: justinrun(a)gmail.com Distribution: --- Created attachment 60912 --> https://bugs.winehq.org/attachment.cgi?id=60912 crash log A new update to the DOOM 2016 game on steam is no longer working on wine. I tested this in wine 3.4, 3.0, and 2.21. I also tried it with both OpenGL and Vulkan rendering. I also tried it with nvidia drivers 390.48 and 384.130. It always just starts up to a black screen. I have to kill the process to close it. This did not happen prior to the most recent game update. I also tried adding a launch argument to disable the intro video in case playing it was the issue. It still did not work. I attached a crash log. -- 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 21

[Bug 45311] New: Skyrim Special Edition: ambient sounds do not attenuate with distance
by wine-bugs＠winehq.org July 9, 2024

July 9, 2024

https://bugs.winehq.org/show_bug.cgi?id=45311 Bug ID: 45311 Summary: Skyrim Special Edition: ambient sounds do not attenuate with distance Product: Wine Version: 3.9 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: xaudio2 Assignee: wine-bugs(a)winehq.org Reporter: forestcode(a)ixio.org Distribution: --- In Skyrim SE, ambient sounds are supposed to attenuate based on the camera's distance from the source, so that distant sounds will be barely perceptible, nearby sounds will be loud and clear, and moving closer or farther from the source will gradually change the sound's volume accordingly. When running on wine with builtin xaudio, distance attenuation does not work; any time the camera enters a certain (fairly distant) radius from a sound source, that sound will suddenly start playing at full volume, as if the source was in the player's ear. This results in disturbing situations like startlingly loud footsteps and voices produced by distant NPCs, or a sudden roar of water rushing the moment the player crosses an invisible threshold in the vicinity of a river. When running with Microsoft's native 64-bit xaudio libs, distance attenuation works properly. Note: While winetricks xact is probably the easiest way to install the native xaudio libs for testing purposes, recent versions of winetricks do not install the 64-bit versions. (See wine bug 41618#c5.) Reverting this commit is therefore necessary in order to get the libs needed for Skyrim SE's 64-bit executable: https://github.com/Winetricks/winetricks/commit/f2b3d268d941120d13b4c3c3960… I have identified a few locations in the early part of game where this bug is prominent: 1. A point on the road from Helgen to Riverwood where the rumbling of a nearby river cuts in suddenly as the player approaches it. 2. A point on the same road, closer to the river, where the whooshing of rushing water cuts in suddenly as the player approaches. 3. A point in Riverwood where the creaking of the wooden water wheel cuts in at full volume as the player approaches. When standing at any of these points, one can hear the ambient sounds cut in and out either by walking closer/farther from the sound source, or by zooming out to third-person view and rotating the camera around the player, such that the camera enters/exits the sound's radius. I will attach screen shots showing these locations. -- 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 33

[Bug 29985] New: Joystick (DragonRise Inc. Generic USB Joystick) incorrect setting in analog.
by wine-bugs＠winehq.org July 9, 2024

July 9, 2024

http://bugs.winehq.org/show_bug.cgi?id=29985 Bug #: 29985 Summary: Joystick (DragonRise Inc. Generic USB Joystick) incorrect setting in analog. Product: Wine Version: 1.4-rc4 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-dinput AssignedTo: wine-bugs(a)winehq.org ReportedBy: fael_mc(a)msn.com Classification: Unclassified Created attachment 39035 --> http://bugs.winehq.org/attachment.cgi?id=39035 Pictures to explain better Greetings I have a very good experience with games in wine, but there is a bug with my joystick, which disturbs some games. I have a PS2 joystick style (DragonRise Inc. Generic USB Joystick) very popular here in where I live, work and usually no problem with native linux games. In wine, almost everything works normally, it recognizes, and works in all games. But there is a problem with the axes of the analog. In Games, I set up the axes of analog, such as "Pro Evolution Soccer 5" everything is right. But some games you can not configure the axes - Example "GTA San Andreas." The problem is with the analog number 2 in the GTA is the camera, only works up and down, left and right does not work, the function of the left and right analog camera is in paragraph 1, which is normal, but beyond move to "CJ" also moves the camera to the left and right. "San Andreas" is just one example, this same problem hap wine in all games that use analog 2. To explain the problem better, I am attaching a zip file with two photos The first is a photo of the joystick, and a second drawing I made to explain the problem better. -- 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 16

[Bug 39436] New: Gta Vice City - the black screen while playing clip at the game start
by wine-bugs＠winehq.org July 9, 2024

July 9, 2024

https://bugs.winehq.org/show_bug.cgi?id=39436 Bug ID: 39436 Summary: Gta Vice City - the black screen while playing clip at the game start Product: Wine Version: 1.7.52 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: trivial Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: geeronzero(a)gmail.com Distribution: --- Gta Vice City - the black screen while playing clip at the game start. The is music in it, but no image. -- 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 9

[Bug 19816] New: Enhancement request: MSVBVM60
by wine-bugs＠winehq.org July 9, 2024

July 9, 2024

http://bugs.winehq.org/show_bug.cgi?id=19816 Summary: Enhancement request: MSVBVM60 Product: Wine Version: unspecified Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: bammzilla(a)astronomy.com.ph I would like to request that Wine have its own built-in version of MSVBVM60. I don't know how difficult it would be, but since WinXP has it by default I would love Wine to have it as well. -- 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 39

[Bug 31786] New: Run the tests on real hardware
by wine-bugs＠winehq.org July 9, 2024

July 9, 2024

http://bugs.winehq.org/show_bug.cgi?id=31786 Bug #: 31786 Summary: Run the tests on real hardware Product: Wine-Testbot Version: unspecified Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: fgouget(a)codeweavers.com Classification: Unclassified It would be very useful to run some tests on real hardware. * This is the case for all the 3D graphics tests. For these we would even want to run them on both AMD and NVidia graphics cards(*). Currently they are essentially ignored by WineTestBot because the virtual graphic cards don't provide meaningful 3D support. * It could somewhat be useful for sound tests too, mostly to avoid timing issues, but also to ensure the results we get are not tainted by bugs in the emulated sound card. Also emulated sound cards typically don't support MIDI emulation. The problem is that it's very important to limit the test duration and to restore the test environment to a clean state after each test, no matter what happens, for two reasons: * Because it's not uncommon for tests to have side effects and for them to leave the test environment in an unusable state. Granted it happens much more often with older Windows releases as they are more prone to crashes. However graphics drivers also tend to be buggy and we would not want the tests to be tainted by a previous run (though a reboot should take care of most issues). * But also the Wine TestBot runs anything that gets posted by anonymous users on wine-patches. That's ok as long as such code is properly confined and not allowed to run for too long. That supposes thoroughly cleaning up the environment after a test has run, including anything that could happen at boot time. Virtual machines provide a simple solution to both of these issues which is why the TestBot relies on them heavily. With QEmu it's possible to let the guest OS access some peripherals directly via the 'passthrough' mode. This is normally done for network cards. If it worked for graphics cards that would be a great solution but it's not clear that it's feasible. Another option would be to play tricks with Grub scripts: have it boot from a clean Linux partition (or from the network?), restore the Windows partition from a clean disk image, reboot into that partition, and back on the clean partition with the next reboot. That still leaves the issue of forcing a reboot in case of a freeze or malware taking control of Windows (use a remote controlled power switch like in data centers?). (*) We currently have two such machines ready for this: http://www.winehq.org/pipermail/wine-devel/2012-February/094080.html -- 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 9

[Bug 33912] New: Remove All Wine Home Content - Button
by wine-bugs＠winehq.org July 9, 2024

July 9, 2024

http://bugs.winehq.org/show_bug.cgi?id=33912 Bug #: 33912 Summary: Remove All Wine Home Content - Button Product: Wine Version: 1.6-rc4 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: programs AssignedTo: wine-bugs(a)winehq.org ReportedBy: moceap(a)hotmail.com Classification: Unclassified This enhancement what I require that a button not remove only .wine folder in home , also delete all installed-by-wine-application desktop integration files Such as :: $HOME/.local/share/mime/packages/wine* $HOME/.local/share/applications/wine* And others . -- 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 7

[Bug 41668] New: wineboot mishandles user dir symlinks during update
by wine-bugs＠winehq.org July 9, 2024

July 9, 2024

https://bugs.winehq.org/show_bug.cgi?id=41668 Bug ID: 41668 Summary: wineboot mishandles user dir symlinks during update Product: Wine Version: 1.9.22 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: programs Assignee: wine-bugs(a)winehq.org Reporter: galtgendo(a)o2.pl Distribution: --- In a standard wine prefix 'Desktop', 'My Documents', etc. are symlinks to ${HOME}. As are their localized versions. I consider the first a wrong choice and and make those normal dirs in the prefix; as for the second, I turn those into symlinks to their English counterparts. Yet... Upon 'wineboot' at each wine update, while the English dirs stay untouched, the localized symlinks get reset into ${HOME} symlinks. If it's WAD, it's a misfeature; otherwise, it's a bug. -- 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 15