https://bugs.winehq.org/show_bug.cgi?id=52090
Bug ID: 52090
Summary: New failures in d3d11:d3d11 in Wine
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
Running d3d11:d3d11 on the TestBot debiant2 VM used to consistently produce 70
failures. But on 2021-11-04 the failure mix changed and the count increased to
a steady 77 failures.
The new failures happen in void test_fractional_viewports() and
test_negative_viewports().
In typical unified diff style:
-d3d11.c:5926: Test failed: Got unexpected CPrimitives count: 3.
-d3d11.c:5943: Test failed: Got unexpected CPrimitives count: 3.
+d3d11.c:28242: Test failed: Got 0xffffffff, expected 0xff00ff00 at (639, 479,
0), sub-resource 0.
+d3d11.c:28242: Test succeeded inside todo block: Got 0xffffffff, expected
0xffffffff at (640, 480, 1), sub-resource 0.
+d3d11.c:28251: Test failed: Got 0xffffffff, expected 0xff00ff00 at (639, 479,
0), sub-resource 0.
+d3d11.c:28251: Test succeeded inside todo block: Got 0xffffffff, expected
0xffffffff at (640, 480, 1), sub-resource 0.
+d3d11.c:28188: Test failed: Got texcoord {8.43750119e-001, 1.56249881e-001},
expected {8.43750000e-001, 1.56250000e-001} at (3, 3), offset 1.25000000e-001.
+d3d11.c:28242: Test failed: Got 0xffffffff, expected 0xff00ff00 at (639, 479,
0), sub-resource 0.
+d3d11.c:28188: Test failed: Got texcoord {8.71093690e-001, 1.28906310e-001},
expected {8.71093750e-001, 1.28906250e-001} at (3, 3), offset 1.56250000e-002.
+d3d11.c:28251: Test failed: Got 0xffffffff, expected 0xff00ff00 at (639, 479,
0), sub-resource 0.
+d3d11.c:28188: Test failed: Got texcoord {7.51953065e-001, 2.48046935e-001},
expected {7.51953125e-001, 2.48046875e-001} at (3, 3), offset 4.92187500e-001.
https://test.winehq.org/data/patterns.html#d3d11:d3d11
A bisect shows that the new failures started with the commit below:
commit 26a53f674c234aaba4a85ec36bae48384899b705
Author: Stefan Dösinger <stefan(a)codeweavers.com>
Date: Wed Nov 3 20:15:30 2021 +0300
wined3d: Emulate fractional viewports if GL doesn't support them.
This allows test_fractional_viewports to pass regardless of GL capabilies.
I don't think we can get rid of WINED3D_PIXEL_CENTER_INTEGER (and add +0.5
in the client libs) due to vpos in d3d9 shaders.
Signed-off-by: Stefan Dösinger <stefan(a)codeweavers.com>
Signed-off-by: Henri Verbeet <hverbeet(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=51703
Bug ID: 51703
Summary: Opening Omnisphere Authorization window with a large
amount of text on the clipboard causes an unhandled
page fault
Product: Wine-staging
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: andrew(a)amorgan.xyz
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
Created attachment 70576
--> https://bugs.winehq.org/attachment.cgi?id=70576
backtrace
I'm attempting to register my Spectatronics Omnisphere installation, which
requires pasting an authorization code into the application.
However, it appears that during authorization Omnisphere will attempt to read
the contents of the clipboard in order to validate the authorization code, but
upon doing so with any clipboard size that is significantly large, the
application will crash with a page fault.
Unfortunately, I cannot work around this issue as there is no option to type in
the authorization code rather than pasting it in in full.
Running the application with a small amount of text on the clipboard works
fine. I also found that simply having 500 letter 'A's on my clipboard
('AAAAA...') will also cause the application to crash, so it appears that the
characters involved does not matter - only the size of the clipboard's content
does.
Through trial and error I have found that a string of 110 A's is fine, but 111
A's on the clipboard will cause the application to crash.
--
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=45896
Bug ID: 45896
Summary: Dungeon Keeper 2 - Patch'ed v1.8 - doesn't start
Product: Wine
Version: 3.0.3
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: thomas000bauer(a)gmail.com
Distribution: ---
Hi,
i have tried to launch Dungeon Keeper 2 with the "unofficial" Patch to Version
v1.8 so the necessity of a noCD Crack is obsolete.
When i try to execute the "wine" command it takes about 4-5seconds with/and
without attached debug-log export to get me a new command line. But nothing
else happens, no Output in the Terminal no nothing.
I do as followed to launch Dungeon Keeper 2:
[code]
export WINEPREFIX="/media/daten350/games-software/wine/dungeon.keeper.2"
export
WINEDEBUG=+timestamp,+tid,+loaddll,+winediag,+synchronous,+seh,+x11drv,+xrandr
cd /media/daten350/games-software/wine/dungeon.keeper.2/drive_c/Program\ Files\
\(x86\)/Bullfrog/Dungeon\ Keeper\ 2/
wine Dkii.exe &>~/wine-vanilla-3.0.2_loaddl_wgl_log.txt
[/code]
here the Log is on Git
[url]https://gist.github.com/Phenicien/16b7fb1230df0e1becc0845351e80cdb[/url]
as well as i have attached it as a .zip file.
I already created a Form Thread
[url]https://forum.winehq.org/viewtopic.php?f=2&t=31165&sid=b68c344b875b8472…]
I'm grateful for every help or solution. Thanks
--
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=27269
Summary: Bitcoin display ugly
Product: Wine
Version: 1.3.20
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: fracting(a)gmail.com
Created an attachment (id=34876)
--> (http://bugs.winehq.org/attachment.cgi?id=34876)
Screenshot : bitcoin
1. download bitcoin
http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.3.21/bitcoi…
$ sha1sum bitcoin-0.3.21-win32-setup.exe
3f94d6a8b08c455a7886561089270247eaada7b4 bitcoin-0.3.21-win32-setup.exe
2. install with wine
3. start bitcoin
$ wine bitcoin.exe
fixme:msvcrt:_setmbcp trail bytes data not available for DBCS codepage 0 -
assuming all bytes
fixme:toolhelp:CreateToolhelp32Snapshot Unimplemented: heap list snapshot
fixme:toolhelp:Heap32ListFirst : stub
fixme:system:SetProcessDPIAware stub!
fixme:ntdll:NtLockFile I/O completion on lock not implemented yet
fixme:toolhelp:CreateToolhelp32Snapshot Unimplemented: heap list snapshot
fixme:toolhelp:Heap32ListFirst : stub
some part of bitcoin became transparent, see screenshot for details
--
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=40733
Bug ID: 40733
Summary: page fault on read access to 0x00000004 in 32-bit code
(0x007091ad).
Product: Wine
Version: 1.6.2
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: martin.suc(a)googlemail.com
Distribution: ---
Created attachment 54639
--> https://bugs.winehq.org/attachment.cgi?id=54639
backtrace of the inkscape
Crash of the inkscape application:
Unhandled exception: page fault on read access to 0x00000004 in 32-bit code
(0x007091ad).
System information:
Wine build: wine-1.6.2
Platform: i386 (WOW64)
Host system: Linux
Host version: 4.4.0-23-generic
--
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=50527
Bug ID: 50527
Summary: Dying Light shows a black screen after starting a new
game
Product: Wine
Version: 5.22
Hardware: x86-64
OS: Linux
Status: NEW
Keywords: regression
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: andrey.goosev(a)gmail.com
CC: hverbeet(a)gmail.com
Regression SHA1: 8b3cc57df0b791ca6c33f383f9358e1613206b84
Distribution: ---
Reverting the commit helps.
--
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=52292
Bug ID: 52292
Summary: Cygwin compilation fails in ld: undefined reference to
`__main' @ include/wine/test.h
Product: Wine
Version: 7.0-rc3
Hardware: x86-64
OS: other
Status: UNCONFIRMED
Severity: blocker
Priority: P2
Component: activeds
Assignee: wine-bugs(a)winehq.org
Reporter: saulius2(a)gmail.com
(This is continuation from the bug 52287)
make fails during following `winegcc` step:
--- snip ---
tools/winegcc/winegcc.exe -o dlls/activeds/tests/activeds_test.exe
--wine-objdir . -Wl,--disable-stdcall-fixup \
-fasynchronous-unwind-tables -mno-cygwin dlls/activeds/tests/activeds.o \
dlls/activeds/tests/testlist.o dlls/ole32/libole32.a
dlls/oleaut32/liboleaut32.a \
dlls/activeds/libactiveds.a dlls/winecrt0/libwinecrt0.a
dlls/msvcrt/libmsvcrt.a \
dlls/kernel32/libkernel32.a dlls/ntdll/libntdll.a
/usr/lib/gcc/i686-pc-cygwin/10/../../../../i686-pc-cygwin/bin/ld:
dlls/activeds/tests/testlist.o: in function `main':
/home/saukrs/src/wine/include/wine/test.h:669: undefined reference to `__main'
collect2: error: ld returned 1 exit status
winegcc: /usr/bin/gcc.exe failed
make: *** [Makefile:2000: dlls/activeds/tests/activeds_test.exe] Error 2
--- snip ---
--
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=52157
Bug ID: 52157
Summary: ntdll:wow64 fails on 64-bit Wine
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:wow64 fails on 64-bit Wine:
wow64.c:329: Test failed: debugging failed
wow64.c:332: Test failed: BeingDebugged is 0
wow64.c:337: Test failed: BeingDebugged is 0
https://test.winehq.org/data/patterns.html#ntdll:wow64
The timeout only happens on WoW64 wineprefixes but impacts both real machines
(cw-gtx560, cw-rx460) and VMs (notably the TestBot's debiant2 VM).
A bisect shows that this started with the commit below:
commit a041075cd2c26874757e0b6e1449c23c1326241c
Author: Alexandre Julliard <julliard(a)winehq.org>
Date: Thu Dec 2 09:59:49 2021 +0100
makefiles: Support per-platform values for EXTRADLLFLAGS.
Signed-off-by: Alexandre Julliard <julliard(a)winehq.org>
However the current thought is that the commit only revealed a preexisting bug
by changing the ntdll base address.
--
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=52144
Bug ID: 52144
Summary: Ketarin stops refreshing program window on Wine 6.22
Product: Wine
Version: 6.22
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: jim_henderson(a)sil.org
Distribution: ---
Running Ketarin 1.8.11.0 on Wine 6.22 on Lubuntu 20.04.3 LTS (64-bit)
Shows error messages as in attached file.
When I run the program it looks for updates to many software installers and
successfully downloads any updated ones, but then gets to a state where the
program fails to refresh the screen after a move or resize or xrefresh. The
Control menu (program icon at top-left corner) still works, however, and I can
use it to move the window to a different desktop or iconify or maximise the
window. Window borders appear and change size properly, but no window contents
are drawn.
The initial error messages when I run the program are attached to bug #52143.
The latest part of the error messages when this happens are shown in the
attachment to bug #52142.
Hoping someone can help me :-)
--
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.