July 2022 - Wine-bugs - list.winehq.org

[Bug 53322] New: Ride 2 config tool needs mfc140u.dll
by WineHQ Bugzilla 07 Jul '22

07 Jul '22

https://bugs.winehq.org/show_bug.cgi?id=53322 Bug ID: 53322 Summary: Ride 2 config tool needs mfc140u.dll Product: Wine Version: 7.12 Hardware: x86-64 OS: Linux Status: NEW Severity: minor Priority: P2 Component: mfc Assignee: wine-bugs(a)winehq.org Reporter: andrey.goosev(a)gmail.com Distribution: --- 049c:err:module:import_dll Library mfc140u.dll (which is needed by L"C:\\Program Files (x86)\\Steam\\steamapps\\common\\Ride 2\\ConfigDialogX64.dll") not found wine-7.12-111-g9af3a79b963 -- 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.

1 0

[Bug 40865] New: Steam needs to be online to update. Please confirm your network connection and try again.
by wine-bugs＠winehq.org 07 Jul '22

07 Jul '22

https://bugs.winehq.org/show_bug.cgi?id=40865 Bug ID: 40865 Summary: Steam needs to be online to update. Please confirm your network connection and try again. Product: Wine Version: 1.9.12 Hardware: x86 OS: NetBSD Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: adrien_fernandes2(a)hotmail.com Created attachment 54877 --> https://bugs.winehq.org/attachment.cgi?id=54877 WINEDEBUG=+winhttp,+wininit,+winsock,+teh,+sid wine Steam.exe Steam can not fetch client (http problem ?). I don't think it is because it can't find my network, I was using mupen64pp.exe and I successfully joined a friend online to play with him. -- 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

[Bug 53318] New: error on c sharp program
by WineHQ Bugzilla 06 Jul '22

06 Jul '22

https://bugs.winehq.org/show_bug.cgi?id=53318 Bug ID: 53318 Summary: error on c sharp program Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: pingo-power(a)hotmail.fr Distribution: --- Created attachment 72699 --> https://bugs.winehq.org/attachment.cgi?id=72699 logs a -- 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.

1 2

[Bug 53320] New: Star Craft 2 bad textures
by WineHQ Bugzilla 06 Jul '22

06 Jul '22

https://bugs.winehq.org/show_bug.cgi?id=53320 Bug ID: 53320 Summary: Star Craft 2 bad textures Product: Wine-staging Version: 7.12 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: terapy-session(a)bk.ru CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Created attachment 72702 --> https://bugs.winehq.org/attachment.cgi?id=72702 screen Red squares around some units, such as those from the company. Launched with DXVK installed, but the HUD in the game did not work, perhaps DXVK does not work for this game, and bugs with OpenGL (which sometimes happens with OpenGL) -- 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.

1 0

[Bug 53316] New: WGL context sharing does not work on Intel driver
by WineHQ Bugzilla 06 Jul '22

06 Jul '22

https://bugs.winehq.org/show_bug.cgi?id=53316 Bug ID: 53316 Summary: WGL context sharing does not work on Intel driver Product: Wine Version: 7.12 Hardware: x86-64 OS: Windows Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: trass3r(a)gmail.com Originally encountered when testing DK2: https://bugs.winehq.org/show_bug.cgi?id=44260#c8 3de8:trace:d3d:texture2d_blt dst_texture 00B11400, ... 3de8:warn:d3d:context_create_wgl_attribs Failed to create a WGL context with wglCreateContextAttribsARB, last error 0xaa. 3de8:err:d3d:wined3d_context_gl_create_wgl_ctx Failed to create a WGL context. 0xaa is ERROR_BUSY, which is returned because the context to be shared by the new context in the helper thread is still current in the main thread. See https://github.com/roxlu/windows-opengl-context#solution- https://bugzilla.gnome.org/show_bug.cgi?id=792407#c2 https://gitlab.freedesktop.org/gstreamer/gst-plugins-good/blob/master/ext/q… Tested on Win11, Intel UHD620 Driver 30.0.101.3113 with wine reg add 'HKCU\Software\Wine\Direct3D' /v csmt /t REG_DWORD /d 0 The problem does not occur when replacing the driver with GLonD3D12 from https://github.com/pal1000/mesa-dist-win -- 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.

