wine-bugs March 2023

wine-bugs@winehq.org

1 participants
3438 discussions

[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 29804] New: Forever grayed out "agree" button
by wine-bugs＠winehq.org 19 Apr '23

19 Apr '23

http://bugs.winehq.org/show_bug.cgi?id=29804 Bug #: 29804 Summary: Forever grayed out "agree" button Product: Wine Version: 1.3.28 Platform: x86 URL: http://erwin.com/products/detail/ca_erwin_data_modeler _community_edition/ OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: richedit AssignedTo: wine-bugs(a)winehq.org ReportedBy: rambo_8713(a)hotmail.com Classification: Unclassified Created attachment 38713 --> http://bugs.winehq.org/attachment.cgi?id=38713 Some times gives invalid arguement -1 when changing riched20 and msls31 I can not agree to the EULA for CA ERWIN MODELER Community Edition, i have used native riched20.dll and msls31.dll. With and without the dlls and one on and/or the other dll not overriden. I have the lastest wine version 1.3, fresh install as of today. When using native msls31.dll, before the EULA screen appears, after u click next after it computes space requirements, it gives an invalid argument: -1 I am running ubuntu 11.10, i have tried winetricks as well, to configure the windows dlls -- 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 12

[Bug 53898] New: Programmer's File Editor MDI window contents incorrectly refreshed after closing an MDI document
by WineHQ Bugzilla 18 Apr '23

18 Apr '23

https://bugs.winehq.org/show_bug.cgi?id=53898 Bug ID: 53898 Summary: Programmer's File Editor MDI window contents incorrectly refreshed after closing an MDI document Product: Wine Version: 7.20 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: wine_bugzilla(a)sctb.ch Distribution: --- Created attachment 73439 --> https://bugs.winehq.org/attachment.cgi?id=73439 Corrupted window. I've been using Programmer's File Editor (PFE), a text editor from 1999, with WINE, since the beginning of time. There has always been a problem that when the editor has multiple MDI windows open, and a single window has been maximized (so it fills the entire editor), and that window is closed, the window which replaces it does not correctly refresh the editor display - the content is visually garbled. Minimizing and restoring the editor induces a correct refresh. Screenshot attached of a garbled window, and then the same window after a min-restore induced refresh (so you can more easily see the corruption). -- 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 54065] New: Windower 4 with FFXI Online has no keyboard input
by WineHQ Bugzilla 18 Apr '23

18 Apr '23

https://bugs.winehq.org/show_bug.cgi?id=54065 Bug ID: 54065 Summary: Windower 4 with FFXI Online has no keyboard input Product: Wine Version: 7.20 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: blocker Priority: P2 Component: dinput Assignee: wine-bugs(a)winehq.org Reporter: reaper2021(a)protonmail.com Distribution: --- Created attachment 73616 --> https://bugs.winehq.org/attachment.cgi?id=73616 error log Keyboard input in FFXI with Windower 4 has been broken for a long time. It fails in 7.20, and all the way down to 5.0rc2 or earlier (I stopped testing there). Keyboard input works in wine-staging-5-0rc5, and no longer works in wine-staging-5-0-rc6. My installation for which I posted the log uses dxvk and dgVoodoo, but the problem also occurs without that. Steps to reproduce: 1. make a 32 bit prefix, windows version seems noncritical (7 or 10). 2. install official FFXI distribution from http://www.playonline.com/ff11us/download/media/install_win.html (install hangs for a seemingly long time at some step, disk space check if I recall, just wait) 3. winetricks dotnet462 gdiplus (without dotnet, windower will not work. Gdiplus just makes the fonts in the windower console look nicer, it's not absolutely required for reproduction.) 4. install windower 4.3 from https://www.windower.net/ , to $WINEPREFIX/drive_c/windower4.3/ 5. wine $WINEPREFIX/drive_c/windower4.3/Windower.exe At this step, you'll need an FFXI subscription and character to log in and get to the point where you see that the keyboard doesn't work. -- 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 9

[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 54013] New: Cannot install Trimble Sketchup Pro 2022 at all
by WineHQ Bugzilla 16 Apr '23

