Same workaround as used in is_window_resizable, except it's on a different
code path. This also affects other WMs (e.g. Kwin, compiz).

Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=56149Signed-off-by: Gabriel Ivăncescu <gabrielopcode@gmail.com>

This reverts commit 790133e9.

It was incorrect, sorry about that. The issue was weirder in a different place (MWM_FUNC_RESIZE not set before setting fullscreen).

Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=56149

Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=56117

Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=54387

Signed-off-by: Nikolay Sivov <nsivov@codeweavers.com>

Signed-off-by: Nikolay Sivov <nsivov@codeweavers.com>

Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=56152

Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=56152

This is required to support systems with a larger XSAVE area.

`(BYTE *)dst_ex - (BYTE *)dst` is the size of the legacy context, but
`dst_ex->All` already contains the legacy context.  Therefore,
`context_length` has the legacy context size added *twice*.

This becomes a problem when `context_length` exceeds
`sizeof(src_context_buffer)`.  This confuses `check_changes_in_range()`,
causing out-of-bounds read and unpredictable test results.

The penultimate element of `ranges_x86` array has an incorrect value: it
should be *at least* 0x2f0, which is the minimum size of an extended
context.

Fix this by setting it to 0x440, which is the minimum size of an
extended context *with* CONTEXT_I386_XSTATE.  This is consistent with
`ranges_amd64`, the penultimate element of which has the minimum size of
an extended context *with* CONTEXT_AMD64_XSTATE.

Note that the incorrect value does not always lead to a test failure,
since check_changes_in_range_() effectively ignores range `start`s that
are not in order.  Reproducing the failure requires a system with a
sufficiently large XSAVE area; specifically, the following condition is
necessary for check_changes_in_range_() to pick up the wrong value:

    0x2cc < 0x294 + src_ex->XState.Length - sizeof(XSTATE).

Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=56134

Fixes: 5b60f464
Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=56113

Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=56130

These got obsolete with eaca0f44.
Signed-off-by: Bernhard Kölbl <bkoelbl@codeweavers.com>

Fixes: b2f13103
Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=55540

Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=56117

Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=56117

Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=56110

This mainly allows Wine to reset the tty settings upon
termination and not let gdb do it (cf bug report).

Change: user is now required to explicitely terminate gdb
('quit' command) upon debuggee termination.

Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=56032Signed-off-by: Eric Pouech <epouech@codeweavers.com>

So that ddraw isn't always loaded, esp. for app not requesting vmr7.
Could lower memory pressure on 32bit.
Signed-off-by: Eric Pouech <epouech@codeweavers.com>

Fixes a regression introduced by 7255f63a,
which effectively made the taskbar always visible even when virtual desktop
was supposed to be fullscreen.
Signed-off-by: Gabriel Ivăncescu <gabrielopcode@gmail.com>

Signed-off-by: Eric Pouech <epouech@codeweavers.com>

All paths are relative to the installation directory by default.

That variable is not used by the server.

DMUS_PMSG::dwType is the type of the message, but we are comparing it to
curve types. We should be using DMUS_CURVE_PMSG::bType instead.

F_GETPATH is currently only implemented on macOS.

Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=56047