September 2023 - Wine-bugs - list.winehq.org

[Bug 44276] New: Poor resolution change handling with Shadow of Memories demo
by wine-bugs＠winehq.org 13 Oct '23

13 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=44276 Bug ID: 44276 Summary: Poor resolution change handling with Shadow of Memories demo Product: Wine Version: 2.21 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: jhansonxi(a)gmail.com Distribution: Ubuntu Created attachment 60099 --> https://bugs.winehq.org/attachment.cgi?id=60099 Log from successful demo gameplay start When game starts (fresh boot) it shows only the upper-left quadrant of the logo screens. It then changes resolution and shows the intro video the size of a postage stamp (often loses focus and an alt-tab is needed to see it). It then shows only the upper-left quadrant of the main menu. It's possible to pan around and see all of it but the button graphics don't align with the buttons so they're hard to target with the pointer. At the main menu, if the game is started it often freezes at the "Prologue" screen. Alt-tabbing during these various stages can trigger some odd effects (at least with the Nvidia proprietary driver). The game will crash, the screen gets left at a low resolution, etc. Eventually the behavior changes - the game launches the opening screens correctly sized but with the Xfce desktop panel still visible. The game will then be startable (won't freeze at the "Prologue" screen). It still seems to freeze further along, normally after the tea house scene when control is returned to the player. The behavior is persistent until the system is rebooted. The CD version of the game acts the same except it never seems to get past "Prologue". Some of this may be related to bug #44275. Install notes (demo download link on same page): https://appdb.winehq.org/objectManager.php?sClass=version&iId=31628#notes System tested: Xubuntu 17.04 x86, Intel Pentium D 3.46GHz, GeForce 8600 GT with Nvidia 340.102 driver. wine-staging 2.21.0~zesty from dl.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.

2 6

[Bug 43017] New: Unreal Tournament 2004/UT2004.exe crashes due to " intel_do_flush_locked failed: Cannot allocate memory"
by wine-bugs＠winehq.org 13 Oct '23

13 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=43017 Bug ID: 43017 Summary: Unreal Tournament 2004/UT2004.exe crashes due to "intel_do_flush_locked failed: Cannot allocate memory" Product: Wine Version: 2.7 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: krichter(a)posteo.de Distribution: --- Unreal Tournament 2004/UT2004.exe crashes due to `intel_do_flush_locked failed: Cannot allocate memory` the debug output of PlayOnLinux reads ``` [05/12/17 23:55:35] - Running wine-2.7 UT2004.exe (Working directory : /home/richter/.PlayOnLinux/wineprefix/UnrealT2004/drive_c/Program Files/Unreal Tournament 2004/System) err:module:load_builtin_dll failed to load .so lib for builtin L"winebus.sys": libudev.so.0: cannot open shared object file: No such file or directory err:winedevice:async_create_driver failed to create driver L"WineBus": c0000142 fixme:process:GetProcessWorkingSetSize (0xffffffff,0x32e540,0x32e53c): stub fixme:system:SystemParametersInfoW Unimplemented action: 59 (SPI_SETSTICKYKEYS) err:ole:CoGetClassObject class {96749377-3391-11d2-9ee3-00c04f797396} not registered err:ole:CoGetClassObject class {96749377-3391-11d2-9ee3-00c04f797396} not registered err:ole:create_server class {96749377-3391-11d2-9ee3-00c04f797396} not registered err:ole:CoGetClassObject no class object {96749377-3391-11d2-9ee3-00c04f797396} could be created for context 0x7 fixme:win:EnumDisplayDevicesW ((null),0,0x32bc98,0x00000000), stub! fixme:d3d:wined3d_swapchain_set_gamma_ramp Ignoring flags 0x1. err:xvidmode:ComputeGammaFromRamp low-biased gamma ramp (3604), rejected fixme:d3d:wined3d_swapchain_set_gamma_ramp Ignoring flags 0x1. err:xvidmode:ComputeGammaFromRamp low-biased gamma ramp (3604), rejected fixme:imm:ImmReleaseContext (0x1007c, 0x2165e0): stub fixme:hnetcfg:fw_profile_get_FirewallEnabled 0x6404c88, 0x32ccc4 err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_ENUM in glClampColorARB(clamp)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=-1042267284)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1082643741)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1129305379)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=-1017464658)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1106373278)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1061644189)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1103102115)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1102202262)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1127878391)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1133393126)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1064431753)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1056334452)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1103590910)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1128011843)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=-1012511863)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1129177136)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1064579615)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1107545964)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1127492263)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1131588260)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=-1009667614)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1064940315)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1102388947)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1107645235)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1127352012)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1106599611)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1065065837)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1056114040)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1104285584)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1127422744)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=-1029644321)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1126051816)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1065075311)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_ENUM in glClampColorARB(clamp)". intel_do_flush_locked failed: Cannot allocate memory ``` -- 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 54744] New: explorerframe:taskbarlist - test_ITaskbarList() sometimes gets E_NOTIMPL on Windows
by WineHQ Bugzilla 13 Oct '23

