wine-bugs September 2015

wine-bugs@winehq.org

1 participants
8222 discussions

[Bug 21101] New: Can't use SHIFT key with onboard visual keyboard and wine application
by wine-bugs＠winehq.org 15 Feb '19

15 Feb '19

http://bugs.winehq.org/show_bug.cgi?id=21101 Summary: Can't use SHIFT key with onboard visual keyboard and wine application Product: Wine Version: 1.1.35 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: malicorne(a)chez.com Wine 1.35 Ubuntu 9.10 To reproduce, press alt-F2 and execute "onboard" Execute a notepad with wine Then enter text using onboard with the shift key for uppercase characters for exemple. It does'nt work. It works with gedit so onboard working fine. If you use the capslock, it's working but the shift key doesn't do anything. -- 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.

1 15

[Bug 36380] New: valgrind shows a possible leak in in ddraw/tests/ddraw1.c
by wine-bugs＠winehq.org 15 Feb '19

15 Feb '19

https://bugs.winehq.org/show_bug.cgi?id=36380 Bug ID: 36380 Summary: valgrind shows a possible leak in in ddraw/tests/ddraw1.c Product: Wine Version: 1.7.18 Hardware: x86 OS: Linux Status: NEW Keywords: download, source, testcase Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com ==5320== 28 bytes in 1 blocks are possibly lost in loss record 256 of 978 ==5320== at 0x7BC508EB: RtlAllocateHeap (heap.c:255) ==5320== by 0x61B3BE8: apartment_getclassobject (compobj.c:526) ==5320== by 0x61B6FF6: get_inproc_class_object (compobj.c:2894) ==5320== by 0x61B9D5F: CoGetClassObject (compobj.c:3032) ==5320== by 0x61BA4E7: CoCreateInstance (compobj.c:3197) ==5320== by 0x50F4EDF: func_ddraw1 (ddraw1.c:2767) ==5320== by 0x50CC30B: main (test.h:584) ==5320== -- 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 36689] New: ddrawex/tests/surface.c crashes under valgrind/nvidia
by wine-bugs＠winehq.org 15 Feb '19

15 Feb '19

https://bugs.winehq.org/show_bug.cgi?id=36689 Bug ID: 36689 Summary: ddrawex/tests/surface.c crashes under valgrind/nvidia Product: Wine Version: 1.7.19 Hardware: x86 OS: Linux Status: NEW Keywords: download, source, testcase, valgrind Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com ../../../tools/runtest -q -P wine -T ../../.. -M ddrawex.dll -p ddrawex_test.exe.so surface && touch surface.ok preloader: Warning: failed to reserve range 00110000-68000000 preloader: Warning: failed to reserve range 7f000000-82000000 fixme:win:EnumDisplayDevicesW ((null),0,0x4ddf3c4,0x00000000), stub! fixme:win:EnumDisplayDevicesW ((null),0,0x4ddf494,0x00000000), stub! fixme:d3d:resource_check_usage Unhandled usage flags 0x20000000. fixme:d3d:resource_check_usage Unhandled usage flags 0x20000000. fixme:win:EnumDisplayDevicesW ((null),0,0x4ddf3c4,0x00000000), stub! fixme:d3d:resource_check_usage Unhandled usage flags 0x20000000. fixme:d3d:resource_check_usage Unhandled usage flags 0x20000000. fixme:d3d:resource_check_usage Unhandled usage flags 0x20000000. fixme:d3d:resource_check_usage Unhandled usage flags 0x20000000. fixme:d3d:resource_check_usage Unhandled usage flags 0x20000000. fixme:d3d:resource_check_usage Unhandled usage flags 0x20000000. fixme:d3d:resource_check_usage Unhandled usage flags 0x20000000. fixme:d3d:resource_check_usage Unhandled usage flags 0x20000000. fixme:win:EnumDisplayDevicesW ((null),0,0x4ddf484,0x00000000), stub! --23344-- VALGRIND INTERNAL ERROR: Valgrind received a signal 11 (SIGSEGV) - exiting --23344-- si_code=1; Faulting address: 0x24448B94; sp: 0x8814cccc valgrind: the 'impossible' happened: Killed by fatal signal ==23344== at 0x38064477: vgPlain_get_StackTrace_wrk (m_stacktrace.c:322) ==23344== by 0x38064854: vgPlain_get_StackTrace (m_stacktrace.c:1439) ==23344== by 0x38049E4D: record_ExeContext_wrk (m_execontext.c:341) ==23344== by 0x3802DE93: make_mem_undefined_w_tid_and_okind (mc_main.c:1815) ==23344== by 0x3802E378: mc_handle_client_request (mc_main.c:5869) ==23344== by 0x380A33A0: vgPlain_scheduler (scheduler.c:2011) ==23344== by 0x380B4A07: run_a_thread_NORETURN (syswrap-linux.c:103) sched status: running_tid=1 Thread 1: status = VgTs_Runnable /bin/sh: line 1: 23344 Segmentation fault OpenGL renderer string: GeForce GTX 460/PCIe/SSE2 OpenGL core profile version string: 4.3.0 NVIDIA 337.25 -- 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 19748] New: Unreal Tournament 3: Wrong Thread Problems
by wine-bugs＠winehq.org 15 Feb '19

