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

[Bug 19446] New: Icy Tower 1.4 installer erroneously creates an installation log in an invalid directory
by wine-bugs＠winehq.org 19 Apr '23

19 Apr '23

http://bugs.winehq.org/show_bug.cgi?id=19446 Summary: Icy Tower 1.4 installer erroneously creates an installation log in an invalid directory Product: Wine Version: 1.1.26 Platform: PC URL: http://download.cnet.com/Icy-Tower/3000-2099_4-1007506 0.html OS/Version: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: arethusa26(a)gmail.com With wine-1.1.26-183-gc6570a5, after installing Icy Tower 1.4, a directory listing of the Wine drive_c folder shows an unusual directory created in the root of drive_c: andrew(a)ubuntu-desktop:~$ ls ~/icytower/drive_c C: games Program Files users windows andrew(a)ubuntu-desktop:~$ ls ~/icytower/drive_c/C:/windows/temp INSTALL.LOG >From relay log: 0019:Call KERNEL32.CreateDirectoryA(0033f354 "C:",00000000) ret=1000c978 0019:Ret KERNEL32.CreateDirectoryA() retval=00000000 ret=1000c978 ... 0019:Call KERNEL32.CreateDirectoryA(0033f354 "C:\\C:",00000000) ret=1000c978 0019:Ret KERNEL32.CreateDirectoryA() retval=00000001 ret=1000c978 ... 0019:Call KERNEL32.CreateFileA(0033f354 "C:\\C:\\windows\\temp\\INSTALL.LOG",40000000,00000000,00000000,00000002,00000080,00000000) ret=100140c9 0019:Ret KERNEL32.CreateFileA() retval=00000068 ret=100140c9 The directory creation operation that was logged does not succeed on Windows, and it should not succeed on Wine. -- 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 26532] New: Barnes and Noble Nook eReader sync data to server.
by wine-bugs＠winehq.org 19 Apr '23

19 Apr '23

http://bugs.winehq.org/show_bug.cgi?id=26532 Summary: Barnes and Noble Nook eReader sync data to server. Product: Wine Version: 1.3.16 Platform: All OS/Version: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: wininet AssignedTo: wine-bugs(a)winehq.org ReportedBy: JNowka(a)gmail.com Download: http://www.barnesandnoble.com/download/ereader/ereader-windows.asp Version: 2.5.3.4630 Licence Type: Proprietary Cost: Free The Barnes And Noble Nook e-Reader for PC does not upload updates to bookmarks or annotations to the server. The errors and fixmes that are returned when it is ran from the command line is as follows: fixme:wininet:set_cookie persistent cookies not handled (L"expires=Mon, 21-Mar-2016 23:20:09 GMT; path=/") err:wininet:HTTP_ParseDateAsAsctime unexpected weekday L"-1" err:wininet:HTTP_ParseDate unexpected date format L"-1" fixme:wininet:CommitUrlCacheEntryInternal entry already in cache - don't know what to do! fixme:wininet:InternetCheckConnectionW fixme:wininet:InternetSetOptionW Option 7 STUB fixme:wininet:InternetSetOptionW Option INTERNET_OPTION_DATA_RECEIVE_TIMEOUT (180000): STUB The fixme warnings are repeated consistently until the software is closed. -- 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 52987] New: comctl32:tooltips - test_customdraw() fails systematically on some Windows 10 machines
by WineHQ Bugzilla 17 Apr '23

17 Apr '23