13 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=54744 Bug ID: 54744 Summary: explorerframe:taskbarlist - test_ITaskbarList() sometimes gets E_NOTIMPL on Windows Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: explorerframe Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com explorerframe:taskbarlist - test_ITaskbarList() sometimes gets E_NOTIMPL on Windows: taskbarlist.c:61: Test failed: Got hr 0x80004001. taskbarlist.c:66: Test failed: Got hr 0x80004001. See https://test.winehq.org/data/patterns.html#explorerframe:taskbarlist Where 0x80004001 == E_NOTIMPL On average this happens about once every other month on recent Windows 10 versions: * 2022-08-31 on w1064-tsign-64 (21h2) * 2022-11-14 on w1064-tsign-32 (21h2) * 2023-01-10 on fgtb-w10pro64-rx550-64 (22h2) * 2023-02-06 on w10pro64-rx550-64 (22h2) * 2023-03-27 on w10pro64-ar-64 (21h1) -- 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 55658] New: psapi:psapi_main - test_EnumProcessModules*() fails on macOS
by WineHQ Bugzilla 13 Oct '23

13 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=55658 Bug ID: 55658 Summary: psapi:psapi_main - test_EnumProcessModules*() fails on macOS Product: Wine Version: unspecified Hardware: x86-64 OS: Mac OS X Status: NEW Severity: normal Priority: P2 Component: psapi Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com psapi:psapi_main - test_EnumProcessModules*() fails on macOS: psapi_main.c:156: Test failed: got 0, error 5 psapi_main.c:158: Test failed: expected non-NULL module psapi_main.c:162: Test failed: got error 5 psapi_main.c:163: Test failed: got PÛ psapi_main.c:166: Test failed: got error 5 psapi_main.c:167: Test failed: got psapi_main.c:170: Test failed: got error 5 psapi_main.c:183: Test failed: got error 5 psapi_main.c:184: Test failed: third DLL in wow64 should be one of wow*.dll () psapi_main.c:239: Test failed: pcs-6432: 1: didn't succeed 5 psapi_main.c:239: Test failed: pcs-6432: 2: didn't succeed 5 psapi_main.c:239: Test failed: pcs-6432: 0: didn't succeed 5 psapi_main.c:239: Test failed: pcs-6432: 3: didn't succeed 5 psapi_main.c:507: Test failed: pcs-6432: expecting 32bit modules psapi_main.c:510: Test marked todo: pcs-6432: expecting 64bit modules psapi_main.c:345: Test failed: pcs-6432: 1: got error 5 psapi_main.c:346: Test failed: pcs-6432: 1: expecting msinfo32.exe but got psapi_main.c:348: Test failed: pcs-6432: 1: got error 5 psapi_main.c:349: Test failed: pcs-6432: 1: expecting C:\windows\syswow64\msinfo32.exe but got psapi_main.c:352: Test failed: pcs-6432: 1: got error 5 psapi_main.c:353: Test failed: pcs-6432: 1: expected 00000000DEADBEEF, got 0000000178010008 psapi_main.c:355: Test failed: pcs-6432: 1: got entry point 0000000000000000 psapi_main.c:345: Test failed: pcs-6432: 0: got error 5 psapi_main.c:346: Test failed: pcs-6432: 0: expecting msinfo32.exe but got psapi_main.c:348: Test failed: pcs-6432: 0: got error 5 psapi_main.c:349: Test failed: pcs-6432: 0: expecting C:\windows\syswow64\msinfo32.exe but got psapi_main.c:352: Test failed: pcs-6432: 0: got error 5 psapi_main.c:353: Test failed: pcs-6432: 0: expected 00000000DEADBEEF, got 0000000178010008 psapi_main.c:355: Test failed: pcs-6432: 0: got entry point 0000000000000000 psapi_main.c:345: Test failed: pcs-6432: 3: got error 5 psapi_main.c:346: Test failed: pcs-6432: 3: expecting msinfo32.exe but got psapi_main.c:348: Test failed: pcs-6432: 3: got error 5 psapi_main.c:349: Test failed: pcs-6432: 3: expecting C:\windows\syswow64\msinfo32.exe but got psapi_main.c:352: Test failed: pcs-6432: 3: got error 5 psapi_main.c:353: Test failed: pcs-6432: 3: expected 00000000DEADBEEF, got 0000000178010008 psapi_main.c:355: Test failed: pcs-6432: 3: got entry point 0000000000000000 psapi_main.c:529: Test succeeded inside todo block: pcs-6432: Wrong count 0 in C:\windows\syswow64 See https://test.winehq.org/data/patterns.html#psapi:psapi_main This set of failures started on 2023-09-14 and only happens on macOS (see Remi's rbernon-macos-* cloud test machines). -- 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 55674] New: 64-bit wineserver/wine-preloader hangs on macOS 14.
by WineHQ Bugzilla 13 Oct '23