15 Feb '19

http://bugs.winehq.org/show_bug.cgi?id=19748 Summary: Unreal Tournament 3: Wrong Thread Problems Product: Wine Version: 1.1.27 Platform: PC-x86-64 OS/Version: Linux Status: NEW Severity: enhancement Priority: P2 Component: directx-d3d AssignedTo: wine-bugs(a)winehq.org ReportedBy: nerv(a)dawncrow.de Playing UT3 throws a lot of Fixme's with Wrong thread Stubs like: fixme:d3d:IWineD3DEventQueryImpl_GetData Wrong thread, reporting GPU idle. and very often: fixme:d3d:IWineD3DOcclusionQueryImpl_GetData 0x19dbfe28 Wrong thread, returning 1. -- 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.

1 57

[Bug 36658] New: valgrind shows an invalid read in ddraw/tests/d3d.c
by wine-bugs＠winehq.org 15 Feb '19

15 Feb '19

https://bugs.winehq.org/show_bug.cgi?id=36658 Bug ID: 36658 Summary: valgrind shows an invalid read in ddraw/tests/d3d.c Product: Wine Version: 1.7.19 Hardware: x86 OS: Linux Status: NEW Keywords: download, source, testcase, valgrind Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com ../../../tools/runtest -q -P wine -T ../../.. -M ddraw.dll -p ddraw_test.exe.so d3d && touch d3d.ok preloader: Warning: failed to reserve range 00110000-68000000 preloader: Warning: failed to reserve range 7f000000-82000000 fixme:win:EnumDisplayDevicesW ((null),0,0x4f9f4a0,0x00000000), stub! fixme:win:EnumDisplayDevicesW ((null),0,0x4f9f520,0x00000000), stub! ==9737== Invalid read of size 4 ==9737== at 0x635FB00: ??? (in /tmp/.glF7Rc58 (deleted)) ==9737== by 0x5109AE4: fixup_extensions (directx.c:1542) ==9737== by 0x510FF86: wined3d_adapter_init_gl_caps (directx.c:3131) ==9737== by 0x5115459: wined3d_adapter_init (directx.c:5180) ==9737== by 0x51159B2: wined3d_init (directx.c:5272) ==9737== by 0x51BE953: wined3d_create (wined3d_main.c:105) ==9737== by 0x4DE1E2B: ddraw_init (ddraw.c:4874) ==9737== by 0x4DF61F2: DDRAW_Create (main.c:274) ==9737== by 0x4DF6403: DirectDrawCreate (main.c:309) ==9737== by 0x4CA7528: CapsTest (d3d.c:810) ==9737== by 0x4CB7D2D: func_d3d (d3d.c:3953) ==9737== by 0x4D720F8: run_test (test.h:584) ==9737== by 0x4D724E7: main (test.h:654) ==9737== Address 0xeb4f7c0 is on thread 1's stack ==9737== OpenGL renderer string: GeForce GTX 460/PCIe/SSE2 OpenGL core profile version string: 4.3.0 NVIDIA 337.25 -- 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 36620] New: valgrind shows a few invalid reads in ddraw/tests/ddraw1.c
by wine-bugs＠winehq.org 15 Feb '19

15 Feb '19

