wine-bugs November 2023

wine-bugs@winehq.org

1 participants
2132 discussions

[Bug 16214] New: Copy command does not work as expected
by wine-bugs＠winehq.org 15 Nov '23

15 Nov '23

http://bugs.winehq.org/show_bug.cgi?id=16214 Summary: Copy command does not work as expected Product: Wine Version: 1.0.1 Platform: Other OS/Version: other Status: NEW Severity: enhancement Priority: P2 Component: dos AssignedTo: wine-bugs(a)winehq.org ReportedBy: scott(a)open-vote.org >From Launchpad: https://bugs.edge.launchpad.net/ubuntu/+source/wine/+bug/272921 In Windows, the COPY command run in a command prompt allows users to concatenate files by using a plus ("+") operator, for example: copy file1+file2 outfile In wine's cmd.exe, it seems to read file1+file2 as a single path and therefore outputs a "Path Not Found". Also, it does not recognize the "con" keyword used to represent stdout/stdin. Therefore another method of concatenating files: copy file1 outfile copy file2 con >> outfile does not work either. My Ubuntu version is 8.04, AMD64 architecture, though I have seen the same issue on the x86 version as well. -- 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 19

[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 48247] New: Darksiders 2 (GOG) crashes after intro
by WineHQ Bugzilla 13 Nov '23

13 Nov '23

https://bugs.winehq.org/show_bug.cgi?id=48247 Bug ID: 48247 Summary: Darksiders 2 (GOG) crashes after intro Product: Wine-staging Version: 4.20 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: fzielcke(a)z-51.de CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Created attachment 65912 --> https://bugs.winehq.org/attachment.cgi?id=65912 log + crash dump with wine-4.20 (staging) Darksiders 2 directly crashes after the intro. This is on Debian unstable with the official winehq-staging 4.20 packages for bullseye -- 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 55806] New: recent updates broke Wine
by WineHQ Bugzilla 13 Nov '23

13 Nov '23

https://bugs.winehq.org/show_bug.cgi?id=55806 Bug ID: 55806 Summary: recent updates broke Wine Product: Wine-staging Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: johnmagdy437(a)yahoo.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- after upgrading Wine, i found that whenever i try to run any application it refuses to open... even winecfg is not working ``` 0220:fixme:ntdll:find_reg_tz_info Can't find matching timezone information in the registry for EEST, bias -120, std (d/m/y): 27/10/2023, dlt (d/m/y): 28/04/2023 0228:fixme:ntdll:find_reg_tz_info Can't find matching timezone information in the registry for EEST, bias -120, std (d/m/y): 27/10/2023, dlt (d/m/y): 28/04/2023 0230:fixme:ntdll:find_reg_tz_info Can't find matching timezone information in the registry for EEST, bias -120, std (d/m/y): 27/10/2023, dlt (d/m/y): 28/04/2023 0238:fixme:ntdll:find_reg_tz_info Can't find matching timezone information in the registry for EEST, bias -120, std (d/m/y): 27/10/2023, dlt (d/m/y): 28/04/2023 0238:err:winediag:nodrv_CreateWindow Application tried to create a window, but no driver could be loaded. 0238:err:winediag:nodrv_CreateWindow L"The explorer process failed to start." ``` ***timedatectl status***: ``` Local time: Thu 2023-10-19 02:30:48 EEST Universal time: Wed 2023-10-18 23:30:48 UTC RTC time: Wed 2023-10-18 23:30:48 Time zone: Africa/Cairo (EEST, +0300) System clock synchronized: yes NTP service: active RTC in local TZ: no ``` Wine Version: 8.0.2 ***cat /etc/timezone**: ``` Africa/Cairo ``` similar issues: https://forum.winehq.org/viewtopic.php?t=31104 https://bugs.winehq.org/show_bug.cgi?id=32916 https://bugs.winehq.org/show_bug.cgi?id=45786 https://github.com/ValveSoftware/Proton/issues/944#issuecomment-417303447 i tried to run **TZ="America/Manaus" winecfg** and it fixed that timezone error but it still failed to run any application even winecfg... and regarding window problem i never found any fix nor patch for 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 7

[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

[Bug 54642] New: Page fault on read access to 0x0000
by WineHQ Bugzilla 12 Nov '23

12 Nov '23

https://bugs.winehq.org/show_bug.cgi?id=54642 Bug ID: 54642 Summary: Page fault on read access to 0x0000 Product: Wine-staging Version: 8.3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: santafejayyt(a)gmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Created attachment 74172 --> https://bugs.winehq.org/attachment.cgi?id=74172 Wine debugger backtrace on game start I'm attempting to run Konami's E-Amusement Cloud Sound Voltex Exceed Gear game, and the launcher and its components work fine, however when attempting to launch the game, the window opens, but the game does not start, and stays on a black screen. I have installed the required dependencies for the game via winetricks (DXVK / D3DX9, FAudio, & XACT). -- 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 24

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