https://bugs.winehq.org/show_bug.cgi?id=52987 Bug ID: 52987 Summary: comctl32:tooltips - test_customdraw() fails systematically on some Windows 10 machines Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: comctl32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com comctl32:tooltips - test_customdraw() fails systematically on some Windows machines: tooltips.c:251: Test failed: 0: Failed to get current tool 0. tooltips.c:258: Test failed: 0: Unexpected hwnd CCCCCCCCCCCCCCCC. tooltips.c:259: Test failed: 0: Unexpected hinst CCCCCCCCCCCCCCCC. tooltips.c:260: Test failed: 0: Unexpected uId cccccccccccccccc. tooltips.c:261: Test failed: 0: Unexpected lParam cccccccccccccccc. tooltips.c:251: Test failed: 1: Failed to get current tool 0. tooltips.c:258: Test failed: 1: Unexpected hwnd CCCCCCCCCCCCCCCC. tooltips.c:259: Test failed: 1: Unexpected hinst CCCCCCCCCCCCCCCC. tooltips.c:260: Test failed: 1: Unexpected uId cccccccccccccccc. tooltips.c:261: Test failed: 1: Unexpected lParam cccccccccccccccc. [... all 6 iterations fail ...] https://test.winehq.org/data/patterns.html#comctl32:tooltips Also this impacts both test_customdraw() calls: the one after test_create_tooltip(FALSE) and the one after test_create_tooltip(TRUE) though the latter is more random. When the latter fails there is an extra couple of failures in test_TTN_SHOW(): tooltips.c:261: Test failed: 5: Unexpected lParam cccccccccccccccc. tooltips.c:1216: Test failed: TTN_SHOW parent seq: the msg sequence is not complete: expected 004e - actual 0000 tooltips.c:1216: Failed sequence TTN_SHOW parent seq: tooltips.c:1216: 0: expected: msg 004e - actual: nothing v6util.h:92: created cc6.manifest tooltips.c:251: Test failed: 0: Failed to get current tool 0. [...] tooltips.c:1216: Test failed: TTN_SHOW parent seq: the msg sequence is not complete: expected 004e - actual 0000 However the failure pattern is strange: * The failures mostly happen on the cw-gtx560 and cw-rx460 machines. But w1064v1709-64 has the same failures so it's not a real hardware vs. VM issue. * The failures happen on Windows 10 1709, 21h1 and 21h2, but not on 1507, 1607, 1809 or 2004. 1909 had failures on March 21 and 22 but not in the month since then. So it does not really seem related to the Windows version. * cw-gtx560-21H1 and cw-rx460-21H1 never had failures in the 32-bit tests but the failures happen in 32-bit on cw-gtx560-1709 and cw-rx460-1709. So it's not a bitness issue and it should not be a machine configuration issue either. The failure on line 251 indicates that there is no tooltip at all. Maybe there is a window that has the focus and prevented the tooltip from opening? (that window if any is not visible in the final screenshot) If it is a focus issue, skipping when the windows does not have the focus could avoid the failures. -- 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 30826] New: Gigasoft's ProEssentials demo crashes on startup
by wine-bugs＠winehq.org 16 Apr '23

16 Apr '23

http://bugs.winehq.org/show_bug.cgi?id=30826 Bug #: 30826 Summary: Gigasoft's ProEssentials demo crashes on startup Product: Wine Version: 1.5.5 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: dank(a)kegel.com Classification: Unclassified To reproduce, wget http://www.gigasoft.com/PE7-Pro-Setup.exe wine PE7-Pro-Setup.exe cd .wine/drive_c/ProEssentials7/DEMO wine PEDemo.exe Click the popup window to make it go away. Unhandled exception: page fault on read access to 0x5050ff98 in 32-bit code (0x7ed36a26). Or, sometimes: Unhandled exception: page fault on read access to 0x00000048 in 32-bit code (0x7ed2ea26). The backtrace seems the same either way: Backtrace: =>0 get_log_fontW+0x16(font=0x720041, graphics=0x154780, lf=0x32e92c) [dlls/gdiplus/font.c:486] 1 get_font_hfont+0x10e(graphics=0x154780, font=0x720041, hfont=0x32eb58) [dlls/gdiplus/graphics.c:2139] 2 GdipDrawString+0x2c1(graphics=0x154780, string="Bollinger Upper", length=0xf, font=0x720041, rect=0x32eba8, format=0x149e28, brush=0x154b68) [dlls/gdiplus/graphics.c:5210] 486 lf->lfHeight = -em_size_to_pixel(font->emSize, font->unit, font->family->dpi); Installing corefonts doesn't 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 23

[Bug 48734] New: How to Survive crashes when starting a new game
by WineHQ Bugzilla 16 Apr '23

16 Apr '23

https://bugs.winehq.org/show_bug.cgi?id=48734 Bug ID: 48734 Summary: How to Survive crashes when starting a new game Product: Wine Version: 5.0-rc1 Hardware: x86 URL: https://store.steampowered.com/app/250400/How_to_Survi ve/ OS: Linux Status: NEW Keywords: regression Severity: normal Priority: P2 Component: quartz Assignee: wine-bugs(a)winehq.org Reporter: gyebro69(a)gmail.com CC: z.figura12(a)gmail.com Regression SHA1: 94822bae5fed8a3bbda00adb4e79652cd9374309 Distribution: --- Created attachment 66616 --> https://bugs.winehq.org/attachment.cgi?id=66616 terminal output The game was started in windowed mode to work around bug #48732. When I start a new single-player game from the menu, Wine crashes when attempting to play the first video. I think it's 'prologue.avi' which should be playing at this point. Cutscenes didn't work properly before the regression, only a black screen was shown and pressing <Space> or <Esc> made it possible to skip the video. Now Wine crashes. The crash was introduced by commit 94822bae5fed8a3bbda00adb4e79652cd9374309 quartz/vmr9: Create the rendering window when the filter is created. To reproduce the problem select <Local Game> in the main menu, then <Story Mode>, <1 Player>, choose a character and difficulty level. After a short loading animation Wine crashes. Tested in wine-5.3-181-geb63713f60. -- 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 49332] New: CounterPath Bria Solo crashes after login dialog
by WineHQ Bugzilla 14 Apr '23

