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

[Bug 49193] New: Denuvo Anti-Cheat 'denuvo-anti-cheat.sys' needs 'wdfldr.sys'
by WineHQ Bugzilla Sept. 7, 2026

Sept. 7, 2026

https://bugs.winehq.org/show_bug.cgi?id=49193 Bug ID: 49193 Summary: Denuvo Anti-Cheat 'denuvo-anti-cheat.sys' needs 'wdfldr.sys' Product: Wine Version: 5.8 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: focht(a)gmx.net Distribution: --- Hello folks, as it says. Continuation of bug 49192 Disclaimer for the general populace, to avoid these stupid comments on Reddit/your-favourite-gossip-site: This is not an attempt to make anything work. --- snip --- $ WINEDEBUG=+seh,+relay,+ntoskrnl wine net start "Denuvo Anti-Cheat" >>log.txt 2>&1 ... 00d0:trace:ntoskrnl:load_driver loading driver L"C:\\Program Files\\Denuvo Anti-Cheat\\denuvo-anti-cheat.sys" 00d0:Call KERNEL32.LoadLibraryW(0078eff0 L"C:\\Program Files\\Denuvo Anti-Cheat\\denuvo-anti-cheat.sys") ret=00236828 ... 00d0:err:module:import_dll Library netio.sys (which is needed by L"C:\\Program Files\\Denuvo Anti-Cheat\\denuvo-anti-cheat.sys") not found ... 00d0:err:module:import_dll Library wdfldr.sys (which is needed by L"C:\\Program Files\\Denuvo Anti-Cheat\\denuvo-anti-cheat.sys") not found 00d0:Ret ntdll.LdrLoadDll() retval=c0000135 ret=7b01d770 ... 00d0:Ret KERNEL32.LoadLibraryW() retval=00000000 ret=00236828 ... 00d0:trace:ntoskrnl:IoDeleteDriver (00000000000FB930) ... 00d0:err:ntoskrnl:ZwLoadDriver failed to create driver L"\\Registry\\Machine\\System\\CurrentControlSet\\Services\\Denuvo Anti-Cheat": c0000142 --- snip --- --- snip --- $ winedump -j import drive_c/Program\ Files/Denuvo\ Anti-Cheat/denuvo-anti-cheat.sys Contents of drive_c/Program Files/Denuvo Anti-Cheat/denuvo-anti-cheat.sys: 1553128 bytes Import Table size: 00000050 offset 0017381c netio.sys Hint/Name Table: 0017F670 TimeDateStamp: 00000000 (Thu Jan 1 01:00:00 1970) ForwarderChain: 00000000 First thunk RVA: 0017F000 Thunk Ordn Name 0017f000 1 WskDeregister 0017f008 2 WskRegister 0017f010 3 WskReleaseProviderNPI 0017f018 0 WskCaptureProviderNPI offset 00173830 ntoskrnl.exe Hint/Name Table: 0017F698 TimeDateStamp: 00000000 (Thu Jan 1 01:00:00 1970) ForwarderChain: 00000000 First thunk RVA: 0017F028 Thunk Ordn Name 0017f028 0 ExAcquireFastMutex 0017f030 1 ExAllocatePoolWithQuotaTag 0017f038 2 ExAllocatePoolWithTag 0017f040 3 ExCreateCallback 0017f048 4 ExFreePoolWithTag 0017f050 5 ExRegisterCallback 0017f058 6 ExReleaseFastMutex 0017f060 7 ExUnregisterCallback 0017f068 8 IoAllocateIrp 0017f070 9 IoAllocateMdl 0017f078 10 IoFreeIrp 0017f080 11 IoFreeMdl 0017f088 12 IoGetCurrentProcess 0017f090 13 IoGetInitialStack 0017f098 14 IoReuseIrp 0017f0a0 15 KdDebuggerEnabled 0017f0a8 16 KdRefreshDebuggerNotPresent 0017f0b0 17 KeAcquireSpinLockAtDpcLevel 0017f0b8 18 KeAcquireSpinLockRaiseToDpc 0017f0c0 19 KeBugCheckEx 0017f0c8 20 KeCancelTimer 0017f0d0 21 KeDelayExecutionThread 0017f0d8 22 KeGenericCallDpc 0017f0e0 23 KeGetCurrentProcessorNumberEx 0017f0e8 24 KeInitializeDpc 0017f0f0 25 KeInitializeEvent 0017f0f8 26 KeInitializeMutex 0017f100 27 KeInitializeTimer 0017f108 28 KeLowerIrql 0017f110 29 KeQueryActiveProcessorCountEx 0017f118 30 KeReleaseMutex 0017f120 31 KeReleaseSpinLock 0017f128 32 KeReleaseSpinLockFromDpcLevel 0017f130 33 KeRevertToUserAffinityThreadEx 0017f138 34 KeSetEvent 0017f140 35 KeSetSystemAffinityThreadEx 0017f148 36 KeSetTimer 0017f150 37 KeSignalCallDpcDone 0017f158 38 KeSignalCallDpcSynchronize 0017f160 39 KeStackAttachProcess 0017f168 40 KeUnstackDetachProcess 0017f170 41 KeWaitForSingleObject 0017f178 42 KfRaiseIrql 0017f180 43 MmBuildMdlForNonPagedPool 0017f188 44 MmGetPhysicalAddress 0017f190 45 MmGetSystemRoutineAddress 0017f198 46 MmGetVirtualForPhysical 0017f1a0 47 MmIsAddressValid 0017f1a8 48 MmMapIoSpace 0017f1b0 49 MmUnmapIoSpace 0017f1b8 50 ObOpenObjectByPointer 0017f1c0 51 ObReferenceObjectByHandle 0017f1c8 52 ObRegisterCallbacks 0017f1d0 53 ObUnRegisterCallbacks 0017f1d8 54 ObfDereferenceObject 0017f1e0 55 ObfReferenceObject 0017f1e8 56 PsCreateSystemThread 0017f1f0 57 PsGetCurrentProcessId 0017f1f8 58 PsGetCurrentThreadTeb 0017f200 59 PsGetProcessId 0017f208 60 PsGetThreadProcessId 0017f210 61 PsGetVersion 0017f218 62 PsLookupProcessByProcessId 0017f220 63 PsProcessType 0017f228 64 PsRemoveLoadImageNotifyRoutine 0017f230 65 PsSetLoadImageNotifyRoutine 0017f238 66 PsTerminateSystemThread 0017f240 67 PsThreadType 0017f248 68 RtlAnsiCharToUnicodeChar 0017f250 69 RtlAnsiStringToUnicodeString 0017f258 70 RtlCheckRegistryKey 0017f260 71 RtlCopyUnicodeString 0017f268 72 RtlFreeUnicodeString 0017f270 73 RtlGetVersion 0017f278 74 RtlInitAnsiString 0017f280 75 RtlInitUnicodeString 0017f288 76 RtlQueryRegistryValues 0017f290 77 RtlRandomEx 0017f298 78 RtlUnicodeToMultiByteN 0017f2a0 79 ZwClose 0017f2a8 80 ZwCreateFile 0017f2b0 81 ZwCreateKey 0017f2b8 82 ZwDeleteFile 0017f2c0 83 ZwDeleteKey 0017f2c8 84 ZwDeleteValueKey 0017f2d0 85 ZwDuplicateObject 0017f2d8 86 ZwLoadDriver 0017f2e0 87 ZwOpenFile 0017f2e8 88 ZwOpenProcess 0017f2f0 89 ZwQuerySystemInformation 0017f2f8 90 ZwQueryVirtualMemory 0017f300 91 ZwReadFile 0017f308 92 ZwSetValueKey 0017f310 93 ZwUnloadDriver 0017f318 94 ZwWriteFile 0017f320 95 __C_specific_handler 0017f328 96 __chkstk 0017f330 97 _purecall offset 00173844 wdfldr.sys Hint/Name Table: 0017F9B0 TimeDateStamp: 00000000 (Thu Jan 1 01:00:00 1970) ForwarderChain: 00000000 First thunk RVA: 0017F340 Thunk Ordn Name 0017f340 1 WdfVersionBindClass 0017f348 2 WdfVersionUnbind 0017f350 3 WdfVersionUnbindClass 0017f358 0 WdfVersionBind Done dumping drive_c/Program Files/Denuvo Anti-Cheat/denuvo-anti-cheat.sys --- snip --- When looking for interface/prototype definitions: Microsoft KMDF is open source. https://github.com/Microsoft/Windows-Driver-Frameworks https://github.com/microsoft/Windows-Driver-Frameworks/blob/master/src/fram… $ wine --version wine-5.8-173-g9e26bc8116 Regards -- 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 26

