https://bugs.winehq.org/show_bug.cgi?id=51188
Bug ID: 51188
Summary: test_user_shared_data() fails in ntdll:virtual
Product: Wine
Version: 6.8
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Created attachment 70061
--> https://bugs.winehq.org/attachment.cgi?id=70061
AllFeatures traces
test_user_shared_data() fails on Windows 7 and 8.1 in ntdll:virtual.
https://test.winehq.org/data/patterns.html#ntdll:virtual
On Windows 7 there are two failures:
virtual.c:962: Test failed: Got unexpected AllFeatures[1] 128, expected 256.
virtual.c:966: Test failed: Got unexpected Features[1].Size 128, expected 256.
And on Windows 8.1 there is one:
virtual.c:957: Test failed: Got unexpected AllFeatureSize 0.
The test also has a special case which claims to be for Windows 10 Pro, though
in fact the broken behavior seems to describe the behavior of all Windows 10
versions:
ok(xstate.AllFeatures[i] == feature_sizes[i]
|| broken(!xstate.AllFeatures[i]) /* win10pro */,
Given that this is related to processor features it's interesting to check what
processors are involved:
https://testbot.winehq.org/JobDetails.pl?Key=91253
w7u Win7 IvyBridge-IBRS (QEmu) fails
w7pro64 Win7 SandyBridge (QEmu) success
w2008s64 Win2008 kvm64 (QEmu) skipped (missing XState features)
cw-gtx560 Win8.1 i7-2600K fails
cw-rx460 Win8.1 i7-2600K fails
w8 Win8.1 kvm32 (QEmu 32-bit) skipped (missing XState features)
w864 Win8.1 core2duo (QEmu) skipped (missing XState features)
cw-rx460 Win10 1507 i7-2600K broken (success)
w1064v1507 Win10 1507 IvyBridge-IBRS (QEmu) broken (success)
w1064v1607 Win10 1607 IvyBridge-IBRS (QEmu) broken (success)
w1064v1709 Win10 1709 IvyBridge-IBRS (QEmu) broken (success)
w1064v1809 Win10 1809 IvyBridge-IBRS (QEmu) broken (success)
w1064v1909 Win10 1909 IvyBridge-IBRS (QEmu) broken (success)
w10pro64 Win10 2004 IvyBridge-IBRS (QEmu) broken (success)
w1064 Win10 2009 IvyBridge-IBRS (QEmu) broken (success)
So it looks like there is no XState support on kvm32, kvm64 and core2duo
processors which explains why the TestBot gets no failure on Windows 8.1.
As for the half-size issue on w7u, this may be because that processor is 32-bit
and not 64-bit.
Finally, at best the comment for the broken(!xstate.AllFeatures[i]) is wrong,
or that broken statement itself is wrong given that it considers the behavior
of all Windows 10 versions to be broken.
--
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=50975
Bug ID: 50975
Summary: Multiple applications need an implementation of
undocumented socket "poll" ioctl 0x12027 (Rust
applications using the Mio or Smol libraries,
Starcraft Remastered)
Product: Wine
Version: 5.0
Hardware: x86-64
OS: Linux
Status: NEW
Keywords: download, patch
Severity: normal
Priority: P2
Component: winsock
Assignee: wine-bugs(a)winehq.org
Reporter: z.figura12(a)gmail.com
Depends on: 50974
Distribution: ---
Split from bugs 50520 and 50366. This is the third problem facing those
applications.
An example application is attached to bug 50520.
This is addressed by a currently out-of-tree patch series
<https://repo.or.cz/wine/zf.git/shortlog/refs/heads/sock4>; the last necessary
patch is
<https://repo.or.cz/wine/zf.git/commitdiff/3cb658976c8bf6c981b03a5e259d65c16…>.
--
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=41253
Bug ID: 41253
Summary: GZDoom Builder : Unable to make a new project
Product: Wine
Version: 1.9.17
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: janusczpawlacz(a)protonmail.ch
Distribution: ---
Created attachment 55547
--> https://bugs.winehq.org/attachment.cgi?id=55547
Terminal error outpot of Builder.exe
So every time I try to open a new project or opening a existing map for editing
a error appears and it just plain crashes.
Error Message:
Fatal Windows Forms error occured: CompilationException While [unreadable]
Fatal Windows Forms Error
http://devbuilds.drdteam.org/doombuilder2-gzdb/GZDoom%20Builder%20R2364%20I…
sha1sum: aa65a19b1275deb09680f4227f81218d27308422
Distribution: Linux Mint 18 Mate X86_64 (64bit)
--
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=51209
Bug ID: 51209
Summary: Regression: Wine-mono installers in the parent folder
of build trees can not be found
Product: Wine
Version: 6.9
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: zzhang(a)codeweavers.com
Distribution: ---
~$ sha256sum ~/src/mono/wine-mono-6.1.1-x86.msi
ac3b14beafde34b8482287e597000113dc06a915f32c9fd06c77eb819079e38b
/home/eric/src/mono/wine-mono-6.1.1-x86.msi
~$ ls -l ~/src/wine/mono
lrwxrwxrwx 1 eric eric 7 Nov 4 2020 /home/eric/src/wine/mono -> ../mono
The build tree is in ~/src/wine/win32-build
WINEDEBUG=+file bad log
0064:trace:file:GetFileAttributesW
L"\\\\?\\Z:\\home\\eric\\src\\wine\\win32-build\\..\\mono\\wine-mono-6.1.1-x86.msi"
0064:trace:file:RtlDosPathNameToNtPathName_U_WithStatus
(L"\\\\?\\Z:\\home\\eric\\src\\wine\\win32-build\\..\\mono\\wine-mono-6.1.1-x86.msi",0031FBD0,00000000,00000000)
0064:trace:file:nt_to_unix_file_name
L"home\\eric\\src\\wine\\win32-build\\..\\mono\\wine-mono-6.1.1-x86.msi" not
found in /home/eric/.wine/dosdevices/z:€~°)€~0)€~€~
€~°Æ~Ç~@Ç~ð)€~P€~p)€~€Æ~ÀÉ~ðÉ~É~ Ê~PÊ~€Ê~°Ê~àÊ~@Ë~pË~
Ë~Ë~Í~ÀÍ~Ð)€~°×~Ø~ Ø~ÐØ~
0064:warn:file:NtQueryAttributesFile
L"\\??\\Z:\\home\\eric\\src\\wine\\win32-build\\..\\mono\\wine-mono-6.1.1-x86.msi"
not found (c0000033)
WINEDEBUG=+file good log
0064:trace:file:GetFileAttributesW
L"\\\\?\\Z:\\home\\eric\\src\\wine\\win32-build\\..\\mono\\wine-mono-6.1.1-x86.msi"
0064:trace:file:RtlDosPathNameToNtPathName_U_WithStatus
(L"\\\\?\\Z:\\home\\eric\\src\\wine\\win32-build\\..\\mono\\wine-mono-6.1.1-x86.msi",0031FBD0,00000000,00000000)
0064:trace:file:nt_to_unix_file_name
L"\\??\\Z:\\home\\eric\\src\\wine\\win32-build\\..\\mono\\wine-mono-6.1.1-x86.msi"
->
"/home/eric/.wine/dosdevices/z:/home/eric/src/wine/win32-build/../mono/wine-mono-6.1.1-x86.msi"
A bisect points to
405666b736f7e471e301f051cfbe68bcbef7e0f6 is the first bad commit
commit 405666b736f7e471e301f051cfbe68bcbef7e0f6
Author: Alexandre Julliard <julliard(a)winehq.org>
Date: Tue Apr 13 12:55:59 2021 +0200
ntdll: Reject NT path names that are not in canonical form.
Signed-off-by: Alexandre Julliard <julliard(a)winehq.org>
dlls/ntdll/tests/path.c | 92 +++++++++++++++++++++++++++++++++++++++++++++
dlls/ntdll/unix/file.c | 99 ++++++++++++++++++++++++++-----------------------
2 files changed, 144 insertions(+), 47 deletions(-)
However, 405666b is correct. The root cause is in appwiz.cpl/addon.c
install_from_default_dir() and install_from_dos_file(), which constructs a path
starting with "\\?\" and contains "..". According to 405666b and
GetFileAttributesExW() tests (also applies for GetFileAttributesW()),
"\\\\?\\Z:\\home\\eric\\src\\wine\\win32-build\\..\\mono\\wine-mono-6.1.1-x86.msi"
should be canonicalized before passing it to GetFileAttributesW().
--
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=50989
Bug ID: 50989
Summary: ntdll:time: New intermittent QpcSystemTimeIncrement
failure
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
ntdll:time has the following intermittent failure:
time.c:179: Test failed: unexpected QpcSystemTimeIncrement 800000d6bf963e2f,
expected 1<<63
See: https://test.winehq.org/data/tests/ntdll:time.html
So far this failure has only happened when running the 64-bit test on the
following TestBot VMs:
w10pro64_ar (3 times)
w10pro64_he (1 time)
w10pro64_ja (2 times)
w10pro64_zh_CN (2 times)
>From the time this test was introduced to now there have been 8 failures out of
68 WineTest runs on the impacted VMs, that is at most an 11.7% failure rate.
It is strange that it has not happened on the other configurations like
w10pro64, w10pro64_fr, w10pro64_ko, etc. Given the low failure rate this may
just be a matter of time though.
This check was introduced in the following commit:
commit d9d478e277bcf60e47803d00d1897e8aa649027c
Author: Rémi Bernon <rbernon(a)codeweavers.com>
Date: Thu Mar 18 17:22:06 2021 +0100
ntdll/tests: Add RtlQueryPerformanceCounter tests.
Signed-off-by: Rémi Bernon <rbernon(a)codeweavers.com>
Signed-off-by: Jacek Caban <jacek(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=50987
Bug ID: 50987
Summary: dinput8:device fails on the w10pro64_fr TestBot VM
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: directx-dinput
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
The following test failure happens specifically on the w10pro64_fr TestBot VM:
device.c:110: Test failed: Retrieval of action failed uAppData=4294967295
expected=4
See: https://test.winehq.org/data/tests/dinput8:device.html
This test regression was introduced by the following commit:
commit 8d206333fd50347cb45a8db72ecb191aa787ddb9
Author: Arkadiusz Hiler <ahiler(a)codeweavers.com>
Date: Mon Mar 8 14:36:11 2021 +0200
dinput: Implement DIPROP_APPDATA.
This fixes not working analog inputs on game controllers in Slay the Spire.
Signed-off-by: Arkadiusz Hiler <ahiler(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=46320
Bug ID: 46320
Summary: Kindle don't get installed: abnormal program
temrination
Product: Wine
Version: 4.0-rc2
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: raffamaiden(a)gmail.com
Distribution: ---
Created attachment 63054
--> https://bugs.winehq.org/attachment.cgi?id=63054
command line log file + screenshot
Kindle for PC version 1.24.51068 don't even get installed. After the installer
showing up the dialog in which it says it is decompressing the files, after the
dialog in which it says it is copying (I presume?) the files, an error message
shows up "abnormal program termination"
I attach log and screenshot
--
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=48094
Bug ID: 48094
Summary: Simplify debugging test timeouts
Product: Wine
Version: unspecified
Hardware: x86
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: testcases
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
When a Wine test times out one has to manually add traces to figure out where
it gets stuck, or what the slow parts are. This is all the more difficult when
the timeout is random and happens on a TestBot VM.
I propose to leverage the ok() calls to simplify getting timing information on
the tests.
* Recognize the $WINETEST_TIME environment variable and, if it is set, add the
elapsed time since the test started to the trace() and ok() messages.
* Ideally this elapsed time would have sub-second precision for those cases
where it's more an issue of a long loop being slow. How many decimals to print
is a matter of taste: one may be enough, three would feel quite standard if
maybe a bit overkill.
* Also when $WINETEST_TIME is set, an ok() call would be printed even if
successful when more than 1 second has elapsed since adding a message to the
report (trace/ok/skip). This should allow identifying which part of the test
causes trouble without altering its timing with thousands of traces.
* And when combined with $WINETEST_REPORT_SUCCESS of course every ok() call
would print the elapsed time.
Once the Wine side is implemented a few other components should be updated:
* The TestBot should allow setting $WINETEST_TIME when submitting a job.
* The TestBot should recognize the failure/todo/skip lines even with the extra
timing information.
* The TestBot could be modified to automatically rerun and set $WINETEST_TIME
if a test times out.
* The above may be particularly interesting for the full WineTest runs.
* We may also want to have test.winehq.org recognize the new failure/todo/skip
line formats.
--
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=34746
Bug #: 34746
Summary: Dino Crisis Demo doesn't play video sequences even
though Indeo codecs are installed
Product: Wine
Version: 1.7.4
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: winebugs140(a)gmail.com
Classification: Unclassified
Created attachment 46322
--> http://bugs.winehq.org/attachment.cgi?id=46322
Dino Crisis Demo Log without Indeo
Tested with:
Ubuntu 13.04, GeForce 9600M GS (NVIDIA driver 313)
Mac OS X 10.7.5, ATI HD 2600 Pro, Mac Driver/X11
--
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.
http://bugs.winehq.org/show_bug.cgi?id=31310
Bug #: 31310
Summary: TIE: Fighter: Collectors Edition -- Application
Crashes on Launch
Product: Wine
Version: 1.5.9
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: muleyryan(a)fastmail.fm
Classification: Unclassified
Wine running on 3.4.6-1-ARCH, with S3 Inc. SuperSavage IX/C SDR (rev 05)
xf86-video-savage and MESA savage drivers installed.
Using gdi as d3d renderer.
Application (TIE95.exe) crashes on launch
Backtrace here:
http://pastebin.com/mTX4bPet
Regression test pending.
--
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.