February 2023 - Wine-Bugs - list.winehq.org

[Bug 54446] New: Tiger Woods 2000 crashes after title video into main menu
by WineHQ Bugzilla Feb. 4, 2023

Feb. 4, 2023

https://bugs.winehq.org/show_bug.cgi?id=54446 Bug ID: 54446 Summary: Tiger Woods 2000 crashes after title video into main menu Product: Wine Version: 8.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: adec2011.ac(a)gmail.com Distribution: --- Tiger Woods 2000 shows EA title then the main video but crashes before displaying the main menu -- 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 51481] New: Why is the Epson printer printing blank pages?
by WineHQ Bugzilla Feb. 4, 2023

Feb. 4, 2023

https://bugs.winehq.org/show_bug.cgi?id=51481 Bug ID: 51481 Summary: Why is the Epson printer printing blank pages? Product: WineHQ.org Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: www-unknown Assignee: wine-bugs(a)winehq.org Reporter: baroncorrz(a)gmail.com Distribution: --- Epson printer printing blank pages because there must be some problem related to the cartridge ink or the nozzle. The cartridge ink must have been depleted. You need to check the level of ink by comparing the ink level with the marker on the ink tank. If the ink level is low, then it means that you need to put in a new cartridge. If you have an ink tank with a low ink level, then fill the ink tank with the ink. The problem can also be due to the clogging of the nozzle. You need to clean the nozzle if this happens. One of the best ways to prevent this is by giving fewer jobs to the printer. https://www.epsonprintersupportpro.us/blog/printer-printing-blank-pages/ -- 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 54445] New: some buttons in AIMP3 interface are missing on hovering, gap between main window and playlist
by WineHQ Bugzilla Feb. 4, 2023

Feb. 4, 2023

https://bugs.winehq.org/show_bug.cgi?id=54445 Bug ID: 54445 Summary: some buttons in AIMP3 interface are missing on hovering, gap between main window and playlist Product: Wine-staging Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: HarlanStaggs(a)gmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: Fedora Created attachment 73997 --> https://bugs.winehq.org/attachment.cgi?id=73997 gap and missing button is shown by red arrows how to reproduce: 1) open aimp3 (v3.60 build 1508 if its important) in some modern wine (personally i am using wine-staging 8.0rc2 but this bug occurs at least since wine 7.2) 2) play some music 3) set interface skin "all-in-one" (its one of default program skins, built-in) 4) hover/click mouse on stop/pause/repeat/etc button 5) button disappears 6) move mouse to somewhere else 7) button is still not visible you can still click on button but to see it you will have to restart program. my wine is not from fedora repos, its from wine repo. i downloaded and tried some custom wine like ge-wine, wine from bottles, built-in lutris wine - this bug occurs in all of them. i tried to switch to wayland and back to x11 - it doesnt help. also when this bug occurs there is another bug - gap between main window and playlist, i added an attachment to show how it looks. its minor bug and occurs occasionally, but its quite annoying. -- 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 53816] New: KartRider: Failed to initialize Nexon Game Security with error code e3010104
by WineHQ Bugzilla Feb. 4, 2023

Feb. 4, 2023

https://bugs.winehq.org/show_bug.cgi?id=53816 Bug ID: 53816 Summary: KartRider: Failed to initialize Nexon Game Security with error code e3010104 Product: Wine Version: 7.19 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: j20001970(a)yahoo.com.tw Distribution: --- The game is unable to get past the initialization stage to login window. How to reproduce the bug: 1. Install the game with PopKart_Setup_<version number>.exe 2. Locate the game directory (the installation path is "C:\Program Files (x86)\Gamania\PopKart\M01" by default) and run KartRider.exe with wine. 3. You will see game splash at the center with "Init...Ok", and Nexon Game Security splash at bottom right, then popup "Nexon Game Security Initialize Error.|Code = e3010104" will show. Game account registration is **NOT** required to reproduce the 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.