[Bug 53847] New: NfRemote: mouse input ignored
by WineHQ Bugzilla Sept. 7, 2026

Sept. 7, 2026

https://bugs.winehq.org/show_bug.cgi?id=53847 Bug ID: 53847 Summary: NfRemote: mouse input ignored Product: Wine Version: 7.0 Hardware: x86-64 OS: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: thelen(a)radiomankato.com https://www.telosalliance.com/uploads/Omnia%20Products/Software/NfRemote.exe Say hello to nfremote. It's a little piece of software used to administer a particular manufacturer's equipment, commonly used at radio and TV stations. I can confirm it has, and does, work fine under Wine 2.21 - just tested today on a MacBookPro8,1 running the official binaries (https://dl.winehq.org/wine-builds/macosx/pool/winehq-staging-2.21.pkg) under OS 10.13.6. Meanwhile, I have a new Mac (MacBookPro16,2 - Intel-based), on which I’ve deployed Wine 7.0 via homebrew under OS 12.6.1. There I can start nfremote just fine... but it ignores my mouse input. If I were to start it with the command-line argument "run", it presents me with a window where both keyboard and mouse input are accepted; there I can type in the text fields, so I know it's responsive. But when I hover the cursor over buttons, they do not 'light up’ to indicate such. And when I click, nothing happens. Even in years past, I found that newer versions of Wine exhibited the issue I describe below, so I simply never updated beyond 2.21. Wonder if this might be a long-undiscovered regression of some sort? -- 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 12