13 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=55674 Bug ID: 55674 Summary: 64-bit wineserver/wine-preloader hangs on macOS 14. Product: Wine Version: 8.16 Hardware: x86-64 OS: Mac OS X Status: NEW Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: jactry92(a)gmail.com This is a regression introduced by a81c53504ae32715e6e91bd020fdebd5bef20d48. Before this commit, I can run Notepad++ with a WOW64 build on macOS 14. But now, I can't even start `winecfg` and create a wineprefix. I don't reproduce this issue with 64-bit Wine on Linux, so this is a Mac-specific issue. -- 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 55241] New: The 64-bit winmm:capture & winmm:wave crash on Windows 8
by WineHQ Bugzilla 13 Oct '23

13 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=55241 Bug ID: 55241 Summary: The 64-bit winmm:capture & winmm:wave crash on Windows 8 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: winmm&mci Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com The 64-bit winmm:capture & winmm:wave crash on Windows 8: capture.c:171: this is the last test seen before the exception 07d0:capture: unhandled exception c0000005 at 00007FFDC66DCF38 wave.c:686: this is the last test seen before the exception 0b14:wave: unhandled exception c0000005 at 00007FFDC66DCF38 See https://test.winehq.org/data/patterns.html#winmm:capture https://test.winehq.org/data/patterns.html#winmm:wave This started with the GitLab CI's switch to Debian 12 (bookworm) for the build system: * The winmm_test.exe binary produced by the TestBot's Debian 11-based build VM produces no failures when run on Windows while GitLab CI's binary for the same Wine version produces this set of failures. * And the TestBot runs the official WineTest builds on its Windows VMs which is why the failures appeared on 2023-07-10 which corresponds to this commit: commit 5799e89f15b5584f186dcc2fd24b98e0a7bd6c10 Author: Alexandre Julliard <julliard(a)winehq.org> Date: Mon Jul 10 17:18:49 2023 +0200 gitlab: Upgrade the Debian image to bookworm. Now the question is whether the new build environment revealed a preexisting bug in Wine, or if the new build environment itself is broken, or if the bug is elsewhere such as in the MinGW compiler. This is also likely the same issue as bug 55240. -- 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 54069] New: ddraw:ddraw7 - test_texture_wrong_caps() sometimes fails on Windows 8+
by WineHQ Bugzilla 13 Oct '23

13 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=54069 Bug ID: 54069 Summary: ddraw:ddraw7 - test_texture_wrong_caps() sometimes fails on Windows 8+ Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: d3d Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com ddraw:ddraw7 - test_texture_wrong_caps() sometimes fails on Windows 8+. ddraw7.c:18954: Test failed: Got unexpected color 0x00000040. and ddraw7.c:18972: Test failed: Got unexpected color 0x00ff00ff. See https://test.winehq.org/data/patterns.html#ddraw:ddraw7 Notes: * There is no evidence of this happening on Windows 11. * This seems to only happen with Microsoft's "Microsoft Basic Display Adapter" driver: the "-1qxl" and "-2qxl" (dual-monitor) configuration use the "Red Hat QXL controller" driver and are are not affected. Neither are the AMD / NVIDIA PCI passthrough configurations. * The 0x00000040 result mostly happens on Windows 8 to Windows 10 1607 but it also happened a couple of times on Windows 10 21H2. Meanwhile the 0x00ff00ff result seems to only happen on Windows 10 2004+. * ddraw:ddraw1, ddraw:ddraw2 and ddraw:ddraw4 have a similar test function but don't have this failure. -- 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 43185] New: "Battle Bugs" game in unresponsive once game starts
by wine-bugs＠winehq.org 13 Oct '23