https://bugs.winehq.org/show_bug.cgi?id=36620 Bug ID: 36620 Summary: valgrind shows a few invalid reads in ddraw/tests/ddraw1.c Product: Wine Version: 1.7.18 Hardware: x86 OS: Linux Status: NEW Keywords: download, source, testcase Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com ==13886== Invalid read of size 4 ==13886== at 0x4BC58CC: d3d_viewport_Clear (viewport.c:671) ==13886== by 0x4A83D8A: test_material (ddraw1.c:4948) ==13886== by 0x4A873B1: func_ddraw1 (ddraw1.c:5522) ==13886== by 0x4B24F84: run_test (test.h:584) ==13886== by 0x4B25373: main (test.h:654) ==13886== Address 0xa060788 is 40 bytes inside a block of size 108 free'd ==13886== at 0x7BC4C7AA: notify_free (heap.c:263) ==13886== by 0x7BC510EF: RtlFreeHeap (heap.c:1762) ==13886== by 0x4BAB294: d3d_material3_Release (material.c:155) ==13886== by 0x4BABD73: d3d_material1_Release (material.c:400) ==13886== by 0x4A6C23C: destroy_material (ddraw1.c:426) ==13886== by 0x4A83A74: test_material (ddraw1.c:4917) ==13886== by 0x4A873B1: func_ddraw1 (ddraw1.c:5522) ==13886== by 0x4B24F84: run_test (test.h:584) ==13886== by 0x4B25373: main (test.h:654) ==13886== -- 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 20083] New: Invalid PIO_STACK_LOCATION->FileObject passed into IRP_MJ_DEVICE_CONTROL dispatch routine
by wine-bugs＠winehq.org 15 Feb '19

15 Feb '19

http://bugs.winehq.org/show_bug.cgi?id=20083 Summary: Invalid PIO_STACK_LOCATION->FileObject passed into IRP_MJ_DEVICE_CONTROL dispatch routine Product: Wine Version: 1.1.29 Platform: PC URL: http://rh-software.com/ OS/Version: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: ntoskrnl AssignedTo: wine-bugs(a)winehq.org ReportedBy: ray(a)pobox.co.uk When the SIVDRIVER IRP_MJ_DEVICE_CONTROL dispatch routine is called the PIO_STACK_LOCATION->FileObject in incalid, in fact it's set of 0x66666666. This caused the v4.00 SIVDRIVER to crash as it expects to setup PFILE_OBJECT->FsContext in file create callback and use it while processing IRP_MJ_DEVICE_CONTROL. For 4.01 I managed to stop the crashes by adding code to check for 0x66666666. This really needs to be fixed though. -- 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.

1 15

[Bug 36343] New: valgrind shows some leaks in ddraw/tests/ddraw4.c
by wine-bugs＠winehq.org 15 Feb '19

15 Feb '19