[Bug 54285] New: Mostly UE4 games failing to start when trying to use faudio by wine itself
by WineHQ Bugzilla Sept. 6, 2026

Sept. 6, 2026

https://bugs.winehq.org/show_bug.cgi?id=54285 Bug ID: 54285 Summary: Mostly UE4 games failing to start when trying to use faudio by wine itself Product: Wine Version: 7.0.1 Hardware: x86-64 OS: FreeBSD Status: UNCONFIRMED Severity: normal Priority: P2 Component: xaudio2 Assignee: wine-bugs(a)winehq.org Reporter: Alexander88207(a)Protonmail.com Created attachment 73852 --> https://bugs.winehq.org/attachment.cgi?id=73852 Sea of Thieves Hello, since the update to wine 7 it is not possible to run mostly Unreal Engine 4 games. In the log there were indications that something might be wrong with the xaudio 2_7 dll. So I just applied faudio via winetricks and the games work again. Unfortunately this is not a permanent solution as there is a bug on platforms like Mac OS, FreeBSD that if you use native,buildin xaudio the sound does not work correctly in terms of stuttering and slightly distorted sound. As far as I know the games worked correctly in Wine 6.0.1. Unfortunately it is not possible for me to test more in wine-devel because the port is very often defective and also just once again not working. (Last version tested was 7.21 and it was there too) Thanks in advance! -- 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 12

[Bug 56681] New: 3d games continue receiving mouse input while not focused
by WineHQ Bugzilla Sept. 6, 2026

Sept. 6, 2026

https://bugs.winehq.org/show_bug.cgi?id=56681 Bug ID: 56681 Summary: 3d games continue receiving mouse input while not focused Product: Wine Version: 9.8 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winewayland Assignee: wine-bugs(a)winehq.org Reporter: pmargeti34(a)gmail.com Distribution: --- Wine wayland windows seem to get the mouse input even if the application window is not focused. 3D game world continues to respond to mouse input as if the game still had focus. To reproduce: -launch a 3d game in wayland mode (warframe in my example) -open another application and make sure it has focus -observe that when the mouse cursor is over the game window, game still receives input -- 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 17

[Bug 57289] New: Performance degradation after LFH
by WineHQ Bugzilla Sept. 6, 2026

Sept. 6, 2026

https://bugs.winehq.org/show_bug.cgi?id=57289 Bug ID: 57289 Summary: Performance degradation after LFH Product: Wine Version: 9.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: rikul(a)inbox.ru Distribution: --- In one of my applications, there is a performance degradation in a specific scenario after LFH. I still can’t localize the problem to send you the block of code where the tool experiences performance issues. Are you aware of any known issues related to this? The main part of the degradation occurs in the LFH group release section. -- 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 60184] New: Keyboard activity where keys are sometimes ignored or appear to stick causing input repeat
by WineHQ Bugzilla Sept. 5, 2026

Sept. 5, 2026