1 7

[Bug 54429] New: Feather Launcher Crashes after checking settings, mods, players etc..
by WineHQ Bugzilla Feb. 3, 2023

Feb. 3, 2023

https://bugs.winehq.org/show_bug.cgi?id=54429 Bug ID: 54429 Summary: Feather Launcher Crashes after checking settings, mods, players etc.. Product: Wine Version: 8.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: hyper.miniaturki(a)gmail.com Distribution: --- Created attachment 73979 --> https://bugs.winehq.org/attachment.cgi?id=73979 Logs Feather Launcher Crashes after checking settings, mods, players etc.. -- 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 50129] New: Calibre-portable error initializing the bypy frozen importer
by WineHQ Bugzilla Feb. 3, 2023

Feb. 3, 2023

https://bugs.winehq.org/show_bug.cgi?id=50129 Bug ID: 50129 Summary: Calibre-portable error initializing the bypy frozen importer Product: Wine Version: 5.0.3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: bilbiliblus(a)gmail.com Distribution: --- When I try to run Calibre-portable.exe y have this message: There was an error initializing the bypy frozen importer: <class 'MemoryError'>: Traceback (most recent call last): File bypy-importer.py, line 250, in <module> File bypy-importer.py, line 195, in __init__ It only happens since Calibre changed to version 5 and on. This very morning I've tried with Calibre 5.3 Thank you -- 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 53205] New: user32:input - test_rawinput() has a rare pair of failures in Wine
by WineHQ Bugzilla Feb. 2, 2023

Feb. 2, 2023

https://bugs.winehq.org/show_bug.cgi?id=53205 Bug ID: 53205 Summary: user32:input - test_rawinput() has a rare pair of failures in Wine Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- user32:input - test_rawinput() has a rare pair of failures in Wine: input.c:2784: Test failed: 15: expected WM_INPUT message input.c:2787: Test failed: 15: expected RIM_INPUT message https://test.winehq.org/data/patterns.html#user32:input These failures don't seem to depend on the locale or bitness. But there are only two known instances of these failures in WineTest making them likely to cause false positives (~0.5% failure rate). -- 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 52461] New: The Legend of Heroes: Trails of Cold Steel III usually hangs on exit
by WineHQ Bugzilla Feb. 2, 2023

Feb. 2, 2023

https://bugs.winehq.org/show_bug.cgi?id=52461 Bug ID: 52461 Summary: The Legend of Heroes: Trails of Cold Steel III usually hangs on exit Product: Wine Version: 7.0 Hardware: x86-64 OS: Linux Status: NEW Keywords: patch Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: z.figura12(a)gmail.com Distribution: --- Created attachment 71749 --> https://bugs.winehq.org/attachment.cgi?id=71749 patch mitigating the race To reproduce it's sufficient to install the game from Steam, get into the main menu, and select the "exit" option (page down with the S key then press Enter). Closing the window also works. The hang doesn't happen every time but does happen most times I tested. This is an application bug. There are two threads—a main thread and a worker thread. The main thread closes the handle to a mutex, goes off and does some other things, and then tries to wait on the mutex handle again (with a timeout of INFINITE). The worker thread basically does a timed wait, in a loop, on a set of handles, except that instead of passing a timeout to WaitForMultipleObjects(), it repeatedly creates a non-periodic auto-reset timer object, sets it for 1 ms, and adds it to the wait array, and then closes the handle. Because of the way handles are allocated in Wine (i.e. "lowest slot first"), and because of the specific pattern of handle usage of the program, what usually happens is that when the mutex handle is closed, the value is reused for a timer handle in the worker thread. While the worker thread is sleeping on the timer, the main thread also waits on it, and when the timer fires, it only wakes up the worker thread (which is almost always first in the queue). Closing the handle of a waitable object in Windows doesn't interrupt other waits in progress, and because the timer is non-periodic and auto-reset, the main thread ends up waiting forever. It turns out that Windows doesn't allocate handles like this. Rather, it seems to use a free list, much like we use in other places in Wine: testing shows that handles are always allocated in the reverse order that they are freed, including across multiple threads, and regardless of how many handles were just allocated. Changing Wine to use a free list like this actually does mitigate the problem. Because the worker thread closes its timer handle and then immediately creates a new one, it will almost always get back the same handle value. The main thread will most likely close its mutex handle while the worker thread is still sleeping, with the effect that the mutex handle won't be reallocated and the subsequent wait will return STATUS_INVALID_HANDLE. In theory the potential for the race is still there, however; it's still possible for the mutex handle to be closed after the timer handle is closed but before a new timer is created, in which case the mutex handle value will be reused for the timer value as it is currently. In practice I'm not sure if this happens more than a negligible fraction of the time. I certainly couldn't reproduce it after 6 or so tries, although that's not very many. Note that there are also reports of it hanging on Windows [1]... [1] https://steamcommunity.com/app/991270/discussions/0/2145343189632898904/ -- 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 54328] New: nsi:nsi - test_tcp_tables() sometimes crashes in Wine
by WineHQ Bugzilla Feb. 2, 2023