16 Apr '23

https://bugs.winehq.org/show_bug.cgi?id=54013 Bug ID: 54013 Summary: Cannot install Trimble Sketchup Pro 2022 at all Product: Wine Version: 7.22 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: gdpo22(a)orange.fr Distribution: --- Created attachment 73589 --> https://bugs.winehq.org/attachment.cgi?id=73589 Trying to install sketchup without sed solution After downloading the sketchup pro 2022 trial, the sketchup installer displayed a lot of error windows "Invalid descriptor" with an "ok" button. After 6 or 7 click on "ok", the install terminates with a final window error of trimble saying that the installation cannot complete. (see attachement) The same with 7.0 wine stable version. Then I succeeded to install by applying a dirty solution I have seen on a forum: sed 's/GetFinalPathNameByHandleW/QetFinalPathNameByHandleW/' SketchUpPro-2022-0-354-126.exe > hacked_installer.exe But when I try to click on 'connexion' button from welcome screen, nothing happens. -- 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 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 51134] New: Support redirecting GetOpenFileName and GetSaveFileName through org.freedesktop.portal.FileChooser
by WineHQ Bugzilla 15 Apr '23

15 Apr '23

https://bugs.winehq.org/show_bug.cgi?id=51134 Bug ID: 51134 Summary: Support redirecting GetOpenFileName and GetSaveFileName through org.freedesktop.portal.FileChooser Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: from_wine_bugzilla(a)ssokolow.com Distribution: --- While not all options in the OPENFILENAME structure can be supported via the org.freedesktop.portal.FileChooser interface, providing the option to redirect an application's request for a common Open/Save dialog through the XDG chooser system would have two beneficial effects on non-OSX POSIX systems: 1. Better integration, since the application run under Wine would use the native desktop file pickers, complete with the user's Places sidebar bookmarks and any other customizations they've enacted. 2. More practical security, since Wine could then be run in a filesystem sandbox, with the portal host mounting files/directories into the sandboxed environment on demand. I'd suggest a three-state option exposed through winecfg's Desktop Integration: 1. Opportunistically (Qt's approach to integrating support for XDG portals into QFileDialog provides precedent for making this the default. Uses the portal-based file chooser unless an application requests a combination of OPENFILENAME settings that cannot be represented by the portal API.) 2. Forced (An option for power users to set on a per-application basis to intentionally sacrifice the application's customizations in favour of better integration with the understanding that things may break.) 3. Never (An option for users who prefer consistency between their Windows applications over consistency with the rest of their desktop or have deleted the Z: mapping and configured their Wine prefix around the idea of only working with drive letters.) These high-level preferences could also apply equally well to any other platform's native file chooser, should integration with it be implemented. The D-Bus API in question is documented at https://flatpak.github.io/xdg-desktop-portal/portal-docs.html#gdbus-org.fre… While it is outside the scope of this feature request, it may also be possible to use the TrashFile() method of this API to integrate with the host desktop's Trash. -- 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 54463] New: wbemprox: wrong version value is returned from win32_operatingsystem on win10 (regression)
by WineHQ Bugzilla 15 Apr '23

15 Apr '23

https://bugs.winehq.org/show_bug.cgi?id=54463 Bug ID: 54463 Summary: wbemprox: wrong version value is returned from win32_operatingsystem on win10 (regression) Product: Wine Version: 8.1 Hardware: x86-64 URL: https://github.com/PowerShell/PowerShell/releases/down load/v7.0.3/PowerShell-7.0.3-win-x64.msi OS: Linux Status: NEW Keywords: regression Severity: normal Priority: P2 Component: wmi&wbemprox Assignee: wine-bugs(a)winehq.org Reporter: xerox.xerox2000x(a)gmail.com CC: hans(a)meelstraat.net Distribution: Debian Following powershell script returns wrong version on win10 (winetricks dotnet48 is required): $searcher = [wmisearcher]'Select version From win32_operatingsystem' $searcher.scope.path = "\\.\root\cimv2" $searcher.get() Result: __GENUS : 2 __CLASS : Win32_OperatingSystem __RELPATH : __PROPERTY_COUNT : 1 __DERIVATION : {} __SERVER : __NAMESPACE : __PATH : Version : 6.3.18362 PSComputerName : In wine 8.0 it reports correctly: __GENUS : 2 __CLASS : Win32_OperatingSystem __RELPATH : __PROPERTY_COUNT : 1 __DERIVATION : {} __SERVER : __NAMESPACE : __PATH : Version : 10.0.18362 PSComputerName : This bug results in Chocolateley downloading tons off MB's off updates because it believes version is <win10. -- 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 54713] New: dinput:device8 - test_mouse_keyboard() fails on some Window 7 locales
by WineHQ Bugzilla 14 Apr '23