http://bugs.winehq.org/show_bug.cgi?id=60184 Bug ID: 60184 Summary: Keyboard activity where keys are sometimes ignored or appear to stick causing input repeat Product: Wine Version: 11.15 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: hid Assignee: wine-bugs(a)list.winehq.org Reporter: flues.fault4b(a)icloud.com Target Milestone: --- Distribution: --- Created attachment 81859 --> http://bugs.winehq.org/attachment.cgi?id=81859 Console log, evtest, and journalctl during issue observation When running wine/steam apps, I notice buggy keyboard activity where keys are sometimes ignored or sticky. Confirmed Accessibility/sticky keys are disabled. Issue appears app agnostic as it appears even when running regedit and notepad. If key is pressed when reset event starts, system repeat rate issues keycode. If key is pressed before reset completes, no key event registers. Attempted wine 9.0, 11.0, 11.15. Issue persists. journalctl -kf shows event `kernel: usb 3-1: reset full-speed USB device number 2 using xhci_hcd` almost 1 per second while wine is active. Attached console output. WINEDEBUG=+hid,+rawinput Not change in output with or without debug options (also tried WINEDEBUG=+all) Device details at https://linux-hardware.org/?probe=b64b678cd7 symptomatic built-in keyboard is 0b05:19b6 ASUS N-KEY Device using usbhid. Currently on COSMIC, cannot disable sticky-keys/key repeat. This was recommended in some historic forums but should not be considered as solution. -- 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 18

[Bug 60255] New: ntdll: NtQuerySystemInformation(SystemPerformanceInformation) causes unhandled page fault (execute access to NULL) on native Win64 app
by WineHQ Bugzilla Sept. 5, 2026

Sept. 5, 2026

http://bugs.winehq.org/show_bug.cgi?id=60255 Bug ID: 60255 Summary: ntdll: NtQuerySystemInformation(SystemPerformanceInformation) causes unhandled page fault (execute access to NULL) on native Win64 app Product: Wine Version: 11.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: blocker Priority: P2 Component: ntdll Assignee: wine-bugs(a)list.winehq.org Reporter: atayksll(a)gmail.com Target Milestone: --- Distribution: --- # Summary Unhandled page fault (jump to NULL instruction pointer) immediately after `fixme:ntdll:NtQuerySystemInformation info_class SYSTEM_PERFORMANCE_INFORMATION`, reproducible with SpaceEngine (beta 0.990.48.2034) on startup. Same crash occurs across three different Wine-derived runtimes. # Environment - Distro: Fedora Linux (KDE Plasma 6, Wayland) - Kernel: 7.1.10-200.fc44.x86_64 - GPU: AMD Radeon RX 5600 XT (Navi 10), Mesa 26.1.6 (git-ffa422e53d), RADV/radeonsi, ACO - CPU: Intel Core i7-10700F (16 threads) - RAM: 32 GB - Wine builds tested (all produce the identical crash): - wine-experimental.bleeding.edge.11.0.411656.20260810 (TkG Plain) - Wine 11.0 stable - Proton (added SpaceEngine.exe as a non-Steam game) - Application: SpaceEngine beta 0.990.48.2034 (native Win64 build, not DXVK/vkd3d — game uses Wine's built-in OpenGL translation directly) # Reproduction steps 1. Install SpaceEngine (Win64 beta build) into a 64-bit Wine prefix. 2. Launch `SpaceEngine.exe` from its `system` folder. 3. The launcher/splash appears for under a second, then the process crashes with no dialog. # Observed behavior With `WINEDEBUG=+loaddll` the process log shows normal startup: all core DLLs load, `SpaceEngine.exe`, `SDL2.dll`, `openvr_api.dll`, etc. all load successfully as `native`, OpenGL context creation succeeds, and the game's own log (`se.log`, included below) shows OpenGL init, SDL init, and SDL_mixer init all completing normally before entering its hardware-detection ("INITIALIZING LOADER") step. The crash consistently happens at this exact point, right after: ``` 00ec:trace:loaddll:build_module Loaded L"C:\windows\system32\dinput8.dll" at 00006FFFFDB70000: builtin 015c:fixme:avrt:AvSetMmThreadCharacteristicsW (L"Pro Audio",...): stub 00ec:fixme:ntdll:NtQuerySystemInformation info_class SYSTEM_PERFORMANCE_INFORMATION wine: Unhandled page fault on execute access to 0000000000000000 at address 0000000000000000 (thread 00ec), starting debugger... ``` No further trace lines appear between the `fixme` line and the fault, which suggests the fault happens inside ntdll's own handling of this info class rather than after control returns to the application. Register dump (identical register values and stack contents reproduced across separate runs and separate Wine builds): ``` rip:0000000000000000 rsp:000000000010f8e8 rbp:0000000000000000 rax:0000000000000000 rbx:0000000000000000 rcx:0000000000000000 rdx:0000000000000000 rsi:ffffffffffffffff rdi:0000000000000004 r8:00000000ffffffff r9:0000000000000000 r11:0000000000000000 r12:0000000000001000 r13:0000000140d8f2a8 r14:0000000000000003 r15:0000000000000001 Backtrace: =>0 0000000000000000 (0000000000000000) 0000000000000000: -- no code accessible -- ``` `r13` (0000000140d8f2a8) consistently points to a fixed static offset inside `spaceengine.exe`'s own address space (module base 0000000140000000), the same value across every crash, on every Wine build tested — behavior is fully deterministic. # se.log excerpt (SpaceEngine's own log, up to the last line printed before crash) ``` INITIALIZING LOADER [MT] Number of CPUs: 16 [MT] Worker threads: 14 [MT] Total RAM: 31997 Mb [MT] Available RAM: 26908 Mb [MT] Max SE RAM: 8192 Mb ``` No further lines are ever written to se.log after this point — the crash happens before the next planned log line. # What has been ruled out - GPU/Vulkan driver stack: `vulkaninfo` runs cleanly and correctly identifies the RX 5600 XT via RADV. - `GL_ARB_bindless_texture`: hiding it via `MESA_EXTENSION_OVERRIDE=-GL_ARB_bindless_texture` had no effect on the crash (ruling out the known AMD bindless-texture driver bug class as the cause here). - `openvr_api.dll`: this is a hard load-time import of the executable; removing it just fails earlier with `STATUS_DLL_NOT_FOUND` rather than avoiding the real crash, so VR init isn't the trigger. - Wine build/runner choice: identical crash (same register values, same crash address) on wine-experimental TkG bleeding-edge, wine-11.0 stable, and Proton. # Question / request Is `SystemPerformanceInformation` handling in `ntdll`'s `NtQuerySystemInformation` known to be incomplete or buggy on x86-64 Linux hosts in a way that could produce this kind of null-pointer-execute fault rather than a clean error return? Happy to provide the full debug logs, `se.log`, or test further patches/builds if that would help narrow this down — this crash is 100% reproducible on this hardware. generated via claude. it did all the work finding this bug while trying to fix space engine for me. sorry. -- 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 54573] New: win64 bug: err:module:import_dll Library iconv.dll
by WineHQ Bugzilla Sept. 5, 2026

