wine-bugs November 2022

wine-bugs@winehq.org

1 participants
3726 discussions

[Bug 52708] New: libs/xslt/libxslt/attributes.c:136:9: error: variadic functions must use the base AAPCS variant
by WineHQ Bugzilla 21 Dec '22

21 Dec '22

https://bugs.winehq.org/show_bug.cgi?id=52708 Bug ID: 52708 Summary: libs/xslt/libxslt/attributes.c:136:9: error: variadic functions must use the base AAPCS variant Product: Wine Version: 6.20 Hardware: arm OS: Linux Status: NEW Keywords: download, regression, source Severity: major Priority: P2 Component: build-env Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com Regression SHA1: 9d9d4fcc379b2541a43b14f197facb6fa8c93ee8 Distribution: Debian gcc -c -o libs/xslt/libxslt/attributes.o libs/xslt/libxslt/attributes.c -Ilibs/xslt -Iinclude -Iinclude/msvcrt \ -I./libs/xml2/include -I./libs/xslt -DLIBXML_STATIC -DLIBXSLT_STATIC -D_UCRT -pipe \ -fcf-protection=none -fno-stack-protector -fno-strict-aliasing -Wno-packed-not-aligned -gdwarf-4 \ -fPIC -fasynchronous-unwind-tables -D_WIN32 -fno-builtin -fshort-wchar -Wno-format -g -O2 -mthumb -mfloat-abi=hard libs/xslt/libxslt/attributes.c: In function 'xsltNewAttrElem': libs/xslt/libxslt/attributes.c:136:9: error: variadic functions must use the base AAPCS variant 136 | xsltGenericError(xsltGenericErrorContext, | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 137 | "xsltNewAttrElem : malloc failed\n"); | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ libs/xslt/libxslt/attributes.c: In function 'xsltNewUseAttrSet': libs/xslt/libxslt/attributes.c:217:9: error: variadic functions must use the base AAPCS variant 217 | xsltGenericError(xsltGenericErrorContext, | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 218 | "xsltNewUseAttrSet : malloc failed\n"); | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ libs/xslt/libxslt/attributes.c: In function 'xsltResolveAttrSet.part.0': libs/xslt/libxslt/attributes.c:651:17: error: variadic functions must use the base AAPCS variant 651 | xsltGenericDebug(xsltGenericDebugContext, | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 652 | "xsl:attribute-set : merging import for %s\n", name); | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ libs/xslt/libxslt/attributes.c: In function 'xsltResolveSASCallback': libs/xslt/libxslt/attributes.c:694:6: error: variadic functions must use the base AAPCS variant 694 | xsltGenericError(xsltGenericErrorContext, | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 695 | "xsl:attribute-set : internal error, can't move imported " | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 696 | " attribute set %s\n", name); | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~ libs/xslt/libxslt/attributes.c: In function 'xsltParseStylesheetAttributeSet': libs/xslt/libxslt/attributes.c:432:2: error: variadic functions must use the base AAPCS variant 432 | xsltGenericDebug(xsltGenericDebugContext, | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 433 | "creating attribute set table\n"); | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ libs/xslt/libxslt/attributes.c:301:9: error: variadic functions must use the base AAPCS variant 301 | xsltGenericError(xsltGenericErrorContext, | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 302 | "xsltNewAttrSet : malloc failed\n"); | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ libs/xslt/libxslt/attributes.c:473:6: error: variadic functions must use the base AAPCS variant 473 | xsltGenericDebug(xsltGenericDebugContext, | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 474 | "add attribute to list %s\n", ncname); | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ libs/xslt/libxslt/attributes.c:518:3: error: variadic functions must use the base AAPCS variant 518 | xsltGenericDebug(xsltGenericDebugContext, | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 519 | "xsl:attribute-set : %s adds use %s\n", ncname, curval); | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ libs/xslt/libxslt/attributes.c:555:5: error: variadic functions must use the base AAPCS variant 555 | xsltGenericDebug(xsltGenericDebugContext, | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 556 | "updated attribute list %s\n", ncname); | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ libs/xslt/libxslt/attributes.c:399:2: error: variadic functions must use the base AAPCS variant 399 | xsltGenericError(xsltGenericErrorContext, | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 400 | "xsl:attribute-set : name is missing\n"); | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ libs/xslt/libxslt/attributes.c:399:2: error: variadic functions must use the base AAPCS variant libs/xslt/libxslt/attributes.c: In function 'xsltResolveStylesheetAttributeSet': libs/xslt/libxslt/attributes.c:713:5: error: variadic functions must use the base AAPCS variant 713 | xsltGenericDebug(xsltGenericDebugContext, | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 714 | "Resolving attribute sets references\n"); | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ libs/xslt/libxslt/attributes.c:722:3: error: variadic functions must use the base AAPCS variant 722 | xsltGenericDebug(xsltGenericDebugContext, | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 723 | "creating attribute set table\n"); | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ libs/xslt/libxslt/attributes.c: In function 'xsltApplyAttributeSet': libs/xslt/libxslt/attributes.c:1172:13: error: variadic functions must use the base AAPCS variant 1172 | xsltGenericDebug(xsltGenericDebugContext, | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 1173 | "apply attribute set %s\n", curstr); | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ make: *** [Makefile:159245: libs/xslt/libxslt/attributes.o] Error 1 Specific to armv7l, without mingw: Linux blah 5.9.12 #1 SMP PREEMPT Tue Mar 30 23:29:49 CDT 2021 armv7l GNU/Linux gcc version 10.2.1 20210110 (Debian 10.2.1-6) with llvm-mingw-20211002 (self-compiled, there's no linux/armv7l binary build afaik), however, wine builds. -- 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 49517] New: Warframe crashes during loading before menu with wined3d, gives popup
by WineHQ Bugzilla 21 Dec '22