14 Apr '23

https://bugs.winehq.org/show_bug.cgi?id=54713 Bug ID: 54713 Summary: dinput:device8 - test_mouse_keyboard() fails on some Window 7 locales Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: dinput Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com dinput:device8 - test_mouse_keyboard() fails on some Window 7 locales: device8.c:684: Test failed: IDirectInputDevice8_Acquire failed: 0x80070005 device8.c:686: Test failed: IDirectInputDevice8_Acquire failed: 0x80070005 device8.c:690: Test failed: GetRegisteredRawInputDevices returned 1, raw_devices_count: 3 device8.c:691: Test failed: Unexpected raw device flags: 0 device8.c:692: Test failed: Unexpected raw device flags: 0 See https://test.winehq.org/data/patterns.html#dinput:device8 This has been happening on Windows 7 since 2023-01-06: * 2023-01-06 on w7u-pt-PT 32-bit * 2023-01-27 on w7u-adm 32-bit * 2023-03-03 on w7u-de 32-bit But on 2023-03-16 this seems to have become systematic on w7u-el, w7u-es and w7u-pt-PT. A bisect shows that the failure rate seems to have increased with the commit below: commit 07753da93ce1f78c710f666e193a0434eb99699b Author: Rémi Bernon <rbernon(a)codeweavers.com> Date: Wed Mar 15 21:04:01 2023 +0100 dinput/tests: Remove BuildActionMap / SaveActionMap mouse and keyboard tests. -- 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 54106] New: taskschd:scheduler - test_GetTask() fails on Windows 7 when it has insufficient privileges
by WineHQ Bugzilla 14 Apr '23

14 Apr '23

https://bugs.winehq.org/show_bug.cgi?id=54106 Bug ID: 54106 Summary: taskschd:scheduler - test_GetTask() fails on Windows 7 when it has insufficient privileges Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: taskschd Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com test_GetTask() fails on Windows 7 when it has insufficient privileges: scheduler.c:802: Test failed: DeleteTask error 0x80070005 scheduler.c:798: Test failed: 1: expected 0, got 0x800700b7 scheduler.c:798: Test failed: 2: expected 0x80070002, got 0 scheduler.c:802: Test failed: DeleteTask error 0x80070005 scheduler.c:802: Test failed: DeleteTask error 0x80070005 scheduler.c:814: Test failed: RegisterTask error 0x800700b7 scheduler.c:960: Test failed: DeleteTask error 0x80070005 scheduler.c:962: Test failed: DeleteTask error 0x80070005 scheduler.c:965: Test failed: expected ERROR_FILE_NOT_FOUND, got 0x80070005 scheduler.c:993: Test failed: DeleteFolder error 0x80070091 This can be seen on the w7u_adm VM. When run as part of the full WineTest run this test crashes in test_FolderCollection() which prevents seeing this failure in the nightly WineTest runs. See https://test.winehq.org/data/patterns.html#taskschd:scheduler But this set of failures is impacting merge requests such as MR!1732 and MR!1736. -- 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 54594] New: dinput:device8 - test_dik_codes() sometimes gets timeouts on the GitLab CI
by WineHQ Bugzilla 14 Apr '23

14 Apr '23

