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.
https://bugs.winehq.org/show_bug.cgi?id=53955
Bug ID: 53955
Summary: Fractal Mapper stopped working after wine upgrade
Product: Wine
Version: 7.20
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: msxml3
Assignee: wine-bugs(a)winehq.org
Reporter: goeran(a)uddeborg.se
Distribution: ---
After upgrading wine on my Fedora 37 system Fractal Mapper no longer works. The
output ends withe a couple of error messages.
010c:err:module:find_forwarded_export module not found for forward
'msxml3.DllGetClassObject' used by L"C:\\windows\\system32\\msxml.dll"
010c:err:ole:apartment_add_dll couldn't find function DllGetClassObject in
L"C:\\windows\\system32\\msxml.dll"
010c:err:ole:create_server class {2933bf90-7b36-11d2-b20e-00c04f983e60} not
registered
010c:err:ole:com_get_class_object no class object
{2933bf90-7b36-11d2-b20e-00c04f983e60} could be created for context 0x5
010c:err:seh:NtRaiseException Exception frame is not in stack limits => unable
to dispatch exception.
The can be reproduced with the trial version from
https://www.nbos.com/nox/item/144. Run like this
- wine fm8trial.exe
- cd $WINEPREFIX/drive_c/Program\ Files\ \(x86\)/nbos
- wine Mapper8.exe
To get Fractal Mapper fully working with wine I have previously documented some
steps in the appdb. This new problem appears regardless if you do those extra
steps or not however.
There have been several upgrades of wine in Fedora, I don't know exactly at
which upgrade this broke.
--
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=53510
Bug ID: 53510
Summary: ntoskrnl.exe:ntoskrnl sometimes fails on Windows 7 and
8
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: ntoskrnl
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
ntoskrnl.exe:ntoskrnl sometimes fails on Windows 7 and 8:
driver.c:2478: Test failed: Got control flags 0x4.
driver.c:2495: Test failed: Got control flags 0x4.
driver.c:1758: Test failed: Got control flags 0x4.
driver.c:1769: Test failed: Got control flags 0x4.
https://test.winehq.org/data/patterns.html#ntoskrnl.exe:ntoskrnl
This set of four errors is usually repeated 3 times but sometimes has different
flags:
driver.c:2478: Test failed: Got control flags 0x8.
or
driver.c:2478: Test failed: Got control flags 0x4e.
or
driver.c:2478: Test failed: Got control flags 0x82.
--
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=53250
Bug ID: 53250
Summary: ole32:compobj - test_CoGetClassObject() sometimes
fails on Windows 7 and 8
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: ole32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
ole32:compobj - test_CoGetClassObject() sometimes fails on Windows 7 and 8:
compobj.c:831: Test failed: Section not found.
compobj.c:841: Test failed: Unexpected return value.
compobj.c:850: Test failed: Unexpected return value.
compobj.c:856: Test failed: Unexpected module name L"testlib.dll".
https://test.winehq.org/data/patterns.html#ole32:compobj
The failures are 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=53222
Bug ID: 53222
Summary: shell32:shlfolder - test_SHChangeNotify() gets
unexpected WM_USER_NOTIFY messages on Windows 10
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: shell32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
shell32:shlfolder - test_SHChangeNotify() gets unexpected WM_USER_NOTIFY
messages on Windows 10. The exact failures vary a bit though:
shlfolder.c:5027: SHChangeNotify tests (0)
...
shlfolder.c:5014: RMDIR: took 2 tries
shlfolder.c:4964: verifying pidls for: RMDIR
shlfolder.c:4977: Test failed: Didn't expect a WM_USER_NOTIFY message (event:
10)
or
shlfolder.c:4978: SHChangeNotify tests (0)
shlfolder.c:4915: verifying pidls for: MKDIR
shlfolder.c:4928: Test failed: Didn't expect a WM_USER_NOTIFY message (event:
40000)
or
shlfolder.c:5027: SHChangeNotify tests (0)
shlfolder.c:4964: verifying pidls for: MKDIR
shlfolder.c:5014: MKDIR: took 2 tries
shlfolder.c:4964: verifying pidls for: MKDIR
shlfolder.c:4977: Test failed: Didn't expect a WM_USER_NOTIFY message (event:
8)
or
shlfolder.c:4978: SHChangeNotify tests (1)
...
shlfolder.c:4965: CREATE: took 0 tries
shlfolder.c:4915: verifying pidls for: RMDIR
shlfolder.c:4928: Test failed: Didn't expect a WM_USER_NOTIFY message (event:
3)
or
shlfolder.c:5014: CREATE: took 3 tries
shlfolder.c:4960: Test failed: CREATE: expected notification type 2, got: 40000
shlfolder.c:4964: verifying pidls for: CREATE
shlfolder.c:4967: Test failed: GetDisplayNameOf failed: 0x80070057
shlfolder.c:4977: Test failed: Didn't expect a WM_USER_NOTIFY message (event:
3)
https://test.winehq.org/data/patterns.html#shell32:shlfolder
The failures have been seen on Windows 10 1507, 21H1 and 21H2 but it is likely
that the other Windows 10 versions behave the same way.
--
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=41784
Bug ID: 41784
Summary: Wine error under LinuxMint 17.3 after running PDF24
Creator
Product: Wine
Version: unspecified
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: marialvez(a)gmail.com
Distribution: ---
Created attachment 56219
--> https://bugs.winehq.org/attachment.cgi?id=56219
Using the PDF24 Creator program, in Wine mode and after close the application,
my Pc show these bug.- Y work with Linux Mint 17.3 Cinnamon 64-bit Version
2.8.8
Using the PDF24 Creator program, in Wine mode and after close the application,
my Pc show these bug.- Y work with Linux Mint 17.3 Cinnamon 64-bit Version
2.8.8
--
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=52930
Bug ID: 52930
Summary: d3dcompiler_47:hlsl_d3d9 fails randomly on Windows
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: directx-d3d-util
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Created attachment 72305
--> https://bugs.winehq.org/attachment.cgi?id=72305
Small patch to apply on top of 58d20aae3772^ to get failures
d3dcompiler_47:hlsl_d3d9 fails randomly on Windows 8.1 to 21H2:
hlsl_d3d9.c:1691: Test failed: Got unexpected hr 0x88760b59.
hlsl_d3d9.c:1692: Test failed: Got unexpected blob.
hlsl_d3d9.c:1693: Test failed: Got unexpected errors.
https://test.winehq.org/data/patterns.html#d3dcompiler_47:hlsl_d3d9
A bisect against Windows 10 21H1 on cw-gtx560 shows that the failures started
with the commit below:
commit 58d20aae3772473a90e43ee236b793f0421eecb1
Author: Eric Pouech <eric.pouech(a)gmail.com>
Date: Tue Feb 8 19:48:44 2022 +0100
d3dcompiler/tests: Build without -DWINE_NO_LONG_TYPES.
Signed-off-by: Eric Pouech <eric.pouech(a)gmail.com>
Signed-off-by: Henri Verbeet <hverbeet(a)codeweavers.com>
Signed-off-by: Alexandre Julliard <julliard(a)winehq.org>
The patch does not actually make any change that should matter but I have
confirmed the bisect result manually:
58d20aae3772^ -> 200 consecutive runs with no failure
58d20aae3772 -> fails after 9 to 33 runs
- Applying just the Makefile.in parts and last 4 chunks of hlsl_d3d9.c of that
commit is sufficient to get the failures.
- Patching only the makefiles is not enough.
- I did not try to identify which of the 4 chunks are needed to get failures.
They all patch code that's executed after the failure anyway.
So there must be some memory corruption that's sensitive to memory layout or
some subtle issue with the generated code.
I also if(0)ed-out all the other test_xxx() functions, and also if(0)ed-out the
tests that preceded the failing one in test_include() but I still get the
failure so it's not a case where an ill-advised NULL-behavior test causes
memory corruption.
--
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=53978
Bug ID: 53978
Summary: d3dx9_*, d3dx10_* and d3dx11_* dlls missing on some
TestBot VMs
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 d3dx9_*, d3dx10_* and d3dx11_* dlls are missing on some TestBot VMs.
Specifically:
* w7pro64
Only runs the 64-bit tests which report that these dlls are missing (plus
atl100, atl110 and d3d8). w7u runs the 32-bit tests and, surprisingly, does not
report any of these dlls to be missing. Adding the missing dlls on w7pro64
probably is not worth it.
* w1064v1507 missing the 32- and 64-bit dlls
Not worth adding them.
* w10pro64v2004 missing the 32- and 64-bit dlls
Not worth adding them.
* w11pro64 32- and 64-bit dlls
-> Add them.
w11pro64_nv actually had a couple of these before I fixed the Windows Update
issue. It seems that they got installed for the NVIDIA GUI and did not get
installed when I rebuilt the VM with just the NVIDIA driver.
* fgtb-w10pro64-64 missing the 32- and 64-bit dlls
Not a TestBot VM but add them 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.