13 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=43185 Bug ID: 43185 Summary: "Battle Bugs" game in unresponsive once game starts Product: Wine Version: 2.9 Hardware: x86-64 OS: Linux Status: NEW Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: matt(a)nightrealms.com Distribution: --- Created attachment 58457 --> https://bugs.winehq.org/attachment.cgi?id=58457 Wine output from before starting the game When playing the free game "Battle Bugs" (https://ldjam.com/events/ludum-dare/38/battle-bugs) on 64 bit Linux, the game start screen loads just fine, and pressing an indicated key starts the game just fine, but once the game starts nothing is moving and the game doesn't respond to any keys. Got the same results with both versions of the executable, and both WINEARCH unspecified or set to win32 -- 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 55211] New: Print file not truncated when printing to file in FrameMaker 8
by WineHQ Bugzilla 13 Oct '23

13 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=55211 Bug ID: 55211 Summary: Print file not truncated when printing to file in FrameMaker 8 Product: Wine Version: 8.12 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: spooler Assignee: wine-bugs(a)winehq.org Reporter: ulrich.gemkow(a)ikr.uni-stuttgart.de Distribution: --- A existing print file ist not truncated when printing to the same file again. So when printing a smaller document to the print file which was generated for a larger file, the resultung file contains garbage at its end. This happens in Framemaker 8 and may happen in other apps too. To reproduce - Install Framemaker from the given URL - Print the attached Document Large.fm to a file (select print to file in the printer dialog). Check the size of the generated file. - Print the attached Document Small.fm to the same file generated in the previous step. Check again the size of the file - its the same. Depending on the used Postscript interpreter reading the file fails because of the garbage at the files end. This is simple to see when using different documents as descibed above. When printing existing documents again after (even small) changes the resulting print file may be garbage without notice. -- 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 13

[Bug 55273] New: ntdll:wow64 - The 64-bit test_cpu_area() gets bad offsets on Windows 10 1607 & 1709
by WineHQ Bugzilla 13 Oct '23

13 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=55273 Bug ID: 55273 Summary: ntdll:wow64 - The 64-bit test_cpu_area() gets bad offsets on Windows 10 1607 & 1709 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com ntdll:wow64 - The 64-bit test_cpu_area() gets bad offsets on Windows 10 1607 & 1709: wow64.c:783: Test failed: 0:0: wrong offset 4 wow64.c:783: Test failed: 0:1: wrong offset 6 wow64.c:783: Test failed: 0:2: wrong offset 4 wow64.c:783: Test failed: 0:3: wrong offset 6 wow64.c:783: Test failed: 0:4: wrong offset 4 wow64.c:783: Test failed: 0:5: wrong offset 6 wow64.c:783: Test failed: 0:6: wrong offset 4 wow64.c:783: Test failed: 0:7: wrong offset 6 wow64.c:783: Test failed: 1:0: wrong offset 16 wow64.c:783: Test failed: 1:1: wrong offset 14 wow64.c:783: Test failed: 1:2: wrong offset 12 wow64.c:783: Test failed: 1:3: wrong offset 10 wow64.c:783: Test failed: 1:4: wrong offset 8 wow64.c:783: Test failed: 1:5: wrong offset 6 wow64.c:783: Test failed: 1:6: wrong offset 4 wow64.c:783: Test failed: 1:7: wrong offset 18 wow64.c:783: Test failed: 2:0: wrong offset 8 wow64.c:783: Test failed: 2:1: wrong offset 6 wow64.c:783: Test failed: 2:2: wrong offset 4 wow64.c:783: Test failed: 2:3: wrong offset 10 wow64.c:783: Test failed: 2:4: wrong offset 8 wow64.c:783: Test failed: 2:5: wrong offset 6 wow64.c:783: Test failed: 2:6: wrong offset 4 wow64.c:783: Test failed: 2:7: wrong offset 10 wow64.c:783: Test failed: 3:0: wrong offset 16 wow64.c:783: Test failed: 3:1: wrong offset 14 wow64.c:783: Test failed: 3:2: wrong offset 12 wow64.c:783: Test failed: 3:3: wrong offset 10 wow64.c:783: Test failed: 3:4: wrong offset 8 wow64.c:783: Test failed: 3:5: wrong offset 6 wow64.c:783: Test failed: 3:6: wrong offset 4 wow64.c:783: Test failed: 3:7: wrong offset 18 See https://test.winehq.org/data/patterns.html#ntdll:wow64 The failures started with GitLab CI's switch to Debian 12 for the WineTest builds which are used in the WineTest nightlies. However they also happen with binaries built on Debian 11 so in this case it is just a coincidence. See also bug 55272 for ntdll:exception crashes that started at the same time on the same set of machines. -- 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