http://bugs.winehq.org/show_bug.cgi?id=60051 Bug ID: 60051 Summary: Input queue delivers hardware messages with garbage message IDs (0, 3, 0xffffffff), application deadlocks ("not responding") — regression in 11.13 Product: Wine Version: 11.13 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: win32u Assignee: wine-bugs@list.winehq.org Reporter: ilkwon2@gmail.com Target Milestone: --- Distribution: --- Since upgrading wine-staging 11.12 → 11.13 (WineHQ Ubuntu repo), KakaoTalk (Windows messenger, version 26.6.0.5208, 32-bit, WINEARCH=win64 prefix) intermittently deadlocks a few minutes after startup. When it happens, the console/journal floods with: ``` 01b0:err:msg:process_hardware_message unknown message type ffffffff 0078:err:msg:process_hardware_message unknown message type 3 0024:err:msg:process_hardware_message unknown message type 0 ``` (thousands of occurrences within 2-3 minutes; the message ID value varies between runs: 0, 3, 0xffffffff — i.e. garbage), after which every thread of the process parks in futex waits (0% CPU) and the window stops responding to _NET_WM_PING. The corruption survives the app process: explorer.exe of the same prefix keeps logging the same error on every subsequent input event, and a relaunched app instance joining the same wine session hangs again immediately. Full recovery requires `wineserver -k`. **Trigger:** reproducibly correlated with opening a new window — in one captured case a chat window (richedit init + FlashWindowEx immediately before the flood), in another the built-in image viewer window. **Regression evidence:** systemd journal retention on this machine goes back to 2026-05-13. Grepping the whole journal for `process_hardware_message` yields ZERO hits from May 13 through July 22 (wine-staging 11.7 → 11.12, same KakaoTalk version since July 13, heavy daily use), and 28,792 hits on July 23 alone — the first day of real use after the 11.13 upgrade. 11.12 was in use for 16 days (2026-07-06 → 2026-07-22) without a single occurrence. Ruled out: KakaoTalkAdBlock (third-party window tool) — the hang reproduces with it completely absent from the process list. Possibly related: a MusicBee user reported the same signature ("err:msg:process_hardware_message unknown message type 0" flood + freeze) on 2026-07-20: https://discuss.cachyos.org/t/program-through-wine-freezing-or-closing-itsel... Note: the commits "win32u: Ignore empty mouse input in NtUserSendHardwareInput" (9329917d) and "server: Skip dispatching rawinput message when it is empty" (e01ecb4a) are already included in 11.13, so they do not cover this path. **Environment details:** - winehq-staging 11.13~noble-1 (dl.winehq.org/wine-builds/ubuntu) - X11 (Xorg) session, fcitx IME (XMODIFIERS=@im=fcitx), X11 Driver InputStyle=root, UseTakeFocus=N - USB serial adapters present (/dev/ttyUSB0-2 mapped to COM33-35) - WINE_VK_WAYLAND_DISABLE=1 -- 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.