https://bugs.winehq.org/show_bug.cgi?id=50159
Bug ID: 50159
Summary: Lylian demo plays: we can hear sounds but no video.
Product: Wine
Version: 5.22
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: quartz
Assignee: wine-bugs(a)winehq.org
Reporter: jeremielapuree(a)yahoo.fr
Distribution: ---
Created attachment 68676
--> https://bugs.winehq.org/attachment.cgi?id=68676
console output with quartz debug channel enabled
All is said in the tile.
Demo starts, one can hear sound, but no video is played.
--
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=49397
Bug ID: 49397
Summary: DX11 Sample "Texturing and Lighting" fails with error
"Failed to load texture"
Product: Wine
Version: 5.10
Hardware: x86-64
URL: https://drive.google.com/uc?export=download&id=0B0ND0J
8HHfaXenFyNC12ZlJlS1U
OS: Linux
Status: NEW
Keywords: download, source
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: gijsvrm(a)gmail.com
Distribution: ArchLinux
Created attachment 67467
--> https://bugs.winehq.org/attachment.cgi?id=67467
+d3d11,+d3d,+dxgi
I'm running Arch Linux with a GTX 750Ti (driver version 440.82).
Attached is a +d3d11,+d3d,+dxgi log.
--
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=47875
Bug ID: 47875
Summary: kernel32:file: FindFirstFile("foo\nul\bar") succeeds
on AMD graphics!
Product: Wine
Version: 4.17
Hardware: x86
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: kernel32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
On some machines kernel32:file systematically gets the following two failures:
file.c:2709: Test failed: FindFirstFile on C:\foo\bar\nul should fail
file.c:2710: Test failed: Bad Error number -559038801
-559038801 is 0xdeadbeaf which is the value LastError is set to before the
test:
SetLastError( 0xdeadbeaf );
strcpy(buffer2, buffer);
strcat(buffer2, "foo\\bar\\nul");
handle = FindFirstFileA(buffer2, &data);
ok ( handle == INVALID_HANDLE_VALUE, "FindFirstFile on %s should fail\n",
buffer2 );
ok ( err == ERROR_PATH_NOT_FOUND, "Bad Error number %d\n", err );
This suggests that FindFirstFile() succeeds in finding "foo\bar\nul".
Furthermore this only happens on two Windows 8.1 machines, cw-rx460 and
dr-RS740, both in the 32 and 64 bit tests.
They share the same build number (9600) but so does cw2-gtx560 which does not
have these failures. The other common point is that they both have an AMD
graphics card and, presumably, the corresponding driver. But why would a
graphics driver change the behavior of FindFirstFile()?
--
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=52260
Bug ID: 52260
Summary: Gothic 3: flickering, low-res textures with built-in
msvcrt.dll
Product: Wine
Version: 6.15
Hardware: x86-64
URL: https://archive.org/download/DemosGothic3/Demos%20-%20
Gothic%203.exe
OS: Linux
Status: NEW
Keywords: download, regression
Severity: normal
Priority: P2
Component: msvcrt
Assignee: wine-bugs(a)winehq.org
Reporter: gyebro69(a)gmail.com
CC: piotr.caban(a)gmail.com
Regression SHA1: f1ef14dc177b23c908e4dd2d47846cb673e3feac
Distribution: ArchLinux
In many places in the game Gothic 3 textures are flashing in and out and they
look like low-resolution textures that are smudged. Most of the buildings have
this glitch.
The problem doesn't occur with native msvcrt.dll.
The bug appeared in Wine 6.15.
What made regression testing difficult was that the offending commit also
caused several applications, including Gothic 3, to crash on start. Therefore I
couldn't perform the regression test in the usual way.
The last good commit where the game starts properly and the bug is *not*
present:
f53b2095f36f1753b9a50d4dcb2eeab6c8c796cd
The next commit broke the game:
f1ef14dc177b23c908e4dd2d47846cb673e3feac
msvcrt: Introduce _setfp helper to access floating point status and control
words.
The breakage was fixed later by
62d2693701c1756264fdf975578cb7f6abd5c1b1
msvcrt: Fix x87 FPU status register assignment detection.
After
git checkout f1ef14dc177b23c908e4dd2d47846cb673e3feac
and the fix applied, the bug is present.
Demos - Gothic 3.exe (1.1G)
md5: 18a1a1b96bed7207944f185f160a689b
(demo needs native d3dx9_29.dll)
wine-7.0-rc2-41-gd03984709d8
--
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=52198
Bug ID: 52198
Summary: MotoGP 2: Controller menu doesn't open when button for
controller menu is pressed
Product: Wine
Version: 6.23
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-dinput
Assignee: wine-bugs(a)winehq.org
Reporter: tobias.boesch(a)googlemail.com
Distribution: Debian
Created attachment 71251
--> https://bugs.winehq.org/attachment.cgi?id=71251
Logs of starting MotoGP 2 demo and klicking the controller configuration button
Hello Wine dev team,
I tried launching MotoGP 2 and found out that
- after the game is installed and
- started via launcher.exe and
- the launcher appears
- klicking the "Configure controllers" button "doesn't work" which means there
is no window opening.
I expect that a window opens where one can associate controller buttons to game
functions.
This works on a recent Windows 10.
I was able to log messages from wine and added them as attachment.
Note: Though the test for this bug report was made with the wine development
version, I also tested it with my Debian default version 5.09 and with that
version that menu opens.
The demo version can be found at:
https://www.fileplanet.com/archive/p-18296/MotoGP-2-PC-Demo
Some people made this game work in older wine versions by overriding
dinput8.dll. See:
https://appdb.winehq.org/objectManager.php?sClass=version&iId=5418&iTesting…
I tried that in another test and was not successful.
I run Debian 11.
--
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=48032
Bug ID: 48032
Summary: Errors when installing games in Origin (regression)
Product: Wine
Version: 4.18
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: sashok.olen(a)gmail.com
Distribution: ---
During game installations, Origin will almost always print "An unexpected error
has occurred. Please try again in a few moments. Error: 327682:11" and not flag
the game as successfully installed.
Through bisect I've found that this is a regression which was caused by commit
e4ca5dbec056c977bffce31bd7901aaec884f199 (server: Add new pipe servers to the
end of the servers list). Reverting that commit against wine-4.3 also fixed the
issue (can't revert it against 4.19 as git revert doesn't let me).
I've made a log with +server debug channel. It was too big for bugzilla so I
had to upload it to my Google Drive:
https://drive.google.com/open?id=1doEVWo1qW1ppP_VemoCu8xhFkWXEsn0z
(oh, and ignore errors about wine not finding some .exes - i disabled them
myself for certain reasons).
Let me know if anything else is needed.
--
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=52222
Bug ID: 52222
Summary: WINEDLLOVERRIDES="DINPUT8.dll=n,b" no longer works
since 4f1095a, worked in V6.23.
Product: Wine
Version: 7.0-rc1
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winmm&mci
Assignee: wine-bugs(a)winehq.org
Reporter: billfleming11(a)gmail.com
Distribution: ---
Zebediah pointed out where this new bug was and I confirmed the regression with
a minor code modification. See his comments here for the program I first saw
the regression against.
https://bugs.winehq.org/show_bug.cgi?id=51409#c7
In Wine 3.X, 4.X, 5.X, 6.X we have been able to supply modified DLLs (for
example that some games require to load a translation or a mod to fix bugs,
etc) in the game's directory and override the built-in DLL to load the
modification hook into the application. From 4f1095a on-wards dinput8 became an
IMPORT requirement of winmm makefile leading to the following error in wine,
before it even really attempts to load the application.
LdrInitializeThunk "WINMM.dll" failed to initialize, aborting
I can modify wine 7.0-rc1 to allow the dll to load again, making the game
playable other than any lingering video playback issues it has.
In dlls/winmm/Makefile.in I modified the IMPORTS line to remove dinput8.
In dlls/winmm/joystick.c I commented out the contents of the void
joystick_load( HINSTANCE instance ) function. (lines 157 to 159 as of 7.0-rc1).
Then after rebuilding wine the application will launch again using
WINEDLLOVERRIDES="DINPUT8.dll=n,b"
Note that this regression will affect a large number of video games as it is
almost universal to "hook" into a game using DINPUT8.dll specifically, as
apposed to other possible DLLs.
If anyone really wants to look at a log file I put one here in the old report.
https://bugs.winehq.org/attachment.cgi?id=71302
Note that at least in this one game my xbox 1 controller still works with xow
after removing those lines, but someone who knows what they are doing should
propose a new patch relating to joysticks.
--
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=52073
Bug ID: 52073
Summary: The builtin libxml2/libxslt libraries break
msxml3:domdoc in wow64 mode
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: msxml3
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
The builtin libxml2 / libxslt libraries break msxml3:domdoc in wow64 mode.
More specifically msxml3:domdoc started crashing on 2021-10-20:
domdoc.c:7004: Test marked todo: expected refcount 2, got 1
Unhandled exception: page fault on read access to 0x00000000ffffffff in 64-bit
code (0x00000000013682a8).
[...]
Backtrace:
=>0 0x00000000013682a8 xmlXPathNodeCollectAndTest+0x28(ctxt=<is not available>,
op=<is not available>, first=<is not available>, last=<is not available>,
toBool=<is not available>)
[Z:\home\winetest\winetest\src\libs\xml2\xpath.c:12028] in msxml3
(0x0000000001388348)
1 0x0000000001369d51 xmlXPathNodeCollectAndTest+0x1ad0(ctxt=<is not
available>, op=<is not available>, first=<is not available>, last=<is not
available>, toBool=<is not available>)
[Z:\home\winetest\winetest\src\libs\xml2\xpath.c:13113] in msxml3
(0x0000000001388348)
2 0x000000000136a024 xmlXPathNodeCollectAndTest+0x1da3(ctxt=<is not
available>, op=<is not available>, first=<is not available>, last=<is not
available>, toBool=<is not available>)
[Z:\home\winetest\winetest\src\libs\xml2\xpath.c:13361] in msxml3
(0x0000000001388348)
3 0x000000000136b559 xmlXPathRunEval+0xc8(ctxt=<is not available>, toBool=<is
not available>) [Z:\home\winetest\winetest\src\libs\xml2\xpath.c:13954] in
msxml3 (0x0000000001388348)
4 0x000000000136b775 xmlXPathCompiledEvalInternal+0xc4(comp=<is not
available>, ctxt=<is not available>, resObjPtr=<is not available>, toBool=<is
not available>) [Z:\home\winetest\winetest\src\libs\xml2\xpath.c:14337] in
msxml3 (0x0000000001388348)
5 0x000000000136bb3a xmlXPathCompiledEval+0x19(comp=<is not available>,
ctx=<is not available>) [Z:\home\winetest\winetest\src\libs\xml2\xpath.c:14383]
in msxml3 (0x0000000000fae760)
6 0x0000000001298edc xsltProcessOneNode+0x18b(ctxt=<is not available>,
contextNode=<is not available>, withParams=<is not available>)
[Z:\home\winetest\winetest\src\libs\xslt\libxslt\transform.c:385] in msxml3
(0x0000000000fae760)
7 0x0000000001296517 xsltCopyText+0x706(ctxt=<is not available>, target=<is
not available>, cur=<is not available>, interned=<is not available>)
[Z:\home\winetest\winetest\src\libs\xslt\libxslt\transform.c:2798] in msxml3
(0x0000000000fadc90)
8 0x0000000001298638 xsltLocalVariablePush+0x267(ctxt=<is not available>,
variable=<is not available>, level=<is not available>)
[Z:\home\winetest\winetest\src\libs\xslt\libxslt\transform.c:2388] in msxml3
(0x0000000000fa3c70)
9 0x0000000001298da2 xsltProcessOneNode+0x51(ctxt=0000000000FC2DC0,
contextNode=0000000000FAE760, withParams=0000000000000000)
[Z:\home\winetest\winetest\src\libs\xslt\libxslt\transform.c:3145] in msxml3
(0x0000000000000000)
10 0x000000000129b28f
xsltApplyStylesheetInternal+0x3ce(style=0000000000FA2030, doc=0000000000FAE760,
params=<is not available>, output=<is not available>, profile=<is not
available>, userCtxt=<is not available>)
[Z:\home\winetest\winetest\src\libs\xslt\libxslt\transform.c:6089] in msxml3
(0x0000000000000000)
11 0x000000000129b95e xsltApplyStylesheet+0x1d(style=<is not available>,
doc=<is not available>, params=<is not available>)
[Z:\home\winetest\winetest\src\libs\xslt\libxslt\transform.c:6285] in msxml3
(0x00000000006bf978)
12 0x000000000125c2a7 node_transform_node_params+0xb6(This=0000000000043960,
stylesheet=<is not available>, p=<is not available>, stream=0000000000000000,
params=0000000000000000)
[Z:\home\winetest\winetest\src\dlls\msxml3\node.c:1518] in msxml3
(0x00000000006bf978)
13 0x000000000125c845 unknode_transformNode+0x34(iface=<is not available>,
domNode=<is not available>, p=<is not available>)
[Z:\home\winetest\winetest\src\dlls\msxml3\node.c:1541] in msxml3
(0x00000000000384a8)
14 0x000000000123085a domdoc_transformNode+0x29(iface=<is not available>,
node=0000000000045540, p=00000000006BF978)
[Z:\home\winetest\winetest\src\dlls\msxml3\domdoc.c:1479] in msxml3
(0x00000000000384a8)
15 0x000000000040c180 in msxml3_test (+0xc17f) (0x00000000000384a8)
[...]
https://test.winehq.org/data/patterns.html#msxml3:domdoc
A bisect shows that the crash started happening with the commit below:
commit bca1b7f2faeb0798f4af420c15ff5a1b1f7b40af
Author: Alexandre Julliard <julliard(a)winehq.org>
Date: Wed Oct 20 11:39:06 2021 +0200
mxsml3: Use the bundled libxml2 and libxslt and build with msvcrt.
Signed-off-by: Alexandre Julliard <julliard(a)winehq.org>
The previous two commits are imports of the libxslt and libxml2 code
respectively and don't compile. And msxml3:domdoc does not crash with the
previous commit (9a335d89d0cc).
--
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=51159
Bug ID: 51159
Summary: test_NLSVersion() fails on Windows 10 >= 2004 in
kernel32:locale
Product: Wine
Version: 6.8
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: kernel32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
test_NLSVersion() fails on Windows 10 >= 2004 in kernel32:locale:
locale.c:6900: Test failed: IsValidNLSVersion succeeded
This is the test where dwNLSVersion is decreased compared to its initial
version:
info.dwNLSVersion -= 0x200;
ret = pIsValidNLSVersion( COMPARE_STRING, L"en-US", &info );
ok( !ret, "IsValidNLSVersion succeeded\n" );
Traces show that Windows 8.1 to Windows 10 1809 have NLSVersion=6020f,
while Windows 10 >= 2004 has NLSVersion=60305.
Maybe the test fails because the older Windows accept anything in the 602xx
range and 60206 (60305+1-0x100) falls in that range?
What was the point of that test?
This test was introduced by the commit below:
commit 84cca2baae23c6afa0c8070f5009fdcfa218e039
Author: Alexandre Julliard <julliard(a)winehq.org>
Date: Fri Mar 20 14:43:45 2020 +0100
kernelbase: Implement IsValidNLSVersion().
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=48776
Bug ID: 48776
Summary: GoToMeeting Opener crashes
Product: Wine
Version: 5.4
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: wininet
Assignee: wine-bugs(a)winehq.org
Reporter: bernhardu(a)mailbox.org
Distribution: ---
Tried to get a goto meeting running just with an older Firefox and Wine.
Unfortunately the "GoToMeeting Opener.exe" crashes short after start,
when showing around 10% progress.
I could follow the crash to an allocation of 0x100000 bytes,
to which some data get asynchronously downloaded, written to a file,
and then freed.
But after that, below a INTERNET_WorkerThreadFunc,
a memcpy tries to access the previously freed memory.
Further looking might lead to a SetEvent that get triggered by
the INTERNET_STATUS_RECEIVING_RESPONSE callback,
but I am not sure if this is related or supposed the way it runs now.
A windows Firefox offers for following link a download:
https://global.gotomeeting.com/join/100000000
(meeting id changed - the download is the same
except 176 bytes, but shows the same issue.)
--
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.