https://bugs.winehq.org/show_bug.cgi?id=54594 Bug ID: 54594 Summary: dinput:device8 - test_dik_codes() sometimes gets timeouts on the GitLab CI Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: dinput Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- dinput:device8 - test_dik_codes() sometimes gets timeouts on the GitLab CI. MR2265 & MR2288: device8.c:2182: Test failed: 0x800: lang 0x409: key 0x51, dik 0x10: WaitForSingleObject returned 0x102 MR1714 & MR2185: device8.c:2182: Test failed: 0x800: lang 0x409: key 0x52, dik 0x13: WaitForSingleObject returned 0x102 MR2133: device8.c:2182: Test failed: 0x800: lang 0x409: key 0x54, dik 0x14: WaitForSingleObject returned 0x102 MR2254: device8.c:2182: Test failed: 0x800: lang 0x409: key 0x59, dik 0x15: WaitForSingleObject returned 0x102 The oldest known instance happened on 2023-02-16 (MR2185) so this issue may be pretty recent. This issue never happened in the nightly WineTest runs. It's possible it only happens when the load on the machine running the tests is too high. That would make sense given that the timeouts from from a WaitForSingleObject() call with a 100 ms timeout. One option would be to simply increase the timeout. Yet that timeout seemed sufficient until mid February. So why is it no longer the case? -- 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 54109] New: schedsvc:rpcapi causes taskschd:scheduler to crash on w7u_adm
by WineHQ Bugzilla 14 Apr '23

14 Apr '23

https://bugs.winehq.org/show_bug.cgi?id=54109 Bug ID: 54109 Summary: schedsvc:rpcapi causes taskschd:scheduler to crash on w7u_adm Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: taskschd Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com When run on its own taskschd:scheduler fails on w7u_adm because of its insufficient privileges (see bug 54106). But if schedsvc:rpcapi is run before, taskschd:scheduler crashes in test_FolderCollection() instead: scheduler.c:349: Test failed: DeleteFolder error 0x80070091 scheduler.c:351: Test failed: DeleteFolder error 0x80070091 scheduler.c:354: Test failed: expected ERROR_FILE_NOT_FOUND, got 0x80070091 scheduler.c:450: Test failed: CreateFolder error 0x800700b7 scheduler.c:450: this is the last test seen before the exception 0a78:scheduler: unhandled exception c0000005 at 00403B53 See https://test.winehq.org/data/patterns.html#taskschd:scheduler Where: 0x80070091 == HRESULT_FROM_WIN32(ERROR_DIR_NOT_EMPTY) 0x800700b7 == HRESULT_FROM_WIN32(ERROR_ALREADY_EXISTS) This crash happens before the failures described in bug 54106 which explains why taskschd:scheduler fails one way for regular TestBot jobs (such as when testing merge requests) and another in the nightly WineTest runs. -- 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 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

[Bug 52193] New: schtasks.exe:schtasks fails on Windows 7 when missing privileges
by WineHQ Bugzilla 14 Apr '23

14 Apr '23

https://bugs.winehq.org/show_bug.cgi?id=52193 Bug ID: 52193 Summary: schtasks.exe:schtasks fails on Windows 7 when missing privileges Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: taskschd Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com schtasks.exe:schtasks fails on Windows 7 when missing privileges: schtasks.c:190: Test failed: DeleteTask failed: 80070005 schtasks.c:193: Test failed: r = 0 schtasks.c:201: Test failed: r = 1 schtasks.c:204: Test failed: r = 0 schtasks.c:224: Test failed: r = 1 https://test.winehq.org/data/patterns.html#schtasks.exe:schtasks When running as an administrator but without elevated privileges it looks like Windows 7 allows creating new tasks, but does not allow deleting the freshly created task! This behavior also seems to be specific to Windows 7 since there is no failure on w8adm and w1064-adm. -- 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 42372] New: Watchtower Library 2016, program crashes when trying to play a video from within the program
by wine-bugs＠winehq.org 14 Apr '23

14 Apr '23

https://bugs.winehq.org/show_bug.cgi?id=42372 Bug ID: 42372 Summary: Watchtower Library 2016, program crashes when trying to play a video from within the program Product: Wine Version: 2.0 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: drctheboss(a)charter.net Distribution: --- Created attachment 57155 --> https://bugs.winehq.org/attachment.cgi?id=57155 when the program crashed this was generated All aspects of the program seem to work fine, except when attempting to play a video. Then the program will crash and wine will generate a backtrace report -- 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 40

