https://bugs.winehq.org/show_bug.cgi?id=54021
Bug ID: 54021
Summary: Microsoft Report Builder: crashes on startup
Product: Wine
Version: 7.22
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: mohd.akram(a)outlook.com
Distribution: ---
Created attachment 73590
--> https://bugs.winehq.org/attachment.cgi?id=73590
log of running `wine MSReportBuilder.exe`
I get a System.NullReferenceException exception when running Microsoft Report
Builder (log attached). It is free to download from
https://www.microsoft.com/en-us/download/details.aspx?id=53613.
--
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=54044
Bug ID: 54044
Summary: quartz:memallocator - test_sample_properties() often
gets an unexpected sample start on Windows 11
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: quartz
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
quartz:memallocator - test_sample_properties() often gets an unexpected sample
start on Windows 11:
memallocator.c:476: Test failed: Got sample start 7dd8e0.
memallocator.c:643: Test failed: Got sample start 7dd8e0.
See https://test.winehq.org/data/patterns.html#quartz:memallocator
--
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=54041
Bug ID: 54041
Summary: wmvcore:wmvcore - test_sync_reader_types() sometimes
crashes in Wine
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: wmp&wmvcore
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
wmvcore:wmvcore - test_sync_reader_types() sometimes crashes in Wine:
wmvcore.c:1511: Test marked todo: Stream 0: Got output number 0.
wmvcore.c:1576: Test marked todo: Stream 0: Got hr 0.
wmvcore.c:1666: Test marked todo: Stream 0: Format 0: Got hr 0xc00d0041.
wmvcore.c:1666: Test marked todo: Stream 0: Format 1: Got hr 0xc00d0041.
wmvcore.c:1666: Test marked todo: Stream 0: Format 2: Got hr 0xc00d0041.
wmvcore.c:1617: Test failed: Stream 0: Format 3: Got hr 0x8007000e.
Unhandled exception: page fault on read access to 0x00000000 in 32-bit code
(0x00410d09).
[...useless backtrace...]
See https://test.winehq.org/data/patterns.html#wmvcore:wmvcore
Where:
0xc00d0041 == NS_E_INCOMPATIBLE_FORMAT
0x8007000e == E_OUTOFMEMORY
There are only three known instances of this crash:
* 2022-11-10 on debian11-win32-zh-CN
This is the first known instance which means it never happened in the
previous 5.5 months.
* 2022-11-14 on debian11-win32 for MR!1350
* 2022-11-29 on latestmaster (Linux Mint 21, en-GB)
So this may be caused by a Wine patch that got committed some time in late
October or early November.
--
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=54039
Bug ID: 54039
Summary: wmvcore:wmvcore - test_async_reader_streaming()
sometimes times out in Wine
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: wmp&wmvcore
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
wmvcore:wmvcore - test_async_reader_streaming() sometimes times out in Wine:
wmvcore.c:3009: Test failed: Wait timed out.
See https://test.winehq.org/data/patterns.html#wmvcore:wmvcore
Note that the wait on that line is just 1 second. Maybe the processing got
delayed a bit and increasing the timeout would be a reasonable fix?
The first instance of this failure is on 2022-09-16 and there has been about 3
instances per month since; and none in the 3 preceding months.
Also the TestBot started running two VMs per host around 2022-10-25 (and
certainly after 2022-10-02). So any processing delay cannot be attributed to
this TestBot configuration change.
So this may be related to Wine / test changes (like 453b0a92dbe4 which changes
test_async_reader_streaming() 3 days before the first failure).
--
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=54038
Bug ID: 54038
Summary: user32:win - test_window_info() sometimes gets an
unexpected window status on Windows
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:win - test_window_info() sometimes gets an unexpected window status on
Windows:
win.c:1237: Test failed: wrong dwWindowStatus: 0000 != 0001 active 004A021A fg
00010122 in hook HCBT_MINMAX
See https://test.winehq.org/data/patterns.html#user32:win
This happens mostly on w7u-* and w11pro64-amd but also happened once on
fgtb-w10pro64.
--
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=54001
Bug ID: 54001
Summary: user32:win - test_mdi() sometimes fails on Windows 8
and Windows 10 1607
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:win - test_mdi() sometimes fails on Windows 8 and Windows 10 1607:
win.c:2688: Test failed: style 0x200000: expected !100
win.c:2688: Test failed: style 0x300000: expected !100
See https://test.winehq.org/data/patterns.html#user32:win
More precisely:
* This failure mode happened systematically on w1064v1607 from 2022-08-24 to
2022-11-17 but there is no record of it ever happening outside that range.
* The w1064v1607 snapshot has been updated on 2022-11-20. While that may seem
to rule out the snapshot update as the cause for the change in behavior it is
possible that the successful 2022-11-18 results were (backlogged and) run on
the new 2022-11-20 snapshot.
* It's not clear what could have happened on 2022-08-24 to cause the failure to
start happening.
* This failure mode also happened on the w864 VM on the following dates:
- 2022-06-03 w864-64 (twice)
- 2022-11-18 w8adm (32-bit)
- 2022-11-22 w8adm (32-bit)
- 2022-11-23 w8adm (32-bit) and w864-32
The w864 snapshot was last updated on 2022-06-06.
Because these failures are rare on Windows 8 they have caused some TestBot
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=54022
Bug ID: 54022
Summary: d3d11:d3d11 -
test_clear_buffer_unordered_access_view() fails on
w11pro64_nv
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
d3d11:d3d11 - test_clear_buffer_unordered_access_view() fails on w11pro64_nv:
d3d11.c:16655: Test failed: Got 0xffffffff, expected 0xfefefefe or 0x80808080
at 128, uvec4 0xfefefefe, 0xfefefefe, 0xfefefefe, 0xfefefefe.
d3d11.c:16655: Test failed: Got 0xffffffff, expected 0xfefefefe or 0x80808080
at 128, uvec4 0xfefefefe, 0xfefefefe, 0xfefefefe, 0xfefefefe.
d3d11.c:16655: Test failed: Got 0xffffffff, expected 0xfefefefe or 0x80808080
at 128, uvec4 0xfefefefe, 0xfefefefe, 0xfefefefe, 0xfefefefe.
d3d11.c:16655: Test failed: Got 0xffffffff, expected 0xfefefefe or 0x80808080
at 128, uvec4 0xfefefefe, 0xfefefefe, 0xfefefefe, 0xfefefefe.
d3d11.c:16655: Test failed: Got 0xffffffff, expected 0xfefefefe or 0x80808080
at 128, uvec4 0xfefefefe, 0xfefefefe, 0xfefefefe, 0xfefefefe.
d3d11.c:16655: Test failed: Got 0xffffffff, expected 0xfefefefe or 0x80808080
at 128, uvec4 0xfefefefe, 0xfefefefe, 0xfefefefe, 0xfefefefe.
d3d11.c:16655: Test failed: Got 0xffffffff, expected 0xfefefefe or 0x80808080
at 128, uvec4 0xfefefefe, 0xfefefefe, 0xfefefefe, 0xfefefefe.
...
d3d11.c:16646: Test failed: Got 0xffffffff, expected 0x7f7e7d7c or 0x80808080
at 128, uvec4 0xffffff7c, 0xffffff7d, 0xffffff7e, 0xffffff7f.
d3d11.c:16647: Test failed: Got 0xffffffff, expected 0x7f7e7d7c or 0x80808080
at 128, uvec4 0xffffff7c, 0xffffff7d, 0xffffff7e, 0xffffff7f.
d3d11.c:16648: Test failed: Got 0xffffffff, expected 0x7f7e7d7c or 0x80808080
at 128, uvec4 0xffffff7c, 0xffffff7d, 0xffffff7e, 0xffffff7f.
d3d11.c:16653: Test failed: Got 0xffffffff, expected 0x7f7e7d7c or 0x80808080
at 128, uvec4 0xffffff7c, 0xffffff7d, 0xffffff7e, 0xffffff7f.
d3d11.c:16654: Test failed: Got 0xffffffff, expected 0x7f7e7d7c or 0x80808080
at 128, uvec4 0xffffff7c, 0xffffff7d, 0xffffff7e, 0xffffff7f.
d3d11.c:16655: Test failed: Got 0xffffffff, expected 0xfefefefe or 0x80808080
at 128, uvec4 0xfefefefe, 0xfefefefe, 0xfefefefe, 0xfefefefe.
See https://test.winehq.org/data/patterns.html#d3d11:d3d11
Note: w11pro64_nv is the TestBot's NVIDIA RTX3050 PCI passthrough Windows 11
21H2 VM. The plain QXL (QEmu), and AMD PCI passthrough test configurations have
d3d11:d3d11 failures too but in other test functions.
--
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=54036
Bug ID: 54036
Summary: user32:msg - test_paint_messages() sometimes gets an
invalid WM_NCPAINT wParam in Wine (GitLab CI)
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: user32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
user32:msg - test_paint_messages() sometimes gets an invalid WM_NCPAINT wParam
in Wine:
msg.c:8472: Test failed: InvalidateErase: 0: in msg 0x0085 expecting wParam 0x1
got 0x52040090
msg.c:8497: Test failed: InvalidateErase: 0: in msg 0x0085 expecting wParam 0x1
got 0x270400a1
msg.c:8527: Test failed: InvalidateErase: 0: in msg 0x0085 expecting wParam 0x1
got 0x58040096
msg.c:8540: Test failed: InvalidateErase: 0: in msg 0x0085 expecting wParam 0x1
got 0x3304009d
msg.c:8554: Test failed: InvalidateErase: 0: in msg 0x0085 expecting wParam 0x1
got 0x6f040090
Where 0x85 == WM_NCPAINT
See https://test.winehq.org/data/patterns.html#user32:msg
Strangely enough this only happens in the GitLab CI Wine environment. As such
it has impacted multiple MRs (e.g. MR!1342 MR!1341 MR!1326).
This is also very similar to bug 53129 except that:
* Bug 53129 has extra "region" test failures that don't happen here.
* The places where the failures occur in test_paint_messages() seem a bit
different.
* This only happens in Wine whereas bug 53129 only happens on Windows 7.
--
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=54029
Bug ID: 54029
Summary: PDF-XChange Editor - Error [System]: Call not
implemented
Product: Wine
Version: 7.0
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: klasse(a)partyheld.de
Distribution: ---
Created attachment 73597
--> https://bugs.winehq.org/attachment.cgi?id=73597
Screenshot of the error message
Upon closing of the PDF-XChange Editor, the attached error message appears.
When the PDF-XChange Editor is started from the terminal,
"010c:err:ole:CoUninitialize Mismatched CoUninitialize" appears upon closure of
the Editor as follows:
joe@PC:~$ env WINEPREFIX="/home/joe/.wine" wine-stable
C:\\PROG\~FBU\\TRAC\~EK1\\PDF_\~VHK\\PDFXEdit.exe
010c:err:ole:CoUninitialize Mismatched CoUninitialize
joe@PC:~$
Other than that, PDF-XChange Editor appears to work normally. (Only a brief
trial was done.)
The default Ubuntu Mate 22.10 installation of Wine is used:
wine-7.0 (Ubuntu 7.0~repack-8)
PDF-XChange Editor:
Version: 9.5, build 365.0 [ ]
(Nov 28 2022; 16:25:46)
The issue did not appear with the previous Ubuntu Mate version (22.04) and the
previously used PDF-XChange Editor version 9.5, build 361.0.
--
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.