14 Apr '23

https://bugs.winehq.org/show_bug.cgi?id=49332 Bug ID: 49332 Summary: CounterPath Bria Solo crashes after login dialog Product: Wine Version: 5.10 Hardware: x86 URL: https://www.counterpath.com/bria-solo/ OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: setupapi Assignee: wine-bugs(a)winehq.org Reporter: whydoubt(a)gmail.com Distribution: Fedora After getting past the login dialog, the program crashes almost immediately. It does pop up a dialog that offers to submit logs to the developers. I have not found any logs produced by the software that provide insight into what caused the crash. However, after turning on several debug channels in wine, I found this right before things go sideways: 0024:trace:nls:FormatMessageW (0x1300,00000000,0xe000020e,0x400,0031E634,1,00000000) I tracked down the 0xe000020e error code in this case as coming from SetupDiDestroyDeviceInfoList, even though the call had completed successfully. -- 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 53269] New: uiautomationcore:uiautomation fails on Windows 10 1909
by WineHQ Bugzilla 14 Apr '23

14 Apr '23

https://bugs.winehq.org/show_bug.cgi?id=53269 Bug ID: 53269 Summary: uiautomationcore:uiautomation fails on Windows 10 1909 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: uiautomationcore Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com uiautomationcore:uiautomation fails on Windows 10 1909: uiautomation.c:355: Test failed: unexpected call Accessible_get_accRole uiautomation.c:379: Test failed: unexpected call Accessible_get_accState uiautomation.c:256: Test failed: unexpected call Accessible_get_accChildCount uiautomation.c:254: Test failed: unexpected call Accessible2_get_accChildCount uiautomation.c:474: Test failed: unexpected call Accessible_accLocation uiautomation.c:318: Test failed: unexpected call Accessible_get_accName uiautomation.c:164: Test failed: unexpected call Accessible2_QI_IAccIdentity uiautomation.c:234: Test failed: unexpected call Accessible2_get_accParent uiautomation.c:316: Test failed: unexpected call Accessible2_get_accName uiautomation.c:1478: Test failed: elprov != NULL, elprov 00000000007B2CA0 uiautomation.c:1486: Test failed: elprov != NULL, elprov 00000000007B2FB0 uiautomation.c:1524: Test failed: expected Accessible_get_uniqueID uiautomation.c:355: Test failed: unexpected call Accessible_get_accRole uiautomation.c:379: Test failed: unexpected call Accessible_get_accState uiautomation.c:256: Test failed: unexpected call Accessible_get_accChildCount uiautomation.c:254: Test failed: unexpected call Accessible2_get_accChildCount uiautomation.c:474: Test failed: unexpected call Accessible_accLocation uiautomation.c:318: Test failed: unexpected call Accessible_get_accName uiautomation.c:164: Test failed: unexpected call Accessible2_QI_IAccIdentity uiautomation.c:234: Test failed: unexpected call Accessible2_get_accParent uiautomation.c:316: Test failed: unexpected call Accessible2_get_accName uiautomation.c:1558: Test failed: expected Accessible_get_uniqueID uiautomation.c:1559: Test failed: expected Accessible2_get_uniqueID uiautomation.c:1586: Test failed: elprov != NULL, elprov 00000000007B2D80 uiautomation.c:1589: Test failed: expected Accessible_get_uniqueID uiautomation.c:1590: Test failed: expected Accessible2_get_uniqueID uiautomation.c:1596: Test failed: elprov != NULL, elprov 00000000007B2ED0 https://test.winehq.org/data/patterns.html#uiautomationcore:uiautomation These failures are systematic on Windows 10 1909 and started on 2022-06-15. -- 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 32490] New: Graphical issues in Inquisitor (red squares painted on the screen)
by wine-bugs＠winehq.org 14 Apr '23

14 Apr '23