1 1

[Bug 53179] New: Can't get into the Lineage 2 server
by WineHQ Bugzilla 05 Jul '22

05 Jul '22

https://bugs.winehq.org/show_bug.cgi?id=53179 Bug ID: 53179 Summary: Can't get into the Lineage 2 server Product: Wine-staging Version: 7.11 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: terapy-session(a)bk.ru CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Не зайти на сервер Lineage 2. После авторизации прохожу до выбора сервера, и при нажатии войти никакой реакции, через несколько минут происходит дисконнект. 3 июня работало, возможно повлияло обновление Wine. Старого пакета Wine не сохранилось чтоб проверить. В ошибках логах есть: 0298:err:winediag:WSASocketW Failed to create a socket of type SOCK_RAW, this requires special permissions. Сервер использует WMI, возможно там что-то меняли. -- 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.

1 14

[Bug 53313] New: Weird characters without proper LC_ALL with Inno Setup 4.2.2 installers
by WineHQ Bugzilla 05 Jul '22

05 Jul '22

https://bugs.winehq.org/show_bug.cgi?id=53313 Bug ID: 53313 Summary: Weird characters without proper LC_ALL with Inno Setup 4.2.2 installers Product: Wine Version: 7.11 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: abacadacaba(a)gmail.com Distribution: --- Users shouldn't prepend LC_ALL for every executable if executable contains one or several language(s). Proper language for executable can be guessed from installer. Installer had just one language and this language was correct. Contained Resources by Language: NEUTRAL 6 DUTCH 4 ENGLISH US 3 -- 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.

1 3

[Bug 47871] New: gameux:gameexplorer crashes randomly
by WineHQ Bugzilla 05 Jul '22

05 Jul '22

https://bugs.winehq.org/show_bug.cgi?id=47871 Bug ID: 47871 Summary: gameux:gameexplorer crashes randomly Product: Wine Version: 4.17 Hardware: x86 OS: Windows Status: NEW Severity: normal Priority: P2 Component: gameux Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com gameux:gameexplorer crashes randomly on Windows 8 and 10: gameexplorer.c:633: prepared EXE path: L"C:\\Users\\winetest\\AppData\\Local\\Temp\\wct" gameux:gameexplorer:0940 done (-1073741819) in 1s Test failed: crash (c0000005) Every line with a 'mixed' result is a date when the test crashed: https://test.winehq.org/data/tests/gameux:gameexplorer.html Unfortunately there is no backtrace but the last visible trace is in test_install_uninstall_game() which is the last function to be called. So that narrows down the range where the test crashes. The crash happens in both 32 and 64 bit tests on the following configurations: * cw-rx460-32 *real hardware* machine running Windows 8.1 * w8 and w8adm both Windows 8.1 TestBot VMs, the former running with elevated privileges and the latter just in an administrator account. * w1064v1507 a Windows 10 1507 TestBot VM (elevetated privileges). -- 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.

1 3

[Bug 53305] New: SketchUp 2017: Keyboard entry doesn't work correctly after reinstall.
by WineHQ Bugzilla 04 Jul '22

04 Jul '22

https://bugs.winehq.org/show_bug.cgi?id=53305 Bug ID: 53305 Summary: SketchUp 2017: Keyboard entry doesn't work correctly after reinstall. Product: Wine Version: 7.0-rc6 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: HeartwoodJack(a)gmail.com Distribution: --- SketchUp 2017 stopped working so I reinstalled. Now it works again, very nicely* but keyboard entry doesn't work correctly. I thought that it was just the [Esc] key (to cancel an operation) but numerical entry (to set dimensions etc) don't work. Keyboard shortcuts continue to work. Exploring the behaviour, it seems that if I move or resize the SketchUp window, then the keys work until after an operation. This doesn't apply to internal windows like toolbars or attributes like 'Materials'. It feels like the cursor click on the drawing space steals focus from the part of the program that listens for data or cancellation. Nevertheless, mid-operation, you can still cancel it by selecting a new operation (using a tool shortcut like [M] or [B]) so it isn't deaf to the keyboard input all together. Any ideas? * Works nicely, although this needs to be open in the background, as usual and without effect: Bug 50775 - Sketchup Make 2017 displays error message about sketchup_webhelper.exe -- 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.

