wine-bugs June 2021

wine-bugs@winehq.org

1 participants
5479 discussions

[Bug 41703] New: LdrUnloadDll is not suit for musl( musl lacks unload support though it has a dlclose())
by wine-bugs＠winehq.org 20 Jul '21

20 Jul '21

https://bugs.winehq.org/show_bug.cgi?id=41703 Bug ID: 41703 Summary: LdrUnloadDll is not suit for musl(musl lacks unload support though it has a dlclose()) Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: xw897002528(a)gmail.com Distribution: --- Created attachment 56111 --> https://bugs.winehq.org/attachment.cgi?id=56111 fix for this problem Hey, sorry for my poor english, and here is the problem: First, musl won't unload module even dlclose(). Check here: http://wiki.musl-libc.org/wiki/Functional_differences_from_glibc#Unloading_… Then, musl won't excute init(__wine_spec_init) function if a module is already loaded. That means load_builtin_dll() thought dll is loaded by the current thread since init function was not called, but actually LdrUnloadDll() destroyed them in another thread and nothing is loaded in the current thread. Load_builtin_dll() try to find wm in InLoadOrderModuleList but nothing. After that, app will crash. And I solved this by making LdrUnloadDll() a stub. Patch is uploaded as a attachment. I hope this could be added in official wine by adding a configure option, thx. Here's my tracking details on this problem if you're intereted in how i found this: https://github.com/xhebox/noname-linux/issues/2#issuecomment-258680745 -- 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 36

[Bug 51295] New: ntoskrnl.exe:ntoskrnl occasionally hangs in test_overlapped()
by WineHQ Bugzilla 20 Jul '21

20 Jul '21

https://bugs.winehq.org/show_bug.cgi?id=51295 Bug ID: 51295 Summary: ntoskrnl.exe:ntoskrnl occasionally hangs in test_overlapped() Product: Wine Version: 6.10 Hardware: x86-64 OS: Linux Status: NEW Keywords: regression, source, testcase Severity: normal Priority: P2 Component: wineserver Assignee: wine-bugs(a)winehq.org Reporter: z.figura12(a)gmail.com Regression SHA1: 97afac469fbe012e22acc1f1045c88b1004a241f Distribution: --- Created attachment 70168 --> https://bugs.winehq.org/attachment.cgi?id=70168 make the problem more reproducible Specifically, it hangs if ntoskrnl is able to signal that the IRP is pending (by calling get_next_device_request) before the user space process calls wait_async(). 97afac469 intends for wait_async() to return STATUS_PENDING, because that is the synchronous return of the ioctl. The problem is that we're trying to have the select request *succeed immediately*, but STATUS_PENDING means that it didn't succeed immediately and that the client needs to wait for a wakeup. This can be triggered pretty reliably by running the relevant tests in a loop, as in the attached patch. I think <https://testbot.winehq.org/JobDetails.pl?Key=92616&f401=win32.report#k401> is an example of this happening on the testbot. -- 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 51262] New: Regression: all 32bit programs doesn't start since 308a5e7
by WineHQ Bugzilla 20 Jul '21

20 Jul '21

https://bugs.winehq.org/show_bug.cgi?id=51262 Bug ID: 51262 Summary: Regression: all 32bit programs doesn't start since 308a5e7 Product: Wine Version: 6.10 Hardware: x86-64 OS: Linux Status: NEW Severity: blocker Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: zzhang(a)codeweavers.com Distribution: --- master:wine/win32-build$ wine notepad 002c:err:virtual:virtual_setup_exception stack overflow 1156 bytes in thread 002c addr 0x7bc1f36f stack 0x120b7c (0x120000-0x121000-0x320000) 0024:err:virtual:virtual_setup_exception stack overflow 1156 bytes in thread 0024 addr 0x7bc1f36f stack 0x120b7c (0x120000-0x121000-0x320000) master:wine/win32-build$ which wine wine: aliased to ~/src/wine/win32-build/wine wine is configure with "../configure --enable-silent-rules --disable-tests". Ccache is disabled and wineprefix is new. master:wine/win32-build$ gcc --version gcc (Ubuntu 10.3.0-1ubuntu1) 10.3.0 Copyright (C) 2020 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. master:wine/win32-build$ i686-w64-mingw32-gcc --version i686-w64-mingw32-gcc (GCC) 10-win32 20210408 Copyright (C) 2020 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. master:wine/win32-build$ uname -a Linux eric-pc 5.11.0-18-generic #19-Ubuntu SMP Fri May 7 14:22:03 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux pure 32bit wine, wow32 wine, wow64 wine all crash with stack overflows. Only pure 64bit wine starts fine. Bisect points to 308a5e7c4d01525184b057058949c68c0ee77dba is the first bad commit commit 308a5e7c4d01525184b057058949c68c0ee77dba Author: Alexandre Julliard <julliard(a)winehq.org> Date: Fri Jun 11 10:57:20 2021 +0200 ntdll: Switch to the kernel stack for syscalls on i386. Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> dlls/ntdll/unix/signal_i386.c | 250 ++++++++++++++++++++---------------------- tools/winebuild/import.c | 192 ++++++++++++-------------------- 2 files changed, 186 insertions(+), 256 deletions(-) -- 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 50374] New: pCon.planner doesn't finish installation and doesn't open
by WineHQ Bugzilla 20 Jul '21

