January 2024 - Wine-Bugs - list.winehq.org

[Bug 39793] New: Starcraft freezes when starting a Direct Cable Connection game
by wine-bugs＠winehq.org Jan. 22, 2024

Jan. 22, 2024

https://bugs.winehq.org/show_bug.cgi?id=39793 Bug ID: 39793 Summary: Starcraft freezes when starting a Direct Cable Connection game Product: Wine Version: 1.7.46 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: alexhenrie24(a)gmail.com Distribution: --- To reproduce: 1. Add yourself to the dialout (Ubuntu) or uucp (Arch) user group. 2. Log out and log back in. 3. In Starcraft, click Multiplayer, Direct Cable Connection, Ok. The problem is that Starcraft attempts to detect which serial port is connected by sending a burst of data on all ports COM1 through COM8. On Linux, COM1 through COM4 default to ttyS0 through ttyS3, but even though the device files exist, rarely do all of them correspond to actual physical devices. So, Starcraft hangs forever waiting for the write to complete successfully. A patchset that fixes this bug is available at https://github.com/alexhenrie/wine/commits/master First reported at https://appdb.winehq.org/objectManager.php?sClass=version&iId=149&iTestingI… -- 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 56233] New: On macOS Sonoma, applications respond slowly when caps lock is enabled
by WineHQ Bugzilla Jan. 21, 2024

Jan. 21, 2024

https://bugs.winehq.org/show_bug.cgi?id=56233 Bug ID: 56233 Summary: On macOS Sonoma, applications respond slowly when caps lock is enabled Product: Wine Version: 9.0 Hardware: x86-64 OS: MacOS Status: UNCONFIRMED Severity: normal Priority: P2 Component: winemac.drv Assignee: wine-bugs(a)winehq.org Reporter: bshanks(a)codeweavers.com macOS Sonoma introduces new "accessories" that appear below the text insertion point, like a caps lock indicator or an input language switcher (see [1]). These also show up in Wine windows, since they use existing APIs like NSTextInputClient to discover whether an insertion point is present and where in the view it's located. But, when an accessory like the caps lock indicator is displayed, interacting with the window (say, pulling down menus) is extremely slow. There are half-second pauses when displaying/hiding menus or other windows. This can be easily reproduced using notepad. I ran sample during the slowdown and was able to see the problem. Here's the backtrace, with some unimportant lines removed: 3294 __OnMainThread_block_invoke (in winemac.so) + 16 [0x20b56ac10] cocoa_event.m:507 3070 __macdrv_set_cocoa_window_frame_block_invoke (in winemac.so) + 100 [0x20b577dd4] cocoa_window.m:3464 3070 -[WineWindow setFrameFromWine:] (in winemac.so) + 557 [0x20b57258d] cocoa_window.m:2012 3070 -[WineWindow setFrameAndWineFrame:] (in winemac.so) + 60 [0x20b5721dc] cocoa_window.m:1938 3069 -[WineWindow setFrame:display:] (in winemac.so) + 136 [0x20b575008] cocoa_window.m:2682 ... 3066 -[WineWindow windowDidResize:skipSizeMove:] (in winemac.so) + 441 [0x20b5762d9] cocoa_window.m:3031 3066 -[TUINSCursorUIController invalidateCharacterCoordinates] (in TextInputUIMacHelper) + 113 [0x7ffc12ad733a] ... 1643 -[WineContentView firstRectForCharacterRange:actualRange:] (in winemac.so) + 196 [0x20b56ef24] cocoa_window.m:926 1643 -[WineEventQueue query:timeout:flags:] (in winemac.so) + 217 [0x20b56a209] cocoa_event.m:336 1643 -[WineApplicationController waitUntilQueryDone:timeout:processEvents:] (in winemac.so) + 224 [0x20b55eb70] cocoa_app.m:350 Pulling menus down creates new HWNDs, I think initially with 1x1 size, and then the frame is set. This triggers windowDidResize, which calls [[[self contentView] inputContext] invalidateCharacterCoordinates]. This is sensible, character coordinates might change when the window is resized. And when caps lock is enabled, the system then immediately calls firstRectForCharacterRange:actualRange: to refresh the character coordinates. This triggers a Wine QUERY_IME_CHAR_RECT query. The problem is that the thread that would answer the query is currently in OnMainThread(), things deadlock and the query times out after 300 ms. I think it's called twice, that's how you get 600 ms. The twist is that OnMainThread() does service queries while waiting, except for QUERY_IME_CHAR_RECT, because of a 2016 bug with Japanese input in Excel 2003/2007/2010. If you undo 33610da6b4f5d9ad052173f005fdb735dc471445 so that QUERY_IME_CHAR_RECT is handled normally, the timeout goes away and things work normally. This needs to be fixed, my first thought is that maybe there have been changes in the IME system since 2016 so that the special-case for QUERY_IME_CHAR_RECT is no longer needed? A first step is to revert the 2016 fix and see if the Excel bug can still be reproduced. [1]: https://developer.apple.com/documentation/appkit/text_display/adopting_the_… -- 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 56202] New: Genshin impact cyrillic is ?????
by WineHQ Bugzilla Jan. 21, 2024