https://bugs.winehq.org/show_bug.cgi?id=36343 Bug ID: 36343 Summary: valgrind shows some leaks in ddraw/tests/ddraw4.c Product: Wine Version: 1.7.18 Hardware: x86 OS: Linux Status: NEW Keywords: download, source, testcase Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com ==28085== 20 bytes in 1 blocks are definitely lost in loss record 208 of 1,106 ==28085== at 0x7BC50A9B: RtlAllocateHeap (heap.c:255) ==28085== by 0x4A8BA7E: DirectDrawCreateClipper (ddraw.c:3274) ==28085== by 0x4A8BC42: ddraw7_CreateClipper (ddraw.c:3309) ==28085== by 0x4A8BCEF: ddraw4_CreateClipper (ddraw.c:3320) ==28085== by 0x4D7985C: test_clipper_blt (ddraw4.c:786) ==28085== by 0x4D8B583: func_ddraw4 (ddraw4.c:7301) ==28085== by 0x4DDD6DC: run_test (test.h:584) ==28085== by 0x4DDDACB: main (test.h:654) ==28085== ==28085== 28 bytes in 1 blocks are possibly lost in loss record 285 of 1,106 ==28085== at 0x7BC50A9B: RtlAllocateHeap (heap.c:255) ==28085== by 0x5FCEBB8: apartment_getclassobject (compobj.c:526) ==28085== by 0x5FD1FC6: get_inproc_class_object (compobj.c:2894) ==28085== by 0x5FD4D2F: CoGetClassObject (compobj.c:3032) ==28085== by 0x5FD54B7: CoCreateInstance (compobj.c:3197) ==28085== by 0x4D9093C: func_ddraw4 (ddraw4.c:3233) ==28085== by 0x4DDD6DC: run_test (test.h:584) ==28085== by 0x4DDDACB: main (test.h:654) ==28085== ==28085== 92 bytes in 1 blocks are possibly lost in loss record 550 of 1,106 ==28085== at 0x7BC50A9B: RtlAllocateHeap (heap.c:255) ==28085== by 0x4A82099: d3d3_CreateViewport (ddraw.c:3941) ==28085== by 0x4D859FB: create_viewport.constprop.6 (ddraw4.c:310) ==28085== by 0x4D8786C: test_lighting_interface_versions (ddraw4.c:3767) ==28085== by 0x4D91469: func_ddraw4 (ddraw4.c:7326) ==28085== by 0x4DDD6DC: run_test (test.h:584) ==28085== by 0x4DDDACB: main (test.h:654) ==28085== ==28085== 148 bytes in 1 blocks are possibly lost in loss record 752 of 1,106 ==28085== at 0x40087BA: calloc (in /usr/lib/valgrind/vgpreload_memcheck-x86-linux.so) ==28085== by 0x74466AF: ??? (in /usr/lib/libdrm_intel.so.1.0.0) ==28085== by 0x7441294: drm_intel_bo_alloc (in /usr/lib/libdrm_intel.so.1.0.0) ==28085== by 0x7052078: ??? (in /usr/lib/dri/i965_dri.so) ==28085== by 0x70524E1: ??? (in /usr/lib/dri/i965_dri.so) ==28085== by 0x6DCE2FA: ??? (in /usr/lib/dri/i965_dri.so) ==28085== by 0x6B80BFD: shared_dispatch_stub_462 (in /usr/lib/libglapi.so.0.0.0) ==28085== by 0x51C7020: surface_prepare_map_memory (surface.c:563) ==28085== by 0x51D2387: surface_realize_palette (surface.c:783) ==28085== by 0x51C7EAA: wined3d_surface_set_palette (surface.c:2403) ==28085== by 0x4AA277B: ddraw_surface_set_palette (surface.c:472) ==28085== by 0x4AA2A23: ddraw_surface4_SetPalette (surface.c:4695) ==28085== by 0x4D819F2: test_palette_gdi (ddraw4.c:7163) ==28085== by 0x4D92809: func_ddraw4 (ddraw4.c:7348) ==28085== by 0x4DDD6DC: run_test (test.h:584) ==28085== by 0x4DDDACB: main (test.h:654) ==28085== ==28085== 4,096 bytes in 1 blocks are definitely lost in loss record 1,066 of 1,106 ==28085== at 0x74456F1: ??? (in /usr/lib/libdrm_intel.so.1.0.0) ==28085== by 0x7441378: drm_intel_bo_map (in /usr/lib/libdrm_intel.so.1.0.0) ==28085== by 0x7056342: ??? (in /usr/lib/dri/i965_dri.so) ==28085== by 0x7057B14: ??? (in /usr/lib/dri/i965_dri.so) ==28085== by 0x705E23D: ??? (in /usr/lib/dri/i965_dri.so) ==28085== by 0x6E8D781: ??? (in /usr/lib/dri/i965_dri.so) ==28085== by 0x7060E0E: ??? (in /usr/lib/dri/i965_dri.so) ==28085== by 0x6E76789: ??? (in /usr/lib/dri/i965_dri.so) ==28085== by 0x6E7ADE9: ??? (in /usr/lib/dri/i965_dri.so) ==28085== by 0x6A31BD5: glTexSubImage2D (in /usr/lib/libGL.so.1.2.0) ==28085== by 0x51C54E9: surface_upload_data (surface.c:1680) ==28085== by 0x51D1447: surface_load_texture (surface.c:5062) ==28085== by 0x51CBD1C: surface_load_location (surface.c:5155) ==28085== by 0x51CDCCE: surface_load (surface.c:2192) ==28085== by 0x51DB1F1: wined3d_texture_load (texture.c:539) ==28085== by 0x5133092: arbfp_blit_surface (arb_program_shader.c:7652) ==28085== by 0x51D37B6: wined3d_surface_blt (surface.c:6260) ==28085== by 0x4AADA52: ddraw_surface7_Blt (surface.c:1381) ==28085== by 0x4AAE5F6: ddraw_surface4_Blt (surface.c:1558) ==28085== by 0x4D7B843: test_p8_rgb_blit (ddraw4.c:6812) ==28085== -- 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 35985] New: Microsoft Paint draws rounded-corner rectangle instead of sharp corner
by wine-bugs＠winehq.org 14 Feb '19

14 Feb '19