21 Dec '22

https://bugs.winehq.org/show_bug.cgi?id=49517 Bug ID: 49517 Summary: Warframe crashes during loading before menu with wined3d, gives popup Product: Wine Version: 5.11 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: GloriousEggroll(a)gmail.com Distribution: --- Created attachment 67648 --> https://bugs.winehq.org/attachment.cgi?id=67648 d3d popup error The game crashes during the initial loading screen and gives the attached popup message. Happens on both amd and nvidia. The launcher is also affected by https://bugs.winehq.org/show_bug.cgi?id=44985 in wined3d and can be worked around with WINEDLLOVERRIDES="libglesv2=d" to get the game to the launching/crashing point. -- 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 53894] New: user32:sysparams - test_WM_DISPLAYCHANGE() times out on Windows 7+
by WineHQ Bugzilla 21 Dec '22

21 Dec '22

https://bugs.winehq.org/show_bug.cgi?id=53894 Bug ID: 53894 Summary: user32:sysparams - test_WM_DISPLAYCHANGE() times out on Windows 7+ Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com user32:sysparams - test_WM_DISPLAYCHANGE() times out on Windows 7+: sysparams.c:2474: Test failed: WaitForSingleObject returned 0x102 sysparams.c:2475: Test failed: got WM_DISPLAYCHANGE bpp 4294967295 See: https://test.winehq.org/data/patterns.html#user32:sysparams The failures started on 2022-09-23 which saw two commits to this test. However the test does not fail when run standalone so the commits may not be directly responsible. -- 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 53485] New: Cursor is missing in Visio 2003 when editing text
by WineHQ Bugzilla 21 Dec '22

21 Dec '22