Jan. 21, 2024

https://bugs.winehq.org/show_bug.cgi?id=56202 Bug ID: 56202 Summary: Genshin impact cyrillic is ????? Product: Wine Version: 8.21 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: googa.vo1d(a)gmail.com Distribution: --- Created attachment 75910 --> https://bugs.winehq.org/attachment.cgi?id=75910 привет из ???? switchin in linux to cyrillics causes in genshin this ???? wrote -- 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 5

[Bug 55921] New: EverQuest Titanium/Rof2 Clients: Slow Disk Loading/Freezing?
by WineHQ Bugzilla Jan. 21, 2024

Jan. 21, 2024

https://bugs.winehq.org/show_bug.cgi?id=55921 Bug ID: 55921 Summary: EverQuest Titanium/Rof2 Clients: Slow Disk Loading/Freezing? Product: Wine Version: 8.20 Hardware: arm OS: Mac OS X Status: UNCONFIRMED Severity: minor Priority: P2 Component: d3d Assignee: wine-bugs(a)winehq.org Reporter: rgirard59(a)yahoo.com When you load up the game and try to click through the different screens by clicking the buttons, the game seems to completely freeze for a brief period of time between screen loads. Also, once you try to go to the character select screen, or load into the game, it seems to take significantly longer to load than either on parallels or a intel wine mac. Another thing I had noticed that was odd is that when I used a fresh wine install that didn't have the d3d9 redist june installed, the game would load up fast between these screens like it should, however it would crash once loading to the character select screen, due to missing d3d9 libraries I assume. Once I installed that redist, the screens would start having the freezing issue. Mac Sonoma, M2 -- 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 10

[Bug 56185] New: The GitLab Windows test job runs even when not needed
by WineHQ Bugzilla Jan. 21, 2024

Jan. 21, 2024

https://bugs.winehq.org/show_bug.cgi?id=56185 Bug ID: 56185 Summary: The GitLab Windows test job runs even when not needed Product: WineHQ Gitlab Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: gitlab-unknown Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com The GitLab Windows test jobs run even for MRs that don´t touch the tests. For instance MR!4840 does not touch the test: https://gitlab.winehq.org/wine/wine/-/merge_requests/4840/diffs And yet test-win10-21h2-32 ran (same for the 64-bit tests job): https://gitlab.winehq.org/fgouget/wine/-/jobs/48245 And the corresponding winetest.log file is empty which corresponds to an empty winetest.args file. This makes sense since build-linux systematically generates winetest.args and it's only in the Windows job that we check whether that file is empty or not. This could be avoided by generating dynamic child jobs in build-linux. Then the check for whether it is necessary to run the Windows tests could be done in build-linux and a 'dummy: rules: when: never' job could be generated if nothing needs to be run. See below for an example of a dynamic child job. https://blog.devops.dev/using-dynamic-pipelines-in-gitlab-583cf4f6acd0 -- 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 6

[Bug 56221] New: Quick start failure for Civilization 4
by WineHQ Bugzilla Jan. 21, 2024

Jan. 21, 2024

https://bugs.winehq.org/show_bug.cgi?id=56221 Bug ID: 56221 Summary: Quick start failure for Civilization 4 Product: Wine Version: 9.0 Hardware: x86-64 URL: https://appdb.winehq.org/objectManager.php?sClass=appl ication&iId=2514 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: Markus.Elfring(a)web.de Distribution: --- I tried another start out for the game “Civilization IV” by components from the software package “wine 9.0-1670.1”. Markus_Elfring(a)Sonne:~> wine 'C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Firaxis Games\Sid Meier'\''s Civilization 4\Sid Meier'\''s Civilization 4 starten.lnk' 007c:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005 … 00bc:err:ntoskrnl:ZwLoadDriver failed to create driver L"\\Registry\\Machine\\System\\CurrentControlSet\\Services\\SecDrv": c0000142 003c:fixme:service:scmdatabase_autostart_services Auto-start service L"SecDrv" failed to start: 1114 0024:fixme:exec:SHELL_execute flags ignored: 0x00004000 … I wondered then why a corresponding application window was not presented. Markus_Elfring(a)Sonne:~> strace wine 'C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Firaxis Games\Sid Meier'\''s Civilization 4\Sid Meier'\''s Civilization 4 starten.lnk' … exit_group(3) = ? +++ exited with 3 +++ How will the clarification be continued with such information? -- 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 6

[Bug 56181] New: GitLab fails to detect Windows test failures
by WineHQ Bugzilla Jan. 21, 2024

Jan. 21, 2024