http://bugs.winehq.org/show_bug.cgi?id=35985 Bug ID: 35985 Summary: Microsoft Paint draws rounded-corner rectangle instead of sharp corner Product: Wine Version: 1.7.15 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: Nachanon_Vetjasit(a)hotmail.com Created attachment 48106 --> http://bugs.winehq.org/attachment.cgi?id=48106 Screenshot and output image from WINE 1.7.15 and Windows XP SP3 I've used Microsoft Paint on WINE, most tools work fine. But I found that when I set line thickness to > 1px (using Line tool) then use Rectangle tool to create a rectangle, those rectangle will have round corners, rather than a regular sharp corner that it produces on Windows. Screenshot from WINE (1.7.15) and Windows (XP SP3) also attached, output file from both configuration also attached too. First rectangle is 5px-thick, second is 11px-thick (select 5px and press ^+ 6 times). Note: For knot on the top-left corner of rectangle (invisible in the screenshot, but it's there, and got into the output), I've filed it as a different issue: bug #35984 Microsoft Paint 5.1.2600.5512 (mspaint.exe from Windows XP SP3) mfc42u.dll 6.2.8071.0 picked from Windows XP SP3, placed with the same directory as mspaint.exe WINE: 1.7.15 (git), set to Windows version XP WINE installed without XInput2, OSMesa, OpenCL, CMS, GStreamer, and OSS support System: Debian GNU/Linux 5.0 "Lenny" i386 -- 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 36670] New: valgrind shows invalid read/write in d3d8/tests/device.c
by wine-bugs＠winehq.org 12 Feb '19

12 Feb '19

https://bugs.winehq.org/show_bug.cgi?id=36670 Bug ID: 36670 Summary: valgrind shows invalid read/write in d3d8/tests/device.c Product: Wine Version: 1.7.19 Hardware: x86 OS: Linux Status: NEW Keywords: download, source, testcase, valgrind Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com ==18653== Conditional jump or move depends on uninitialised value(s) ==18653== at 0x7D4EF6A: ??? (in /usr/lib32/libnvidia-glcore.so.337.25) ==18653== by 0x7D51B43: ??? (in /usr/lib32/libnvidia-glcore.so.337.25) ==18653== by 0x783724B: ??? (in /usr/lib32/libnvidia-glcore.so.337.25) ==18653== by 0x783752D: ??? (in /usr/lib32/libnvidia-glcore.so.337.25) ==18653== by 0x4F8A277: wined3d_timestamp_query_ops_get_data (query.c:566) ==18653== by 0x4F88F3D: wined3d_query_get_data (query.c:281) ==18653== by 0x4ED2DF7: d3d9_query_GetData (query.c:161) ==18653== by 0x4CE573A: test_timestamp_query (device.c:4703) ==18653== by 0x4CFADE0: func_device (device.c:8803) ==18653== by 0x4D5B1E8: run_test (test.h:584) ==18653== by 0x4D5B5D3: main (test.h:654) ==18653== Uninitialised value was created by a heap allocation ==18653== at 0x4029155: malloc (vg_replace_malloc.c:292) ==18653== by 0x64F6097: ??? (in /usr/lib32/opengl/nvidia/lib/libGL.so.337.25) ==18653== by 0x7B9FF8F: ??? (in /usr/lib32/libnvidia-glcore.so.337.25) ==18653== by 0x7B60EDF: ??? (in /usr/lib32/libnvidia-glcore.so.337.25) ==18653== by 0x7B521E3: ??? (in /usr/lib32/libnvidia-glcore.so.337.25) ==18653== by 0x7B2C9C8: ??? (in /usr/lib32/libnvidia-glcore.so.337.25) ==18653== by 0x64A075A: ??? (in /usr/lib32/opengl/nvidia/lib/libGL.so.337.25) ==18653== by 0x64A08FF: ??? (in /usr/lib32/opengl/nvidia/lib/libGL.so.337.25) ==18653== by 0x64D0946: ??? (in /usr/lib32/opengl/nvidia/lib/libGL.so.337.25) ==18653== by 0x64C5A78: glXMakeCurrent (in /usr/lib32/opengl/nvidia/lib/libGL.so.337.25) ==18653== by 0x5FFBBE5: X11DRV_WineGL_InitOpenglInfo (opengl.c:486) ==18653== by 0x5FFD2EB: has_opengl (opengl.c:665) ==18653== by 0x6005418: get_glx_driver (opengl.c:3262) ==18653== by 0x5FF0A00: X11DRV_wine_get_wgl_driver (init.c:459) ==18653== by 0x57530B3: __wine_get_wgl_driver (opengl.c:58) ==18653== by 0x4F6811F: wined3d_adapter_init (directx.c:5147) ==18653== by 0x4F689B9: wined3d_init (directx.c:5272) ==18653== by 0x500A714: wined3d_create (wined3d_main.c:105) ==18653== by 0x4ED25D4: d3d9_init (directx.c:647) ==18653== by 0x4EC4DB1: Direct3DCreate9 (d3d9_main.c:45) ==18653== OpenGL renderer string: GeForce GTX 460/PCIe/SSE2 OpenGL core profile version string: 4.3.0 NVIDIA 337.25 -- 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

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 September 2015