https://bugs.winehq.org/show_bug.cgi?id=53485 Bug ID: 53485 Summary: Cursor is missing in Visio 2003 when editing text Product: Wine Version: 7.14 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: winebugs(a)copysoft.org Distribution: --- In Visio 2003 running under Wine 7.14 the text cursor is not displayed when editing text. How to reproduce: Open visio, create a new document, select the text tool, type on the screen, the cursor does not appear. Text input is fine, text is rendered fine and can be selected, copied and pasted, all that is missing is the cursor. I've run a bisect and found that this commit appears to be responsible for the regression: commit b8732c80b112af388264ac84d726aad09d93c8c6 Author: Zebediah Figura <zfigura(a)codeweavers.com> Date: Tue Apr 26 16:06:04 2022 +0100 win32u: Move caret APIs from user32. Signed-off-by: Zebediah Figura <zfigura(a)codeweavers.com> Signed-off-by: Jacek Caban <jacek(a)codeweavers.com> Signed-off-by: Huw Davies <huw(a)codeweavers.com> Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> -- 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 53028] New: gamepad buttons stopped working correctly
by WineHQ Bugzilla 21 Dec '22

21 Dec '22

https://bugs.winehq.org/show_bug.cgi?id=53028 Bug ID: 53028 Summary: gamepad buttons stopped working correctly 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: piotr5(a)netscape.net Distribution: --- ever since upgrading to wine-7.0 my gamepad got reduced to having only 10 functioning buttons and just 5 axes are actually doing anything. I now downgraded to wine-6.0.2 and it has all 14 buttons and 6 axes again. (actually now there are 2 devices of the same name detected, both have 8 axes, the second device is spreading the last 2 axes into being horizontal, while the first correctly assigns a 2d-movement analogue to one axis and nothing to the other. so I disabled the 2nd one.) to be precise, "wine control.exe" has a program for testing my gamepad, and there wine-7.0 is showing me only 10 buttons and 8 axes, of which only 5 are moving. in some game I had assigned one of the missing keys to an action and moving the axis which isn't perceived by wine sometimes triggers that missing button -- cannot see anything like that in this test program. I'm on gentoo linux, wine-vanilla is the only package providing wine there, and stable versions are just 6.0.2 and 7.0. installing newer versions doesn't work for me since it needs vulkan (winegcc aborts with function vkd3d_* not defined errors in wined3d.spec) which I have not installed. is it worth upgrading, or has that joystick bug not been fixed yet? -- 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 6

[Bug 46500] New: Cogpack - Exercises can' t be run - Error 380 - Invalid property value
by wine-bugs＠winehq.org 21 Dec '22

21 Dec '22

https://bugs.winehq.org/show_bug.cgi?id=46500 Bug ID: 46500 Summary: Cogpack - Exercises can't be run - Error 380 - Invalid property value Product: Wine Version: 4.0-rc6 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: maiktapwagner(a)aol.com Distribution: --- Created attachment 63348 --> https://bugs.winehq.org/attachment.cgi?id=63348 Console output on wine 4.0-rc6 Hello everyone, the application in question can be downloaded from and also has a demo version available which has the same "symptoms" as the full version: http://www.markersoftware.com/USA/demoinfo.htm#Download It returns an error message "invalid property value" with an error code of 380. Console output is attached and an entry for the AppDB has been submitted as well. -- 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 53980] New: httpapi:httpapi sometimes crashes testing overlapped I/O with the v2 server in Wine
by WineHQ Bugzilla 21 Dec '22

21 Dec '22

