April 2020 - Wine-bugs - list.winehq.org

[Bug 48950] New: NVDA requires AccessibleObjectFromPoint for mouse tracking
by WineHQ Bugzilla 12 Apr '22

12 Apr '22

https://bugs.winehq.org/show_bug.cgi?id=48950 Bug ID: 48950 Summary: NVDA requires AccessibleObjectFromPoint for mouse tracking Product: Wine Version: 5.6 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: oleacc Assignee: wine-bugs(a)winehq.org Reporter: contact(a)jookia.org Distribution: ArchLinux In order to track the mouse pointer and read what's under the mouse NVDA tries to get an IAccessible object using AccessibleObjectFromPoint. This fails with a stub and mouse tracking 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 7

[Bug 41098] New: Descent 3 (GOG version) has problem when running with OpenGL renderer (Nvidia proprietary drivers )
by wine-bugs＠winehq.org 12 Apr '22

12 Apr '22

https://bugs.winehq.org/show_bug.cgi?id=41098 Bug ID: 41098 Summary: Descent 3 (GOG version) has problem when running with OpenGL renderer (Nvidia proprietary drivers) Product: Wine Version: 1.7.55 Hardware: x86 OS: Linux Status: NEW Keywords: regression Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: gyebro69(a)gmail.com CC: hverbeet(a)gmail.com Regression SHA1: c92451f295242110bf016facf0e80564f3643d94 Distribution: --- The bug reported here occurs with Nvidia binary drivers 367.35, but can't reproduce it with nouveau/mesa. I tried the official demo version, but it just hangs with a black screen with the OpenGL renderer (unrelated to this regression, occurs with nouveau as well and with older Wine versions). When OpenGL renderer is selected in the launcher, the game starts and plays the intro video, then the game quits after displaying this error message: 'Error: Generic renderer error." The OpenGL renderer in Descent 3 used to work until commit c92451f295242110bf016facf0e80564f3643d94 Author: Henri Verbeet <hverbeet(a)codeweavers.com> Date: Wed Nov 4 00:02:48 2015 +0100 wined3d: Always use the same formats in context_create() when "always_offscreen" is enabled. Disabling "AlwaysOffScreen" in the registry works around the problem. Terminal output shows only fixme:win:EnumDisplayDevicesW ((null),0,0x33f0d8,0x00000000), stub! fixme:x11drv:X11DRV_desktop_SetCurrentMode Cannot change screen BPP from 32 to 16 fixme:x11drv:X11DRV_desktop_SetCurrentMode Cannot change screen BPP from 32 to 16 fixme:x11drv:X11DRV_desktop_SetCurrentMode Cannot change screen BPP from 32 to 16 Wine 1.9.16 Fedora 24 OpenGL vendor string: NVIDIA Corporation OpenGL renderer string: GeForce GT 730/PCIe/SSE2 OpenGL core profile version string: 4.5.0 NVIDIA 367.35 OpenGL core profile shading language version string: 4.50 NVIDIA -- 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 18

[Bug 26350] New: Dungeons demo doesn't run
by wine-bugs＠winehq.org 12 Apr '22

12 Apr '22

http://bugs.winehq.org/show_bug.cgi?id=26350 Summary: Dungeons demo doesn't run Product: Wine Version: 1.3.15 Platform: x86 URL: http://www.bigdownload.com/games/dungeons/pc/dungeons- demo/ OS/Version: Linux Status: NEW Keywords: dotnet, download Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: austinenglish(a)gmail.com If I use mono-2.10-1, it fails with an error that mono can't handle it: Method '<Module>:<CrtImplementationDetails>.DoDllLanguageSupportValidation ()' in assembly 'C:\Program Files\Kalypso Media\Dungeons Demo\Mogre.dll' contains native code that cannot be executed by Mono in modules loaded from byte arrays. The assembly was probably created using C++/CLI. Method '<Module>:<CrtImplementationDetails>.ThrowModuleLoadException (string,System.Exception)' in assembly 'C:\Program Files\Kalypso Media\Dungeons Demo\Mogre.dll' contains native code that cannot be executed by Mono in modules loaded from byte arrays. The assembly was probably created using C++/CLI. System.NullReferenceException: Object reference not set to an instance of an object With dotnet35, fails with: Unhandled Exception: System.MissingMethodException: Method not found: 'Void System.Runtime.GCSettings.set_LatencyMode(System.Runtime.GCLatencyMode)'. at Realmforge.MogreUtil.Application.MainApplication`3.Run() at Realmforge.Dungeons.DungeonsMain.Main(String[] args) -- 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 16