20 Jul '21

https://bugs.winehq.org/show_bug.cgi?id=50374 Bug ID: 50374 Summary: pCon.planner doesn't finish installation and doesn't open Product: Wine Version: 6.0-rc2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: tinozzo123(a)gmail.com Distribution: --- Created attachment 68979 --> https://bugs.winehq.org/attachment.cgi?id=68979 Contains installation.txt and backtrace.txt pCon.planner 8.4 Update 2 doesn't install correctly: the progress bar of the installer reaches the end, but the installation complete screen doesn't appear. Trying to cancel the installation once it actually started also doesn't do anything (didn't test if it's the same on Windows), so the only way to quit the installation is by killing wineserver. Wine logs during the installation are attached. The files of the program are there though, but trying to execute it results in the error from TLocaleReader "(-2147418113) Line 4 Column 19", and generates a backtrace I attached below. The uninstaller doesn't work either, with the progress bar not progressing at all and a cancel button that doesn't cancel anything. Link for the program download: https://pcon-planner.com/en/download/ -- 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 45807] New: Incorrect toolbar background in MFC apps, when visual theming enabled
by wine-bugs＠winehq.org 20 Jul '21

20 Jul '21

https://bugs.winehq.org/show_bug.cgi?id=45807 Bug ID: 45807 Summary: Incorrect toolbar background in MFC apps, when visual theming enabled Product: Wine Version: 3.15 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: jimbo1qaz(a)gmail.com Distribution: --- Created attachment 62266 --> https://bugs.winehq.org/attachment.cgi?id=62266 Screenshot of bug When visual theming is enabled, MFC toolbar button backgrounds are rendered as "grab handles", and space between buttons is black. (Also visible in screenshot, in 0CC and j0CC, the instrument editor piano is invisible when theming is enabled. Should I file a separate bug?) Tested with ReactOS.iso Lautus theme, and Zune theme (via .msi). Tested with j0CC-Famitracker and OpenMPT (both use MFC), on dirty WINEPREFIX. Also tested with Lautus and j0CC on clean WINEPREFIX with Lautus theme. -- 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

[Bug 35611] New: A lot of user32:msg tests fail in the Japanese locale
by wine-bugs＠winehq.org 20 Jul '21

20 Jul '21

