wine-bugs February 2023

wine-bugs@winehq.org

1 participants
3309 discussions

[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 42026] New: Monkey Island 2: Special Edition crashes to a black window on launch.
by wine-bugs＠winehq.org 16 Apr '23

16 Apr '23

https://bugs.winehq.org/show_bug.cgi?id=42026 Bug ID: 42026 Summary: Monkey Island 2: Special Edition crashes to a black window on launch. Product: Wine Version: 2.0-rc2 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: thedoogster(a)gmail.com Distribution: --- Created attachment 56488 --> https://bugs.winehq.org/attachment.cgi?id=56488 wine Monkey2 &> log.txt When I use WINE to start Monkey Island 2: Special Edition (from GOG), the screen turns black. Pressing ESC closes the game (with the full-screen, black window), and I can see the attached output in my terminal. I should be able to switch to another desktop and get a debug trace when the black game window is on the screen, if you'd like me to do that. I'm using 375.26 of NVidia's drivers. While I started having WINE issues (including this one) after the driver upgrade, and I've recently had similar issues with Shantae: Pirate's Curse (also from GOG), everything other than WINE seems to be working fine. -- 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 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 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

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 February 2023