March 2026 - Wine-Bugs - list.winehq.org

[Bug 59519] New: ole32: OLE clipboard caches stale window handle after STA thread terminates, breaking subsequent OleSetClipboard calls
by WineHQ Bugzilla May 17, 2026

May 17, 2026

http://bugs.winehq.org/show_bug.cgi?id=59519 Bug ID: 59519 Summary: ole32: OLE clipboard caches stale window handle after STA thread terminates, breaking subsequent OleSetClipboard calls Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ole32 Assignee: wine-bugs(a)list.winehq.org Reporter: ayourk(a)gmail.com Distribution: --- Created attachment 80543 --> http://bugs.winehq.org/attachment.cgi?id=80543 reproducer source This bug is really starting to bug me ;) so I figured it was time to report it and squash it! I know that in REAL Windows, this works fine, but as you can test from the attached sample app, the clipboard copy only really works once before the application has to be restarted for it to work again. OleSetClipboard fails with CLIPBRD_E_CANT_OPEN (0x800401D0) on the second and all subsequent calls when each call is made from a new STA thread and the main thread has OLE initialized. This pattern is used by .NET WinForms applications. Clipboard.SetText() internally spawns a new STA thread, calls OleSetClipboard, then exits the thread. The main thread keeps OLE initialized (.NET runtime), so OLE_moduleLockCount never drops to 0 and clipbrd_uninitialize() never runs on the copy threads. The cached clipboard window HWND from the first (now-dead) thread is never cleared. This is deterministic, not a race condition. 100% reproducible on Wine 9.0 through 11.0. I even tested it on the latest development branch. The buggy caching pattern has been present since the OLE clipboard was first implemented (commit 557ff419bea, July 18, 1999), so this affects every Wine version ever released. It went unnoticed because the trigger pattern (main thread keeps OLE alive + new STA threads for each clipboard operation) is specific to .NET WinForms applications. Affected application: Space Engineers (Steam App ID 244850) — Ctrl+C works once, then freezes for ~1 second on every subsequent Ctrl+C. The clipboard never updates past the first copy. This is also reported at https://github.com/ValveSoftware/Proton/issues/1792 STEPS TO REPRODUCE ================== Prerequisites: Main thread has OLE initialized (OleInitialize), as in any .NET application. 1. Spawn STA Thread A: OleInitialize(NULL) -> OleSetClipboard(NULL) -> OleSetClipboard(data1) -> OleFlushClipboard() -> OleUninitialize() -> thread exits Wait for Thread A to complete. 2. Paste: OpenClipboard(NULL) -> GetClipboardData(CF_TEXT) -> "first" Result: correct. 3. Spawn STA Thread B: OleInitialize(NULL) -> OleSetClipboard(NULL) Result: returns 0x800401D0 (CLIPBRD_E_CANT_OPEN) All 10 retries fail with the same error. 4. Paste: GetClipboardData(CF_TEXT) -> still "first" Expected: "second" 5. All subsequent copy attempts from new threads fail the same way. EXPECTED BEHAVIOR (Windows) =========================== Each copy succeeds immediately. After step 3, the clipboard contains "second". Tested on Windows 7, 10, and 11 -- all succeed. ACTUAL BEHAVIOR (Wine 9.0 through 11.0) ======================================== First copy succeeds. All subsequent copies fail with CLIPBRD_E_CANT_OPEN. The clipboard permanently retains the first copied text. Each failed copy takes ~1 second (10 retries x 100ms). ROOT CAUSE ========== In dlls/ole32/clipboard.c, get_clipbrd_window() caches a single HWND per process: static inline HRESULT get_clipbrd_window(ole_clipbrd *clipbrd, HWND *wnd) { if ( !clipbrd->window ) clipbrd->window = create_clipbrd_window(); *wnd = clipbrd->window; return *wnd ? S_OK : E_FAIL; } When the STA thread that created this window terminates, the window is destroyed but the stale HWND remains cached. clipbrd_uninitialize() (which clears it) only runs when OLE_moduleLockCount drops to 0, which never happens in a .NET app because the main thread keeps OLE alive. PROPOSED FIX ============ Add an IsWindow() check to get_clipbrd_window(): if ( clipbrd->window && !IsWindow(clipbrd->window) ) clipbrd->window = NULL; This detects the stale handle and forces creation of a fresh window on the current thread. Patch is attached. REPRODUCER ========== A standalone GUI test app is attached (clipboard_test.c + .exe). It has two modes: Mode A (Bug): Replicates the exact .NET OLE clipboard path. - Main thread calls OleInitialize (simulates .NET environment) - Each copy spawns a new STA thread: OleInitialize -> OleSetClipboard(NULL) -> OleSetClipboard(data) -> OleFlushClipboard -> OleUninitialize -> exit - 10-retry loop with 100ms delays (matches .NET Clipboard.SetText exactly) - Three copy/paste cycles with "first", "second", "third" - Copy 1 succeeds; Copy 2 and 3 fail with 0x800401D0 Mode B (Fix): Same OLE operations but manages the clipboard window lifetime correctly, demonstrating the fix works. - All three copies succeed. Build: x86_64-w64-mingw32-gcc -o clipboard_test.exe clipboard_test.c \ -lgdi32 -lole32 -luuid -mwindows Run: wine clipboard_test.exe Log output (clipboard_test.log) is attached showing the 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 6