[Bug 54666] New: Compilation fails with gcc 4.8.4 - error: missing binary operator before token "("
by WineHQ Bugzilla 14 Apr '23

14 Apr '23

https://bugs.winehq.org/show_bug.cgi?id=54666 Bug ID: 54666 Summary: Compilation fails with gcc 4.8.4 - error: missing binary operator before token "(" Product: Wine Version: 8.3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: msvcrt Assignee: wine-bugs(a)winehq.org Reporter: version2013(a)protonmail.com Distribution: --- Created attachment 74181 --> https://bugs.winehq.org/attachment.cgi?id=74181 log.txt Compiling in 32 bit distro with: compiler version 4.8.4 # gcc --version glibc 2.19 # ldd --version config line: configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var --with-x --libdir=/usr/lib32 CFLAGS="-O2 -march=i686 -mtune=i686" Compile error in wine-8.3 In file included from ../wine-8.3/include/msvcrt/stdarg.h:24:0, from ../wine-8.3/dlls/acledit/main.c:21: ../wine-8.3/include/msvcrt/vadefs.h:30:91: error: missing binary operator before token "(" -- 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 54634] New: schtasks.exe:schtasks causes taskschd:scheduler to crash on w7u_adm and w8adm
by WineHQ Bugzilla 14 Apr '23

14 Apr '23

https://bugs.winehq.org/show_bug.cgi?id=54634 Bug ID: 54634 Summary: schtasks.exe:schtasks causes taskschd:scheduler to crash on w7u_adm and w8adm Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: taskschd Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com schtasks.exe:schtasks causes taskschd:scheduler to crash on w7u_adm and w8adm: scheduler.c:344: Test failed: expected ERROR_DIR_NOT_EMPTY, got 0x80070005 scheduler.c:351: Test failed: DeleteFolder error 0x80070005 scheduler.c:354: Test failed: expected ERROR_FILE_NOT_FOUND, got 0x80070005 scheduler.c:474: Test failed: expected 2, got 3 scheduler.c:483: Test failed: expected 2, got 3 scheduler.c:515: Test failed: expected \Wine\Folder2, got L"\\Wine\\test" scheduler.c:523: Test failed: expected Folder2, got L"test" scheduler.c:538: Test failed: expected \Wine\Folder2, got L"\\Wine\\test" scheduler.c:546: Test failed: expected Folder2, got L"test" scheduler.c:555: Test failed: expected E_INVALIDARG, got 0 scheduler.c:582: Test failed: expected S_FALSE, got 0 scheduler.c:616: Test failed: expected S_FALSE, got 0 scheduler.c:617: Test failed: expected 0, got 1 scheduler.c:630: Test failed: expected S_FALSE, got 0 scheduler.c:631: Test failed: expected 2, got 3 scheduler.c:647: Test failed: expected \Wine\Folder2, got L"\\Wine\\test" scheduler.c:655: Test failed: expected Folder2, got L"test" scheduler.c:673: Test failed: DeleteFolder error 0x80070005 scheduler.c:776: Test failed: CreateFolder error 0x800700b7 scheduler.c:787: Test failed: expected ERROR_FILE_NOT_FOUND, got 0x80070005 scheduler.c:787: this is the last test seen before the exception 07e4:scheduler: unhandled exception c0000005 at 004017CA See https://test.winehq.org/data/patterns.html#taskschd:scheduler taskschd:scheduler does not crash when run on its own: it's schtasks.exe:schtasks that causes it to crash. The reason is that, at least when run without elevated privileges, schtasks.exe:schtasks leaves behind the "Wine\\test" task folders created by the call below in schtasks.c: register_task("wine\\test\\winetest"); These folders then interfere with taskschd:scheduler. Not that they are mean to be deleted by the calls below but that fail with E_ACCESSDENIED: ITaskFolder_DeleteFolder(root, wine_testW, 0); ITaskFolder_DeleteFolder(root, wineW, 0); -- 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 18773] New: The Westerner: needs MPEG Layer-3 audio codec
by wine-bugs＠winehq.org 14 Apr '23

