https://bugs.winehq.org/show_bug.cgi?id=55328
Bug ID: 55328
Summary: user32:input - test_keyboard_layout_name() fails on
Windows 7 for the Spanish locale
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: user32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
user32:input - test_keyboard_layout_name() fails on Windows 7 for the Spanish
locale:
input.c:3474: Test failed: 04090409: GetKeyboardLayoutNameW returned
L"00000C0A", expected L"00000409"
See https://test.winehq.org/data/patterns.html#user32:input
This failure is systematic and specific to this Spanish Windows 7 Ultimate
configuration. In particular it does not happen in any of the other w7u
configurations.
--
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=55306
Bug ID: 55306
Summary: [REG 8.11] Cannot double click in the server browser
in Worms Armageddon
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: wine(a)thecybershadow.net
Regression SHA1: 10f5ff7f06595bf9d1f487f91dbbd869e5105d26
Distribution: ---
Created attachment 74902
--> https://bugs.winehq.org/attachment.cgi?id=74902
Draft patch
Steps to reproduce:
1. Install Worms Armageddon
2. From the main menu, go into the options screen (bottom right button) ->
Advanced -> check "Use community server list"
3. From the main menu, go to network (bottom left button) -> WormNET (top right
button)
4. Try double-clicking on a link
Expected: Should follow the clicked link / enter the clicked server.
Actual: Nothing happens. Cursor changes from hand pointer to arrow on the first
click.
Regression in 8.11, introduced in commit
10f5ff7f06595bf9d1f487f91dbbd869e5105d26.
Attached patch fixes it for me, though I can't vouch for its correctness.
--
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=52971
Bug ID: 52971
Summary: HardWest 2 (playtest) is broken with OpenGL/Vulkan
backend
Product: Wine
Version: 7.8
Hardware: x86-64
URL: https://store.steampowered.com/app/1282410/Hard_West_2
/
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: berillions(a)gmail.com
Distribution: ---
Created attachment 72342
--> https://bugs.winehq.org/attachment.cgi?id=72342
Hard West 2 with Damavand
Hi,
New game = new test for Damavand.
This game is currently in beta test on Steam for free so i don't know if the
invitations are illimited.
Tried the game with wine-5.8 + vkd3d git (e6ce077a)
VKD3D_DEBUG=trace VKD3D_SHADER_DEBUG=trace
WINEDEBUG=+d3d,+d3d11,+d3d_shader,+seh log here :
https://www.mediafire.com/file/5ozkg59o3dof53r/HardWest2_d3d.7z/file
--
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=55967
Bug ID: 55967
Summary: app regression; SWATH stops working at all as of 8.18
Product: Wine
Version: 8.18
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: mhrivnak(a)hrivnak.org
Distribution: ---
Created attachment 75557
--> https://bugs.winehq.org/attachment.cgi?id=75557
terminal output
SWATH (http://swath.net/) won't run at all starting with 8.18, after having run
successfully under wine for a very long time. It continues to not work as of
8.21.
I did a clean install of Fedora 38 and started testing packages from the winehq
repository.
winehq-devel-8.17-1.1.x86_64 does work.
winehq-devel-8.18-1.1.x86_64 does not work.
Steps to reproduce:
###
wget http://swath.net/downloads/SWATH_v2_0.exe
sudo dnf install wine-mono
sudo dnf install winehq-devel-8.17-1.1.x86_64
wine SWATH_v2_0.exe
< click through the install wizard. At the end, un-select the option to launch>
wine ~/.wine/drive_c/Program\ Files\ \(x86\)/SWATH\ 2.0/SWATH.exe
###
The app will show a dialog about being on a 30-day trial, and then the main
window opens. It works. Now exit, and we'll try again with 8.18.
###
rm -Rf ~/.wine
sudo dnf install winehq-devel-8.18-1.1.x86_64
wine SWATH_v2_0.exe
< click through the install wizard. At the end, un-select the option to launch>
wine ~/.wine/drive_c/Program\ Files\ \(x86\)/SWATH\ 2.0/SWATH.exe
###
The process quickly exits with code 150, never having shown a graphical window
of any kind.
--
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=55288
Bug ID: 55288
Summary: ntdll:reg - The 32-bit test_redirection() fails if run
after the 64 WineTest
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:reg - The 32-bit test_redirection() fails if run after the 64-bit
WineTest:
reg.c:1714: Test failed: NtDeleteKey failed: 0xc0000022
See https://test.winehq.org/data/patterns.html#ntdll:reg
Where 0xc0000022 == STATUS_ACCESS_DENIED
These failures only happen in the fg-deb64-i386 and fg-deb64-wow32 test
configurations which means they only fail if the 64-bit test suite has
previously been run in the same wineprefix. So this is either a test cleanup
issue or Wine messing up the registry in some way.
Furthermore the failures started on 2023-07-17 so they can probably be tied
back to a specific commit.
--
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=51478
Bug ID: 51478
Summary: dinput:keyboard breaks user32:input's
test_keyboard_layout_name() in some locales ()
Product: Wine
Version: 6.10
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: user32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Created attachment 70313
--> https://bugs.winehq.org/attachment.cgi?id=70313
Add test_keyboard_layout_name() traces
The WineTest runs show the following test_keyboard_layout_name() failure in
some locales:
https://test.winehq.org/data/patterns.html#user32:input
input.c:3169: Test failed: Could not find keyboard layout 0000000004110411 in
preload list
This is 100% reproducible in the following configurations (only the keyboard
layout id differs):
win7_newtb-w7u-es
win7_newtb-w7u-pt-PT
win2004_newtb-w10pro64-ar-64
win2004_newtb-w10pro64-he-64
win2004_newtb-w10pro64-hi-64
win2004_newtb-w10pro64-ja-64
win2004_newtb-w10pro64-ko-64
win2004_newtb-w10pro64-pt-BR-64
win2004_newtb-w10pro64-ru-64
win2004_newtb-w10pro64-zh-CN-64
Notes:
* Interestingly this means this failure does not happen in the English, French,
German and Greek locales.
* Also user32:input only fails on the first run that follows dinput:keyboard,
and does not ever fail again, even if dinput:keyboard is run again.
In the w10pro64_pt_BR case, adding extra traces shows that the root of the
issue is that GetKeyboardLayoutList() returns 10 instead of 13. As a result
test_keyboard_layout_name() fails to retrieve all the Keyboard Layout\\Preload
values (there is 12 of these, not 10 or 13!).
Also the items are not in the same order in layouts_preload and layouts so this
causes some entries to be missing.
More notes:
* The ok() message is wrong: it is not layout we are looking for but
layouts[i], aka klid.
* I don't know why the GetKeyboardLayoutList() return value changes in the
first run that follows dinput:keyboard, but I'm not sure it makes sense to
assume it matches the number of entries in the Preload key in the first place.
--
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=55962
Bug ID: 55962
Summary: Program that mixes 32-bit and 64-bit typelibs fails to
find a referenced typelib
Product: Wine
Version: 8.21
Hardware: x86-64
OS: Linux
Status: NEW
Keywords: regression
Severity: normal
Priority: P2
Component: oleaut32
Assignee: wine-bugs(a)winehq.org
Reporter: dmitry(a)baikal.ru
CC: julliard(a)winehq.org
Regression SHA1: 43e5f9e4bfa65ccea633df244a7ec0c790ed8ffb
Distribution: ---
I have a 32-bit program that has a 32-bit typelib (SYS_WIN32) in its resources.
This program also ships a bunch of 32-bit dlls that also have typelibs in their
resources, and these typelibs referense a typelib from main exe by guid.
However all the typelibs in 32-bit dlls have syskind SYS_WIN64, and that
prevents finding a referenced typelib from main exe. This is a regression, and
it's caused by
commit 43e5f9e4bfa65ccea633df244a7ec0c790ed8ffb
Author: Alexandre Julliard <julliard(a)winehq.org>
Date: Fri Sep 9 17:27:27 2022 +0200
oleaut32: Check that the 32/64 syskind matches when getting a typelib from
the cache.
Fixes test failures on 64-bit.
Reverting this commit makes the program work again.
--
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=55942
Bug ID: 55942
Summary: Crazy Chicken Approaching - Nebula Assertion and
Visual C++ Runtime Library Errors
Product: Wine
Version: 8.20
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: nikolas.gur(a)stud.uni-due.de
Distribution: ---
Created attachment 75517
--> https://bugs.winehq.org/attachment.cgi?id=75517
wine output
game info: https://www.mobygames.com/game/20725/crazy-chicken-approaching/
Game does not even boot into main menu. Upon starting, a 'Nebula Assertion'
Error is presented. When clicking "ok", another "Runtime Error" appears, this
time from the Visual C++ Runtime Library. When clicking again on "ok", the game
just exits.
--
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=55667
Bug ID: 55667
Summary: kernel32:file - test_MapFile() fails on macOS
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Mac OS X
Status: NEW
Severity: normal
Priority: P2
Component: kernel32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
kernel32:file - test_MapFile() fails on macOS:
file.c:3131: Test failed: mapping should fail
file.c:3134: Test failed: mapping should fail
See https://test.winehq.org/data/patterns.html#kernel32:file
These failures are systematic, started on 2023-09-26 and only happen on macOS
(see Remi's rbernon-macos-* cloud test machines).
I think the symptoms correspond to the removal of the broken(hmap != NULL) case
in the commit below:
commit 0abd795ff02601474962dfa4b4a070082a9999cd
Author: Alexandre Julliard <julliard(a)winehq.org>
AuthorDate: Mon Sep 25 11:15:14 2023 +0200
kernel32/tests: Fix loader tests on Windows ARM64.
--
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=51314
Bug ID: 51314
Summary: vulkan-1:vulkan crashes on cw-rx460 with recent Radeon
drivers
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
vulkan-1:vulkan crashes on cw-rx460 with recent Radeon drivers:
https://test.winehq.org/data/patterns.html#vulkan-1:vulkan
vulkan.c:425: this is the last test seen before the exception
16c4:vulkan: unhandled exception c0000005 at 6B718FCD
With the Radeon 19.11.3 driver test_private_data() is skipped because the
device creation fails. But with the Radeon >= 21.3.2 driver the function is
being run and the vkSetPrivateDataEXT() call causes a 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.