1 2

[Bug 53303] New: Tycho: When Tycho tries to run a companion exe it corrupts the exe (VirusTotal check is clean)
by WineHQ Bugzilla 03 Jul '22

03 Jul '22

https://bugs.winehq.org/show_bug.cgi?id=53303 Bug ID: 53303 Summary: Tycho: When Tycho tries to run a companion exe it corrupts the exe (VirusTotal check is clean) Product: Wine Version: 7.12 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: jessethecandent(a)gmail.com Distribution: --- Created attachment 72680 --> https://bugs.winehq.org/attachment.cgi?id=72680 sha1 hashes for files A VirusTotal scan for the programs involved is clean along with the corrupted programs. I am using the development version of wine (wine-7.12). Tycho uses a modified version of Find_Orb (find_o64_modified.exe) for some of its tasks but will corrupt it when it tries to use it. If dosbox is available, wine will run the corrupt exe in dosbox. Wine versions 5.16 and below will make a corrupt find_o64_modified.exe.tmp instead of replacing the original exe, which allows Tycho to properly use Find_Orb so Tycho can identify known minor planets. However, a version of wine that old has bad OpenCL support. In a windows 10 VM the hash of find_o64_modified.exe does not change when Tycho uses it. Given Find_Orb's important place in the workflow of searching for minor planets, people would quickly notice if it got corrupted in windows. Corrupt exe observations: -The corrupt exe is usually smaller than the original, even if you target smallexe64.exe (https://github.com/katahiromz/smallexe) giving you a 3 byte exe. -The corrupt exe contains pieces of the original exe and stuff not in the original exe. -The same target exe produces the same corrupt exe but a different target exe produces a different corrupt exe. -Corrupting a corrupt exe does not change it. warn+all doesn't give anything useful and a trace+all capture of the corruption event ran my VM out of disk space. Reproduction instructions: Running Linux in a VM is recommended due to exe corruption. Uninstall dosbox if you don't want to run the corrupted exe. Go to www.tycho-tracker.com/download and download the "Tycho" (v9.2) installer zip and the "Find_Orb [modified for Tycho]" (2021-07-20) zip file. Extract the Tycho installer from its zip file. In a 64 bit wine prefix run the Tycho installer. Extract the find_orb_2021-07-20/find_o64/ directory and place the find_o64 directory in the wine drive_c directory. Make a copy of find_o64_modified.exe and place it somewhere for future reference. Use wine to run Program Files/Tycho/Tycho.exe . Click continue at the invitation to register window. Go to the Settings dropdown menu and click on Find_Orb. In the "Full Path to Find_Orb Modified Executable" section click browse and go to the find_o64_modified.exe extracted previously (or put in a different file you wish to corrupt) Click on "Run Diagnostic Test". THIS WILL CORRUPT THE SELECTED EXE. IT WILL RUN IF YOU HAVE DOSBOX INSTALLED!! A successful test would look like: [2022/07/02 16:20:20]: Ready. [2022/07/02 16:20:22]: Beginning test... [2022/07/02 16:20:23]: [INFO] Returned identifier=[131075], num tries=[0] [2022/07/02 16:20:23]: [ OK ] Version [5] is a supported version. [2022/07/02 16:20:23]: End of test. [2022/07/02 16:20:23]: Ready. Close Tycho and compare the find_o64_modified.exe (or other file you corrupted) to the good copy you have. -- 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.

1 2