http://bugs.winehq.org/show_bug.cgi?id=32490 Bug #: 32490 Summary: Graphical issues in Inquisitor (red squares painted on the screen) Product: Wine Version: 1.5.19 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: directx-d3d AssignedTo: wine-bugs(a)winehq.org ReportedBy: gyebro69(a)gmail.com Classification: Unclassified Created attachment 42861 --> http://bugs.winehq.org/attachment.cgi?id=42861 terminal output Inquisitor is an RPG released in 2012. I guess it uses DirectX8 (or DX7?) because only +d3d8 produces output, not +d3d9. Red squares are present on the screen while in the menus as well as in the main game. This makes the game unplayable. I tested this bug with a Nvidia gfx card: both the open source Nouveau and the binary drivers show the same problem. Wine 1.2.3, 1.4.1, 1.5.19 etc. have the reported problem. No demo available. Let me know if you need a debug log. -- 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 38

[Bug 28586] New: Team Fortress Arcade and Pixel Force: Left 4 Dead have no sound
by wine-bugs＠winehq.org 14 Apr '23

14 Apr '23

http://bugs.winehq.org/show_bug.cgi?id=28586 Bug #: 28586 Summary: Team Fortress Arcade and Pixel Force: Left 4 Dead have no sound Product: Wine Version: 1.3.29 Platform: All OS/Version: All Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-dmusic AssignedTo: wine-bugs(a)winehq.org ReportedBy: sagman.staredsi(a)gmail.com Classification: Unclassified Created attachment 36730 --> http://bugs.winehq.org/attachment.cgi?id=36730 Full Team Fortress Arcade log Team Fortress Arcade and Pixel Force: Left 4 Dead have no sound due a unimplemented function of directmusic: fixme:dmfile:IDirectMusicSegment8Impl_IPersistStream_Load : WAVE form (loading to be checked) fixme:dswave:IDirectMusicWaveImpl_IPersistStream_Load (0x5f148e8, 0x5f148b8): loading not implemented yet (only descriptor is loaded) This two lines are a message that wine repeat often in the output and inform this. -- 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 20

[Bug 53128] New: Without elevated privileges schedsvc:rpcapi fails on Windows 7
by WineHQ Bugzilla 14 Apr '23

14 Apr '23

https://bugs.winehq.org/show_bug.cgi?id=53128 Bug ID: 53128 Summary: Without elevated privileges schedsvc:rpcapi fails on Windows 7 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Without elevated privileges schedsvc:rpcapi fails on Windows 7: rpcapi.c:169: Test failed: expected S_OK, got 0x80070005 rpcapi.c:164: Test failed: 1: expected 0, got 0x800700b7 rpcapi.c:164: Test failed: 2: expected 0x80070002, got 0 rpcapi.c:169: Test failed: expected S_OK, got 0x80070005 rpcapi.c:169: Test failed: expected S_OK, got 0x80070005 rpcapi.c:232: Test failed: expected S_OK, got 0x80070005 rpcapi.c:234: Test failed: expected S_OK, got 0x80070091 rpcapi.c:236: Test failed: expected S_OK, got 0x80070091 rpcapi.c:242: Test failed: expected ERROR_FILE_NOT_FOUND, got 0 rpcapi.c:243: Test failed: expected 0, got 1 rpcapi.c:244: Test failed: expected 0, got 1 rpcapi.c:245: Test failed: expected NULL, got 002ED3F0 rpcapi.c:248: Test failed: expected S_OK, got 0x800700b7 rpcapi.c:255: Test failed: expected 0, got 1 rpcapi.c:256: Test failed: expected 0, got 1 rpcapi.c:257: Test failed: expected NULL, got 002EE9F8 rpcapi.c:260: Test failed: expected S_OK, got 0x800700b7 rpcapi.c:346: Test failed: expected S_OK, got 0x80070091 rpcapi.c:354: Test failed: expected ERROR_FILE_NOT_FOUND, got 0 rpcapi.c:355: Test failed: expected 0, got 1 rpcapi.c:356: Test failed: expected 0, got 1 rpcapi.c:357: Test failed: expected NULL, got 002EEA18 rpcapi.c:362: Test failed: expected S_OK, got 0x800700b7 rpcapi.c:363: Test failed: expected \Wine\Task1, task actual path (null) rpcapi.c:508: Test failed: expected S_OK, got 0x80070005 rpcapi.c:510: Test failed: expected S_OK, got 0x80070005 rpcapi.c:512: Test failed: expected S_OK, got 0x80070005 rpcapi.c:514: Test failed: expected S_OK, got 0x80070091 https://test.winehq.org/data/patterns.html#schedsvc:rpcapi In particular the value at the end of the "expected NULL" failure changes with every run so this failures always looks like it is new :-( This happens systematically on the w7u-adm TestBot VM. Interestingly it does not happen on more recent Windows versions that also run the tests without elevated privileges such as w8adm and w1064-adm. Maybe Microsoft realized they were too strict with the elevated privileges checks. -- 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