Sept. 5, 2026

https://bugs.winehq.org/show_bug.cgi?id=54573 Bug ID: 54573 Summary: win64 bug: err:module:import_dll Library iconv.dll Product: Wine-staging Version: 8.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: romulasry(a)protonmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Created attachment 74116 --> https://bugs.winehq.org/attachment.cgi?id=74116 wine pant.net logfile When I run: wine paint.net.5.0.2.install.anycpu.web.exe See attached log. -- 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 49

[Bug 56366] New: Worms Blast characters become grey/untextured
by WineHQ Bugzilla Sept. 4, 2026

Sept. 4, 2026

https://bugs.winehq.org/show_bug.cgi?id=56366 Bug ID: 56366 Summary: Worms Blast characters become grey/untextured Product: Wine Version: 9.3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: iodreamify(a)gmail.com Distribution: --- Created attachment 76106 --> https://bugs.winehq.org/attachment.cgi?id=76106 wine log If you play a game vs cpu, when 2 characters are on screen, one or both of them will become grey as if they're untextured. Sometimes it's the whole character and sometime only their weapon or boat. It doesn't seem to be tied to any action or event, they'll become grey and then rendered correctly again with color. Tested this with Wine 9.3 inside Wine Steam. Also, in puzzle mode, when there's a single player, it doesn't seem to happen as fast or at all. Steps to reproduce: 1. open game 2. choose game vs cpu 3. select deathmatch 4. swim around in game a bit Kernel Version: 6.7.5-arch1-1 (64-bit) mesa 24.0.1-1 Graphics Platform: X11 Graphics Processor: Mesa Intel® HD Graphics 3000 -- 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 32368] New: Bigrats: UI can't display normally
by wine-bugs＠winehq.org Sept. 4, 2026

Sept. 4, 2026

http://bugs.winehq.org/show_bug.cgi?id=32368 Bug #: 32368 Summary: Bigrats: UI can't display normally Product: Wine Version: 1.5.18 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: jactry92(a)gmail.com Classification: Unclassified Created attachment 42710 --> http://bugs.winehq.org/attachment.cgi?id=42710 The Log Bigrats is a video download tool. reproduce it follow this: 0. download and install it :http://download.flvcd.com/setup/bigrats_setup_0.4.7.2.exe ; 1. cd to path you installede it and 'wine commence.exe' to run it. my test evnoriment: - Kubuntu 12.10 32bit - wine-1.5.18-175-g0104496 - bigrats 0.4.7.2 md5sum bigrats_setup_0.4.7.2.exe 3ef9bc738d0f941cbdf085b5fd531f9a bigrats_setup_0.4.7.2.exe -- 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 11