Feb. 2, 2023

https://bugs.winehq.org/show_bug.cgi?id=54328 Bug ID: 54328 Summary: nsi:nsi - test_tcp_tables() sometimes crashes in Wine Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- nsi:nsi - test_tcp_tables() sometimes crashes in Wine: Unhandled exception: page fault on read access to 0x00000000 in 32-bit code (0x646c35d0). [...] =>0 0x646c35d0 get_extended_tcp_table+0xd0(table=00B40E40, size=0062FCF4, sort=0, family=0x2, table_class=0x8) [Z:\home\fgouget\wine\winetest\src\dlls\iphlpapi\iphlpapi_main.c:3136] in iphlpapi (0x0062fc48) 1 0x646c7288 GetExtendedTcpTable+0x48(table=00B40E40, size=0062FCF4, sort=0, family=0x2, table_class=TCP_TABLE_OWNER_MODULE_ALL, reserved=0) [Z:\home\fgouget\wine\winetest\src\dlls\iphlpapi\iphlpapi_main.c:3185] in iphlpapi (0x0062fc88) 2 0x00403bc9 in nsi_test (+0x3bc9) (0x0062fd28) See https://test.winehq.org/data/patterns.html#nsi:nsi The crash is specific to my Linux desktop, fg-deb64, most likely because it has other network traffic while the test is running. -- 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 51313] New: gdi32:driver sometimes fails with a STATUS_GRAPHICS_PRESENT_OCCLUDED error
by WineHQ Bugzilla Feb. 2, 2023

Feb. 2, 2023

https://bugs.winehq.org/show_bug.cgi?id=51313 Bug ID: 51313 Summary: gdi32:driver sometimes fails with a STATUS_GRAPHICS_PRESENT_OCCLUDED error Product: Wine Version: 6.10 Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: gdi32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com gdi32:driver sometimes gets one or two failures like these: https://test.winehq.org/data/patterns.html#gdi32:driver driver.c:649: Test failed: Got unexpected return code 0xc01e0006. driver.c:689: Test failed: Got unexpected return code 0xc01e0006. 0xc01e0006 is STATUS_GRAPHICS_PRESENT_OCCLUDED. This has happened before but the reason for this error was not identified: https://www.winehq.org/pipermail/wine-devel/2019-July/148494.html I initially suspected a leftover window from a previous test, specifically an Internet Explorer first-run dialog. However the screenshots in the TestBot jobs show that this happens even when there is no such dialog (or at least the dialog is gone by the time the tests complete). The failures always happen on the same two lines despite the occlusion status being checked in other places. Also both failures happen right after minimizing the windows. So it seems likely there is a race condition, either in the test or in the underlying API (if so it spans Windows 10 1607 to 2009). -- 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