https://bugs.winehq.org/show_bug.cgi?id=53485
Bug ID: 53485
Summary: Cursor is missing in Visio 2003 when editing text
Product: Wine
Version: 7.14
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: winebugs(a)copysoft.org
Distribution: ---
In Visio 2003 running under Wine 7.14 the text cursor is not displayed when
editing text.
How to reproduce:
Open visio, create a new document, select the text tool, type on the screen,
the cursor does not appear.
Text input is fine, text is rendered fine and can be selected, copied and
pasted, all that is missing is the cursor.
I've run a bisect and found that this commit appears to be responsible for the
regression:
commit b8732c80b112af388264ac84d726aad09d93c8c6
Author: Zebediah Figura <zfigura(a)codeweavers.com>
Date: Tue Apr 26 16:06:04 2022 +0100
win32u: Move caret APIs from user32.
Signed-off-by: Zebediah Figura <zfigura(a)codeweavers.com>
Signed-off-by: Jacek Caban <jacek(a)codeweavers.com>
Signed-off-by: Huw Davies <huw(a)codeweavers.com>
Signed-off-by: Alexandre Julliard <julliard(a)winehq.org>
--
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=53028
Bug ID: 53028
Summary: gamepad buttons stopped working correctly
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: piotr5(a)netscape.net
Distribution: ---
ever since upgrading to wine-7.0 my gamepad got reduced to having only 10
functioning buttons and just 5 axes are actually doing anything. I now
downgraded to wine-6.0.2 and it has all 14 buttons and 6 axes again. (actually
now there are 2 devices of the same name detected, both have 8 axes, the second
device is spreading the last 2 axes into being horizontal, while the first
correctly assigns a 2d-movement analogue to one axis and nothing to the other.
so I disabled the 2nd one.)
to be precise, "wine control.exe" has a program for testing my gamepad, and
there wine-7.0 is showing me only 10 buttons and 8 axes, of which only 5 are
moving. in some game I had assigned one of the missing keys to an action and
moving the axis which isn't perceived by wine sometimes triggers that missing
button -- cannot see anything like that in this test program.
I'm on gentoo linux, wine-vanilla is the only package providing wine there, and
stable versions are just 6.0.2 and 7.0. installing newer versions doesn't work
for me since it needs vulkan (winegcc aborts with function vkd3d_* not defined
errors in wined3d.spec) which I have not installed. is it worth upgrading, or
has that joystick bug not been fixed yet?
--
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=46500
Bug ID: 46500
Summary: Cogpack - Exercises can't be run - Error 380 - Invalid
property value
Product: Wine
Version: 4.0-rc6
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: maiktapwagner(a)aol.com
Distribution: ---
Created attachment 63348
--> https://bugs.winehq.org/attachment.cgi?id=63348
Console output on wine 4.0-rc6
Hello everyone,
the application in question can be downloaded from and also has a demo version
available which has the same "symptoms" as the full version:
http://www.markersoftware.com/USA/demoinfo.htm#Download
It returns an error message "invalid property value" with an error code of 380.
Console output is attached and an entry for the AppDB has been submitted as
well.
--
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=53980
Bug ID: 53980
Summary: httpapi:httpapi sometimes crashes testing overlapped
I/O with the v2 server in Wine
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: httpapi
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
httpapi:httpapi sometimes crashes testing overlapped I/O with the v2 server in
Wine:
httpapi.c:1539: Test marked todo: Got error 120.
Unhandled exception: page fault on write access to 0x00000000 in 32-bit code
(0x7b020c3f).
[...]
Backtrace:
=>0 0x7b020c3f GetOverlappedResultEx+0x9a(file=<couldn't compute location>,
overlapped=<couldn't compute location>, result=<couldn't compute location>,
timeout=<couldn't compute location>, alertable=<couldn't compute location>)
[Z:\home\winetest\tools\testbot\var\wine\dlls\kernelbase\file.c:3184] in
kernelbase (0x0062f0c8)
1 0x7b020d4a GetOverlappedResult+0x45(file=<couldn't compute location>,
overlapped=<couldn't compute location>, result=<couldn't compute location>,
wait=<couldn't compute location>)
[Z:\home\winetest\tools\testbot\var\wine\dlls\kernelbase\file.c:3144] in
kernelbase (0x0062f118)
2 0x703826c7 HttpReceiveHttpRequest+0x267(queue=<couldn't compute location>,
id=<couldn't compute location>, flags=<couldn't compute location>,
request=<couldn't compute location>, size=<couldn't compute location>,
ret_size=<couldn't compute location>, ovl=<couldn't compute location>)
[Z:\home\winetest\tools\testbot\var\wine\dlls\httpapi\httpapi_main.c:360] in
httpapi (0x0062f1b8)
3 0x0040f6d1 in httpapi_test (+0xf6d1) (0x0062fdb8)
See https://test.winehq.org/data/patterns.html#httpapi:httpapi
There are only four known instances of this crash, meaning it's pretty rare and
thus hard to reproduce:
* 2022-08-30 (fg-deb64-32) This is also the first known instance.
* 2022-11-14 (fg-deb64-32)
* 2022-11-16 (debian11-win32-de-DE)
* 2022-11-17 (debian11-win32) MR!1397
--
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=53977
Bug ID: 53977
Summary: amstream:amstream qedit:mediadet mf:transform
mfmediaengine:mfmediaengine quartz:filtergraph
winmm:mci wmp:media wmvcore:wmvcore mf:mf
mfplay:mfplay qasf:asfreader broken on Debian Testing
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: quartz
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
amstream:amstream qedit:mediadet mf:transform mfmediaengine:mfmediaengine
quartz:filtergraph winmm:mci wmp:media wmvcore:wmvcore mf:mf mfplay:mfplay
qasf:asfreader all have failures on Debian Testing.
The exact failures are not really important, see the corresponding entries on
the failure patterns page if more details are needed:
https://test.winehq.org/data/patterns.html
What's important is that the detection of gst/gst.h now fails on Debian
Testing, resulting in Wine being compiled without GStreamer support which is
what broke all the tests above:
configure:17099: gstreamer-1.0 gstreamer-video-1.0 gstreamer-audio-1.0 cflags:
configure:17100: gstreamer-1.0 gstreamer-video-1.0 gstreamer-audio-1.0 libs:
configure:17103: checking for gst/gst.h
configure:17103: gcc -m32 -c -g -O2 conftest.c >&5
conftest.c:174:10: fatal error: gst/gst.h: No such file or directory
174 | #include <gst/gst.h>
| ^~~~~~~~~~~
And this all started with the commit below, which means this issue is related
to bug 53953 but for Debian Testing instead of Fedora:
commit c7a97b5d5d56ef00a0061b75412c6e0e489fdc99 (HEAD, refs/bisect/bad)
Author: Zebediah Figura <zfigura(a)codeweavers.com>
Date: Thu Nov 17 19:32:39 2022 -0600
configure: Override PKG_CONFIG_LIBDIR instead of PKG_CONFIG_PATH for 32-bit
builds on 64-bit hosts.
This allows 32-bit packages to be found when the user has specified
PKG_CONFIG_PATH for some other reason.
This also mirrors the way e.g. i686-linux-gnu-pkg-config is implemented on
Debian, and possibly other distributions as well.
This also prevents 64-bit .pc files from being found. This was originally
intended as a benefit [1], but can contribute to misdetection of headers
which
are not actually multiarch (e.g. GStreamer, although at the time that [1]
was
written that was a preëxisting problem). In general a distribution which
provides .pc files for one architecture should be expected to provide them
for
any architecture that it actually provides libraries for; even if that was
not
true of Debian in 2017, it is now. I moreover assert it is better to fail
to
find a present library than to incorrectly find the wrong one.
Note that we can't easily use i686-linux-gnu-pkg-config, as would otherwise
be
preferable, for reasons also described in [1].
[1] https://www.winehq.org/pipermail/wine-devel/2017-June/118002.html
--
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=53744
Bug ID: 53744
Summary: WM_SETTEXT between ANSI programs treating LPARAM as
Unicode causing name corruption
Product: Wine
Version: 7.6
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: user32
Assignee: wine-bugs(a)winehq.org
Reporter: dark(a)darkok.xyz
Distribution: ---
When sending a WM_SETTEXT to and from a program expecting ANSI strings, it
seems to be interpreting the string as Unicode, causing the window title to
become corrupted.
Sending a wide string over then makes it work on Wine, but not Windows.
The issue was introduced in Wine 7.6, and still exists in the latest versions.
--
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=52564
Bug ID: 52564
Summary: dxgi:dxgi times out in
test_find_closest_matching_mode() on cw-gtx560
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
When run in Wine, dxgi:dxgi times out in test_find_closest_matching_mode() on
cw-gtx560:
$ WINETEST_NO_MT_D3D=1 WINETEST_TIME=1 ./wine dlls/dxgi/tests/dxgi_test.exe
dxgi
[...]
dxgi.c:1582:1.778 mode_count=130
dxgi.c:1585:1.778 i=0
dxgi.c:1585:2.452 i=1
dxgi.c:1585:3.123 i=2
dxgi.c:1585:3.867 i=3
dxgi.c:1585:4.806 i=4
dxgi.c:1585:5.929 i=5
dxgi.c:1585:7.061 i=6
dxgi.c:1585:8.187 i=7
dxgi.c:1585:9.332 i=8
dxgi.c:1585:10.542 i=9
[...]
dxgi.c:1656:139.600
[...]
0020:dxgi:188.618 12836 tests executed (203 marked as todo, 2 failures), 35
skipped.
https://test.winehq.org/data/patterns.html#dxgi:dxgi
The problem is that it slows down after the first few modes, taking 1060 ms on
average. And there are 130 modes to test so the test hits the 120 second limit.
This issue started with the commit below.
commit 1f2c3e8538b088f678a588121fc0bf7811336efc
Author: Jacek Caban <jacek(a)codeweavers.com>
Date: Wed Dec 1 16:02:43 2021 +0100
win32u: Move NtUserEnumDisplaySettings implementation from user32.
Signed-off-by: Jacek Caban <jacek(a)codeweavers.com>
Signed-off-by: Huw Davies <huw(a)codeweavers.com>
Signed-off-by: Alexandre Julliard <julliard(a)winehq.org>
Before that commit test_find_closest_matching_mode() was much faster.
dxgi.c:1582:1.558 mode_count=130
dxgi.c:1585:1.558 i=0
dxgi.c:1585:1.751 i=1
dxgi.c:1585:1.960 i=2
dxgi.c:1585:2.168 i=3
dxgi.c:1585:2.361 i=4
dxgi.c:1585:2.570 i=5
dxgi.c:1585:2.763 i=6
dxgi.c:1585:2.939 i=7
dxgi.c:1585:3.132 i=8
dxgi.c:1585:3.309 i=9
[...]
dxgi.c:1656:25.519
[...]
0020:dxgi:63.668 12835 tests executed (203 marked as todo, 2 failures), 35
skipped.
(184 ms on average)
Note: cw-rx460 does not have this issue because it has fewer modes to test
(20), and testing each mode is much faster too (28 ms on average).
--
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=50315
Bug ID: 50315
Summary: Silent Hill 2 failed to install -installshield
extraction error
Product: Wine
Version: 6.0-rc1
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: legluondunet(a)gmail.com
Distribution: ---
Created attachment 68897
--> https://bugs.winehq.org/attachment.cgi?id=68897
screenshot installshield error message
Hello,
with last wine version 6, Silent Hill 2 failed to install with an installshield
extraction error (cf screenshot joined).
This bug is new, I can not reproduce it with Wine 5.x
Nothing interesting in terminal log, only that lines:
010c:fixme:file:NtLockFile I/O completion on lock not implemented yet
Initial process has exited (return code: 0)
010c:err:ole:CoReleaseMarshalData StdMarshal ReleaseMarshalData failed with
error 0x8001011d
--
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=50043
Bug ID: 50043
Summary: Kholat from GOG does not launch anymore
Product: Wine
Version: 5.19
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: titan.costa(a)gmail.com
Distribution: ---
Created attachment 68493
--> https://bugs.winehq.org/attachment.cgi?id=68493
Message box
I get the attached message box instead.
This is a regression but I can't bisect as I the following errors with older
wine versions:
wine: could not find __wine_start_process in kernel32.dll, status c000007a
0024:err:environ:run_wineboot failed to start wineboot c000007a
--
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=54105
Bug ID: 54105
Summary: taskschd:scheduler fails on Windows 10 1607+
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: taskschd
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
taskschd:scheduler fails on Windows 10 1607+:
scheduler.c:786: Test failed: DeleteTask error 0x80070002
See https://test.winehq.org/data/patterns.html#taskschd:scheduler
This new failure is caused by the following commit:
commit 7acd3aa429f2d45d96f4699906dc81e47ebd9c13
Author: Sven Baars <sbaars(a)codeweavers.com>
Date: Wed Dec 7 17:19:48 2022 +0100
taskschd/tests: Fix a test failure on w1064v1507.
This failure was also detected by the TestBot in MR!1732 but it was merged
anyway.
--
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=54014
Bug ID: 54014
Summary: advapi32:security sometimes exits prematurely in Wine
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: advapi32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
advapi32:security sometimes exits prematurely in Wine:
security.c:5550: Test marked todo: expected execute access 0x120000, got
0xdeadbeef
advapi32:security:03a8 done (0) in 0s 6852B
What's missing here is the "tests executed..." summary line which typically
indicates some underlying library called "exit()". This is usually accompanied
with a warning message complaining about something being wrong but there is no
trace of such a message in the task log.
There are some strange aspects to this:
* There is no record of it ever happening in the nightly WineTest runs.
* But it impacted 9 merge requests so far:
2022-11-28 MR!1575
2022-11-29 MR!1595 MR!1583 MR!1594
2022-11-25 MR!1537
2022-11-16 MR!1379
2022-11-14 MR!1363 MR!1356
2022-11-13 MR!1315
When it happens the report shows 4 instances of the 5550 todo. Comparing that
to a successful run indicates the early exit happened between the end of
test_kernel_objects_security() and the start of test_CreateWellKnownSid().
Maybe a piece of good news: advapi32:security crashes with WINEDEBUG=heap.
However that crash happens in test_CreateDirectoryA() instead of the expected
place. So it may be an unrelated issue.
--
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=53571
Bug ID: 53571
Summary: PhotoshopCS2 Installer custom action page fault
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: msi
Assignee: wine-bugs(a)winehq.org
Reporter: winebugs(a)copysoft.org
Distribution: ---
While attempting to bisect something else on the Photoshop CS2 installer I've
noticed that this recent commit:
commit 0d0f2067f89545539ab3ae0ccd802239a2dce98e
Author: Jacek Caban <jacek(a)codeweavers.com>
Date: Sun Aug 14 23:24:04 2022 +0200
user32: Pass window name as UNICODE_STRING to NtUserCreateWindowEx.
Breaks the installer and makes it crash when selecting the file types to be
associated with Photoshop.
02dc:err:msi:__wine_msi_call_dll_function Custom action
(L"C:\\users\\username\\Temp\\msic328.tmp":"SelectFileAssoc") caused a page
fault: 0xc0000005
--
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=54032
Bug ID: 54032
Summary: user32:msg - test_broadcast() sometimes fails due to
ERROR_INVALID_PARAMETER on w7pro64
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:msg - test_broadcast() sometimes fails due to ERROR_INVALID_PARAMETER on
w7pro64:
msg.c:17400: Test failed: 5: message ffff, got 0, error 87
msg.c:17405: Test failed: 5,0: message ffff, got 0, error 87
msg.c:17405: Test failed: 5,1: message ffff, got 0, error 87
msg.c:17405: Test failed: 5,2: message ffff, got 0, error 87
msg.c:17405: Test failed: 5,3: message ffff, got 0, error 87
msg.c:17405: Test failed: 5,8: message ffff, got 0, error 87
msg.c:17405: Test failed: 5,9: message ffff, got 0, error 87
msg.c:17405: Test failed: 5,10: message ffff, got 0, error 87
msg.c:17405: Test failed: 5,11: message ffff, got 0, error 87
msg.c:17405: Test failed: 5,12: message ffff, got 0, error 87
See https://test.winehq.org/data/patterns.html#user32:msg
Notes:
* This is specific to w7pro64 and happens roughly twice a month.
* The first known instance dates back to 2022-08-17 and there was none in the 2
months prior.
* The w7pro64 snapshot dates back to 2021-08-23.
So the conclusion is that something changed in Wine back in August that causes
these failures. Since the logs show no change to that test in that timeframe
(the next day does not count), it must be caused by a change in another test
:-(
--
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=54193
Bug ID: 54193
Summary: dinput:force_feedback - test_windows_gaming_input()
sometimes fails in Wine
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: dinput
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
dinput:force_feedback - test_windows_gaming_input() sometimes fails in Wine.
For instance:
* 2022-12-20 on debian11-win32-he-IL (6 failures)
force_feedback.c:5932: Test failed: got status 0
force_feedback.c:5932: Test marked todo: got error 0
force_feedback.c:5932: Test marked todo: GetResults returned 0x8000000e
force_feedback.c:5937: Test failed: handler not invoked
force_feedback.c:5938: Test failed: got async 00000000
force_feedback.c:5939: Test failed: got status 0
force_feedback.c:5945: Test failed: got status 2
force_feedback.c:5945: Test marked todo: got error 0
force_feedback.c:5945: Test marked todo: GetResults returned 0x8000000e
force_feedback.c:4703: iface 006C9128, async 019BEEE8, status 4
force_feedback.c:4703: iface 006C9128, async 019C39C8, status 1
force_feedback.c:4705: Test failed: invoked twice
force_feedback.c:4703: iface 006C9128, async 019C39C8, status 4
* 2022-11-24 fgtb-debian11-wow64 (3 failures)
force_feedback.c:5839: Test failed: got status 0
force_feedback.c:5839: Test marked todo: got error 0
force_feedback.c:5839: Test marked todo: GetResults returned 0x8000000e
force_feedback.c:5844: Test failed: handler not invoked
force_feedback.c:4615: iface 00000000006C8EB0, async 0000000001D77D50, status
3
force_feedback.c:5845: Test failed: got async 0000000000000000
force_feedback.c:5852: Test marked todo: got error 0x8007001e
force_feedback.c:5852: Test marked todo: GetResults returned 0x8007001e
* 2022-11-01 debiant-wow64 (1 failure)
force_feedback.c:5776: Test marked todo: get_SupportedAxes returned
0x80004001
force_feedback.c:5778: Test marked todo: got axes 0xdeadbeef
force_feedback.c:5796: Test failed: got status 0
See https://test.winehq.org/data/patterns.html#dinput:force_feedback
The oldest known instance dates back to 2022-09-01 (same 6 failures as above)
and there has only been a total of 5 instances to date (in the nightly WineTest
runs). So these failures are probably caused by a change some time in August.
--
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=40250
Bug ID: 40250
Summary: Stunt GP too fast timer for stunts, waterfall/screen
animation and starting screens
Product: Wine
Version: 1.9.4
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: trivial
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: 10mkudela(a)gmail.com
Distribution: ---
In the game time frame required to press Shift key to make stunt is much
smaller then in Windows. Also waterfall animation and loading screens are much
faster then in Windows. Everything else is at the same speed.
One additional animation is faster as well: speed of the text on screen in
Germany location is faster as well, but it's speed is changing from what I have
noticed.
There is probably a timer somewhere that is ticking faster then it should be,
and that is used by all those elements.
This bug was tested on 1.9.4 version of Wine, but it is also present on older
versions.
--
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=53716
Bug ID: 53716
Summary: Warlords 3: Darklords Rising: opening dialog window
has messed up colors
Product: Wine
Version: 7.14
Hardware: x86-64
URL: https://www.fileplanet.com/archive/p-27637/Warlords-II
I-Darklords-Rising-Demo
OS: Linux
Status: NEW
Keywords: download, regression
Severity: minor
Priority: P2
Component: win32u
Assignee: wine-bugs(a)winehq.org
Reporter: gyebro69(a)gmail.com
CC: jacek(a)codeweavers.com
Regression SHA1: 47dd8a6a9b1193ec1656cdf04117b94a3cf07025
Distribution: ---
Created attachment 73147
--> https://bugs.winehq.org/attachment.cgi?id=73147
Before -> after image
This was tested with GOG.com version of the game but can also be reproduced
with the original demo version.
When you start the game the opening dialog (where you select game mode/screen
resolution) has strange colors.
The demo uses a 16-bit installer which is currently affected by bug #53646.
Winver needs to be Win95/98.
This is a regression from Wine-7.14, caused by
commit 47dd8a6a9b1193ec1656cdf04117b94a3cf07025
Author: Jacek Caban <jacek(a)codeweavers.com>
Date: Sun Jul 10 16:15:10 2022 +0200
win32u: Use syscall interface for more user painting functions.
Nothing obvious is visible in the terminal output.
Darkdemo.zip (20M)
md5sum: 30f5908552d720e8b5361e0656772da8
wine-7.17-224-g52a83ffe4ef
--
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=53256
Bug ID: 53256
Summary: user32:win - test_window_from_point() and
test_mouse_input() sometimes fail on Windows 10 2009+
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_from_point() and test_mouse_input() sometimes fail on
Windows 10 2009+:
win.c:10238: Test failed: button under static window didn't get WM_LBUTTONUP
02fc:win: 10 tests executed (0 marked as todo, 1 failure), 0 skipped.
...
win.c:4549: Test failed: hwnd 00000000009C02AE/00000000009C02AE message 0204
win.c:4554: Test failed: hwnd 00000000009C02AE/00000000009C02AE message 0205
win.c:4559: Test failed: hwnd 00000000009C02AE/00000000009C02AE message 0206
win.c:4564: Test failed: hwnd 00000000009C02AE/00000000009C02AE message 0205
win.c:4580: Test failed: hwnd 00000000007902D6/00000000007902D6 message 0204
win.c:4584: Test failed: hwnd 00000000007902D6/00000000007902D6 message 0205
win.c:4593: Test failed: hwnd 00000000009C02AE/00000000009C02AE message 0204
win.c:4596: Test failed: hwnd 00000000009C02AE/00000000009C02AE message 0205
win.c:4629: Test failed: hwnd 00000000005C0340/00000000005C0340 message 00a4
win.c:4635: Test failed: hwnd 00000000005C0340/00000000005C0340 message 00a5
win.c:4642: Test failed: hwnd 00000000005C0340/00000000005C0340 message 0206
win.c:4644: Test failed: wparam 2
win.c:4655: Test failed: hwnd 00000000005C0340/00000000005C0340 message 0205
https://test.winehq.org/data/patterns.html#user32:win
Where:
* 204 == WM_RBUTTONDOWN
* 205 == WM_RBUTTONUP
* 206 == WM_RBUTTONDBLCLK
Although they seem unrelated, the test_window_from_point() failure and the set
of 13 test_mouse_input() failures always happen together which means they
probably have a common cause.
Also these failures are usually rare but can be almost systematic at times, for
instance from 2022-04-25 to 2022-05-30 on w1064 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=54188
Bug ID: 54188
Summary: user32:win - test_GetMessagePos() sometimes gets an
unexpected position 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_GetMessagePos() sometimes gets an unexpected position on
Windows and Wine:
win.c:10841: Test failed: pos = 00e700d0
win.c:10845: Test failed: pos = 00e700d0
win.c:10849: Test failed: pos = 00e700d0
or
win.c:10841: Test failed: pos = 00e600d0
win.c:10845: Test failed: pos = 00e600d0
win.c:10849: Test failed: pos = 00e600d0
See https://test.winehq.org/data/patterns.html#user32:win
This happens most frequently on Windows 7 but also happens on Windows 10 21H2
and 22H2.
--
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=53986
Bug ID: 53986
Summary: wininet:http - test_concurrent_header_access()
sometimes fails on Windows 7 & 8
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: wininet
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
wininet:http - test_concurrent_header_access() sometimes fails on Windows 7 &
8:
http.c:7825: Test failed: HttpQueryInfoA failed 6
See https://test.winehq.org/data/patterns.html#wininet:http
This is an old failure going back to at least 2022-06-07 and the failure rate
is below 2% so it is going to be hard to reproduce.
--
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=54042
Bug ID: 54042
Summary: wmvcore:wmvcore - test_sync_reader_types() sometimes
gets an NS_E_INCOMPATIBLE_FORMAT error 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 gets an
NS_E_INCOMPATIBLE_FORMAT error in Wine:
wmvcore.c:1521: Test marked todo: Stream 0: Got output number 0.
wmvcore.c:1579: Test failed: Stream 0: Got hr 0xc00d0041.
wmvcore.c:1586: Test marked todo: Stream 0: Got hr 0.
See https://test.winehq.org/data/patterns.html#wmvcore:wmvcore
This failure first happened on 2022-09-27, there are no record of it in the
previous 4 months, and it has happened about every other week since. So it is
probably caused by a change in Wine that occurred in September.
--
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=54187
Bug ID: 54187
Summary: dxgi:dxgi - test_swapchain_parameters() sometimes gets
access denied errors 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
dxgi:dxgi - test_swapchain_parameters() sometimes gets access denied errors on
Windows 8:
dxgi.c:4487: Test failed: Got unexpected hr 0x80070005, test 10.
dxgi.c:4487: Test failed: Got unexpected hr 0x80070005, test 11.
dxgi.c:4487: Test failed: Got unexpected hr 0x80070005, test 20.
dxgi.c:4487: Test failed: Got unexpected hr 0x80070005, test 33.
dxgi.c:4487: Test failed: Got unexpected hr 0x80070005, test 34.
dxgi.c:4487: Test failed: Got unexpected hr 0x80070005, test 43.
See https://test.winehq.org/data/patterns.html#dxgi:dxgi
Where 0x80070005 == E_ACCESSDENIED
This always happens with the same set of 6 tests.
This happened once on w8adm (2022-11-29) but usually happens on w864 (4
instances) where the test runs with elevated privileges.
--
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=42384
Bug ID: 42384
Summary: WinOmega 10.00.24 attempts to use certmgr.msc
Product: Wine
Version: 2.1
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: enhancement
Priority: P2
Component: crypt32
Assignee: wine-bugs(a)winehq.org
Reporter: info(a)winomega.com
Distribution: ---
Created attachment 57179
--> https://bugs.winehq.org/attachment.cgi?id=57179
certmgr.msc error
WinOmega 10.00.24
(https://appdb.winehq.org/objectManager.php?sClass=version&iId=33538) is yields
an error (see screenshot) when attempting to manage certificates through:
Facturación -> Clientes -> Firmar -> Factura-e
The program relies on certmgr.msc (MMC snap-in) for certificate management. A
possible workaround could be to use certmgr.exe (Certificate Manager Tool) in
its stead. However certmgr.exe isn't usable due to bug 42383
(https://bugs.winehq.org/show_bug.cgi?id=42383).
--
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=51588
Bug ID: 51588
Summary: MS Visio 2016 not work
Product: Wine
Version: 6.0.1
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: mettalhunter(a)yahoo.com.ar
Distribution: ---
Created attachment 70436
--> https://bugs.winehq.org/attachment.cgi?id=70436
cosole output
Hi!
I installed MS Visio 2016 but it does not start, not show Windows, nothing.
I used Gentoo Linux with Wine-6.0 and Wine-6.14.
I installed: riched20, riched30, mfc40, mfc42, msxml6, msxml3, vcrun (2008
until 2017), msftedit.
What is the issues?
--
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=54179
Bug ID: 54179
Summary: Maximized windows are not maximized with built-in
decorations
Product: Wine
Version: 8.0-rc1
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: aros(a)gmx.com
Distribution: ---
Created attachment 73705
--> https://bugs.winehq.org/attachment.cgi?id=73705
Maximized notepad
Steps to reproduce:
1) winecfg -> Graphics -> uncheck "Allow the window manager to decorate the
windows"
2) Run [wine] notepad
3) Maximize it
Results:
You can still resize the window as the mouse cursor changes to double-arrows at
the borders of the screen.
Expected results:
The window is indeed maximized and cannot be resized unless you
restore/unmaximize it.
--
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=50298
Bug ID: 50298
Summary: w1064v1909 shows the "create a Windows account"
fullscreen dialog
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: ---
Created attachment 68868
--> https://bugs.winehq.org/attachment.cgi?id=68868
w1064v1909 "Let's finish setting up your device" dialog
w1064v1909 corresponds to the 1909-live snapshot of the w1064 VM. That snapshot
is created automatically by the TestBot. Currently this snapshot opens on the
"create a Windows account" fullscreen dialog, the one with the following title:
Let's finish setting up your device
It seems this dialog 'pops up' automatically on boot if one does not provide a
Microsoft account when installing Windows. When that happens is hard to
predict, Windows seems to wait a few days or reboots before doing.
Furthermore something WineTest does seems to make this dialog go away because
it's not visible in the final WineTest screenshot. However it is visible if one
runs a single test such as ntdll:exception.
It's not entirely clear if this dialog is interfering with some tests but its
presence is definitely unwanted.
--
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.