[Bug 57473] New: Virtual DJ 2024: Main interface animation flickers
by WineHQ Bugzilla May 17, 2026

May 17, 2026

https://bugs.winehq.org/show_bug.cgi?id=57473 Bug ID: 57473 Summary: Virtual DJ 2024: Main interface animation flickers Product: Wine Version: 9.22 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: rizalmart98(a)gmail.com Distribution: --- The main interface was shaking and flickers The terminal shows this error message: 01f0:fixme:d2d:d2d_text_renderer_DrawGlyphRun Ignoring options 0x6. -- 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 55518] New: VelbusLink: terminates immediately after creating a window
by WineHQ Bugzilla May 16, 2026

May 16, 2026

https://bugs.winehq.org/show_bug.cgi?id=55518 Bug ID: 55518 Summary: VelbusLink: terminates immediately after creating a window Product: Wine Version: 8.14 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: winehq(a)kazlauskas.me Distribution: --- Created attachment 75080 --> https://bugs.winehq.org/attachment.cgi?id=75080 stdout/err of the failing command When launching the application, the application window will briefly flash and disappear as the application terminates. I made few attempts to catch the moment this happens with `winedbg` to no avail. I’m using wine-staging 8.14 to test it, although I’ve tried various versions including 8.0. To reproduce this issue: 1. Download an installer for VelbusLink: $ curl 'https://www.velleman.eu/downloads/velbus/velbuslink/velbuslink-10.8.6.0.exe' -Lo ~/Downloads/velbuslink-10.8.6.0.exe $ sha256sum ~/Downloads/velbuslink-10.8.6.0.exe 39630e960fe5be289232a6f2409c92ffe0c81e1794f166919aaffddf33eb9814 ~/Downloads/velbuslink-10.8.6.0.exe 2. Install it via: `wine ~/Downloads/velbuslink-10.8.6.0.exe '/VERYSILENT'` 3. Run `wine ~/.wine/drive_c/Program\ Files\ $x86$/Velbus/VelbusLink/VelbusLink.exe`. --- Side notes: * With Wine 8.0 the application fails with an assertion as seen in Bug 50282. In Wine 8.14, there is no assertion failure, but the application fails to launch regardles. * Some version of steam proton manages to run the application, but it is rendered incorrectly with the window frame/background appearing in front of the application contents, making application effectively unusable. -- 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 54921] New: ADMS 1J Radio Programmer attempted an unsupported operation
by WineHQ Bugzilla May 16, 2026

May 16, 2026

https://bugs.winehq.org/show_bug.cgi?id=54921 Bug ID: 54921 Summary: ADMS 1J Radio Programmer attempted an unsupported operation Product: Wine Version: 8.7 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: blocker Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: ttvibz(a)tutamail.com Distribution: --- Created attachment 74438 --> https://bugs.winehq.org/attachment.cgi?id=74438 RTSystems radio programmer backtrace. 1) When opening the program, a dialog box is displayed that an unsupported operation was attempted. Clicking "Close", the program opens and displays normally. 2) Tried to open a data file (previously generated under the program while running in Windows) and received a Program Error dialog: "The program RadioEngine_V5.exe has encountered a serious problem and needs to close. We are sorry for the inconvenience." -- 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 7