[Bug 39699] New: WINE Crashed during setup of 'EDT for Windows'
by wine-bugs＠winehq.org 12 Apr '22

12 Apr '22

https://bugs.winehq.org/show_bug.cgi?id=39699 Bug ID: 39699 Summary: WINE Crashed during setup of 'EDT for Windows' Product: Wine Version: 1.6-rc2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: D.Kurtz(a)web.de Distribution: --- Created attachment 52941 --> https://bugs.winehq.org/attachment.cgi?id=52941 Saved Crashfile During running the Setup-Programm WINE crashed. I have Linux-Mint 17.2 and Wine !:1.6.2 You can get the Programm 'EDTW = EDT für Windows' at this Link: http://opg.de/download/edtw/setupedt.exe If possible please answer in German language because my english is very bad. Thanks Dietmar -- 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 19841] New: Wolfenstein (2009): mouse cursor remains onscreen during FPS gameplay even after all menus are closed.
by wine-bugs＠winehq.org 12 Apr '22

12 Apr '22

http://bugs.winehq.org/show_bug.cgi?id=19841 Summary: Wolfenstein (2009): mouse cursor remains onscreen during FPS gameplay even after all menus are closed. Product: Wine Version: 1.1.28 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: ben.r.xiao(a)gmail.com In Wolfenstein (2009), browsing the intelligence reports or upgrading weapons sometimes causes the mouse cursor to remain on screen even when the in-game menus are closed. In other words, during FPS gameplay, the cursor sits right where the crosshairs should be and does not disappear. Needless to say this is quite distracting. This cursor bug seems to appear randomly, but always after browsing an intelligence report or upgrading weapons. The only way to get rid of the cursor is to restart the game. I'll post an attachment showing this bug the next time I see it. -- 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 8

[Bug 46936] New: cannot upgrade to wine-devel 4.5~bionic ( libfaudio0 dependency missing)
by wine-bugs＠winehq.org 10 Apr '22

10 Apr '22

https://bugs.winehq.org/show_bug.cgi?id=46936 Bug ID: 46936 Summary: cannot upgrade to wine-devel 4.5~bionic (libfaudio0 dependency missing) Product: Packaging Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: wine-packages Assignee: wine-bugs(a)winehq.org Reporter: a34ypool3voiz(a)t-online.de CC: michael(a)fds-team.de, sebastian(a)fds-team.de Distribution: --- Created attachment 64049 --> https://bugs.winehq.org/attachment.cgi?id=64049 log showing missing libfaudio0 deps I have installed winehq-devel 4.4 on Ubuntu 18.04 amd64. Currently version 4.5 is available, but installation fails. Trying the usual "apt-get update && apt-get upgrade && apt-get dist-upgrade" lists winehq-devel as package that has been kept back. Then I tried the following: sudo apt-get install winehq-devel wine-devel wine-devel-amd64 wine-devel-i386 -f Now two unmet dependencies are listed, which cause the failure: libfaudio0 and libfaudio0:i386. Those packages do not exist in the repository. -- 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 39

[Bug 46615] New: PC Building Simulator doesn't render fonts
by wine-bugs＠winehq.org 10 Apr '22

10 Apr '22

https://bugs.winehq.org/show_bug.cgi?id=46615 Bug ID: 46615 Summary: PC Building Simulator doesn't render fonts Product: Wine Version: 4.1 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: luca.finizio.mgbx(a)hotmail.it Distribution: Mint I tried to play PC Building Simulator v9.3.4 but it's impossible to play the game because fonts are not rendered. I attached my console output (there are also errors). -- 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 5

[Bug 44950] New: err:ntdll: RtlpWaitForCriticalSection. Supreme Commander FA
by wine-bugs＠winehq.org 10 Apr '22

10 Apr '22