https://bugs.winehq.org/show_bug.cgi?id=53980 Bug ID: 53980 Summary: httpapi:httpapi sometimes crashes testing overlapped I/O with the v2 server in Wine Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: httpapi Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- httpapi:httpapi sometimes crashes testing overlapped I/O with the v2 server in Wine: httpapi.c:1539: Test marked todo: Got error 120. Unhandled exception: page fault on write access to 0x00000000 in 32-bit code (0x7b020c3f). [...] Backtrace: =>0 0x7b020c3f GetOverlappedResultEx+0x9a(file=<couldn't compute location>, overlapped=<couldn't compute location>, result=<couldn't compute location>, timeout=<couldn't compute location>, alertable=<couldn't compute location>) [Z:\home\winetest\tools\testbot\var\wine\dlls\kernelbase\file.c:3184] in kernelbase (0x0062f0c8) 1 0x7b020d4a GetOverlappedResult+0x45(file=<couldn't compute location>, overlapped=<couldn't compute location>, result=<couldn't compute location>, wait=<couldn't compute location>) [Z:\home\winetest\tools\testbot\var\wine\dlls\kernelbase\file.c:3144] in kernelbase (0x0062f118) 2 0x703826c7 HttpReceiveHttpRequest+0x267(queue=<couldn't compute location>, id=<couldn't compute location>, flags=<couldn't compute location>, request=<couldn't compute location>, size=<couldn't compute location>, ret_size=<couldn't compute location>, ovl=<couldn't compute location>) [Z:\home\winetest\tools\testbot\var\wine\dlls\httpapi\httpapi_main.c:360] in httpapi (0x0062f1b8) 3 0x0040f6d1 in httpapi_test (+0xf6d1) (0x0062fdb8) See https://test.winehq.org/data/patterns.html#httpapi:httpapi There are only four known instances of this crash, meaning it's pretty rare and thus hard to reproduce: * 2022-08-30 (fg-deb64-32) This is also the first known instance. * 2022-11-14 (fg-deb64-32) * 2022-11-16 (debian11-win32-de-DE) * 2022-11-17 (debian11-win32) MR!1397 -- 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 53977] New: amstream:amstream qedit:mediadet mf:transform mfmediaengine:mfmediaengine quartz:filtergraph winmm:mci wmp:media wmvcore:wmvcore mf:mf mfplay:mfplay qasf:asfreader broken on Debian Testing
by WineHQ Bugzilla 21 Dec '22

21 Dec '22

https://bugs.winehq.org/show_bug.cgi?id=53977 Bug ID: 53977 Summary: amstream:amstream qedit:mediadet mf:transform mfmediaengine:mfmediaengine quartz:filtergraph winmm:mci wmp:media wmvcore:wmvcore mf:mf mfplay:mfplay qasf:asfreader broken on Debian Testing Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: quartz Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- amstream:amstream qedit:mediadet mf:transform mfmediaengine:mfmediaengine quartz:filtergraph winmm:mci wmp:media wmvcore:wmvcore mf:mf mfplay:mfplay qasf:asfreader all have failures on Debian Testing. The exact failures are not really important, see the corresponding entries on the failure patterns page if more details are needed: https://test.winehq.org/data/patterns.html What's important is that the detection of gst/gst.h now fails on Debian Testing, resulting in Wine being compiled without GStreamer support which is what broke all the tests above: configure:17099: gstreamer-1.0 gstreamer-video-1.0 gstreamer-audio-1.0 cflags: configure:17100: gstreamer-1.0 gstreamer-video-1.0 gstreamer-audio-1.0 libs: configure:17103: checking for gst/gst.h configure:17103: gcc -m32 -c -g -O2 conftest.c >&5 conftest.c:174:10: fatal error: gst/gst.h: No such file or directory 174 | #include <gst/gst.h> | ^~~~~~~~~~~ And this all started with the commit below, which means this issue is related to bug 53953 but for Debian Testing instead of Fedora: commit c7a97b5d5d56ef00a0061b75412c6e0e489fdc99 (HEAD, refs/bisect/bad) Author: Zebediah Figura <zfigura(a)codeweavers.com> Date: Thu Nov 17 19:32:39 2022 -0600 configure: Override PKG_CONFIG_LIBDIR instead of PKG_CONFIG_PATH for 32-bit builds on 64-bit hosts. This allows 32-bit packages to be found when the user has specified PKG_CONFIG_PATH for some other reason. This also mirrors the way e.g. i686-linux-gnu-pkg-config is implemented on Debian, and possibly other distributions as well. This also prevents 64-bit .pc files from being found. This was originally intended as a benefit [1], but can contribute to misdetection of headers which are not actually multiarch (e.g. GStreamer, although at the time that [1] was written that was a preëxisting problem). In general a distribution which provides .pc files for one architecture should be expected to provide them for any architecture that it actually provides libraries for; even if that was not true of Debian in 2017, it is now. I moreover assert it is better to fail to find a present library than to incorrectly find the wrong one. Note that we can't easily use i686-linux-gnu-pkg-config, as would otherwise be preferable, for reasons also described in [1]. [1] https://www.winehq.org/pipermail/wine-devel/2017-June/118002.html -- 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 53744] New: WM_SETTEXT between ANSI programs treating LPARAM as Unicode causing name corruption
by WineHQ Bugzilla 21 Dec '22