[Bug 50282] New: Assertion `pellip->under == 0 && pellip->after == 0' failed.
by WineHQ Bugzilla May 16, 2026

May 16, 2026

https://bugs.winehq.org/show_bug.cgi?id=50282 Bug ID: 50282 Summary: Assertion `pellip->under == 0 && pellip->after == 0' failed. Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: apphelp Assignee: wine-bugs(a)winehq.org Reporter: mr.acar07(a)gmail.com Distribution: --- test(a)debian:~/.wine/drive_c/AKINSOFT/Wolvox8/ERP$ wine WERP8.exe 001d:err:eventlog:ReportEventW L"The registry information is missing.\r\nPlease run the Firebird Configuration Utilit" 0009:err:shell:SHGetFileInfoW pidl is null! 0009:err:shell:SHGetFileInfoW pidl is null! [1208/124013:ERROR:network_change_notifier_win.cc(153)] WSALookupServiceBegin failed with: 0 [1208/124013:ERROR:proxy_service_factory.cc(129)] Cannot use V8 Proxy resolver in single process mode. 0009:err:ole:CoGetClassObject class {54e211b6-3650-4f75-8334-fa359598e1c5} not registered 0009:err:ole:CoGetClassObject no class object {54e211b6-3650-4f75-8334-fa359598e1c5} could be created for context 0x1 [1208/124014:FATAL:direct_manipulation.cc(34)] Check failed: SUCCEEDED(hr). text.c:750: TEXT_NextLineW: Assertion `pellip->under == 0 && pellip->after == 0' failed. text.c:750: TEXT_NextLineW: Assertion `pellip->under == 0 && pellip->after == 0' failed. text.c:750: TEXT_NextLineW: Assertion `pellip->under == 0 && pellip->after == 0' failed. text.c:750: TEXT_NextLineW: Assertion `pellip->under == 0 && pellip->after == 0' failed. text.c:750: TEXT_NextLineW: Assertion `pellip->under == 0 && pellip->after == 0' failed. text.c:750: TEXT_NextLineW: Assertion `pellip->under == 0 && pellip->after == 0' failed. text.c:750: TEXT_NextLineW: Assertion `pellip->under == 0 && pellip->after == 0' failed. Its a paid Turkish accounting app. I make it working but only this error happen. -- 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 59038] New: wow64 mode and Unhandled exception: The type initializer for 'Microsoft.DotNet.Installer.Windows.InstallerBase' threw an exception.
by WineHQ Bugzilla May 16, 2026

May 16, 2026

http://bugs.winehq.org/show_bug.cgi?id=59038 Bug ID: 59038 Summary: wow64 mode and Unhandled exception: The type initializer for 'Microsoft.DotNet.Installer.Windows.InstallerBase' threw an exception. Product: Wine Version: 10.18 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)list.winehq.org Reporter: info(a)fernandolucas.info Distribution: --- Created attachment 79802 --> http://bugs.winehq.org/attachment.cgi?id=79802 wine console output I am using the new packages for Debian Wine 10.18 - 10.19 with the new wow64 mode. Installing .net 10 after initializing the prefix works well. Additional installations of a previous .net core version or running C:\Program Files\dotnet\dotnet.exe workload install wasm-tools fails with 0150:fixme:crypt:CertAddCertificateLinkToStore (00007FFFFED4B850, 00007FFFFE8A3DF8, 00000004, 0000000000000000): semi-stub Unhandled exception: The type initializer for 'Microsoft.DotNet.Installer.Windows.InstallerBase' threw an exception 0130:fixme:unwind:call_user_apc_dispatcher flags 0x3 are not supported. -- 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.

3 6

[Bug 58332] New: ntdll: Session shared memory gets mapped with MAP_PRIVATE, which causes rr-debugger to fail.
by WineHQ Bugzilla May 16, 2026

May 16, 2026

http://bugs.winehq.org/show_bug.cgi?id=58332 Bug ID: 58332 Summary: ntdll: Session shared memory gets mapped with MAP_PRIVATE, which causes rr-debugger to fail. Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: bernhardu(a)mailbox.org Distribution: --- Debugging Wine with rr-debugger allows to record whole wine process trees, and debug later different processes, e.g. wineserver and the .exe process, debug early startup or exception code, debug in reverse and multiple times. Therefore I asked for inclusion of [1] "spurious short writes", which got accepted at 2025-04-25. Thank you very much for it. Unfortunately short after it I found there is still an issue, which was a few months not there. So I started bisecting and arrived at [2] d9d012965de, "ntdll: Always map files as writable and adjust permissions.", committed at 2025-03-25. Unfortuntately this can not be cleanly reverted at current git, but with three more commits reverted it makes a wine tree, which can be used with rr-debugger [2]. I could reduce the changes of this 4 commits to a few lines which, are also able to produce a wine tree usable with rr-debugger [3]. This patch is only changing behaviour once for each .exe process, when the session shared memory gets mapped in via the fd received from wineserver. With unmodified Wine this is currently done with a MAP_PRIVATE flag, which turns out is currently just mapping the file content into the process, but does not receive the updates from wineserver. To investigate if this can be fixed in rr I opened [4]. Unfortunately this would be expected to create a overall slowdown for rr. Therefore I wonder if this change was intentional, to map the session shared memory with mmap(MAP_PRIVATE)? When looking at virtual_map_user_shared_data the shared memory gets mapped with mmap(MAP_SHARED). Would something like [3] be acceptable for inclusion? Kind regards, Bernhard [1] https://gitlab.winehq.org/wine/wine/-/commit/cd197f8588b [2] https://gitlab.winehq.org/wine/wine/-/commit/07160a23fa2 https://gitlab.winehq.org/wine/wine/-/commit/9e006e94c9c https://gitlab.winehq.org/wine/wine/-/commit/8fd49c4d8e9 https://gitlab.winehq.org/wine/wine/-/commit/d9d012965de [3] https://gitlab.winehq.org/bernhardu/wine/-/commit/658e56801a7 [4] https://github.com/rr-debugger/rr/issues/3972 -- 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 2