https://bugs.winehq.org/show_bug.cgi?id=44950 Bug ID: 44950 Summary: err:ntdll:RtlpWaitForCriticalSection. Supreme Commander FA Product: Wine Version: 3.5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: james.ytedmonds(a)gmail.com Distribution: --- This bug has affected Supreme Commander: Forged Alliance since pre-2.21. I have found this bug to affect multiple machines with clean wine prefixes. At some point during gameplay, the game will either stop entirely or the window for it will close. The terminal reads: " 007f:fixme:faultrep:ReportFault 0x153ece4 0x0 stub 0110:err:ntdll:RtlpWaitForCriticalSection section 0xfeec00 "?" wait timed out in thread 0110, blocked by 007f, retrying (60 sec) " The only option after this point is to kill the applications. I have found several things that seem to make the bug more likely: *Playing on large maps (definite correlation) *Using 6+ players (less certain) *High graphics settings (might affect timing of bug, but AFAIK cannot cause it) I have tried to override the "ntdll.dll" with one from real windows, but I believe wine at this time does not support overriding this DLL. The bug is easy to reproduce, on a large map (i.e. "Betrayal Ocean") it can occur within 5-10 minutes. I can get any details and logs needed, but I will need to be told how to get them (I am not experienced with debugging) -- 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 48847] New: dotnet471: often gets a critical section timeout
by WineHQ Bugzilla 10 Apr '22

10 Apr '22

https://bugs.winehq.org/show_bug.cgi?id=48847 Bug ID: 48847 Summary: dotnet471: often gets a critical section timeout Product: Wine Version: 5.5 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com Distribution: --- Created attachment 66764 --> https://bugs.winehq.org/attachment.cgi?id=66764 bt all I've been seeing this when running winetricks-test, for dotnet46* and dotnet471. This info is for dotnet471. austin(a)laptop ~ $ grep 'wait timed out' /tmp/out.txt | sort -u 0048:err:ntdll:RtlpWaitForCriticalSection section 0x7bd2c220 "loader.c: loader_section" wait timed out in thread 0048, blocked by 006e, retrying (60 sec) 006e:err:ntdll:RtlpWaitForCriticalSection section 0x110060 "heap.c: main process heap section" wait timed out in thread 006e, blocked by 0174, retrying (60 sec) 00ad:err:ntdll:RtlpWaitForCriticalSection section 0x7bd2c220 "loader.c: loader_section" wait timed out in thread 00ad, blocked by 006e, retrying (60 sec) 00bb:err:ntdll:RtlpWaitForCriticalSection section 0x110060 "heap.c: main process heap section" wait timed out in thread 00bb, blocked by 0174, retrying (60 sec) 00e2:err:ntdll:RtlpWaitForCriticalSection section 0x7bd2c220 "loader.c: loader_section" wait timed out in thread 00e2, blocked by 006e, retrying (60 sec) 0114:err:ntdll:RtlpWaitForCriticalSection section 0x110060 "heap.c: main process heap section" wait timed out in thread 0114, blocked by 0174, retrying (60 sec) 0166:err:ntdll:RtlpWaitForCriticalSection section 0x7bd2c220 "loader.c: loader_section" wait timed out in thread 0166, blocked by 006e, retrying (60 sec) 0169:err:ntdll:RtlpWaitForCriticalSection section 0x7bd2c220 "loader.c: loader_section" wait timed out in thread 0169, blocked by 006e, retrying (60 sec) 016c:err:ntdll:RtlpWaitForCriticalSection section 0x110060 "heap.c: main process heap section" wait timed out in thread 016c, blocked by 0174, retrying (60 sec) 0193:err:ntdll:RtlpWaitForCriticalSection section 0x7bd2c220 "loader.c: loader_section" wait timed out in thread 0193, blocked by 006e, retrying (60 sec) winedbg bt all is attached. -- 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 19

[Bug 39379] New: test.winehq.org: Show a specific test history for a machine or platform
by wine-bugs＠winehq.org 09 Apr '22

09 Apr '22

https://bugs.winehq.org/show_bug.cgi?id=39379 Bug ID: 39379 Summary: test.winehq.org: Show a specific test history for a machine or platform Product: WineHQ.org Version: unspecified Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: www-unknown Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- Currently it's possible to see at a glance how specific test fared across Wine commits and *all platforms*. For instance: https://test.winehq.org/data/tests/advapi32:service.html But if a platform has multiple test machines, one where the test has always failed and another where it has just started failing, one cannot see when the failures started on the above page. So it would be nice to have a similar page on a per-platform basis; or one with all the reports where that test failed regardless of platform. -- 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 4