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.
https://bugs.winehq.org/show_bug.cgi?id=54158
Bug ID: 54158
Summary: Windows Update is not quite idle in w1064v1709
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
Windows Update is not quite idle in w1064v1709.
It takes a while for it to actually start so it's not obvious right after boot.
Also the network connection is metered so it should not be downloading stuff.
But I think it already had some updates downloaded and ready to install before
the snapshot was taken so that after a while it just proceeds to install them
which breaks some tests.
See also bug 53227.
--
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=54176
Bug ID: 54176
Summary: Vegas pro 16
Product: Wine
Version: 7.22
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: bochtabochta(a)gmail.com
Distribution: ---
Created attachment 73699
--> https://bugs.winehq.org/attachment.cgi?id=73699
BackTrace of crash
Vegas pro 16 crashes at launch when loading i/o file manager
--
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=54129
Bug ID: 54129
Summary: Disable Internet time synchronization in all Windows
configurations
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
Created attachment 73660
--> https://bugs.winehq.org/attachment.cgi?id=73660
kernel32:process: Dump the Internet time synchronization config if passed
w32time.
Internet time synchronization is suspected to be responsible for sending
WM_TIMECHANGE messages which break some tests (see bug 53273, bug 53516, bug
54128). The TestBot has code to disable Internet time synchronization but this
requires a snapshot update.
The following test configurations have Internet time synchronization enabled:
w7u* -> Service start = 0x3 Manual + Type = NTP
w7pro64 -> Service start = 0x3 Manual + Type = NTP
w8* -> Service start = 0x3 Manual + Type = NTP
w864* -> Service start = 0x3 Manual + Type = NTP
w1064v2009 -> Service start = 0x2 Automatic (Delayed) + Type = NoSync
w10pro64v2004 -> Service start = 0x3 Manual + Type = NTP
w10pro64* -> Service start = 0x2 Automatic (Delayed) + Type = NTP
w1164_amd -> Service start = 0x2 Automatic (Delayed) + Type = NoSync
Those that have Type = NoSync are probably okay. They look like partially
failed attempts at disabling time synchronization, or cases where something
tried to re-enable time synchronization.
These are okay:
w1064* -> Service start = 0x4 Disabled + Type = NoSync
w1164 -> Service start = 0x4 Disabled + Type = NoSync
w1164_nv -> Service start = 0x4 Disabled + Type = NoSync
--
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=54160
Bug ID: 54160
Summary: REGRESSION : Drive Usage shows empty CDRom drive with
free space from the last HDD
Product: Wine
Version: unspecified
Hardware: x86-64
OS: other
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: msi
Assignee: wine-bugs(a)winehq.org
Reporter: contact(a)kcsoftwares.com
Created attachment 73684
--> https://bugs.winehq.org/attachment.cgi?id=73684
screenshot
Drive Usage shows empty CDRom drive with free space from the last HDD
Only if CDRom drive is EMPTY
REGRESSION : dlls/msi/dialog.c is faulty because :
- change made to msi_dialog_vcl_add_drives now using GetVolumeInformationW and
flag compared to FILE_READ_ONLY_VOLUME does not work as previous implementation
- GetDiskFreeSpaceExW result is not checked and if failing (eg : empty CDRom
drive) the content of "free" is used (containing last valid data, eg last HDD)
Detected in https://jira.reactos.org/browse/CORE-18758
--
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=54165
Bug ID: 54165
Summary: Tomb Raider Custom Level - Tibetan Winter crashes with
Software Rendering (Backtrace)
Product: Wine
Version: 8.0-rc1
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: maiktapwagner(a)aol.com
Distribution: ---
Created attachment 73690
--> https://bugs.winehq.org/attachment.cgi?id=73690
Backtrace 8.0-rc1 (Slackware 15.0)
Hello everyone,
I am running a patched version of 8.0-rc1 with one specific patch that stems
from
https://bugs.winehq.org/show_bug.cgi?id=54093
but no other patches have been applied.
Download-URL and console output will be provided shortly in its specific field
but here is my checksum for the time being.
sha256sum MrXY-TibetanWinterRemake.zip
3e40a65d05737723efcc614198f83ab871247936fc8d6ff432cf9a208e2a1622
MrXY-TibetanWinterRemake.zip
--
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=54162
Bug ID: 54162
Summary: Unable to read pdf using pdf24
Product: Wine
Version: 8.0-rc1
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: rpc
Assignee: wine-bugs(a)winehq.org
Reporter: tjw123hh(a)outlook.com
Distribution: ---
Created attachment 73687
--> https://bugs.winehq.org/attachment.cgi?id=73687
backtrance
Serious problem opening file with pdf reader in pdf24
However, the pdf creator still works
--
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=54163
Bug ID: 54163
Summary: Unable to open pdf24 toolbox
Product: Wine
Version: 8.0-rc1
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: tjw123hh(a)outlook.com
Distribution: ---
When I tried to open the pdf24 toolbox, it got stuck in the loading screenÂ
(Loading animation moves for a while and then stops)
--
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=54161
Bug ID: 54161
Summary: quartz:filtergraph sometimes times out in Wine
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: ---
quartz:filtergraph sometimes times out in Wine.
In MR!1820 the timeout happened on exit (debian11-win32):
...
filtergraph.c:5567: Test marked todo: Got param2 0xdeadbeef.
0d70:filtergraph: 7291 tests executed (81 marked as todo, 0 as flaky, 0
failures), 0 skipped.
quartz:filtergraph:0d70 done (258) in 120s 5680B
In the nightly WineTest runs filtergraph timeouts only happen on my desktop and
my Debian 11 VM; maybe because they usually see more other CPU activity.
See https://test.winehq.org/data/patterns.html#quartz:filtergraph
The nightly results show only 7 instances in 6 months where filtergraph timed
out on exit as above (e.g. 2022-09-27 fgtb-debian1-wow32).
It is a lot more common for it to timeout on startup: 17 instances over 6
months. For instance on 2022-11-22 fgtb-debian11-wow32:
filtergraph.c:616: running L"test.avi"
quartz:filtergraph:0424 done (258) in 120s 40B
Given that filtergraph normally runs in about 10 seconds it seems unlikely that
this is just a case of the test running a little bit too slow.
--
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=54152
Bug ID: 54152
Summary: mshtml:misc sometimes times out in Wine
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: mshtml
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
mshtml:misc sometimes times out on exit in Wine. Sometimes the timeout happens
on exit:
0a50:misc: 244 tests executed (0 marked as todo, 0 as flaky, 0 failures), 0
skipped.
mshtml:misc:0a50 done (258) in 120s 86B
and sometimes before in which case there is no trace:
mshtml:misc:04c0 done (258) in 120s 0B
See https://test.winehq.org/data/patterns.html#mshtml:misc
The first timeout happened on 2022-11-10 but there is only a bit over 1 per
month. Also the GitLab CI seems to be more prone to getting those.
There is also one case where the test got a failure instead:
misc.c:257: Test failed: key failed 80004005
0a4c:misc: 244 tests executed (0 marked as todo, 0 as flaky, 1 failure), 0
skipped.
mshtml:misc:0a4c done (1) in 0s 131B
256 hres = IHTMLStorage_key(storage, -1, &key);
257 ok(hres == E_INVALIDARG, "key failed %08lx\n", hres);
Where:
0x80004005 == E_FAIL
0x80070057 == E_INVALIDARG
Hopefully that failure is related and the timeout is caused by either
HTMLStorage_key() going into an infinite loop or corrupting the memory.
--
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=54047
Bug ID: 54047
Summary: wiaservc:wia sometimes crashes on Windows 11
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: wia
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
wiaservc:wia sometimes crashes on Windows 11:
0d78:wia: unhandled exception c0000005 at 00007FFE62E43777
See https://test.winehq.org/data/patterns.html#wiaservc:wia
This failure is pretty rare and since there is no trace or backtrace whatsoever
it's unclear where the crash occurs.
Note: On Windows 10 21H1+ it times out instead of crashing (see bug 54046).
These two issues may well be related (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=54154
Bug ID: 54154
Summary: winmm:midi sometimes crashes on exit in Wine
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: winmm&mci
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
winmm:midi sometimes crashes on exit in Wine:
0494:midi: 445 tests executed (4 marked as todo, 0 as flaky, 0 failures), 0
skipped.
winmm:midi:0494 done (-1073741819) in 7s 5788B
See https://test.winehq.org/data/patterns.html#winmm:midi
Where -1073741819 == 0xc0000005
The pid of the test summary line matches the one printed by the WineTest
executable which means this is the summary line of the main process. That means
the crash happens on exit, probably as the result of memory / stack corruption.
There have been 24 crashes in the past 6 months but they became more frequent
after the 2022-09-16 which may correspond to the TestBot switching to running
two VMs are a time. So the failure may be caused by extra load.
There is also at least one case of a timeout on exit (2022-12-09 on
debian11-win32-ja-JP), which is probably the same issue:
05fc:midi: 445 tests executed (4 marked as todo, 0 as flaky, 0 failures), 0
skipped.
winmm:midi:05fc done (258) in 120s 5788B
--
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=54153
Bug ID: 54153
Summary: kernel32:debugger - test_kill_on_exit() sometimes gets
STILL_ACTIVE exit code on Windows
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: kernel32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
kernel32:debugger - test_kill_on_exit() sometimes gets STILL_ACTIVE exit code
on Windows:
debugger.c:2078: Test failed: exit code = 00000103
See https://test.winehq.org/data/patterns.html#kernel32:debugger
Where 0x103 == STILL_ACTIVE == STATUS_PENDING
This should mean the process is still running. So either there is a race
condition in the test or Windows 8 and 10 21H1 are buggy.
With only 3 instances in 6 months this failure is pretty rare:
* 2022-07-11 on w10pro64-ar (64-bit, 21H1)
* 2022-10-31 on w864 (64-bit)
* 2022-12-06 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=54107
Bug ID: 54107
Summary: Windows Defender interferes with the tests on
w1064v1909
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
Windows Defender interferes with the tests on w1064v1909:
sc.exe:sc start programs/sc/tests/sc.c
sc.exe:sc:0000 done (-225) in 0s 0B
Where 225 == ERROR_VIRUS_INFECTED
This is because in this snapshot was created before Windows Defender became a
problem and thus has no exclusion for the folder where the TestBot puts the
test binaries.
w1064v2009 (and presumably snapshots of newer Windows versions) has the needed
exclusion.
v1064v1809 (and presumably snapshots of older Windows versions) does not have
an exclusion but has "Real-time protection" turned off which should ensure
Defender won't interfere (that option is not available in newer Windows
(Defender) 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=54128
Bug ID: 54128
Summary: user32:msg - test_PeekMessage3() sometimes gets an
unexpected WM_TIMECHANGE message on Windows 10
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
test_PeekMessage3() sometimes gets an unexpected WM_TIMECHANGE message on
Windows 10:
msg.c:13549: Test failed: msg.message = 30 instead of WM_TIMER
msg.c:13552: Test failed: msg.message = 275 instead of WM_USER + 1
msg.c:13554: Test failed: expected PeekMessage to return FALSE, got 1
msg.c:13564: Test failed: msg.message = 1025 instead of WM_TIMER
msg.c:13566: Test failed: msg.message = 275 instead of WM_USER
msg.c:13568: Test failed: expected PeekMessage to return FALSE, got 1
msg.c:13577: Test failed: msg.message = 1024 instead of WM_TIMER
msg.c:13579: Test failed: expected PeekMessage to return FALSE, got 1
See https://test.winehq.org/data/patterns.html#user32:msg
Where
30 == WM_TIMECHANGE
275 == WM_TIMER
1024 == WM_USER
1025 == WM_USER + 1
This is similar to the issue happening in test_PeekMessage2() in bug 53273.
This last happened on 2022-12-09 on w10pro64-pt-BR where the Internet time
synchronization has not been disabled. So that may be the source of the
WM_TIMECHANGE messages.
The TestBot now has code to disable Internet time synchronization but the
snapshots have not all been updated. So this bug should be revisited once they
have been updated to see if the failures are still happening.
--
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=54076
Bug ID: 54076
Summary: windows.globalization:globalization -
test_GlobalizationPreferences() sometimes unexpectedly
returns en_US on Windows 10
Product: Wine
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
windows.globalization:globalization - test_GlobalizationPreferences() sometimes
unexpectedly returns en_US on Windows 10:
globalization.c:137: Test failed:
IGlobalizationPreferencesStatics_get_Languages 0 returned len 5, str L"en-US",
expected L"de-DE"
globalization.c:177: Test failed:
IGlobalizationPreferencesStatics_get_Languages 0 returned len 5, str L"en-US",
expected L"de-DE"
See https://test.winehq.org/data/patterns.html#ws2_32:sock
This failure first happened on 2022-11-22 and impacts the de, fr, ja, ko, pt-BR
and ru locales of the w10pro64 VM. It's not systematic but is frequent enough
that it seems like it does not impact the other locales.
The timing of the first failure is suspicious:
* The w10pro64 had a problem where Windows 10 would reset UserDefaultLCID,
ThreadLocale and Country to en_US when the TestBot called SetSystemTime() to
update the clock in the live snapshot. As long as this issue was there there
was no failure.
* On 2022-11-21 LibvirtTool got a workaround to re-set these locale settings
after setting the time and the failures started.
So this sounds like Windows is still messing with the locales :-(
--
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=54147
Bug ID: 54147
Summary: Kholat from GOG: Splash video are not in fullscreen
Product: Wine
Version: 8.0-rc1
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: mfplat
Assignee: wine-bugs(a)winehq.org
Reporter: titan.costa(a)gmail.com
Distribution: ---
Wine wine-8.0-rc1. Ubuntu 22.10.
From bug https://bugs.winehq.org/show_bug.cgi?id=50043.
--
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.