https://bugs.winehq.org/show_bug.cgi?id=55031
Bug ID: 55031
Summary: experimental wow64 mode: crashes in some 3d graphics
code
Product: Wine
Version: 8.10
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: idarktemplar(a)mail.ru
Distribution: ---
Created attachment 74591
--> https://bugs.winehq.org/attachment.cgi?id=74591
wine.crash.log
When I'm trying to run Spellforce 2 with experimental wow64 wine mode, it
crashes. When I'm running it using normal multilib setup, everything runs fine,
at least until main menu, didn't check again further.
Same happens when I'm trying to run Torchlight 2 from Steam. Demo available on:
https://store.steampowered.com/app/200710/Torchlight_II/
Crashing wine build options: ./configure --with-mingw
--enable-archs='i386,x86_64' --prefix=/tmp/wineinstall
Suspicious log lines just before crash:
0114:fixme:opengl:wow64_map_buffer GL_MAP_PERSISTENT_BIT not supported!
wine: Unhandled page fault on write access to 5BFFF000 at address 6AB23144
(thread 0114), starting debugger...
OS: Gentoo Linux amd64 (64bit)
Graphics: X11
Videocard information:
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: Quadro K1000M/PCIe/SSE2
OpenGL core profile version string: 4.6.0 NVIDIA 470.182.03
OpenGL core profile shading language version string: 4.60 NVIDIA
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
--
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=55597
Bug ID: 55597
Summary: Second desktop slows running Planet of Lana
Product: Wine
Version: 8.0.2
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: stephematician(a)gmail.com
Distribution: ---
Created attachment 75129
--> https://bugs.winehq.org/attachment.cgi?id=75129
Short version of log from running program "Planet of Lana"
A second monitor/desktop, plugged in to my laptop via HDMI, slows down
considerably when running Planet of Lana. The laptop monitor/desktop and the
game itself (windowed) appear to run at a normal speed.
This issue is _not_ observed when running the Steam version of the game (using
Proton 8.0.2).
I am using UbuntuMATE 22.04 (X11/LightDM). I have an on-board and NVIDIA
graphics controller, using the NVIDIA 535.86.05 driver.
lspci | grep VGA
01:00.0 VGA compatible controller: NVIDIA Corporation TU106M [GeForce RTX
2060 Max-Q] (rev a1)
05:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI]
Renoir (rev c5)
Logs when running one vs two monitors do not appear materially different, e.g.
# unplug second monitor
wine Planet\ of\ Lana.exe 1&>2 2>one_monitor.log
# plug second monitor in
wine Planet\ of\ Lana.exe 1&>2 2>two_monitor.log
# trim log
sed -r '/semi-stub|stub!/d' one_monitor.log | sed 's/[0-9A-F]\{16\}/HEX/g'
\
| sed 's/^[0-9a-fA-F]\{4\}:/HEX:/g' > one_monitor_trim.log
sed -r '/semi-stub|stub!/d' two_monitor.log | sed 's/[0-9A-F]\{16\}/HEX/g'
\
| sed 's/^[0-9a-fA-F]\{4\}:/HEX:/g' > two_monitor_trim.log
diff one_monitor_trim.log two_monitor_trim.log
# no difference
Attached the (trimmed) one-monitor log for reference.
--
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=55546
Bug ID: 55546
Summary: wine 8.15 breaks with upgrading alsa-lib from 1.2.9 to
1.2.10
Product: Wine
Version: 8.15
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: karabaja4(a)gmail.com
Distribution: ---
Upgrading these packages on Arch:
* alsa-lib (1.2.9-1 -> 1.2.10-1)
* lib32-alsa-lib (1.2.9-1 -> 1.2.10-1)
breaks any Wine game with a sound when using pure ALSA (no pulseaudio, no
pipewire).
The game does not start, and this is the error message from wine output when
trying to run the game:
"Assertion failed: !status, file ../wine/dlls/mmdevapi/mmdevapi_private.h, line
69"
Tested with games:
* Project Diablo 2
* World Of Warcraft Vanilla 1.12.
Using Wine 8.15.
Regards,
Igor
--
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=55539
Bug ID: 55539
Summary: user32:msg test_hvredraw fails in win1709 with
unexpected region
Product: Wine
Version: 8.15
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: user32
Assignee: wine-bugs(a)winehq.org
Reporter: madewokherd(a)gmail.com
Distribution: ---
win1709_newtb-w1064v1709-64 now consistently fails in test_hvredraw with
mismatched regions. This failure appears to have been introduced by
https://gitlab.winehq.org/wine/wine/-/commit/fa038c3c3714cd1293e4de6aad44c1…,
as it was the only change when this test started failing.
There are 34 total failures that look somewhat like this:
msg.c:9655: Test failed: SimpleWindowClassWithHRedraw 00cf0000 SetWindowPos
redraw #1 (0, 0, 50, 0): Update region shall match expected region
msg.c:9655: Test failed: SimpleWindowClassWithHRedraw 00cf0000 SetWindowPos
redraw #2 (0, 0, 50, 50): Update region shall match expected region
msg.c:9655: Test failed: SimpleWindowClassWithHRedraw 00cf0000 SetWindowPos
redraw #3 (0, 0, -50, -50): Update region shall match expected region
msg.c:9655: Test failed: SimpleWindowClassWithHRedraw 00cf0000 SetWindowPos
redraw #5 (-50, -50, 50, 0): Update region shall match expected region
I did a test run with some traces, and it seems the actual update region always
matches the window's visible area. It's not clear to me why running the test in
a temporary desktop would cause this.
--
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=55533
Bug ID: 55533
Summary: setupapi:devinst - test_class_installer() fails on
Windows 7+ and Wine
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: setupapi
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
setupapi:devinst - test_class_installer() fails on Windows 7+ and Wine:
devinst.c:2754: Test failed: Failed to call class installer, error 0xe000020e.
devinst.c:2756: this is the last test seen before the exception
092c:devinst: unhandled exception c0000005 at 000000013F23C92E
See https://test.winehq.org/data/patterns.html#setupapi:devinst
This started on 2023-09-05 and happens on Windows 7+ and Wine.
--
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=55246
Bug ID: 55246
Summary: ntdll:om - The 64-bit test_object_types() crashes on
Windows 8+
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
ntdll:om - The 64-bit test_object_types() crashes on Windows 8+:
om.c:2325: this is the last test seen before the exception
1c98:om: unhandled exception c0000005 at 00007FFFC32A60AB
See https://test.winehq.org/data/patterns.html#ntdll:om
Where c0000005 == STATUS_ACCESS_VIOLATION
This started on 2023-07-10 which corresponds to the GitLab CI switch to Debian
12 for builds which means it is caused by the commit below:
commit 5799e89f15b5584f186dcc2fd24b98e0a7bd6c10
Author: Alexandre Julliard <julliard(a)winehq.org>
Date: Mon Jul 10 17:18:49 2023 +0200
gitlab: Upgrade the Debian image to bookworm.
Note that, to this day, the 64-bit binaries produced by the TestBot still run
successfully on Windows because they are built on Debian 11. But the nightly
WineTest runs fail because they use the official WineTest binaries produced by
the GitLab CI which uses Debian 12.
--
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=54331
Bug ID: 54331
Summary: Game "Antecrypt": Black screen after launch
Product: Wine
Version: 7.22
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: stabilergriller(a)gmail.com
Distribution: ---
Created attachment 73894
--> https://bugs.winehq.org/attachment.cgi?id=73894
Output when running "wine beam.exe"
This shooting game from https://punkcake.itch.io/antecrypt just opens up a
window which is completely black.
I confirm that this game runs on Windows 10.
My set up:
OS: Arch 64-Bit
GPU: Intel HD Graphics 610
Mesa: 22.3.3
Kernel version: 6.1.5
--
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=55507
Bug ID: 55507
Summary: Softerra LDAP Browser needs
LDAP_OPT_CLIENT_CERTIFICATE
Product: Wine
Version: 8.15
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: wldap32
Assignee: wine-bugs(a)winehq.org
Reporter: alexhenrie24(a)gmail.com
Distribution: ---
Steps to reproduce:
1. Run `docker run --detach -p1389:1389 bitnami/openldap`
2. Run `wine ldapbrowser-4.5.19808.0-x64-eng.msi`
3. Run `wine 'C:\Program Files\Softerra\LDAP Browser 4\ldapbrowser.exe'`
3. Click File > New > New Profile
4. Connect to localhost port 1389 anonymously
"COM Error" is displayed in the main window and "fixme:wldap32:ldap_set_optionA
Unsupported option: 0x80" is spammed to the terminal. 0x80 is
LDAP_OPT_CLIENT_CERTIFICATE, which sets the callback function to call to get
the client certificate for mTLS if the LDAP server requires mTLS.
Since most LDAP servers do not require mTLS, for now we can just save the
callback function and not call it.
$ sha256sum ldapbrowser-4.5.19808.0-x64-eng.msi
22fdae1fe8320043e8e9c50e3b4f5bd4d7f6a4b50c4680cc4216a1a65284083d
--
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=55505
Bug ID: 55505
Summary: Vitis 2020.1 needs support for "goto :EOF" command in
batch file
Product: Wine
Version: 8.14
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: cmd
Assignee: wine-bugs(a)winehq.org
Reporter: alexhenrie24(a)gmail.com
Distribution: ---
Steps to reproduce:
1. Run `tar -xvf Xilinx_Unified_2020.1_0602_1208.tar.gz`
2. Run `wine Xilinx_Unified_2020.1_0602_1208/xsetup.exe`
3. When the installer complains that it can't connect to the internet, click
Ignore
4. Run `wine 'C:\Xilinx\Vitis\2020.1\bin\vitis.bat'`
The script prints "Syntax error" to the terminal twice and hangs without
opening Vitis. The first unrecognized command is "goto :EOF".
Registration is required to download Vitis.
$ sha256sum Xilinx_Unified_2020.1_0602_1208.tar.gz
a9e0f81a61eca260c4453ab93a8d17eac31956dd54d0d5fd74dc8b4f2727e3eb
--
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=55501
Bug ID: 55501
Summary: Since commit 3174e86abedf633bcec4884f1303143a696b6062
PS Core (pwsh.exe) fails to start:Call to
unimplemented function wldp.dll.WldpGetLockdownPolicy
Product: Wine
Version: 8.14
Hardware: x86-64
URL: https://github.com/PowerShell/PowerShell/releases/down
load/v7.1.5/PowerShell-7.1.5-win-x64.msi
OS: Linux
Status: NEW
Keywords: download
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: xerox.xerox2000x(a)gmail.com
CC: bunglehead(a)gmail.com
Distribution: Debian
Though technically spoken not a real regression, I added you (Nicolai) to the
bugreport, hope you don't mind
The function is described here:
https://learn.microsoft.com/en-us/windows/win32/api/wldp/nf-wldp-wldpgetloc…
A simple stub returning S_OK is enough to fix this ( not sure what to set
lockdownState to, just setting it to 0 seems to be ok)
(Sidenote: returning E_NOTIMPL allows the program also to start, but several
errrors are reported in the console and maybe further functionality might fail)
Sidenote 2: I suspect Dotnet Core is also affected by this bug, but i didn't
test that.
--
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.