November 2023 - Wine-bugs - list.winehq.org

[Bug 28659] New: rpcrt4/server test crashes on 32-bit FreeBSD9
by wine-bugs＠winehq.org 16 Nov '23

16 Nov '23

http://bugs.winehq.org/show_bug.cgi?id=28659 Bug #: 28659 Summary: rpcrt4/server test crashes on 32-bit FreeBSD9 Product: Wine Version: 1.3.30 Platform: x86 OS/Version: FreeBSD Status: NEW Keywords: download, source, testcase Severity: normal Priority: P2 Component: rpc AssignedTo: wine-bugs(a)winehq.org ReportedBy: austinenglish(a)gmail.com Classification: Unclassified Created attachment 36831 --> http://bugs.winehq.org/attachment.cgi?id=36831 backtrace The rpcrt4/rpc test fails as well, but that may be related to missing ntlm_auth (which I haven't found how to satisfy on FreeBSD). The server test shows that same error, but also crashes, so something nastier is going on. Backtrace attached. -- 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 9

[Bug 55889] New: Valgrind complains about wld_mmap being in Text segment
by WineHQ Bugzilla 15 Nov '23

15 Nov '23

https://bugs.winehq.org/show_bug.cgi?id=55889 Bug ID: 55889 Summary: Valgrind complains about wld_mmap being in Text segment Product: Wine Version: 8.20 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: loader Assignee: wine-bugs(a)winehq.org Reporter: winehq(a)davidebeatrici.dev Distribution: --- Created attachment 75426 --> https://bugs.winehq.org/attachment.cgi?id=75426 Valgrind log I selected "8.20" as the version because it's the latest to be affected, but I'm not sure when the problem was introduced exactly. It could very well be a bug in Valgrind, but I can't reproduce the issue with the current Debian Testing package: https://packages.debian.org/trixie/wine That Wine version appears to be 8.0.1: $ wine --version wine-8.0.1 (Debian 8.0.1~repack-3) The attached log was generated by Valgrind with the suppressions from https://github.com/austin987/wine-valgrind-scripts when attempting to run Wine through it. -- 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 53095] New: system:NtUserChangeDisplaySettings Changing L"\\\\.\\DISPLAY1" display settings returned -2
by WineHQ Bugzilla 15 Nov '23

15 Nov '23

https://bugs.winehq.org/show_bug.cgi?id=53095 Bug ID: 53095 Summary: system:NtUserChangeDisplaySettings Changing L"\\\\.\\DISPLAY1" display settings returned -2 Product: Wine Version: 7.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: zizka(a)seznam.cz Distribution: --- Created attachment 72524 --> https://bugs.winehq.org/attachment.cgi?id=72524 1) Wine 7.0 crash; 2) Attempts to run with the Wine bundled by the vendor (i-deal Games) App: "Jagged Alliance 2 - Wildfire" from Steam Wine 7.0 Ubuntu 2022.04 I am trying to make Jagged Alliance run. The Wine distributed with Jagged Alliance seems not to work, because it has 36 byte long libwine.so and Wine doesn't even start. See the "JA 2 dist Wine log" below. So I tried with Wine 7.0 (current stable), and it failed with: system:NtUserChangeDisplaySettings Changing L"\\\\.\\DISPLAY1" display settings returned -2 Along that, the system switched to fullscreen, with the whole screen black. On a second run, Wine crashed - see the 1st part of the attached text. I will try to contact the company and ask if they could figure out. But in the meantime, I think this is a valid bug on an old Win32 game which could be present on some others. Thanks to anyone who takes a look. -- 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 22904] New: Register URL protocol handlers under Linux
by wine-bugs＠winehq.org 15 Nov '23

15 Nov '23

http://bugs.winehq.org/show_bug.cgi?id=22904 Summary: Register URL protocol handlers under Linux Product: Wine Version: unspecified Platform: All OS/Version: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: programs AssignedTo: wine-bugs(a)winehq.org ReportedBy: kempe.marcus(a)gmail.com winemenubuilder is able to automatically register file type associations and build menus under Linux, when triggered by an application under wine. It would be great if the same thing were true for protocol handlers, so that these would become registered in much the same way as when using gconftool in gnome: gconftool -s /desktop/gnome/url-handlers/spotify/command 'wine c:\\spotify\\spotify.exe %s' --type String gconftool-2 -s /desktop/gnome/url-handlers/spotify/enabled --type Boolean true Would this be possible, hard, or maybe not a good idea? -- 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 55894] New: Windows Journal does not start, needs class ClassicW {3336b8bf-45af-429f-85cb-8c435fbf21e4}
by WineHQ Bugzilla 15 Nov '23

15 Nov '23

