https://bugs.winehq.org/show_bug.cgi?id=46024
Bug ID: 46024 Summary: Qt applications crash after call to WTOpen without tablet hardware attached Product: Wine Version: 3.13 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: wintab32 Assignee: wine-bugs@winehq.org Reporter: bernhardu@mailbox.org Distribution: ---
Was observed first in debian bug [1] with wine-3.13.
In my opinion WTInfo returns some uninitialized stack memory in LOGCONTEXTW. Qt does not look at the return value at all and calls then WTOpen, which puts some window messages near lcMsgBase into the message queue.
Most of the time this works as a random window message is just ignored. But under some circumstances an existing wine internal window message is hit, but that message needs parameters which are not given, therefore it is crashing.
This happens when there is no device attached that is usable via wintab32.dll.
RFC patches and discussion in [1],[2].
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905090 [2] https://www.winehq.org/pipermail/wine-devel/2018-September/132083.html [3] https://www.winehq.org/pipermail/wine-devel/2018-October/133775.html
https://bugs.winehq.org/show_bug.cgi?id=46024
Alex Henrie alexhenrie24@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Fixed by SHA1| |4e122bdaddf1a1c6d6211b5d7ce | |412b23a6efe57 CC| |alexhenrie24@gmail.com Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED
--- Comment #1 from Alex Henrie alexhenrie24@gmail.com --- Fixed by https://source.winehq.org/git/wine.git/commitdiff/4e122bdaddf1a1c6d6211b5d7c...
https://bugs.winehq.org/show_bug.cgi?id=46024
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #2 from Alexandre Julliard julliard@winehq.org --- Closing bugs fixed in 3.19.