14 Apr '23

http://bugs.winehq.org/show_bug.cgi?id=18773 Summary: The Westerner: needs MPEG Layer-3 audio codec Product: Wine Version: 1.1.22 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: winmm&mci AssignedTo: wine-bugs(a)winehq.org ReportedBy: hoehle(a)users.sourceforge.net The Westerner until now had garbage AppDB rating but no bug entry. Deselecting any audio driver in winecfg let's wine play the intro and crash after: err:ole:CoGetClassObject class {38be3000-dbf4-11d0-860e-00a024cfef6d} not registered err:ole:CoGetClassObject no class object {38be3000-dbf4-11d0-860e-00a024cfef6d} could be created for context 0x1 This UUID is the "FriendlyName"="MPEG Layer-3 Decoder" from DirectX9 windows\system32\l3codecx.ax As Wine has its own winemp3.acm, shouldn't it declare this UUID (e.g. via tools/wine.inf)? Is this a simple omission? Does winemp3 implement something entirely different, another win API? When audio is not disabled in winecfg, wine crashes after repeatedly (~13x) opening and closing all winmm codecs, including winemp3.acm (it does not manage to reach the intro). wine regsvr32 l3codecx.ax WINEDLLOVERRIDES=quartz=n wine PICTuRE.exe is what's needed to let the music play, to see the intro, to start gameplay and to bump the AppDB rating from garbage to bronze. (Likely gold except for serious mouse lag, which is another issue.) The loop mentioned above is then avoided, as a driver is found. The native quartz.dll is needed or it won't find some pin (later than the intro). I copied the l3codecx.ax from a separate winetricks DirectX9 install before noticing that The Westerner's CD-ROM also contains it in DirectX9\DirectX.cab. Oddly, the application's cover lists only DirectX 8.1 as requirement. Using The Westerner German Patch v1.3. I guess v1.0 (CD-ROM without patch) would behave the same (guessing from reports in AppDB). -- 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 25

[Bug 51463] New: SnowRunner automobiles aren't rendered
by WineHQ Bugzilla 14 Apr '23

14 Apr '23

https://bugs.winehq.org/show_bug.cgi?id=51463 Bug ID: 51463 Summary: SnowRunner automobiles aren't rendered Product: Wine Version: 6.12 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: andrey.goosev(a)gmail.com Distribution: --- Created attachment 70304 --> https://bugs.winehq.org/attachment.cgi?id=70304 screenshot 077c:fixme:d3d:wined3d_deferred_context_issue_query context 0x7bc8410, query 0x7fcbd7f3a330, flags 0x2, stub! 077c:fixme:d3d:wined3d_deferred_context_issue_query context 0x7bc8410, query 0x7fcbd7f3a330, flags 0x1, stub! 06f0:fixme:d3d:wined3d_context_gl_bind_shader_resources Shader 0x7fcbd4097dc0 needs 64 samplers, but only 32 are supported. 06f0:fixme:d3d:wined3d_context_gl_bind_shader_resources Shader 0x7fcbd40a5170 needs 64 samplers, but only 32 are supported. 06f0:fixme:d3d:wined3d_context_gl_bind_shader_resources Shader 0x7fcbd4097dc0 needs 64 samplers, but only 32 are supported. 06f0:fixme:d3d:wined3d_context_gl_bind_shader_resources Shader 0x7fcbd40a5170 needs 64 samplers, but only 32 are supported. 0770:fixme:d3d:wined3d_deferred_context_issue_query context 0xa7491a0, query 0x9840840, flags 0x2, stub! 0770:fixme:d3d:wined3d_deferred_context_issue_query context 0xa7491a0, query 0x9840840, flags 0x1, stub! 077c:fixme:d3d:wined3d_deferred_context_issue_query context 0x7bc8410, query 0x7fcbd6016100, flags 0x2, stub! 077c:fixme:d3d:wined3d_deferred_context_issue_query context 0x7bc8410, query 0x7fcbd6016100, flags 0x1, stub! wine-6.12-194-g2ffcf440218 -- 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

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-bugs March 2023