https://bugs.winehq.org/show_bug.cgi?id=55894 Bug ID: 55894 Summary: Windows Journal does not start, needs class ClassicW {3336b8bf-45af-429f-85cb-8c435fbf21e4} Product: Wine Version: 8.20 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: inkobj Assignee: wine-bugs(a)winehq.org Reporter: alexhenrie24(a)gmail.com Distribution: --- Created attachment 75431 --> https://bugs.winehq.org/attachment.cgi?id=75431 Terminal output Steps to reproduce: 1. Create a 32-bit Wine bottle. 2. Run `winetricks mfc42`. 3. Run `wine Journal_en-us_x86.msi`. 4. Run `wine 'C:\Program Files\Windows Journal\journal.exe'`. An error dialog appears that says "Open" but has no useful error message. $ sha256sum Journal_en-us_x86.msi e1aee3fca029ad235817b633e089f3fd3bc7603e62e1c5043ffcc263baff67e9 -- 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 55895] New: this can be caused by problem in the program or a deficiency in wine
by WineHQ Bugzilla 14 Nov '23

14 Nov '23

https://bugs.winehq.org/show_bug.cgi?id=55895 Bug ID: 55895 Summary: this can be caused by problem in the program or a deficiency in wine Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winedbg Assignee: wine-bugs(a)winehq.org Reporter: urmilagautam9763(a)gmail.com Distribution: --- Created attachment 75432 --> https://bugs.winehq.org/attachment.cgi?id=75432 it is showing " The program wrapgame.exe has encountered a serious problem and needs to close. This can be caused by problem in the program or a deficiency in wine" it is showing " The program wrapgame.exe has encountered a serious problem and needs to close. This can be caused by problem in the program or a deficiency in wine" -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

1 1

[Bug 20474] New: Wine can't be built with GCC in C99 mode
by wine-bugs＠winehq.org 14 Nov '23

14 Nov '23

http://bugs.winehq.org/show_bug.cgi?id=20474 Summary: Wine can't be built with GCC in C99 mode Product: Wine Version: unspecified Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: build-env AssignedTo: wine-bugs(a)winehq.org ReportedBy: yann(a)droneaud.fr For multiple reason, wine can't be built by GCC in C99 mode ( --std=c99 ). In particular, wine rely on GCC behavor regarding to extern inline. It produces errors regarding asm construct conflicting with extern inline symbols. It produces errors with multiple defination of inline function in object files. According to this, it seems that wine is not compatible with C99, but rely a lot on GCC specific behavor. See also bug #20306 -- 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 26

[Bug 55891] New: mfmediaengine - Frame server mode is implemented incorrectly
by WineHQ Bugzilla 13 Nov '23

13 Nov '23

https://bugs.winehq.org/show_bug.cgi?id=55891 Bug ID: 55891 Summary: mfmediaengine - Frame server mode is implemented incorrectly Product: Wine Version: 8.20 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: mfplat Assignee: wine-bugs(a)winehq.org Reporter: besentv(a)gmail.com Distribution: --- Today, Wine's implementation of media engine plays back the video stream at full speed in frame server mode potentially skipping frames. Windows does in fact play back the video stream at full speed as well, however it uses a custom sink that only requests more frames from the pipeline, when OnVideoStreamTick() was called. The used sink is a private interface which can be created using the activate interface with UUID 4d4dedaa-43c5-480d-9ee0-1464f9f4ff4b (CLSID_SVRActivate) . Additionally Windows prerolls 2 frames by scrubbing at postition 0 (0 rate playback) before actual playback in media engine is started by a call to OnVideoStreamTick(). Even though it seems illogical, the Play() function just generally allows OnVideoStreamTick() to start playback. To properly implement this we seem to be (partially) blocked by the following issues: - No implementation of this custom Sink in Wine. - Scrubbing at 0 rate seems to be broken at the moment. - Need to manually copy frame data from CPU to GPU instead of just passing Samples from the sink to the user program. To fix this, we need to detach decoding from the media source and move it into the pipeline with decoder MFTs. This also needs a minor rewrite of the topo resolving logic. I wrote an extension to the effect test, which better shows the general issue, which is available here: https://gitlab.winehq.org/wine/wine/-/merge_requests/4379 -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 53216] New: d3d11:d3d11 - test_depth_bias() fails in the TestBot VMs
by WineHQ Bugzilla 13 Nov '23

13 Nov '23

