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=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=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=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.
https://bugs.winehq.org/show_bug.cgi?id=47847
Bug ID: 47847
Summary: Disable Windows 10's "privacy wizard" after locale
change
Product: Wine-Testbot
Version: unspecified
Hardware: x86
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: unknown
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
The TestBot can automatically set up locale-specific live snapshots (after the
locale has been manually installed, see point 1 of bug 47804).
However on Windows 10 the mandatory reboot is sometimes followed by a wizard
asking a bunch of questions like whether to use audio speech recognition, what
kind of reports to send Microsoft, etc. I think this is the "Choose your
Privacy Settings" wizard. Of course that breaks the snapshot creation since the
TestBot cannot answer these questions, fails to detect they are even being
asked (because TestAgentd is already running in the background), and creates a
snapshot of the half-baked state.
So one question is: how can one prevent Windows from putting up this wizard?
But then, while I had this wizard for the French locale, I did not get it for
Arabic. Would it perchance only happen for European locales? If so the pain may
be bearable.
--
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=51411
Bug ID: 51411
Summary: Add a mixed locale Windows test configuration.
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 TestBot's locale test configurations usually have a matching set of locales
for SystemDefaultLCID, USystemPreferredUILanguages, UserDefaultUILanguage and
ThreadUILanguage. For instance for French we have:
SystemDefaultLCID 040c
UserDefaultLCID 0409
ThreadLocale 0409
SystemPreferredUILanguages 040C,0409
UserDefaultUILanguage 040c
ThreadUILanguage 040c
As a result tests can substitute GetSystemDefaultLCID() for
GetThreadUILanguage() and get away with it. In turn this allows Wine to
substitute these too without causing the tests to fail (see for instance
mlang:mlang, bug 51410).
To avoid this the TestBot needs a test configuration where all the important
locale settings are different so these issues are detected immediately.
--
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=51451
Bug ID: 51451
Summary: Many Windows 10 VMs are incompletely localized
Product: Wine-Testbot
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: unknown
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
The localized w10pro64* VMs don't have the right UserDefaultLCID and are
sometimes missing even more:
w10pro64 fr_FR
SystemDefaultLCID 040c
UserDefaultLCID 0409 <--- should be 040c
ThreadLocale 0409 ???
SystemPreferredUILanguages 040C,0409
UserDefaultUILanguage 040c
ThreadUILanguage 040c
w10pro64 ar_MA
SystemDefaultLCID 0c01
UserDefaultLCID 0409 <--- should be 0c01
ThreadLocale 0409 ???
SystemPreferredUILanguages 0409 <--- should contain 0c01
UserDefaultUILanguage 0409 <--- should be 0c01
ThreadUILanguage 0409 <--- should be 0c01
w10pro64 he_IL
UserDefaultLCID 0409 <--- should be 40d
w10pro64 hi_IN
Being a Unicode-only language means setting the system locale to Hindi was not
possible in older Windows versions (up to early Windows 10). Now it is but it's
considered Beta and uses the UTF-8 encoding in ANSI APIs. So it's not clear if
it should be changed (and how to do it programmatically).
SystemDefaultLCID 0409 <--- Unicode-only language
UserDefaultLCID 0409 <--- should be 0439
ThreadLocale 0409 ???
SystemPreferredUILanguages 0439,0409
UserDefaultUILanguage 0439
ThreadUILanguage 0439
w10pro64 ja_JP
UserDefaultLCID 0409 <--- should be 411
w10pro64 ko_KO
UserDefaultLCID 0409 <--- should be 412
w10pro64 pt_BR
UserDefaultLCID 0409 <--- should be 416
w10pro64 ru_RU
UserDefaultLCID 0409 <--- should be 419
w10pro64 zh_CN
UserDefaultLCID 0409 <--- should be 804
This prevents testing how Windows behaves when formatting and parsing their
currencies in oleaut32:varformat for instance.
Strangely enough the w7u* VMs don't have this issue:
w7u de_DE
SystemDefaultLCID 0407
UserDefaultLCID 0407
ThreadLocale 0407
SystemPreferredUILanguages 0407
UserDefaultUILanguage 0407
ThreadUILanguage 0407
--
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.
http://bugs.winehq.org/show_bug.cgi?id=12159
Summary: Alt-click moves the windows instead of giving access to
alternate functionalities in Photoshop Cs2
Product: Wine
Version: 0.9.58.
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P1
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: mariejoaile(a)gmail.com
Steps to reproduce:
1- Open Photoshop
2- Create a new document or open one
3- Pick a selection tool or clone or any of the tool making use of an alternate
function using alt
4- Try to use this alt-click option and instead of for instance for the select
tool, deselecting, it will move the window.
This action is very important because there is no other way to use certain of
Photoshop's tool, making tools like clone and healing useless.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
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.