https://bugs.winehq.org/show_bug.cgi?id=35611 Bug ID: 35611 Summary: A lot of user32:msg tests fail in the Japanese locale Product: Wine Version: 1.7.12 Hardware: x86 OS: Windows Status: NEW Severity: normal Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Classification: Unclassified The WineTestBot's w7u VM runs the tests in the Japanese locale. This results in 49 test failures instead of the background of 6 test failures. This can also be seen in the fg-win7u64-ja VM which gets 55 failures. See: http://test.winehq.org/data/tests/user32:msg.html The failures happen in test_dbcs_wm_char() and test_unicode_wm_char(). msg.c:11812: Test failed: got message 31f msg.c:11817: Test failed: bad wparam 81/2260 msg.c:11819: Test failed: got message 102 msg.c:11829: Test failed: bad wparam 201a/2260 msg.c:11836: Test failed: no messages: 0: the msg sequence is not complete: expected 0000 - actual 0102 msg.c:11836: Failed sequence no messages: msg.c:11836: 0: expected: nothing - actual: MsgCheckProc: 00080390 0102 wp 00000081 lp 00000000 (flags 19) msg.c:11838: Test failed: Unicode WM_CHAR: 0: in msg 0x0102 expecting wParam 0x2260 got 0x201a msg.c:11838: Failed sequence Unicode WM_CHAR: msg.c:11838: 0: expected: msg 0102 - actual: MsgCheckProc: 00080390 0102 wp 0000201a lp 00000000 (flags 19) msg.c:11845: Test failed: no messages: 0: the msg sequence is not complete: expected 0000 - actual 0102 msg.c:11845: Failed sequence no messages: msg.c:11845: 0: expected: nothing - actual: MsgCheckProc: 00080390 0102 wp 00000081 lp 00000000 (flags 19) msg.c:11847: Test failed: Unicode WM_CHAR: 0: in msg 0x0102 expecting wParam 0x2260 got 0x201a msg.c:11847: Failed sequence Unicode WM_CHAR: msg.c:11847: 0: expected: msg 0102 - actual: MsgCheckProc: 00080390 0102 wp 0000201a lp 00000000 (flags 19) msg.c:11854: Test failed: no messages: 0: the msg sequence is not complete: expected 0000 - actual 0102 msg.c:11854: Failed sequence no messages: msg.c:11854: 0: expected: nothing - actual: MsgCheckProc: 00080390 0102 wp 00000081 lp 00000000 (flags 19) msg.c:11856: Test failed: Unicode WM_CHAR: 0: in msg 0x0102 expecting wParam 0x2260 got 0x201a msg.c:11856: Failed sequence Unicode WM_CHAR: msg.c:11856: 0: expected: msg 0102 - actual: MsgCheckProc: 00080390 0102 wp 0000201a lp 00000000 (flags 19) msg.c:11863: Test failed: no messages: 0: the msg sequence is not complete: expected 0000 - actual 0102 msg.c:11863: Failed sequence no messages: msg.c:11863: 0: expected: nothing - actual: MsgCheckProc: 00080390 0102 wp 00000081 lp 00000000 (flags 19) msg.c:11865: Test failed: Unicode WM_CHAR: 0: in msg 0x0102 expecting wParam 0x2260 got 0x201a msg.c:11865: Failed sequence Unicode WM_CHAR: msg.c:11865: 0: expected: msg 0102 - actual: MsgCheckProc: 00080390 0102 wp 0000201a lp 00000000 (flags 19) msg.c:11872: Test failed: no messages: 0: the msg sequence is not complete: expected 0000 - actual 0102 msg.c:11872: Failed sequence no messages: msg.c:11872: 0: expected: nothing - actual: MsgCheckProc: 00080390 0102 wp 00000081 lp 00000000 (flags 19) msg.c:11874: Test failed: Unicode WM_CHAR: 0: in msg 0x0102 expecting wParam 0x2260 got 0x201a msg.c:11874: Failed sequence Unicode WM_CHAR: msg.c:11874: 0: expected: msg 0102 - actual: MsgCheckProc: 00080390 0102 wp 0000201a lp 00000000 (flags 19) msg.c:11882: Test failed: no messages: 0: the msg sequence is not complete: expected 0000 - actual 0102 msg.c:11882: Failed sequence no messages: msg.c:11882: 0: expected: nothing - actual: MsgCheckProc: 00080390 0102 wp 00000081 lp 00000000 (flags 19) msg.c:11885: Test failed: Unicode WM_CHAR: 0: in msg 0x0102 expecting wParam 0x2260 got 0x201a msg.c:11885: Failed sequence Unicode WM_CHAR: msg.c:11885: 0: expected: msg 0102 - actual: MsgCheckProc: 00080390 0102 wp 0000201a lp 00000000 (flags 19) msg.c:11890: Test failed: no messages: 0: the msg sequence is not complete: expected 0000 - actual 0102 msg.c:11890: Failed sequence no messages: msg.c:11890: 0: expected: nothing - actual: MsgCheckProc: 003C03CE 0102 wp 00000081 lp 00000000 (flags 19) msg.c:11892: Test failed: Unicode WM_CHAR: 0: in msg 0x0102 expecting wParam 0x2260 got 0x201a msg.c:11892: Failed sequence Unicode WM_CHAR: msg.c:11892: 0: expected: msg 0102 - actual: MsgCheckProc: 00080390 0102 wp 0000201a lp 00000000 (flags 19) msg.c:11900: Test failed: no messages: 0: the msg sequence is not complete: expected 0000 - actual 0102 msg.c:11900: Failed sequence no messages: msg.c:11900: 0: expected: nothing - actual: MsgCheckProc: 003C03CE 0102 wp 00000081 lp 00000000 (flags 19) msg.c:11908: Test failed: bad wparam 201a/2260 msg.c:11912: Test failed: Unicode WM_CHAR: 0: in msg 0x0102 expecting wParam 0x2260 got 0x201a msg.c:11912: Failed sequence Unicode WM_CHAR: msg.c:11912: 0: expected: msg 0102 - actual: MsgCheckProc: 00080390 0102 wp 0000201a lp 00000000 (flags 19) msg.c:11920: Test failed: no messages: 0: the msg sequence is not complete: expected 0000 - actual 0102 msg.c:11920: Failed sequence no messages: msg.c:11920: 0: expected: nothing - actual: MsgCheckProc: 00080390 0102 wp 00000081 lp 00000000 (flags 19) msg.c:11920: 1: expected: nothing - actual: MsgCheckProc: 00080390 0102 wp 00000081 lp 00000000 (flags 19) msg.c:11922: Test failed: Unicode WM_CHAR: 0: in msg 0x0102 expecting wParam 0x2260 got 0x201a msg.c:11922: Failed sequence Unicode WM_CHAR: msg.c:11922: 0: expected: msg 0102 - actual: MsgCheckProc: 00080390 0102 wp 0000201a lp 00000000 (flags 19) msg.c:11924: Test failed: Unicode WM_CHAR: 0: in msg 0x0102 expecting wParam 0x2260 got 0x201a msg.c:11924: Failed sequence Unicode WM_CHAR: msg.c:11924: 0: expected: msg 0102 - actual: MsgCheckProc: 00080390 0102 wp 0000201a lp 00000000 (flags 19) msg.c:11933: Test failed: no messages: 0: the msg sequence is not complete: expected 0000 - actual 0102 msg.c:11933: Failed sequence no messages: msg.c:11933: 0: expected: nothing - actual: MsgCheckProc: 00080390 0102 wp 00000081 lp 00000000 (flags 19) msg.c:11933: 1: expected: nothing - actual: MsgCheckProc: 00080390 0102 wp 00000081 lp 00000000 (flags 19) msg.c:11936: Test failed: Unicode WM_CHAR: 0: in msg 0x0102 expecting wParam 0x2260 got 0x201a msg.c:11936: Failed sequence Unicode WM_CHAR: msg.c:11936: 0: expected: msg 0102 - actual: MsgCheckProc: 00080390 0102 wp 0000201a lp 00000000 (flags 19) msg.c:11938: Test failed: Unicode WM_CHAR: 0: in msg 0x0102 expecting wParam 0x2260 got 0x201a msg.c:11938: Failed sequence Unicode WM_CHAR: msg.c:11938: 0: expected: msg 0102 - actual: MsgCheckProc: 00080390 0102 wp 0000201a lp 00000000 (flags 19) msg.c:11944: Test failed: no messages: 0: the msg sequence is not complete: expected 0000 - actual 0102 msg.c:11944: Failed sequence no messages: msg.c:11944: 0: expected: nothing - actual: MsgCheckProc: 00080390 0102 wp 00000081 lp 00000000 (flags 19) msg.c:11944: 1: expected: nothing - actual: MsgCheckProc: 00080390 0102 wp 00000081 lp 00000000 (flags 19) msg.c:11946: Test failed: Unicode WM_CHAR: 0: in msg 0x0102 expecting wParam 0x2260 got 0x201a msg.c:11946: Failed sequence Unicode WM_CHAR: msg.c:11946: 0: expected: msg 0102 - actual: MsgCheckProc: 00080390 0102 wp 0000201a lp 00000000 (flags 19) msg.c:11948: Test failed: Unicode WM_CHAR: 0: in msg 0x0102 expecting wParam 0x2260 got 0x201a msg.c:11948: Failed sequence Unicode WM_CHAR: msg.c:11948: 0: expected: msg 0102 - actual: MsgCheckProc: 00080390 0102 wp 0000201a lp 00000000 (flags 19) msg.c:11953: Test failed: Unicode WM_CHAR: 0: in msg 0x0102 expecting wParam 0x2260 got 0x201a0081 msg.c:11953: Failed sequence Unicode WM_CHAR: msg.c:11953: 0: expected: msg 0102 - actual: MsgCheckProc: 003C03CE 0102 wp 201a0081 lp 00000000 (flags 19) msg.c:11962: Test failed: bad wparam 81/30fb msg.c:11969: Test failed: bad wparam 81/30fb msg.c:11980: Test failed: bad wparam 3f/81 msg.c:11982: Test failed: no message msg.c:11985: Test failed: bad wparam 3f/81 msg.c:11995: Test failed: bad wparam 3f/81 msg.c:12001: Test failed: unexpected hwnd 003C03CE msg.c:12002: Test failed: unexpected message 31f msg.c:12003: Test failed: bad wparam 1/81 msg.c:12012: Test failed: bad wparam 3f/81 msg.c:12019: Test failed: unexpected hwnd 00000000 msg.c:12021: Test failed: bad wparam 81/81 msg.c:12022: Test failed: bad lparam 0 msg.c:12023: Test failed: bad time 1b0e62/1b0e90 msg.c:12032: Test failed: unexpected hwnd 003C03CE msg.c:12037: Test failed: unexpected hwnd 003C03CE msg.c:12044: Test failed: bad wparam 3f/81 msg.c:12049: Test failed: bad wparam 3f/81 -- 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 6