21 Dec '22

https://bugs.winehq.org/show_bug.cgi?id=53744 Bug ID: 53744 Summary: WM_SETTEXT between ANSI programs treating LPARAM as Unicode causing name corruption Product: Wine Version: 7.6 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: dark(a)darkok.xyz Distribution: --- When sending a WM_SETTEXT to and from a program expecting ANSI strings, it seems to be interpreting the string as Unicode, causing the window title to become corrupted. Sending a wide string over then makes it work on Wine, but not Windows. The issue was introduced in Wine 7.6, and still exists in the latest versions. -- 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 52564] New: dxgi:dxgi times out in test_find_closest_matching_mode() on cw-gtx560
by WineHQ Bugzilla 21 Dec '22

21 Dec '22

https://bugs.winehq.org/show_bug.cgi?id=52564 Bug ID: 52564 Summary: dxgi:dxgi times out in test_find_closest_matching_mode() on cw-gtx560 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: --- When run in Wine, dxgi:dxgi times out in test_find_closest_matching_mode() on cw-gtx560: $ WINETEST_NO_MT_D3D=1 WINETEST_TIME=1 ./wine dlls/dxgi/tests/dxgi_test.exe dxgi [...] dxgi.c:1582:1.778 mode_count=130 dxgi.c:1585:1.778 i=0 dxgi.c:1585:2.452 i=1 dxgi.c:1585:3.123 i=2 dxgi.c:1585:3.867 i=3 dxgi.c:1585:4.806 i=4 dxgi.c:1585:5.929 i=5 dxgi.c:1585:7.061 i=6 dxgi.c:1585:8.187 i=7 dxgi.c:1585:9.332 i=8 dxgi.c:1585:10.542 i=9 [...] dxgi.c:1656:139.600 [...] 0020:dxgi:188.618 12836 tests executed (203 marked as todo, 2 failures), 35 skipped. https://test.winehq.org/data/patterns.html#dxgi:dxgi The problem is that it slows down after the first few modes, taking 1060 ms on average. And there are 130 modes to test so the test hits the 120 second limit. This issue started with the commit below. commit 1f2c3e8538b088f678a588121fc0bf7811336efc Author: Jacek Caban <jacek(a)codeweavers.com> Date: Wed Dec 1 16:02:43 2021 +0100 win32u: Move NtUserEnumDisplaySettings implementation from user32. Signed-off-by: Jacek Caban <jacek(a)codeweavers.com> Signed-off-by: Huw Davies <huw(a)codeweavers.com> Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> Before that commit test_find_closest_matching_mode() was much faster. dxgi.c:1582:1.558 mode_count=130 dxgi.c:1585:1.558 i=0 dxgi.c:1585:1.751 i=1 dxgi.c:1585:1.960 i=2 dxgi.c:1585:2.168 i=3 dxgi.c:1585:2.361 i=4 dxgi.c:1585:2.570 i=5 dxgi.c:1585:2.763 i=6 dxgi.c:1585:2.939 i=7 dxgi.c:1585:3.132 i=8 dxgi.c:1585:3.309 i=9 [...] dxgi.c:1656:25.519 [...] 0020:dxgi:63.668 12835 tests executed (203 marked as todo, 2 failures), 35 skipped. (184 ms on average) Note: cw-rx460 does not have this issue because it has fewer modes to test (20), and testing each mode is much faster too (28 ms on average). -- 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 6

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 2022