https://bugs.winehq.org/show_bug.cgi?id=54063
Bug ID: 54063
Summary: msctf:inputprocessor sometimes gets an unexpected
OnSetFocus event in Windows & Wine
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: msctf
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
msctf:inputprocessor sometimes gets an unexpected OnSetFocus event in Windows &
Wine:
inputprocessor.c:2288: found {575F3783-70C8-47C8-AE5D-91A01A1F7592}
inputprocessor.c:549: Test failed: Unexpected ThreadMgrEventSink_OnSetFocus
sink
inputprocessor.c:1020: TextService_Deactivate
inputprocessor.c:1249: Disabling
See https://test.winehq.org/data/patterns.html#msctf:inputprocessor
This pretty rare. There are only 3 instances in about 6 months:
* 2022-06-17 on fgtb-debian11 (64-bit), in two runs
* 2022-11-30 on w7u-2qxl (32-bit)
--
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.
https://bugs.winehq.org/show_bug.cgi?id=54062
Bug ID: 54062
Summary: msctf:inputprocessor - test_AssociateFocus() sometimes
crashes in Wine
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: msctf
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
msctf:inputprocessor - test_AssociateFocus() sometimes crashes in Wine:
inputprocessor.c:2437: Test failed: Expected DocumentMgr not focused
Unhandled exception: page fault on read access to 0x00000000 in 32-bit code
(0x0040ae26).
[...useless backtrace...]
See https://test.winehq.org/data/patterns.html#msctf:inputprocessor
The earliest known instance occurred on 2022-07-04 on debian11-wow64. This
impacts both the 32- and 64-bit builds.
--
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.
https://bugs.winehq.org/show_bug.cgi?id=53252
Bug ID: 53252
Summary: d3d10core:d3d10core - test_occlusion_query() sometimes
fails on Windows 10 1909+
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
d3d10core:d3d10core - test_occlusion_query() sometimes fails on Windows 10
1909+:
d3d10core.c:4665: Test failed: Got unexpected query result 0x0000000000000000.
https://test.winehq.org/data/patterns.html#d3d10core:d3d10core
These failures only seem to happen on with Windows' basic 'VGA' driver (whether
it's on top of QEmu's VGA or QXL GPU).
They are also rare enough to cause false positives.
--
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.
https://bugs.winehq.org/show_bug.cgi?id=53465
Bug ID: 53465
Summary: conhost.exe:tty - test_tty_output() sometimes fails on
Windows 10
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: programs
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
conhost.exe:tty - test_tty_output() sometimes fails on Windows 10.
There are only three known failures spread across two similar failure modes:
* 2022-07-27 w10pro64-pt-BR
* 2022-07-27 w10pro64-mx-MX (mixed locale)
tty.c:1051: Test failed: avail = 3
tty.c:1051: Test failed: expected empty buffer, got "\x1b[m"
tty.c:1058: Test failed: 0: expected "\x1b[9;4H" got
"\x1b[30m\x1b[9;4H5\x1b[4;3H\x1b[?25h"
tty.c:1059: Test failed: 0: expected "5" got
"\x1b[30m\x1b[9;4H5\x1b[4;3H\x1b[?25h"
tty.c:1060: Test failed: 0: expected "\x1b[4;3H" got
"\x1b[30m\x1b[9;4H5\x1b[4;3H\x1b[?25h"
tty.c:1061: Test failed: 0: expected "\x1b[?25h" got
"\x1b[30m\x1b[9;4H5\x1b[4;3H\x1b[?25h"
tty.c:1062: Test failed: expected empty buffer, got
"\x1b[30m\x1b[9;4H5\x1b[4;3H\x1b[?25h"
* 2022-07-29 w10pro64-pt-BR
tty.c:1055: Test failed: expected hide cursor escape
tty.c:1057: Test failed: 0: expected "\x1b[30m" got
"\x1b[25l\x1b[30m\x1b[9;4H5\x1b[4;3H\x1b[?25h"
tty.c:1058: Test failed: 0: expected "\x1b[9;4H" got
"\x1b[25l\x1b[30m\x1b[9;4H5\x1b[4;3H\x1b[?25h"
tty.c:1059: Test failed: 0: expected "5" got
"\x1b[25l\x1b[30m\x1b[9;4H5\x1b[4;3H\x1b[?25h"
tty.c:1060: Test failed: 0: expected "\x1b[4;3H" got
"\x1b[25l\x1b[30m\x1b[9;4H5\x1b[4;3H\x1b[?25h"
tty.c:1061: Test failed: 0: expected "\x1b[?25h" got
"\x1b[25l\x1b[30m\x1b[9;4H5\x1b[4;3H\x1b[?25h"
tty.c:1062: Test failed: expected empty buffer, got
"\x1b[25l\x1b[30m\x1b[9;4H5\x1b[4;3H\x1b[?25h"
--
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.
https://bugs.winehq.org/show_bug.cgi?id=54059
Bug ID: 54059
Summary: user32:input - test_GetMouseMovePointsEx() sometimes
fails on Windows 10+
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: user32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
user32:input - test_GetMouseMovePointsEx() sometimes fails on Windows 10+:
input.c:1647: Test failed: expected to get 62 mouse move points but got 64
input.c:1649: Test failed: expected cursor position to be 30x30 but got 150 150
See https://test.winehq.org/data/patterns.html#user32:input
This impacts Windows 10 from 1809 to Windows 11 but it seems it can also happen
on Windows 7 (though in practice not on the TestBot VMs?).
--
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.
https://bugs.winehq.org/show_bug.cgi?id=53474
Bug ID: 53474
Summary: Change in memory handling gives crash in Framemaker 8
Product: Wine
Version: 7.14
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: kernel32
Assignee: wine-bugs(a)winehq.org
Reporter: ulrich.gemkow(a)ikr.uni-stuttgart.de
Distribution: ---
The following commit
commit a4966b6690b31c4884d07a8a745017adb6363834
Author: Rémi Bernon <rbernon(a)codeweavers.com>
Date: Thu Jun 9 14:13:53 2022 +0200
kernelbase: Cleanup and simplify (Global|Local)ReAlloc.
Signed-off-by: Rémi Bernon <rbernon(a)codeweavers.com>
dlls/kernel32/heap.c | 22 ++++++++-
dlls/kernel32/tests/heap.c | 15 -------
dlls/kernelbase/memory.c | 108 +++++++++++++++------------------------------
3 files changed, 56 insertions(+), 89 deletions(-)
leads to a crash in Framemaker 8. Reverting the patch on top of wine-7.14
solves the problem.
To reproduce (simplest way):
- Start Framemaker and create a new document
- Open the print dialog (Ctrl-P)
- Select another printer (lower part of the dialog)
- Framemaker crashes with an internal error
Framemaker generates a log file (which is IMHO useless but attached anyway)
I can provide a demo version of framemaker if this would help.
--
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.
https://bugs.winehq.org/show_bug.cgi?id=54006
Bug ID: 54006
Summary: d3d8:device - test_reset() sometimes crashes on
Windows 8+
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: d3d
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
d3d8:device - test_reset() sometimes crashes. There are a few failure modes
that look like they are related:
device.c:1967: Test failed: Failed to reset device, hr 0x88760873.
device.c:1967: this is the last test seen before the exception
163c:device: unhandled exception c0000005 at 74D3CC42
and
device.c:2022: Test failed: Reset failed, hr 0x88760873.
device.c:2024: Test failed: TestCooperativeLevel failed, hr 0x88760869.
device.c:2029: Test failed: GetBackBuffer failed, hr 0x8876086c.
device.c:2031: Test failed: Got hr 0.
device.c:2033: Test failed: Got hr 0.
device.c:2033: this is the last test seen before the exception
0b00:device: unhandled exception c0000005 at 0043032C
and
device.c:1747: Test failed: Reset failed, hr 0x88760873.
device.c:1749: Test failed: TestCooperativeLevel failed, hr 0x88760869.
device.c:1761: Test failed: D3DVIEWPORT->Width = 400.
device.c:1762: Test failed: D3DVIEWPORT->Height = 300.
device.c:1764: this is the last test seen before the exception
03c0:device: unhandled exception c0000005 at 743FA86E
and
device.c:1807: Test failed: Reset failed, hr 0x80070057.
device.c:1809: Test failed: TestCooperativeLevel failed, hr 0x88760869.
device.c:1835: Test failed: D3DVIEWPORT->Width = 500, expected 200.
device.c:1837: Test failed: D3DVIEWPORT->Height = 400, expected 150.
device.c:1840: this is the last test seen before the exception
09d8:device: unhandled exception c0000005 at 7448946E
See https://test.winehq.org/data/patterns.html#d3d8:device
Where:
0x88760873 == ???
0x88760869 == D3DERR_DEVICENOTRESET
0x80070057 == E_INVALIDARG
--
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.
https://bugs.winehq.org/show_bug.cgi?id=53685
Bug ID: 53685
Summary: ntdll:rtl is broken on Windows 10 1809+ in the GitLab
WineTest builds
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
ntdll:rtl is broken on Windows 10 1809+ in the GitLab WineTest builds:
rtl.c:2790: Running test 1 (compressed_size=10, uncompressed_size=8,
status=0x00000000)
rtl.c:2790: this is the last test seen before the exception
1538:rtl: unhandled exception c0000005 at 005532C0
https://test.winehq.org/data/patterns.html#ntdll:rtl
The failures started on 2022-07-26 which is when the WineTest builds switched
from the old build system to GitLab. A test with winetest-889fe64d9f2e.exe
(built on 2022-07-25) confirms that this test still succeeds when using
binaries from the old build system.
--
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.
https://bugs.winehq.org/show_bug.cgi?id=53663
Bug ID: 53663
Summary: Subnautica Below Zero permanently loses focus if the
active window changes
Product: Wine
Version: 7.17
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: achurch+wine(a)achurch.org
Distribution: ---
In the game Subnautica: Below Zero (version 45391), when playing in windowed
mode, if the game window loses focus, the game will no longer accept
mouse/keyboard input even after the window regains focus again. If the game is
set to pause when in the background, it remains paused even after the window
regains focus.
This bug also occurs with stable Wine (7.0), but it does not occur with Proton
7.0.4 (the game properly accepts input again and unpauses when the window
regains focus).
--
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.
https://bugs.winehq.org/show_bug.cgi?id=43812
Bug ID: 43812
Summary: Divinity Original Sin 2 some parts display white
ingame
Product: Wine-staging
Version: 2.17
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: holzminister(a)t-online.de
CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de,
sebastian(a)fds-team.de
Distribution: ---
Created attachment 59354
--> https://bugs.winehq.org/attachment.cgi?id=59354
log from terminal
I play Divinity Original Sin 2 with the workaround described in bug
https://bugs.winehq.org/show_bug.cgi?id=43660 ("winetricks xact"). With this
the game works quiet well. But there is one small but annoying bug for that
kinda game. When you try to read books or other papers you find ingame they
only show up white and empty. Also the buff icons of the unitframes are plain
white. (See screenshots).
--
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.