[Bug 34966] New: Academagia (WPF game) dialog windows are invisible until alt-tabed out
by wine-bugs＠winehq.org 20 Jul '21

20 Jul '21

http://bugs.winehq.org/show_bug.cgi?id=34966 Bug #: 34966 Summary: Academagia (WPF game) dialog windows are invisible until alt-tabed out Product: Wine Version: 1.7.6 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: i30817(a)gmail.com Classification: Unclassified installed dotnet51sp1 from the latest winetricks on a 32 bits prefix installed windowscodecs from the latest winetricks the same 32 bits prefix installed the game on the same 32 bits prefix then; started notpad: WINEPREFIX='/home/i30817/wine32bits' WINEARCH='win32' notepad started the game with these options: WINEPREFIX='/home/i30817/wine32bits' WINEARCH='win32' WINEDEBUG=+tid,+seh,+relay wine ./Academagia.exe >>log.txt 2>&1 And waited until the first dialog window i was able to activate, alt-tabed out (that was when i noticed it became visible) and killed the corresponding wineserver with: WINEPREFIX='/home/i30817/wine32bits' WINEARCH='win32' wineserver -k The log is quite large uncompressed (1.5 GB), but actually 30mb compressed. Still too large to upload here; but it can go to my google drive: https://drive.google.com/file/d/0BzxkBmaf1EiWTmhiQjJ1YkllZWc/edit?usp=shari… -- 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 4

