https://bugs.winehq.org/show_bug.cgi?id=53216
Bug ID: 53216
Summary: d3d11:d3d11 - test_depth_bias() fails in the TestBot
VMs
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: ---
d3d11:d3d11 - test_depth_bias() fails in the TestBot VMs:
d3d11.c:28093: Test failed: Got depth 4.99374978e-003, expected
4.99999994e-003.
d3d11.c:28093: Test failed: Got depth 4.99374978e-003, expected
4.99999994e-003.
d3d11.c:28093: Test failed: Got depth 2.50997487e-003, expected
2.50999994e-003.
d3d11.c:28093: Test failed: Got depth 7.48750009e-003, expected
7.49999994e-003.
d3d11.c:28093: Test failed: Got depth 7.48750009e-003, expected
7.49999994e-003.
d3d11.c:28093: Test failed: Got depth 2.50997487e-003, expected
2.50999994e-003.
d3d11.c:28093: Test failed: Got depth 1.24749998e-002, expected
1.24999999e-002.
d3d11.c:28093: Test failed: Got depth 1.24749998e-002, expected
1.24999999e-002.
d3d11.c:28093: Test failed: Got depth 2.50997487e-003, expected
2.50999994e-003.
d3d11.c:28093: Test failed: Got depth 6.40899956e-001, expected
6.42500000e-001.
d3d11.c:28093: Test failed: Got depth 6.40899956e-001, expected
6.42500000e-001.
d3d11.c:28093: Test failed: Got depth 2.50997487e-003, expected
2.50999994e-003.
d3d11.c:28093: Test failed: Got depth 2.50997487e-003, expected
2.50999994e-003.
d3d11.c:28093: Test failed: Got depth 2.50997487e-003, expected
2.50999994e-003.
d3d11.c:27965: Test marked todo: Got 0xffffff00, expected 0x00ffffff at (0, 0,
0), sub-resource 0.
d3d11.c:28101: Test failed: Got value 0x14745 (4.99373704e-003), expected
0x147ae (4.99999553e-003).
d3d11.c:28101: Test failed: Got value 0x14745 (4.99373704e-003), expected
0x147ae (4.99999553e-003).
d3d11.c:28101: Test failed: Got value 0x8528f (3.25097461e-002), expected
0x85293 (3.25099845e-002).
d3d11.c:28101: Test failed: Got value 0x1eab3 (7.48747632e-003), expected
0x1eb85 (7.49999329e-003).
d3d11.c:28101: Test failed: Got value 0x1eab3 (7.48747632e-003), expected
0x1eb85 (7.49999329e-003).
d3d11.c:28101: Test failed: Got value 0x8528f (3.25097461e-002), expected
0x85293 (3.25099845e-002).
d3d11.c:28101: Test failed: Got value 0x33190 (1.24750145e-002), expected
0x33333 (1.24999888e-002).
d3d11.c:28101: Test failed: Got value 0x33190 (1.24750145e-002), expected
0x33333 (1.24999888e-002).
d3d11.c:28101: Test failed: Got value 0x8528f (3.25097461e-002), expected
0x85293 (3.25099845e-002).
d3d11.c:28101: Test failed: Got value 0xa41204 (6.40899935e-001), expected
0xa47ae1 (6.42500022e-001).
d3d11.c:28101: Test failed: Got value 0xa41204 (6.40899935e-001), expected
0xa47ae1 (6.42500022e-001).
d3d11.c:28101: Test failed: Got value 0x8528f (3.25097461e-002), expected
0x85293 (3.25099845e-002).
d3d11.c:28101: Test failed: Got value 0x8528f (3.25097461e-002), expected
0x85293 (3.25099845e-002).
d3d11.c:28101: Test failed: Got value 0x8528f (3.25097461e-002), expected
0x85293 (3.25099845e-002).
d3d11.c:28110: Test failed: Got value 0x28e (9.97940032e-003), expected 0x290
(1.00099184e-002).
d3d11.c:28110: Test failed: Got value 0x28e (9.97940032e-003), expected 0x290
(1.00099184e-002).
d3d11.c:28110: Test failed: Got value 0x331 (1.24666209e-002), expected 0x334
(1.25123980e-002).
d3d11.c:28110: Test failed: Got value 0x331 (1.24666209e-002), expected 0x334
(1.25123980e-002).
d3d11.c:28110: Test failed: Got value 0x476 (1.74258030e-002), expected 0x47b
(1.75020981e-002).
d3d11.c:28110: Test failed: Got value 0x476 (1.74258030e-002), expected 0x47b
(1.75020981e-002).
d3d11.c:28110: Test failed: Got value 0xa411 (6.40894179e-001), expected 0xa47a
(6.42496376e-001).
d3d11.c:28110: Test failed: Got value 0xa411 (6.40894179e-001), expected 0xa47a
(6.42496376e-001).
https://test.winehq.org/data/patterns.html#d3d11:d3d11
These failures:
* Don't happen on Debian 11 + Intel / KDE
* Happen on Debian 11 + QXL + single-monitor
* Happen on Debian 11 + QXL + multi-monitor
* Don't happen on Debian Testing + QXL + multi-monitor
So they are probably caused by some bug in the Debian 11 QXL support.
Note that despite being systematic these failures could cause false positives
due to the test multi-threading (see bug 53212).
--
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=48247
Bug ID: 48247
Summary: Darksiders 2 (GOG) crashes after intro
Product: Wine-staging
Version: 4.20
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: fzielcke(a)z-51.de
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
Created attachment 65912
--> https://bugs.winehq.org/attachment.cgi?id=65912
log + crash dump with wine-4.20 (staging)
Darksiders 2 directly crashes after the intro.
This is on Debian unstable with the official winehq-staging 4.20 packages for
bullseye
--
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=54642
Bug ID: 54642
Summary: Page fault on read access to 0x0000
Product: Wine-staging
Version: 8.3
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: santafejayyt(a)gmail.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
Created attachment 74172
--> https://bugs.winehq.org/attachment.cgi?id=74172
Wine debugger backtrace on game start
I'm attempting to run Konami's E-Amusement Cloud Sound Voltex Exceed Gear game,
and the launcher and its components work fine, however when attempting to
launch the game, the window opens, but the game does not start, and stays on a
black screen. I have installed the required dependencies for the game via
winetricks (DXVK / D3DX9, FAudio, & XACT).
--
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=54183
Bug ID: 54183
Summary: wineserver crash when running d3d9:visual
Product: Wine
Version: 8.0-rc1
Hardware: x86-64
OS: Linux
Status: NEW
Keywords: testcase
Severity: normal
Priority: P2
Component: wineserver
Assignee: wine-bugs(a)winehq.org
Reporter: z.figura12(a)gmail.com
CC: rbernon(a)codeweavers.com
Distribution: ---
d3d9:visual on this machine breaks somewhere in the middle, apparently while
trying to do mode switches, and leaves the display switched off. Not sure what
triggers it exactly; I've certainly had working runs on other machines. What's
important is that then when d3d9_test.exe exits, it triggers a wined3d crash.
Simple tl;dr version is that set_cursor_pos gets triggered not from a client
request, and tries to access current->process, which crashes.
The backtrace is:
Core was generated by `/home/elizabeth/git/wine64/loader/../server/wineserver
-d'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x00005598e8b43ac0 in set_cursor_pos (desktop=desktop@entry=0x5598ea1ce5d0,
x=32767, y=32767) at ../wine/server/queue.c:427
427 if ((device = current->process->rawinput_mouse) && (device->flags &
RIDEV_NOLEGACY))
(gdb) bt
#0 0x00005598e8b43ac0 in set_cursor_pos (desktop=desktop@entry=0x5598ea1ce5d0,
x=32767, y=32767) at ../wine/server/queue.c:427
#1 0x00005598e8b43c7b in set_clip_rectangle
(desktop=desktop@entry=0x5598ea1ce5d0, rect=rect@entry=0x0,
send_clip_msg=send_clip_msg@entry=1) at ../wine/server/queue.c:476
#2 0x00005598e8b43da1 in set_foreground_input (input=0x0,
desktop=0x5598ea1ce5d0) at ../wine/server/queue.c:483
#3 set_foreground_input (input=0x0, desktop=0x5598ea1ce5d0) at
../wine/server/queue.c:480
#4 thread_input_destroy (obj=0x5598ea1ba430) at ../wine/server/queue.c:1106
#5 0x00005598e8b3b144 in release_object (ptr=0x5598ea1ba430) at
../wine/server/object.c:451
#6 release_object (ptr=0x5598ea1ba430) at ../wine/server/object.c:440
#7 0x00005598e8b43800 in msg_queue_destroy (obj=0x5598ea1ae4d0) at
../wine/server/queue.c:1077
#8 0x00005598e8b3b144 in release_object (ptr=0x5598ea1ae4d0) at
../wine/server/object.c:451
#9 release_object (ptr=ptr@entry=0x5598ea1ae4d0) at
../wine/server/object.c:440
#10 0x00005598e8b3224e in release_object_from_handle (obj=0x5598ea1ae4d0) at
../wine/server/handle.c:115
#11 handle_table_destroy (obj=0x5598ea1d3810) at ../wine/server/handle.c:185
#12 0x00005598e8b3b144 in release_object (ptr=0x5598ea1d3810) at
../wine/server/object.c:451
#13 release_object (ptr=0x5598ea1d3810) at ../wine/server/object.c:440
#14 0x00005598e8b3260f in close_process_handles
(process=process@entry=0x5598ea1ce7a0) at ../wine/server/handle.c:197
#15 0x00005598e8b3d990 in process_killed (process=0x5598ea1ce7a0) at
../wine/server/process.c:970
#16 remove_process_thread (process=0x5598ea1ce7a0,
thread=thread@entry=0x5598ea1d4020) at ../wine/server/process.c:1020
#17 0x00005598e8b5b37f in kill_thread (thread=0x5598ea1d4020,
violent_death=<optimized out>, violent_death@entry=0) at
../wine/server/thread.c:1294
#18 0x00005598e8b3dcb0 in kill_process (violent_death=0,
process=0x5598ea1ce7a0) at ../wine/server/process.c:1077
#19 kill_process (process=0x5598ea1ce7a0, violent_death=<optimized out>) at
../wine/server/process.c:1058
#20 0x00005598e8b2d587 in fd_poll_event (event=<optimized out>, fd=<optimized
out>) at ../wine/server/fd.c:542
#21 main_loop_epoll () at ../wine/server/fd.c:636
#22 0x00005598e8b2d7ee in main_loop () at ../wine/server/fd.c:992
#23 0x00005598e8b1ea7d in main (argc=2, argv=0x7ffd26625e48) at
../wine/server/main.c:237
Rémi, do you have any immediate insight on what we should be doing here?
--
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=16552
Summary: CreateIoCompletionPort fails in Chromium unit tests
Product: Wine
Version: 1.1.10
Platform: Other
URL: http://chromium.org
OS/Version: other
Status: NEW
Keywords: download, source
Severity: normal
Priority: P2
Component: wineserver
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: dank(a)kegel.com
http://src.chromium.org/viewvc/chrome/trunk/src/base/message_pump_win.cc
contains the code
port_.Set(CreateIoCompletionPort(INVALID_HANDLE_VALUE, NULL, NULL, 1));
DCHECK(port_.IsValid());
...
HANDLE port = CreateIoCompletionPort(file_handle, port_, key, 1);
DCHECK(port == port_.Get());
The DCHECK fires when running one of the Chromium unit tests:
wine Debug/ui_tests.exe
...
001b:Call KERNEL32.CreateFileW(00ed7208
L"\\\\.\\pipe\\chrome.ChromeTestingInterface:8.1",c0000000,00000000,00000000,00000003,40110000,00000000)
ret=010e0220
001b:Ret KERNEL32.CreateFileW() retval=000000c0 ret=010e0220
...
0021:Call KERNEL32.CreateIoCompletionPort(ffffffff,00000000,00000000,00000001)
ret=01a304b3
0021:Ret KERNEL32.CreateIoCompletionPort() retval=000000c8 ret=01a304b3
0021:Call KERNEL32.CreateIoCompletionPort(000000c0,000000c8,00ed5aa0,00000001)
ret=01a30760
trace:ntdll:NtSetInformationFile
(0xc0,0x7cdee318,0x7cdee320,0x00000008,0x0000001e)
0021:Ret KERNEL32.CreateIoCompletionPort() retval=00000000 ret=01a30760
0021:Call KERNEL32.OutputDebugStringA(00ed95a8
"[26:33:1249:FATAL:message_pump_win.cc(428)] Check failed: port == port_.Get().
\r\n") ret=019a7af3
I think it's failing in wineserver for some reason during NtSetInformationFile
in set_completion_info.
--
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=52792
Bug ID: 52792
Summary: Error messages for invalid .exe files could be
improved
Product: Wine
Version: 7.6
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: wineserver
Assignee: wine-bugs(a)winehq.org
Reporter: aros(a)gmx.com
Distribution: ---
Trying to run a 0 byte .exe file under Wine will get you this:
Application could not be started, or no application associated with the
specified file.
ShellExecuteEx failed: File not found.
This doesn't look correct.
--
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=48004
Bug ID: 48004
Summary: winserver memory overflow
Product: Wine
Version: 4.0.2
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: wineserver
Assignee: wine-bugs(a)winehq.org
Reporter: heiko(a)stark-jena.de
Distribution: ---
with default and 'wineserver -d2 -f -p10' settings
I run simulations with the software Opensim (https://opensim.stanford.edu/) and
restart the Opensim one after the other with a script. This seems to cause a
memory overflow (> 64 GB).
Kill wineserver helps to fix the memory overflow.
Is there a way to debug this?
Best regards,
Heiko
--
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=52716
Bug ID: 52716
Summary: Sending key stroke (using
[System.Windows.Forms.SendKeys]::SendWait) fails
(seems to go into a loop?)
Product: Wine
Version: 7.4
Hardware: x86-64
URL: https://github.com/PowerShell/PowerShell/releases/down
load/v7.0.3/PowerShell-7.0.3-win-x64.msi
OS: Linux
Status: NEW
Keywords: dotnet, download
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: xerox.xerox2000x(a)gmail.com
Distribution: ---
Created attachment 72077
--> https://bugs.winehq.org/attachment.cgi?id=72077
ps script
Hi, I have a powershell script where I need to send a keystroke to a program.
I found code snippet on the internet and made little script that I tested in
windows (using powershell core) and it works.
It sends ctrp^p to notepad, and that opens the printer-dialog correctly on
windows.
On wine however it doesn`t work, cpu-usage goes up so it seems to get into
loop(???)
Script (also see attachment):
###################################################################
Start-Process "notepad.exe"
Sleep 3
$WindowHandle = Get-Process | Where-Object { $_.MainWindowTitle -Match
"Notepad" } | Select-Object -ExpandProperty MainWindowHandle
[void][System.Reflection.Assembly]::LoadWithPartialName('System.Windows.Forms')
[System.Windows.Forms.SendKeys]::SendWait("^{p}")
#####################################################################
Steps to reproduce:
1. winetricks -q dotnet48
2. wget
https://github.com/PowerShell/PowerShell/releases/download/v7.0.3/PowerShel…
3. wine PowerShell-7.0.3-win-x64.msi
4. Save the script from attachment as a.ps1 in current folder
5. wine pwsh -file ./a.ps1
Notepad opens but nothing really happens and cpu-usage goes up
--
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=53213
Bug ID: 53213
Summary: d3d11:d3d11 - test_texture() fails in the TestBot VMs
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: ---
d3d11:d3d11 - test_texture() fails in the TestBot VMs:
d3d11.c:9837: Test failed: Test 60: Got unexpected color 0xff0000ff at (0, 0).
d3d11.c:9837: Test failed: Test 60: Got unexpected color 0xff00ffff at (1, 0).
d3d11.c:9837: Test failed: Test 60: Got unexpected color 0xff00ff00 at (2, 0).
d3d11.c:9837: Test failed: Test 60: Got unexpected color 0xffffff00 at (3, 0).
d3d11.c:9837: Test failed: Test 60: Got unexpected color 0xffff0000 at (0, 1).
d3d11.c:9837: Test failed: Test 60: Got unexpected color 0xffff00ff at (1, 1).
d3d11.c:9837: Test failed: Test 60: Got unexpected color 0xff000000 at (2, 1).
d3d11.c:9837: Test failed: Test 60: Got unexpected color 0xff7f7f7f at (3, 1).
d3d11.c:9837: Test failed: Test 60: Got unexpected color 0xffffffff at (0, 2).
d3d11.c:9837: Test failed: Test 60: Got unexpected color 0xffffffff at (1, 2).
d3d11.c:9837: Test failed: Test 60: Got unexpected color 0xffffffff at (2, 2).
d3d11.c:9837: Test failed: Test 60: Got unexpected color 0xff000000 at (3, 2).
d3d11.c:9837: Test failed: Test 60: Got unexpected color 0xffffffff at (0, 3).
d3d11.c:9837: Test failed: Test 60: Got unexpected color 0xff000000 at (2, 3).
d3d11.c:9837: Test failed: Test 60: Got unexpected color 0xff000000 at (3, 3).
https://test.winehq.org/data/patterns.html#d3d11:d3d11
These failures don't happen on my box which has an Intel graphics card instead
of QEmu's QXL graphics card.
Note also that these failures still happen on my debian11 VM which has a single
monitor instead of the TestBot VMs' multi-monitor setup.
So this seems to be related to the VMs QXL GPU.
Note that despite being systematic these failures could cause false positives
(see bug 53212).
--
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=54519
Bug ID: 54519
Summary: d3d9:visual - test_mipmap_upload() fails on AMD and
Nvidia GPUs
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: d3d
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
d3d9:visual - test_mipmap_upload() fails on AMD and Nvidia GPUs.
This impacts three VMs:
fgtb-w10pro64_rx550 (AMD RX550):
visual.c:27986: Test failed: pool 0x2: level 0: Got unexpected color
0x00000000.
visual.c:27986: Test failed: pool 0x2: level 1: Got unexpected color
0x00000000.
visual.c:27986: Test failed: pool 0x2: level 2: Got unexpected color
0x00000000.
visual.c:27986: Test failed: pool 0x2: level 3: Got unexpected color
0x00000000.
visual.c:27986: Test failed: pool 0x2: level 4: Got unexpected color
0x00000000.
visual.c:27986: Test failed: pool 0x2: level 5: Got unexpected color
0x00000000.
w11pro64_amd (AMD RX660):
visual.c:404: Test failed: pool 0x2: level 0: Got hr 0x80004005.
visual.c:27986: Test failed: pool 0x2: level 0: Got unexpected color
0x00ff0000.
visual.c:404: Test failed: pool 0x2: level 1: Got hr 0x80004005.
visual.c:27986: Test failed: pool 0x2: level 1: Got unexpected color
0x00ff0000.
visual.c:404: Test failed: pool 0x2: level 2: Got hr 0x80004005.
visual.c:27986: Test failed: pool 0x2: level 2: Got unexpected color
0x00ff0000.
visual.c:404: Test failed: pool 0x2: level 3: Got hr 0x80004005.
visual.c:27986: Test failed: pool 0x2: level 3: Got unexpected color
0x00ff0000.
visual.c:404: Test failed: pool 0x2: level 4: Got hr 0x80004005.
visual.c:27986: Test failed: pool 0x2: level 4: Got unexpected color
0x00ff0000.
visual.c:404: Test failed: pool 0x2: level 5: Got hr 0x80004005.
visual.c:27986: Test failed: pool 0x2: level 5: Got unexpected color
0x00ff0000.
w11pro64_nv (NVIDIA RTX3050):
visual.c:195: pool 0x2: level 0: Can't create an offscreen plain surface to
read the render target data, hr 0x80004005.
visual.c:27986: Test failed: pool 0x2: level 0: Got unexpected color
0x00adbeef.
visual.c:27986: Test failed: pool 0x2: level 1: Got unexpected color
0x00000000.
visual.c:195: pool 0x2: level 2: Can't create an offscreen plain surface to
read the render target data, hr 0x80004005.
visual.c:27986: Test failed: pool 0x2: level 2: Got unexpected color
0x00adbeef.
visual.c:195: pool 0x2: level 3: Can't create an offscreen plain surface to
read the render target data, hr 0x80004005.
visual.c:27986: Test failed: pool 0x2: level 3: Got unexpected color
0x00adbeef.
visual.c:195: pool 0x2: level 4: Can't create an offscreen plain surface to
read the render target data, hr 0x80004005.
visual.c:27986: Test failed: pool 0x2: level 4: Got unexpected color
0x00adbeef.
visual.c:195: pool 0x2: level 5: Can't create an offscreen plain surface to
read the render target data, hr 0x80004005.
visual.c:27986: Test failed: pool 0x2: level 5: Got unexpected color
0x00adbeef.
See https://test.winehq.org/data/patterns.html#d3d9:visual
These failures all started on 2023-01-06 and a bisect shows that, on all three
machines, they started with the commit below:
commit 2954d3e4a23025657740fb178ddbe110890c0cc8
Author: Zebediah Figura <zfigura(a)codeweavers.com>
Date: Tue Dec 20 17:43:39 2022 -0600
d3d9/tests: Test uploading the whole mipmap chain in one map.
Signed-off-by: Zebediah Figura <zfigura(a)codeweavers.com>
--
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=54399
Bug ID: 54399
Summary: d3d11:d3d11 - test_vertex_formats() fails on Windows
11 + AMD
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: d3d
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
d3d11:d3d11 - test_vertex_formats() fails on Windows 11 + AMD:
d3d11.c:34906: Test failed: Format 0x58: Got {3.96078438e-001, 2.62745112e-001,
1.29411772e-001, 1.42236653e-019}, expected {3.96078438e-001, 2.62745112e-001,
1.29411772e-001, 1.00000000e+000} at (0, 0), sub-resource 0.
See w11pro64-amd in https://test.winehq.org/data/patterns.html#d3d11:d3d11
The failures started on 2023-01-24, that is on the date the test was added by
this commit:
commit dc19f5c517af5d04bebb4f26bd79220b02f1ba64
Author: Zebediah Figura <zfigura(a)codeweavers.com>
AuthorDate: Wed Jan 11 19:25:11 2023 -0600
d3d11/tests: Add a basic test for vertex 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.
https://bugs.winehq.org/show_bug.cgi?id=53218
Bug ID: 53218
Summary: d3d10core:d3d10core - test_uint_shader_instructions()
fails in the TestBot VMs
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: ---
d3d10core:d3d10core - test_uint_shader_instructions() fails in the TestBot VMs:
d3d10core.c:13215: Test failed: Got {0x80000000, 0x00000000, 0x00000000,
0x00000000}, expected {0x00000000, 0xffffffff, 0x00000000, 0x00000000} at (0,
0), sub-resource 0.
d3d10core.c:13215: Test failed: Got {0x00000000, 0x80000000, 0x00000000,
0x00000000}, expected {0xffffffff, 0x00000000, 0x00000000, 0x00000000} at (0,
0), sub-resource 0.
d3d10core.c:13215: Test failed: Got {0xffffffff, 0x00000001, 0x00000000,
0x00000000}, expected {0x00000000, 0x00000001, 0x00000000, 0x00000000} at (0,
0), sub-resource 0.
d3d10core.c:13215: Test failed: Got {0x00000001, 0xffffffff, 0x00000000,
0x00000000}, expected {0x00000001, 0x00000000, 0x00000000, 0x00000000} at (0,
0), sub-resource 0.
https://test.winehq.org/data/patterns.html#d3d10core:d3d10core
These failures:
* Don't happen on Debian 11 + Intel / KDE
* Happen on Debian 11 + QXL + single-monitor
* Happen on Debian 11 + QXL + multi-monitor
* Happen on Debian Testing + QXL + multi-monitor (it actually has a couple
extra)
So they are probably related to QXL.
Note that despite being systematic these failures could cause false positives
due to the test multi-threading (see bug 53212).
--
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=53522
Bug ID: 53522
Summary: Need for Speed III: joystick doesn't work after evdev
removal
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: dinput
Assignee: wine-bugs(a)winehq.org
Reporter: DirtY.iCE.hu(a)gmail.com
CC: rbernon(a)codeweavers.com
Regression SHA1: adfee25b45af8160848f94fdb24279d63d5f91f4
Distribution: Gentoo
Created attachment 72888
--> https://bugs.winehq.org/attachment.cgi?id=72888
WINEDEBUG=+dinput, ds4 usb, overriden, nfs3 demo with git master wine
I decided to try NFS3 after some time and realized that joystick no longer
works with newer releases. Git bisect lead me to commit
adfee25b45af8160848f94fdb24279d63d5f91f4, where the evdev and js backends were
removed. With the new backend, in NFS3 deadzone calibration screen, all axes
are at constant 0, and it doesn't respond to any keypress either. I've tried it
with DualShock 4 (both usb and bt), DS3 (only usb), and some noname cheap
controller, the same results. Interestingly, in joy.cpl the joysticks do work,
I've tried to click on override to move the controller from the xinput to the
non-xinput list, but no change. I also have no force-feedback support with the
new backend.
Tested it with the retail version of nfs3 and also with this patch, the results
are the same: https://veg.by/en/projects/nfs3/
Also tested it with the demo version and the latest git
(bfc73b0b80a1da2b137b5da4a2fcf530ee3a9d7d), same results.
1. Download demo from here: https://archive.org/details/nfs3_demo
2. Create a new 32-bit wine prefix (I've only compiled a 32-bit wine)
3. In winecfg, set windows compatibility to 98 (otherwise the install refuses
to start), go to drives and add a (fake) cdrom device (otherwise setup refuses
to start), and probably you should set a virtual desktop (the game likes to
mess with your resolution)
4. Run setup.exe (it will throw a registry error but still installs the game)
5. Start the game with taskset: `taskset -c 0 path/to/wine nfs3demo -d3d0` (the
game crashes/freezes if run on multicore cpu)
6. After the race countdown, press esc, controls, and try to bind some keys or
click on dead zone to see axes values.
I'm attaching a log with WINEDEBUG=+dinput and overridden joystick on joy.cpl.
--
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=49988
Bug ID: 49988
Summary: NosTale (and probably some other games) doesn't handle
mouse clicks correctly
Product: Wine
Version: 5.19
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: theszczepancio(a)gmail.com
Distribution: ---
Created attachment 68390
--> https://bugs.winehq.org/attachment.cgi?id=68390
Wine-staging 5.19 log
Releated issues:
https://bugs.winehq.org/show_bug.cgi?id=42999https://bugs.winehq.org/show_bug.cgi?id=21739
Some info:
Tested the issue with wine and wine-staging.
Bug persists in 5.17, 5.18, 5.19 versions of wine.
I have installed Arch Linux on r5 3600/rx5700 XT.
I use D9VK (newest) for improvements of performance.
Installing dinput8 is not fixing anything.
I use Sway/wlroots on wayland, also I own newest kernel.
Game works as should on steam proton with same version of D9VK.
OpenGL backend works fine.
Wine log in attachement.
--
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=52444
Bug ID: 52444
Summary: Regression prevent eclipse from hitting breakpoints
Product: Wine
Version: 7.0-rc6
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: dark.shadow4(a)web.de
Distribution: ---
I usually use eclipse with normal gdb for debugging. For that I compile without
mingw, since it doesn't find the symbols when using real dlls.
Since a while this is broken, and eclipse doesn't hit any breakpoints anymore.
Bisected to
commit 28fe84da45bea7de56539b50eac8ebcec54342de
Author: Alexandre Julliard <julliard(a)winehq.org>
Date: Wed Mar 24 10:53:53 2021 +0100
ntdll: Load the main image from the Unix side.
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=47848
Bug ID: 47848
Summary: Graphical glitches in "The suffering" game
Product: Wine
Version: 4.0
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-d3dx9
Assignee: wine-bugs(a)winehq.org
Reporter: inferrna(a)gmail.com
Distribution: ---
Created attachment 65353
--> https://bugs.winehq.org/attachment.cgi?id=65353
wine 1.5.17, good
My system is Ubuntu 18.04.2
RX560 on Mesa 19.08
Last good wine version for this game is 1.5.17. Starting from 1.5.18 3D not
shown, just HUD over black screen. But in some of later versions (somewhere
between 1.7 and 2.0) bug was kind of half-fixed, at least starting from 2.0 3D
is not all black, bus only some planes - floor, for example. Unfortunately I
can't test versions between 1.7 and 2.0 because it this versions game just not
fails to start with "X Error of failed request: BadWindow (invalid Window
parameter)".
--
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=19534
Summary: Office 2007 menu button loses focus
Product: Wine
Version: 1.1.11
Platform: PC
OS/Version: Linux
Status: NEW
Severity: trivial
Priority: P3
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: kennybobs(a)o2.co.uk
Created an attachment (id=22740)
--> (http://bugs.winehq.org/attachment.cgi?id=22740)
wine-1.1.26-231-gfe9d360 console output
I can't take a screenshot because it also loses focus, so I hope this makes
sense.
The Office 2007 apps have had their sensible menus replaced with a button in
the top left of the window.
The problem occurs when hovering over one option (say Send) so that it's
sub-menu opens, then moving the cursor over to another menu option (say Print).
The menu closes. This doesn't happen under Windows.
Tested Excel and Word. Can't really test the other apps as they have their own
problems preventing them from starting.
Nothing new is printed in the console when this happens, but log attached.
Went back to Wine 1.1.11 to check for a recent regression but problem occurs
there too. Same in latest git.
--
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=32206
Bug #: 32206
Summary: Primer Premier 6.12 doesn't draw its UI
Product: Wine
Version: 1.5.17
Platform: x86
URL: http://www.premierbiosoft.com/DATAFILES/PP612Installer
Win32.exe
OS/Version: Linux
Status: NEW
Keywords: download
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: fracting(a)gmail.com
Classification: Unclassified
Created attachment 42481
--> http://bugs.winehq.org/attachment.cgi?id=42481
Screenshot: primer premier 6.12 doesn't draw its UI
1. install Primer Premier
$ wine PP612InstallerWin32.exe
2. start
$ cd ~/.wine/drive_c/Program\ Files/Primer\ Premier\ 6.12
$ wine Primer\ Premier\ 6.exe
Expect result:
The UI should be draw completed as Screenshot:
primer-premier-6-with-workaround.png
Actual result:
The UI doesn't draw at first, if you move the mouse onto Primer Premier, then
some parts of the UI draws but still not complete.
See screenshot primer-premier-doesnt-draw.png
Workaround:
Setting a virtual desktop, start Primer Premier, carefully move the mouse onto
the title bar of Primer Premier.
fixme:win:EnumDisplayDevicesW ((null),0,0x30e850,0x00000000), stub!
fixme:win:EnumDisplayDevicesW ((null),1,0x30e850,0x00000000), stub!
fixme:ddraw:DirectDrawEnumerateExA flags 0x00000001 not handled
fixme:win:EnumDisplayDevicesW ((null),0,0x31f444,0x00000000), stub!
fixme:win:EnumDisplayDevicesW ((null),0,0x31f6b4,0x00000000), stub!
fixme:font:freetype_SelectFont Untranslated charset 255
fixme:imm:ImmGetOpenStatus (0x4452438): semi-stub
fixme:imm:ImeHandleNotify WM_IME_NOTIFY:IMN_SETCOMPOSITIONWINDOW
fixme:imm:ImeHandleNotify WM_IME_NOTIFY:IMN_SETCOMPOSITIONWINDOW
err:ole:CoReleaseMarshalData IMarshal::ReleaseMarshalData failed with error
0x8001011d
--
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=23008
Summary: winhelp: Popups disappear immediately and are the
wrong size
Product: Wine
Version: 1.2-rc2
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: markk(a)clara.co.uk
Created an attachment (id=28516)
--> (http://bugs.winehq.org/attachment.cgi?id=28516)
ONLCFG.HLP compressed with bzip2
Links in help files which open pop-ups are broken in Wine winhlp32. (These
links typically appear in green with a dotted underline.)
What should happen: the popup appears when the link is clicked, and remains
present when the user releases the mouse button.
What actually happens: the popup appears, but vanishes when the user releases
the mouse button. The popup is the wrong size, and has scrollbars on the right
and bottom edges. (It's impossible to use the scrollbars since the popup
disappears when the button is released.) Some popups have text missing.
Example:
Open the attached ONLCFG.HLP file in Wine winhlp32. Click "How do I?". Click
"Letting your Intuit software ...". Click each of the underlined links: dial
type, dialing prefix and disable call waiting. Notice there is no text other
than the heading in the dialing prefix and disable call waiting popups. Click
Tell me more. The popup which appears contains links to other pages in the help
file, but it's impossible to select them due to the popup vanishing on mouse
release.
Compare with using winhlp32.exe from Windows under Wine to view that file.
--
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=41345
Bug ID: 41345
Summary: One Way Heroics: music does not play while in the game
Product: Wine
Version: 1.9.18
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: fjfrackiewicz(a)gmail.com
Distribution: ---
Created attachment 55694
--> https://bugs.winehq.org/attachment.cgi?id=55694
Terminal output Wine 1.9.18 launching and playing the game
One Way Heroics does not play any music while actually playing the game. The
game's music is played while in the main menu or any other screen except for
the actual game.
Terminal output attached.
--
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=48687
Bug ID: 48687
Summary: Wont run Acwebbrowser.exe has encountered a serious
problem and needs to be closed
Product: Wine
Version: 4.0
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: dmiller45383(a)gmail.com
Distribution: ---
Created attachment 66552
--> https://bugs.winehq.org/attachment.cgi?id=66552
Error text
It will not run Autodesk app
--
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=45670
Bug ID: 45670
Summary: WeChat requires explicitly setting locale for Chinese
to be displayed.
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: lockywolf(a)gmail.com
Distribution: ---
So I'm trying to run WeChat on Wine.
If all required configuration steps are performed (such as installing the
native riched), I can run it almost flawlessly with the following command-line:
LC_ALL=zh_CN.utf8 wine WeChat.exe
If the locale is not set, then WeChat displays Chinese characters as tofu.
On Windows, however, there is not need to run WeChat through AppLocale, or,
basically, set the locale in any way, WeChat still runs fine, displaying all
Chinese needed.
There should be some way to avoid explicitly setting locale when running
WeChat.
--
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=46374
Bug ID: 46374
Summary: GUI Crash when starting Positive Grid BIAS FX -
CefSubprocess.exe
Product: Wine
Version: 4.0-rc3
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: other(a)jan-feld.de
Distribution: ---
Created attachment 63116
--> https://bugs.winehq.org/attachment.cgi?id=63116
Crash-Log from Positive Grid BIAS FX GUI-Crash.
When starting Positive Grids BIAS FX wine/the GUI crashes in
"CefSubprocess.exe".
I can get sounds out of it even after the crash. When i start it with Carlas
Bridge-Mode i can even modify some of its parameters but i still can't get no
GUI to modify it like it should be. It seems to have some problems with some
GUI components when using libcef.
System:
Arch Linux 4.19.12
Wine 4.0-rc3
Crash-Log attached below.
--
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=42334
Bug ID: 42334
Summary: Worms World Party from Steam shows black square for a
few seconds and does not start
Product: Wine
Version: 2.0
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: amarel(a)amarel.info
Distribution: ---
Created attachment 57096
--> https://bugs.winehq.org/attachment.cgi?id=57096
winedbg log
Worms World Party from Steam shows black square for a few seconds and does not
start. Tested on wine 1.6 and wine staging 2.0. Debug log included.
--
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.