https://bugs.winehq.org/show_bug.cgi?id=53216 Bug ID: 53216 Summary: d3d11:d3d11 - test_depth_bias() fails in the TestBot VMs Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- d3d11:d3d11 - test_depth_bias() fails in the TestBot VMs: d3d11.c:28093: Test failed: Got depth 4.99374978e-003, expected 4.99999994e-003. d3d11.c:28093: Test failed: Got depth 4.99374978e-003, expected 4.99999994e-003. d3d11.c:28093: Test failed: Got depth 2.50997487e-003, expected 2.50999994e-003. d3d11.c:28093: Test failed: Got depth 7.48750009e-003, expected 7.49999994e-003. d3d11.c:28093: Test failed: Got depth 7.48750009e-003, expected 7.49999994e-003. d3d11.c:28093: Test failed: Got depth 2.50997487e-003, expected 2.50999994e-003. d3d11.c:28093: Test failed: Got depth 1.24749998e-002, expected 1.24999999e-002. d3d11.c:28093: Test failed: Got depth 1.24749998e-002, expected 1.24999999e-002. d3d11.c:28093: Test failed: Got depth 2.50997487e-003, expected 2.50999994e-003. d3d11.c:28093: Test failed: Got depth 6.40899956e-001, expected 6.42500000e-001. d3d11.c:28093: Test failed: Got depth 6.40899956e-001, expected 6.42500000e-001. d3d11.c:28093: Test failed: Got depth 2.50997487e-003, expected 2.50999994e-003. d3d11.c:28093: Test failed: Got depth 2.50997487e-003, expected 2.50999994e-003. d3d11.c:28093: Test failed: Got depth 2.50997487e-003, expected 2.50999994e-003. d3d11.c:27965: Test marked todo: Got 0xffffff00, expected 0x00ffffff at (0, 0, 0), sub-resource 0. d3d11.c:28101: Test failed: Got value 0x14745 (4.99373704e-003), expected 0x147ae (4.99999553e-003). d3d11.c:28101: Test failed: Got value 0x14745 (4.99373704e-003), expected 0x147ae (4.99999553e-003). d3d11.c:28101: Test failed: Got value 0x8528f (3.25097461e-002), expected 0x85293 (3.25099845e-002). d3d11.c:28101: Test failed: Got value 0x1eab3 (7.48747632e-003), expected 0x1eb85 (7.49999329e-003). d3d11.c:28101: Test failed: Got value 0x1eab3 (7.48747632e-003), expected 0x1eb85 (7.49999329e-003). d3d11.c:28101: Test failed: Got value 0x8528f (3.25097461e-002), expected 0x85293 (3.25099845e-002). d3d11.c:28101: Test failed: Got value 0x33190 (1.24750145e-002), expected 0x33333 (1.24999888e-002). d3d11.c:28101: Test failed: Got value 0x33190 (1.24750145e-002), expected 0x33333 (1.24999888e-002). d3d11.c:28101: Test failed: Got value 0x8528f (3.25097461e-002), expected 0x85293 (3.25099845e-002). d3d11.c:28101: Test failed: Got value 0xa41204 (6.40899935e-001), expected 0xa47ae1 (6.42500022e-001). d3d11.c:28101: Test failed: Got value 0xa41204 (6.40899935e-001), expected 0xa47ae1 (6.42500022e-001). d3d11.c:28101: Test failed: Got value 0x8528f (3.25097461e-002), expected 0x85293 (3.25099845e-002). d3d11.c:28101: Test failed: Got value 0x8528f (3.25097461e-002), expected 0x85293 (3.25099845e-002). d3d11.c:28101: Test failed: Got value 0x8528f (3.25097461e-002), expected 0x85293 (3.25099845e-002). d3d11.c:28110: Test failed: Got value 0x28e (9.97940032e-003), expected 0x290 (1.00099184e-002). d3d11.c:28110: Test failed: Got value 0x28e (9.97940032e-003), expected 0x290 (1.00099184e-002). d3d11.c:28110: Test failed: Got value 0x331 (1.24666209e-002), expected 0x334 (1.25123980e-002). d3d11.c:28110: Test failed: Got value 0x331 (1.24666209e-002), expected 0x334 (1.25123980e-002). d3d11.c:28110: Test failed: Got value 0x476 (1.74258030e-002), expected 0x47b (1.75020981e-002). d3d11.c:28110: Test failed: Got value 0x476 (1.74258030e-002), expected 0x47b (1.75020981e-002). d3d11.c:28110: Test failed: Got value 0xa411 (6.40894179e-001), expected 0xa47a (6.42496376e-001). d3d11.c:28110: Test failed: Got value 0xa411 (6.40894179e-001), expected 0xa47a (6.42496376e-001). https://test.winehq.org/data/patterns.html#d3d11:d3d11 These failures: * Don't happen on Debian 11 + Intel / KDE * Happen on Debian 11 + QXL + single-monitor * Happen on Debian 11 + QXL + multi-monitor * Don't happen on Debian Testing + QXL + multi-monitor So they are probably caused by some bug in the Debian 11 QXL support. Note that despite being systematic these failures could cause false positives due to the test multi-threading (see bug 53212). -- 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 55214] New: Overwatch 2 crashes on launch on macOS
by WineHQ Bugzilla 12 Nov '23

12 Nov '23

https://bugs.winehq.org/show_bug.cgi?id=55214 Bug ID: 55214 Summary: Overwatch 2 crashes on launch on macOS Product: Wine-staging Version: 8.12 Hardware: x86-64 OS: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: yehia.wael(a)gmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Created attachment 74824 --> https://bugs.winehq.org/attachment.cgi?id=74824 Crash backtrace Overwatch 2 fails to launch on macOS, both when compiled with --enable-archs=i386,x86_64 and without. The game is launched directly from _retail_/Overwatch.exe and works as expected on Linux (tested on Ubuntu 22.04 and Archlinux, with both packaged and self-compiled wine versions), but does not launch on macOS. -- 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