https://bugs.winehq.org/show_bug.cgi?id=37640
Bug ID: 37640
Summary: Opening Windroy and it crashes.
Product: Wine
Version: 1.6.2
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: fholiveira1(a)hotmail.com
Distribution: ---
Created attachment 50094
--> https://bugs.winehq.org/attachment.cgi?id=50094
Extract from Wine report of bug.
I was trying to open Windroy and it crashes. The system open a bug report,
attached.
--
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=54508
Bug ID: 54508
Summary: psapi:psapi_main - The 64-bit
test_EnumProcessModulesEx() gets unexpected snapshot
counts on Windows 7 and 11
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: psapi
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
psapi:psapi_main - The 64-bit test_EnumProcessModulesEx() gets unexpected
snapshot counts on Windows 7 and 11:
w7pro64:
psapi_main.c:483: Test failed: pcs-6432: Wrong count 23 in C:\Windows\SysWOW64
psapi_main.c:488: Test failed: pcs-6432: Wrong count 2 in C:\Windows\system32
w11pro64:
psapi_main.c:488: Test failed: pcs-6432: Wrong count 0 in C:\Windows\system32
See https://test.winehq.org/data/patterns.html#psapi:psapi_main
These failures don't happen on Windows 8 to Windows 10!
These tests and failures were introduced in the following commit:
commit e38455a2181ab5ce0bf842f2c9a638b3ee9b538c
Author: Eric Pouech <eric.pouech(a)gmail.com>
AuthorDate: Tue Feb 14 11:06:57 2023 +0100
psapi/tests: Test directory of enumerated loaded modules.
Showing that Wine incorrectly reports, for a Wow64 process, the system
DLLs from within the wow64 directory while they should be from system32.
Signed-off-by: Eric Pouech <eric.pouech(a)gmail.com>
--
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=54662
Bug ID: 54662
Summary: The winscard tests are not run on the TestBot Wine VMs
Product: Wine-Testbot
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: unknown
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
The winscard tests are not run on the TestBot Wine VMs:
winscard missing
See the newtb-debian11-*, newtb-debian11b-* and newtb-debiant-* Linux results
on:
http://winetest.dolphin/data/tests/winscard:winscard.html
The reason is that the VMs are missing the libpcsclite libraries and maybe
other infrastructure needed to actually run the tests: if one just installs the
libraries the tests immediately get an SCARD_E_NO_SERVICE error and bail out:
can't establish context, make sure pcscd is running
--
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=54658
Bug ID: 54658
Summary: gdi32:driver -
test_D3DKMTCheckVidPnExclusiveOwnership() sometimes
fails due to occlusion error on Windows 8
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: gdi32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
gdi32:driver - test_D3DKMTCheckVidPnExclusiveOwnership() sometimes fails due to
INVALID_VIDEO_PRESENT_SOURCE error on Windows 8:
driver.c:461: Test failed: Got unexpected return code 0xc01e0006 at test 0.
driver.c:461: Test failed: Got unexpected return code 0xc01e0006 at test 1.
driver.c:461: Test failed: Got unexpected return code 0xc01e0006 at test 2.
[... same for tests 3 -> 58 ...]
driver.c:461: Test failed: Got unexpected return code 0xc01e0006 at test 59.
driver.c:481: Test failed: Got unexpected return code 0xc01e0304.
driver.c:505: Test failed: Got unexpected return code 0xc01e0006.
driver.c:556: Test failed: Got unexpected return code 0xc01e0006 at test 0.
[... same for tests 1 -> 16 ...]
driver.c:523: Test failed: Got unexpected return code 0xc01e0304 at test 17.
[... more code 0xc01e0304 errors ...]
driver.c:754: Test failed: Got unexpected return code 0xc01e0304.
driver.c:766: Test failed: Got unexpected return code 0.
[... more code 0 errors ...]
driver.c:785: Test failed: Got unexpected return code 0.
driver.c:807: Test failed: Got unexpected return code 0xc01e0006.
See https://test.winehq.org/data/patterns.html#gdi32:driver
Where:
0xc01e0006 == STATUS_GRAPHICS_PRESENT_OCCLUDED
0xc01e0304 == STATUS_GRAPHICS_INVALID_VIDEO_PRESENT_SOURCE
The oldest known instance was on 2023-12-09 and there has been about one per
month since:
* 2022-12-09 on w864 64-bit
* 2023-02-06 on w864 64-bit
* 2023-03-09 on w864 64-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=54476
Bug ID: 54476
Summary: Sims 3 Crash at launch
Product: Wine
Version: 8.1
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: pardisetm(a)gmail.com
Distribution: ---
Created attachment 74028
--> https://bugs.winehq.org/attachment.cgi?id=74028
screenshot of error dialog (in french, translated in description)
When launching the sims 3, it crash and display an error:
"impossible to start the game"
"Initialization of service (0x0175d824) failed"
--
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=54654
Bug ID: 54654
Summary: urlmon:protocol - The "http protocol from urlmon" test
sometimes gets unexpected BSCF_FIRSTDATANOTIFICATION
on Windows
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: urlmon
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
urlmon:protocol - The "http protocol from urlmon" test sometimes gets
unexpected BSCF_FIRSTDATANOTIFICATION on Windows:
protocol.c:3557: Testing http protocol (not from urlmon)...
protocol.c:1122: Test failed: grcfBSCF = 00000001
protocol.c:3561: Testing http protocol (from urlmon)...
See https://test.winehq.org/data/patterns.html#urlmon:protocol
Where:
00000001 == BSCF_FIRSTDATANOTIFICATION
This happens a bit over once per month on average but with sometimes month-wide
gaps. This also impacts all Windows versions, from Windows 7 to Windows 11.
--
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=54081
Bug ID: 54081
Summary: urlmon:protocol - The "http protocol direct read test"
sometimes causes a timeout in Wine
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: urlmon
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
urlmon:protocol - The "http protocol direct read" test sometimes causes a
timeout in Wine:
protocol.c:3576: Testing http protocol (direct read)...
protocol.c:1083: Test failed: unexpected call ReportData2
protocol.c:1085: Test failed: grfBSCF = 00000001
protocol.c:1093: Test failed: Read returned: 00000000, expected E_FALSE
protocol.c:1094: Test failed: read = 14096
protocol.c:693: Test failed: expected ReportData
protocol.c:3438: Test failed: wait timed out
protocol.c:3439: Test failed: expected Switch
protocol.c:348: Test failed: unexpected call OnResponse
protocol.c:839: Test failed: unexpected call ReportProgress_MIMETYPEAVAILABLE
protocol.c:1083: Test failed: unexpected call ReportData2
protocol.c:1085: Test failed: grfBSCF = 00000002
protocol.c:1093: Test failed: Read returned: 00000000, expected E_FALSE
protocol.c:1094: Test failed: read = 14096
protocol.c:693: Test failed: expected ReportData
urlmon:protocol:06f4 done (258) in 120s
See https://test.winehq.org/data/patterns.html#urlmon:protocol
This always happens in "Testing http protocol (direct read)...", never in the
https or "from urlmon" variants.
The first known instance happened on 2022-08-05 on debiant-wow32 (there was no
such failure in the previous 2 months) and the nightly WineTest runs have had
about one failure per month since.
--
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=54652
Bug ID: 54652
Summary: urlmon:url - The "http protocol direct read test"
sometimes get an unexpected ref count on Windows
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: urlmon
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
urlmon:url - The "http protocol direct read test" sometimes get an unexpected
ref count on Windows:
protocol.c:3576: Testing http protocol (direct read)...
protocol.c:3525: Test failed: ref=3
protocol.c:3580: Testing http protocol (redirected)...
See https://test.winehq.org/data/patterns.html#urlmon:protocol
With only 5 instances over the past 8 months this is pretty rare but may be
getting more frequent:
* 2022-08-08 on w8adm 32-bit
* 2022-08-11 on w8adm 32-bit
* 2023-01-09 on w10pro64-hi-u8 64-bit
* 2023-01-13 on w10pro64-ko 64-bit
* 2023-03-06 on w864 32-bit
Like many other refcount tests:
* Is this a race condition? Could it be some windows thread holding references
to the object?
* Is this test really needed?
--
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=54651
Bug ID: 54651
Summary: user32:input - test_rawinput() sometimes gets
unexpected (RIM|WM)_INPUT messages 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:input - test_rawinput() sometimes gets unexpected (RIM|WM)_INPUT
messages on Windows:
input.c:2921: Test failed: 6: unexpected WM_INPUT message
input.c:2924: Test failed: 6: unexpected RIM_INPUT message
See https://test.winehq.org/data/patterns.html#user32:input
This happened on w11pro64 back in October but that was with test 12 and I think
it stopped when I fixed disabling Windows update.
More recently it started happening on Windows 10:
* 2023-03-08 on w10pro64-ja 64-bit
* 2023-03-08 on w10pro64-zh-CN 64-bit
* 2023-03-06 on MR2334 w10pro64_ja & w10pro64_zh_CN
See also bug 53205 and bug 54437 where the test 15 is missing these messages.
--
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.