wine-bugs May 2023

wine-bugs@winehq.org

1 participants
3049 discussions

[Bug 51622] New: i2c/ddc support in Wine
by WineHQ Bugzilla 20 Nov '23

20 Nov '23

https://bugs.winehq.org/show_bug.cgi?id=51622 Bug ID: 51622 Summary: i2c/ddc support in Wine Product: Wine Version: 6.15 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: aros(a)gmx.com Distribution: --- Does it exist? I've tried grepping Wine source code and haven't found anything. -- 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 54601] New: Compilation fails with gcc 4.3.4 (error: unknown field ‘Type’ specified in initializer)
by WineHQ Bugzilla 19 Nov '23

19 Nov '23

https://bugs.winehq.org/show_bug.cgi?id=54601 Bug ID: 54601 Summary: Compilation fails with gcc 4.3.4 (error: unknown field ‘Type’ specified in initializer) Product: Wine Version: 8.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: version2013(a)protonmail.com Distribution: --- Created attachment 74133 --> https://bugs.winehq.org/attachment.cgi?id=74133 log.txt in distro: # uname --kernel-release 3.0.66 # gcc --version 4.3.4 # ldd --version 2.10.1 Compiling wine-8.1 fails with: ../wine-8.1/dlls/ntdll/unix/server.c: In function ‘invoke_system_apc’: ../wine-8.1/dlls/ntdll/unix/server.c:409: error: unknown field ‘Type’ specified in initializer ../wine-8.1/dlls/ntdll/unix/server.c:409: warning: missing braces around initializer ../wine-8.1/dlls/ntdll/unix/server.c:409: warning: (near initialization for ‘ext.<anonymous>’) ../wine-8.1/dlls/ntdll/unix/server.c:410: error: unknown field ‘Pointer’ specified in initializer ../wine-8.1/dlls/ntdll/unix/server.c:411: warning: initialization makes integer from pointer without a cast Compiling also fails with wine-8.2 -- 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 54838] New: Wine names dinput devices (and likely other HID devices) incorrectly
by WineHQ Bugzilla 18 Nov '23

18 Nov '23

https://bugs.winehq.org/show_bug.cgi?id=54838 Bug ID: 54838 Summary: Wine names dinput devices (and likely other HID devices) incorrectly Product: Wine Version: 8.5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: dinput Assignee: wine-bugs(a)winehq.org Reporter: burneddi(a)protonmail.com Distribution: --- Joysticks and other dinput devices have the wrong instance and product names on Wine as compared to Windows. I will illustrate the problem by example. I have a joystick that reports the following information: $ udevadm info -n /dev/input/by-id/usb-VKB-Sim_©_Alex_Oz_2021_VKBsim_Gladiator_EVO_R-event-joystick [...] E: ID_MODEL_ENC=\x20VKBsim\x20Gladiator\x20EVO\x20\x20R\x20\x20 E: ID_VENDOR_ENC=VKB-Sim\x20©\x20Alex\x20Oz\x202021 [...] Under Wine, this device is identified by apps as well as the Game Controllers interface in the Wine Control Panel as "VKB-Sim © Alex Oz 2021 VKBsim Gladiator EVO R". On Windows it is identified as " VKBsim Gladiator EVO R". In other words, the Wine's dinput's tszInstanceName and tszProductName fields contain the vendor field concatenated with the model field, whereas it should only contain the model field. This breaks some applications. I discovered this issue when Star Citizen failed to save configuration for the joystick, which turned out to be because of the copyright symbol in the device name as exposed by Wine. While config saving breaking due to the copyright symbol is technically a bug in the game, it does not manifest on Windows, because on Windows the name of the instance/product does not include the vendor part and therefore does not include the copyright symbol. It is also possible that game controller configuration software might be tripped up by this discrepancy. -- 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 54177] New: vbscript fails to compile sub call when argument expression contains multiplication
by WineHQ Bugzilla 16 Nov '23

16 Nov '23

https://bugs.winehq.org/show_bug.cgi?id=54177 Bug ID: 54177 Summary: vbscript fails to compile sub call when argument expression contains multiplication Product: Wine Version: 7.21 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: vbscript Assignee: wine-bugs(a)winehq.org Reporter: jsm174(a)gmail.com Distribution: --- While working on the port of Visual Pinball, we found a script with code similar to the following that fails to compile: Public Sub AddTimer(aDelay, aMessage) End Sub Dim ii ii = 1 AddTimer (ii-1)*200, "Message" If the expression is wrapped in parenthesis, it compiles successfully: AddTimer ((ii-1)*200), "Message" -- 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 11

[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 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 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 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 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

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