https://bugs.winehq.org/show_bug.cgi?id=56181 Bug ID: 56181 Summary: GitLab fails to detect Windows test failures Product: WineHQ Gitlab Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: gitlab-unknown Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com In MR!4839 I introduced a test failure in serialui:confdlg: https://gitlab.winehq.org/wine/wine/-/merge_requests/4839/diffs This is confirmed by the test-linux-32 job which fails: https://gitlab.winehq.org/fgouget/wine/-/jobs/48236 But both the test-win10-21h2-32 and test-win10-21h2-64 jobs succeed: https://gitlab.winehq.org/fgouget/wine/-/jobs/48237 https://gitlab.winehq.org/fgouget/wine/-/jobs/48238 In fact the corresponding winetest.log only contain: [...] | ACP=1252 | Dll info: | Test output: So it looks like the jobs did not even run any test? -- 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 4

[Bug 56228] New: err:module:import_dll Library WDFLDR.SYS
by WineHQ Bugzilla Jan. 20, 2024

Jan. 20, 2024

https://bugs.winehq.org/show_bug.cgi?id=56228 Bug ID: 56228 Summary: err:module:import_dll Library WDFLDR.SYS Product: Wine-staging Version: 8.21 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: dz.wbdev(a)gmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- i want to install ad driver for zte modem and i get this error: wine ZTEDrvSetup.exe.dat  127 ✘ 0098:fixme:wineusb:query_id Unhandled ID query type 0x5. 0098:fixme:wineusb:query_id Unhandled ID query type 0x5. 0098:fixme:wineusb:query_id Unhandled ID query type 0x5. 0098:fixme:wineusb:query_id Unhandled ID query type 0x5. 0098:fixme:wineusb:query_id Unhandled ID query type 0x5. 0098:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005 0098:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005 0098:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005 0098:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005 00e0:err:module:import_dll Library WDFLDR.SYS (which is needed by L"C:\\windows\\system32\\drivers\\DBUtilDrv2.sys") not found 00e0:err:ntoskrnl:ZwLoadDriver failed to create driver L"\\Registry\\Machine\\System\\CurrentControlSet\\Services\\DBUtilDrv2": c0000142 003c:fixme:service:scmdatabase_autostart_services Auto-start service L"DBUtilDrv2" failed to start: 1114 0024:fixme:file:NtLockFile I/O completion on lock not implemented yet 0024:fixme:apphelp:ApphelpCheckInstallShieldPackage stub: 0055F04C L"C:\\users\\pc\\Temp\\{E5BBC2B9-701D-439F-B0CA-4A221FF3A0DF}\\Disk1\\data1.hdr" 0024:fixme:sfc:SRSetRestorePointA 010E8570 010EC070 0024:fixme:sfc:SRSetRestorePointA 010E8570 010EC070 0138:err:ole:std_release_marshal_data could not map object ID to stub manager, oxid=13400000138, oid=2 0138:err:ole:CoReleaseMarshalData StdMarshal ReleaseMarshalData failed with error 0x8001011d how to fix it? -- 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 4

[Bug 48908] New: Dr Brain 3 broken color palette
by WineHQ Bugzilla Jan. 20, 2024

Jan. 20, 2024

https://bugs.winehq.org/show_bug.cgi?id=48908 Bug ID: 48908 Summary: Dr Brain 3 broken color palette Product: Wine Version: 5.5 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: maxmusterm(a)gmail.com Distribution: --- Created attachment 66865 --> https://bugs.winehq.org/attachment.cgi?id=66865 Example image of dr brain running in xephyr Dr Brain 3 is a 16bit Windows program that requires 8bit colors. So to get it running we have to use one of these methods https://wiki.winehq.org/256_Color_Mode I tried every last one of those methods and every method leads to the same result you can see in the image attached to this bug. No error message is printed out by wine. I encountered this bug a few years ago for the first time, but didn't open a bug report for it, since I thought this could be a problem with the virtual X. However when viewing images in the Xephyr session all colors are displayed correctly. Right now the only way for me to run this game is using dosbox with win3.1 or another form of emulation. -- 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 54349] New: 'wine-mono' package doesn't re-ask for installation if you click cancel and subsequent run a .NET program (by contrast, the Gecko package does)
by WineHQ Bugzilla Jan. 20, 2024

Jan. 20, 2024

https://bugs.winehq.org/show_bug.cgi?id=54349 Bug ID: 54349 Summary: 'wine-mono' package doesn't re-ask for installation if you click cancel and subsequent run a .NET program (by contrast, the Gecko package does) Product: Wine Version: 8.0-rc4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: NM64+bugs.winehq.org(a)PM.me Distribution: --- Created attachment 73920 --> https://bugs.winehq.org/attachment.cgi?id=73920 video demonstration of the full process for reproducing the issue (tested with wine v8.0-rc4 since v8.0-rc5 isn't yet available in Mint's package manager) Simply put, when the message appears asking to install the 'wine-mono' package, if you click cancel and then subsequently try to run a program that requires .NET, it will not ask about installing the 'wine-mono' package again. By contrast, if you try to run a program that requires the Gecko package, it will always ask if you want to install the Gecko package even if you click cancel - it will still ask again the next time you run the program. See the attached video file on fully reproducing the issue; it was tested using the Mint 21.1 Cinnamon live ISO. -- 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