https://bugs.winehq.org/show_bug.cgi?id=52761
Bug ID: 52761
Summary: mscoree:mscoree test fails without a display or
console
Product: Wine
Version: 7.5
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: madewokherd(a)gmail.com
Distribution: ---
The mscoree:mscoree test fails if you run it like this:
$ DISPLAY= wine mscoree_test.exe mscoree </dev/null >log 2>&1
Without the DISPLAY=, it makes a bunch of console windows. That doesn't seem to
happen on Windows, but that could be caused by our csc.exe.
--
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=52937
Bug ID: 52937
Summary: msvcr110:msvcr110 fails on Windows with the UTF-8
codepage
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: msvcrt
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
msvcr110:msvcr110 fails on Windows with the UTF-8 codepage:
msvcr110.c:135: Test failed: expected syr-SY, got
LC_COLLATE=syr-SY;LC_CTYPE=EN-US;LC_MONETARY=syr-SY;LC_NUMERIC=syr-SY;LC_TIME=syr-SY
https://test.winehq.org/data/patterns.html#msvcr110:msvcr110
Note that the LC_CTYPE value in the above string corresponds to the last value
it was set to. So if one tests fr-FR right before syr-SY the string contains
LC_CTYPE=fr-FR. This is also why the en-US case is weird.
Furthermore with a non-UTF-8 codepage setlocale() does return "syr-SY".
So it looks like:
1. msvcr110 returns a long string specifying the details of the locale settings
whenever they have different values.
2. msvcr110 does not support setting LC_CTYPE to syr-SY, but only when the
codepage is UTF-8 for whatever reason.
--
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=51298
Bug ID: 51298
Summary: d3d8:visual: lighting_test() fails on Windows 10 >=
2004
Product: Wine
Version: 6.10
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
d3d8:visual has a failure in lighting_test() on Windows 10 >= 2004:
https://test.winehq.org/data/patterns.html#d3d8:visual
visual.c:544: Test failed: Lit quad with singular world matrix has color
0x00000000.
This happens on cw-rx460, cw-gtx560 and on those TestBot VMs that run the
32-bit tests. That means it's not a VM or graphics driver issue but a Windows
version one.
The test was introduced by this commit:
commit 589f1072df9535104c074e5382ef7d8ce28f0f33
Author: Matteo Bruni <mbruni(a)codeweavers.com>
AuthorDate: Tue Apr 21 15:11:19 2015 +0200
d3d8/tests: Add a lighting test with non-affine worldview matrix.
--
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=51104
Bug ID: 51104
Summary: mf:mf crashes on Windows + NVidia
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: mfplat
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
mf:mf crashes on the cw-gtx560 and cw-rx460 machines but not on the TestBot VMs
(except w7u-2qxl, but that's a different crash).
https://test.winehq.org/data/patterns.html#mf:mf
The crash happens on the same test_evr() line from Windows 8.1 to Windows 10
2009:
hr = MFGetService((IUnknown *)stream_sink2, &MR_VIDEO_ACCELERATION_SERVICE,
&IID_IMFVideoSampleAllocator,
(void **)&allocator);
A bisect shows that the commit causing the crash is not the one that added this
line but the one below:
commit 430c179fe86dd7f9b3ddfb6ef30f6359633ef0b8
Author: Nikolay Sivov <nsivov(a)codeweavers.com>
Date: Fri Oct 9 13:54:38 2020 +0300
mf/evr: Set stream media type to the mixer.
Signed-off-by: Nikolay Sivov <nsivov(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.
http://bugs.winehq.org/show_bug.cgi?id=34782
Bug #: 34782
Summary: crypt32/chain tests crash with gcc-4.8.1 (win64)
Product: Wine
Version: 1.7.4
Platform: x86
OS/Version: Linux
Status: NEW
Keywords: download, source, win64
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: austinenglish(a)gmail.com
Classification: Unclassified
Running: crypt32:chain (3 of 15)
fixme:crypt:CertVerifyCertificateChainPolicy unimplemented for 0
fixme:crypt:CRYPT_CriticalExtensionsSupported unsupported critical extension
"1.2.3"
fixme:crypt:CRYPT_CriticalExtensionsSupported unsupported critical extension
"1.2.3"
fixme:crypt:CRYPT_CriticalExtensionsSupported unsupported critical extension
"1.2.3"
wine: Unhandled page fault at address 0x7f579f85aa74 (thread 0043), starting
debugger...
fixme:dbghelp_dwarf:dwarf2_parse_variable Unsupported constant (parameter)
pEncodePara in function
fixme:dbghelp_dwarf:dwarf2_parse_variable Unsupported constant (parameter)
dwFlags in function
fixme:dbghelp_dwarf:dwarf2_parse_subprogram_block Unhandled Tag type 0x15 at
ctx(0x23aa10,L"kernel32<elf>"), for debug_info(abbrev:0x7b3c80,symt:(nil))
fixme:dbghelp_dwarf:dwarf2_parse_subprogram_block Unhandled Tag type 0xf at
ctx(0x23aa10,L"kernel32<elf>"), for debug_info(abbrev:0x7b3c80,symt:(nil))
it works with gcc-4.7.3. I'll bisect gcc.
--
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=28220
Summary: kernel32/process.ok: test fails when redirected
Product: Wine
Version: 1.3.27
Platform: x86
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: kernel32
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: dank(a)kegel.com
It's not uncommon to want to do
make test > log 2>&1
but if you do this, kernel32/process.ok will fail with
../../../tools/runtest -q -P wine -M kernel32.dll -T ../../.. -p
kernel32_test.exe.so process.c && touch process.ok
wine: cannot find L"C:\\windows\\system32\\doesnotexist.exe"
wine: cannot find L"C:\\windows\\system32\\does.exe"
process.c:1344: Test failed: Opening ConOut
process.c:1347: Test failed: Getting sb info
process.c:1348: Test failed: Getting console modes
--
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=53004
Bug ID: 53004
Summary: 63ce060 causes a white border line in winecfg
Product: Wine
Version: 7.8
Hardware: x86-64
OS: Linux
Status: NEW
Keywords: regression
Severity: normal
Priority: P2
Component: win32u
Assignee: wine-bugs(a)winehq.org
Reporter: andrey.goosev(a)gmail.com
CC: jacek(a)codeweavers.com
Regression SHA1: 63ce060e5b33ca4b58d508be11af4d3c214fae33
Distribution: ---
Created attachment 72372
--> https://bugs.winehq.org/attachment.cgi?id=72372
example
As the title says.
--
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=52970
Bug ID: 52970
Summary: kernelbase:process breaks lz32:lzexpand_main on
Windows 1809+
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
kernelbase:process breaks lz32:lzexpand_main on Windows 1809+:
lzexpand_main.c:148: Test failed: LZOpenFileA returned
'C:\Users\winetest\AppData\Local\Temp\wct\testfile.xxx', but was expected to
return 'C:\Users\winetest\AppData\Local\Temp\wct\testfile.xx_'
lzexpand_main.c:228: Test failed: LZOpenFileA succeeded on nonexistent file
lzexpand_main.c:230: Test failed: GetLastError() returns 0
lzexpand_main.c:232: Test failed: LZOpenFileA set test.cBytes to 136
lzexpand_main.c:234: Test failed: LZOpenFileA set test.nErrCode to 0
lzexpand_main.c:236: Test failed: LZOpenFileA returned
'C:\Users\winetest\AppData\Local\Temp\wct\testfile.xxx', but was expected to
return 'C:\Users\winetest\AppData\Local\Temp\wct\testfile.xx_' or
'¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥C:\Users\winetest\AppData\Local\Temp\wct\testfile.xx_'
lzexpand_main.c:550: Test failed: LZOpenFileW returned
'C:\Users\winetest\AppData\Local\Temp\wct\testfile.xxx', but was expected to
return 'C:\Users\winetest\AppData\Local\Temp\wct\testfile.xx_'
lzexpand_main.c:628: Test failed: LZOpenFileW succeeded on nonexistent file
lzexpand_main.c:630: Test failed: GetLastError() returns 0
lzexpand_main.c:632: Test failed: LZOpenFileW set test.cBytes to 136
lzexpand_main.c:634: Test failed: LZOpenFileW set test.nErrCode to 0
lzexpand_main.c:636: Test failed: LZOpenFileW returned
'C:\Users\winetest\AppData\Local\Temp\wct\testfile.xxx', but was expected to
return 'C:\Users\winetest\AppData\Local\Temp\wct\testfile.xx_' or
'¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥'
https://test.winehq.org/data/patterns.html#lz32:lzexpand_main
As mentioned before, lz32:lzexpand_main succeeds on its own. It's only when
kernelbase:process is run before that this test fails. The simplest way to
reproduce the failures is to run:
winetest.exe -c -o - -t foo kernelbase:process lz32:lzexpand_main
The failure happens because kernelbase:process leaves a "testfile.xxx" file
behind, file which is also used by the lz32:lzexpand_main test unit.
Finally a bisect shows that these failures started with the commit below.
commit 9c40a80100febb9ac23dae1e51605ba4f2f46f6f
Author: Nikolay Sivov <nsivov(a)codeweavers.com>
Date: Wed May 4 14:55:36 2022 +0300
kernelbase: Implement MapViewOfFile3().
Signed-off-by: Nikolay Sivov <nsivov(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=51376
Bug ID: 51376
Summary: Wine causes PC to lock or crash wine when loading more
than 1 VST addon into WaveLab 6
Product: Wine
Version: 6.0.1
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: shagooserver(a)gmail.com
Distribution: ---
Created attachment 70232
--> https://bugs.winehq.org/attachment.cgi?id=70232
backtrace
I have a number of VST add-ons I use with Wavelab, they come from a number of
different software houses and work differently, for example some require vcrun
libraries to work while others do not. In the main, I can load any single
add-on and it works as expected but as soon as I add/open a second add-on my PC
will either crash wine or it will lock up altogether requiring a hard restart.
This was not an issue in wine 5.0.
Backtrace is attached.
Possibly a duplicate of bug 51259 or is quite similar.
--
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=51283
Bug ID: 51283
Summary: d3d8:device breaks evr:evr on w7u-2qxl
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
The WineTest reports show that evr:evr crashes on w7u-2qxl:
https://test.winehq.org/data/patterns.html#evr:evr
evr.c:1335: Test failed: Unexpected hr 0x80070057.
evr.c:1335: this is the last test seen before the exception
07ac:evr: unhandled exception c0000005 at 0040CBD0
evr:evr:07ac done (-1073741819) in 0s
Test failed: crash (c0000005)
However when run on its own it succeeds consistently. It turns out that it is
d3d8:device that causes evr:evr to crash. More specifically it is
test_multi_adapter() that interferes with evr:evr.
Also if d3d8:device succeeds then evr:evr crashes but if d3d8:device fails as
shown below then evr:evr succeeds as can be seen by comparing the pattern below
with the evr:evr one.
https://test.winehq.org/data/patterns.html#d3d8:device
device.c:4205: Test failed: Got a different mode.
device.c:4208: Test failed: Got a different mode.
--
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.