[Bug 56431] New: Dotnet TreeView disappearing plus-sign
by WineHQ Bugzilla May 16, 2026

May 16, 2026

https://bugs.winehq.org/show_bug.cgi?id=56431 Bug ID: 56431 Summary: Dotnet TreeView disappearing plus-sign Product: Wine Version: 9.3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: Wagner.a18(a)yahoo.com Distribution: --- I try to get a dotnet application, which has a treeview element on board, running. If I expand a tree node to display the next level of child tree nodes with a press on the plus-sign and collapse the child tree node level with the minus-sign after that. The plus-sign disappears and I am not able to expand the tree node again. I have to restart the whole application to be able to expand the tree node again. I installed this packages - WINEPREFIX=~/.wine-32 winetricks vcrun2005 vcrun2008 vcrun2010 vcrun2012 vcrun2013 vcrun2015 - WINEPREFIX=~/.wine-32 winetricks msxml3 - WINEPREFIX=~/.wine-32 winetricks msxml4 - WINEPREFIX=~/.wine-32 winetricks msxml6 - WINEPREFIX=~/.wine-32 winetricks mdac28 - WINEPREFIX=~/.wine-32 winetricks jet40 -- 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 35

[Bug 29579] New: winhelp: winhlp32.exe doesn't support making its window non-resizeable or without menu strip
by wine-bugs＠winehq.org May 16, 2026

May 16, 2026

http://bugs.winehq.org/show_bug.cgi?id=29579 Bug #: 29579 Summary: winhelp: winhlp32.exe doesn't support making its window non-resizeable or without menu strip Product: Wine Version: 1.3.36 Platform: x86-64 URL: http://download.microsoft.com/download/aoe/Trial/1.0/W IN98/EN-US/MSAoE.exe OS/Version: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: markk(a)clara.co.uk Classification: Unclassified In Windows, help files can cause the winhlp32 window to open with fixed (non-resizeable) dimensions, and/or with no menu strip. Wine winhlp32 does not support that feature. For example, download the Age of Empires trial version from http://www.microsoft.com/games/empires/downloads.htm direct download URL is http://download.microsoft.com/download/aoe/Trial/1.0/WIN98/EN-US/MSAoE.exe Either run MSAoE.exe to install the demo, or use cabextract to unpack the files inside. Run winhlp32.exe from Windows under Wine and load Empires.hlp. Notice the window has no menu strip and cannot be resized. (I tested winhlp32.exe from Windows 98 and XP.) Run Wine winhlp32.exe and load Empires.hlp. (The window contents are completely messed up and unusable, but that's not what this bug covers.) Notice the winhlp32 window is resizeable and has a menu strip. -- 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.

3 7

[Bug 59472] New: FreeArc hangs on startup in new wow64 mode
by WineHQ Bugzilla May 16, 2026

May 16, 2026