[Bug 41460] New: Visual Studio C++ 6.0 crash when exit and a menu is oppened
by wine-bugs＠winehq.org 19 Jul '21

19 Jul '21

https://bugs.winehq.org/show_bug.cgi?id=41460 Bug ID: 41460 Summary: Visual Studio C++ 6.0 crash when exit and a menu is oppened Product: Wine Version: 1.8.4 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: dianaxxyyzz(a)gmail.com Distribution: --- Created attachment 55837 --> https://bugs.winehq.org/attachment.cgi?id=55837 backtrace Hello , To reproduce the bug is easy . Open Visual Studio C++ 6.0 and click on Help menu so it to open .Leave it open and close the program . There will be a crash .Attached is backtrace -- 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 13

[Bug 12968] New: MS Visual Studio V6 setup error 258 since 0.9.58
by wine-bugs＠winehq.org 19 Jul '21

19 Jul '21

http://bugs.winehq.org/show_bug.cgi?id=12968 Summary: MS Visual Studio V6 setup error 258 since 0.9.58 Product: Wine Version: 0.9.61. Platform: All OS/Version: Linux Status: UNCONFIRMED Severity: critical Priority: P1 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: k.king177(a)ntlworld.com trying to install Visual Studio v6 get MS Msgbox headed "Setup Error 258" with text Your setup files may be damaged. Try restarting the setup program from where you originally ran it. this is probably related or from same issue causing bug# 12967 for Office 97 see that bug for environment details. -- 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 5

[Bug 15948] New: Error generated when trying to install visual studio 6.0 into centos5 via wine
by wine-bugs＠winehq.org 19 Jul '21

19 Jul '21

http://bugs.winehq.org/show_bug.cgi?id=15948 Summary: Error generated when trying to install visual studio 6.0 into centos5 via wine Product: Wine Version: 1.1.7 Platform: PC-x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: enhancement Priority: P4 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: boniemx(a)gmail.com Created an attachment (id=17135) --> (http://bugs.winehq.org/attachment.cgi?id=17135) error-log for installation of visual studio 6.0 via wine into centos5 Hi, am trying to install Visual studio 6.0, but it produces the error that I have attached. Please I need to do this urgently. Please help -- 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 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 June 2021