http://bugs.winehq.org/show_bug.cgi?id=59472 Bug ID: 59472 Summary: FreeArc hangs on startup in new wow64 mode Product: Wine Version: 11.3 Hardware: x86-64 URL: https://archive.org/details/FreeArc-0.666-win32bin-Sou rces OS: Linux Status: NEW Keywords: download, testcase, wow64 Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)list.winehq.org Reporter: arethusa26(a)gmail.com Distribution: --- Created attachment 80459 --> http://bugs.winehq.org/attachment.cgi?id=80459 Largest memory block loop test case executable When running the FreeArc archiver tool on the command line to add a file to an archive with a new wow64 build of Wine, the tool hangs indefinitely with only a banner output string: $ wine freearc/bin/Arc.exe a test.arc empty_file 0124:fixme:ntdll:NtQuerySystemInformation info_class SYSTEM_PERFORMANCE_INFORMATION FreeArc 0.666 With a old wow64 build of Wine, the tool runs and completes successfully: $ wine freearc/bin/Arc.exe a test.arc empty_file 0024:fixme:ntdll:NtQuerySystemInformation info_class SYSTEM_PERFORMANCE_INFORMATION FreeArc 0.666 0024:err:virtual:map_view anon mmap error Cannot allocate memory, size 0x80010000, unix_prot 0 0024:err:virtual:allocate_virtual_memory out of memory for allocation, base (nil) size 80000000 0024:err:virtual:map_view anon mmap error Cannot allocate memory, size 0x78010000, unix_prot 0 0024:err:virtual:allocate_virtual_memory out of memory for allocation, base (nil) size 78000000 ... creating archive: test.arc Compressing 1 file, 1,024 bytes. Processed 0% 0024:err:virtual:map_view anon mmap error Cannot allocate memory, size 0x80010000, unix_prot 0 0024:err:virtual:allocate_virtual_memory out of memory for allocation, base (nil) size 80000000 0024:err:virtual:map_view anon mmap error Cannot allocate memory, size 0x78010000, unix_prot 0 0024:err:virtual:allocate_virtual_memory out of memory for allocation, base (nil) size 78000000 ... Compressed 1 file, 1,024 => 44 bytes. Ratio 4.2% Compression time: cpu 0.62 secs, real 0.31 secs. Speed 3 kB/s All OK To reproduce the issue with FreeArc, download "FreeArc-portable-0.666-win32.zip" from the URL link and extract the contents of the ZIP file to a directory named "freearc". The Arc.exe binary can be run with the provided command line. When FreeArc is run with new wow64 Wine, there appears to be a thread that is stuck repeatedly calling VirtualAlloc with 0 size: 0124:trace:virtual:NtAllocateVirtualMemory 0xffffffffffffffff (nil) 00000000 2000 00000004 0124:trace:virtual:NtFreeVirtualMemory 0xffffffffffffffff (nil) 00000000 8000 0124:trace:virtual:NtAllocateVirtualMemory 0xffffffffffffffff (nil) 00000000 2000 00000004 0124:trace:virtual:NtFreeVirtualMemory 0xffffffffffffffff (nil) 00000000 8000 The code involved in the hang appears to be the LargestMemoryBlock::LargestMemoryBlock() constructor in Environment.cpp from the FreeArc sources. It's a (buggy) loop that attempts a binary search for the largest size it can successfully pass to VirtualAlloc. I have extracted the logic to create a standalone test case, which is built with: i686-w64-mingw32-gcc -O2 -Wall -Wl,--large-address-aware -o largest_memory_block.exe largest_memory_block.c On Windows 10, the largest_memory_block.exe test case shows the following output: a = 0 b = ffffffff Freeing pointer 00000000 with VirtualFree Allocating 7fffffff bytes with VirtualAlloc VirtualAlloc returned 00000000 VirtualAlloc failed, updating b to 7fffffff a = 0 b = 7fffffff Freeing pointer 00000000 with VirtualFree Allocating 3fffffff bytes with VirtualAlloc VirtualAlloc returned 01970000 VirtualAlloc succeeded, updating a to 3fffffff ... a = 7f98ffff b = 7f990001 Freeing pointer 00000000 with VirtualFree Allocating 7f990000 bytes with VirtualAlloc VirtualAlloc returned 7fff0000 VirtualAlloc succeeded, updating a to 7f990000 On new wow64 Wine, the test case shows the following output: a = 0 b = ffffffff Freeing pointer 00000000 with VirtualFree Allocating 7fffffff bytes with VirtualAlloc VirtualAlloc returned 7fff0000 VirtualAlloc succeeded, updating a to 7fffffff a = 7fffffff b = ffffffff Freeing pointer 7fff0000 with VirtualFree Allocating 3fffffff bytes with VirtualAlloc VirtualAlloc returned 00900000 VirtualAlloc succeeded, updating a to 3fffffff ... a = 1 b = ffffffff Freeing pointer 003f0000 with VirtualFree Allocating 0 bytes with VirtualAlloc VirtualAlloc returned 00000000 VirtualAlloc failed, updating b to 0 a = 1 b = 0 Freeing pointer 00000000 with VirtualFree Allocating 0 bytes with VirtualAlloc VirtualAlloc returned 00000000 VirtualAlloc failed, updating b to 0 ... The midpoint computation "c = (a + b) / 2" in the loop overflows when the initial allocation succeeds on Wine and leads to incorrect execution, whereas the initial allocation doesn't appear to succeed on Windows. -- 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