https://bugs.winehq.org/show_bug.cgi?id=55394
Bug ID: 55394
Summary: comctl32:listbox - test_LBS_NODATA() fails in Wine for
the Hindi locale
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: comctl32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
comctl32:listbox - test_LBS_NODATA() fails in Wine for the Hindi locale:
listbox.c:2630: Test failed: Unexpected return value 6.
listbox.c:2630: Test failed: Unexpected return value 6.
See https://test.winehq.org/data/patterns.html#comctl32:listbox
This failure is systematic and first happened on 2023-07-27 and Hindi is the
only locale that fails.
--
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=55005
Bug ID: 55005
Summary: Program Treecomp - some widgets are not drawn
Product: Wine
Version: 8.9
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: danny.schneider(a)posteo.de
Distribution: ---
Created attachment 74557
--> https://bugs.winehq.org/attachment.cgi?id=74557
two attached files compressed in a tar.bz2
recently another Bug by me was fixed:
Bug 54640
Treecomp listviews and possibly other widgets are not drawn
and after the fix everything worked fine again - until now.
affected is the program
Treecomp (exists since NT4 / W2k...)
https://lploeger.home.xs4all.nl/TreeComp.htmhttps://lploeger.home.xs4all.nl/TreeCompx64Latest_noinstall.zip
this time the treeview in the left pane seems to be OK, is accessible and
working,
but the right Pane is Empty (table widget?) --> see attached picture
I guess the problem is similar to the one of the Bug mentioned above.
If you need more information, please ask. I then can try to provide.
I have attached the Version currently installed, Distri is arch.
--
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=55446
Bug ID: 55446
Summary: Using C run-time for unicode strings comparison breaks
case insensitive LB_FINDSTRING
Product: Wine
Version: 8.13
Hardware: x86-64
OS: Linux
Status: NEW
Keywords: regression
Severity: normal
Priority: P2
Component: user32
Assignee: wine-bugs(a)winehq.org
Reporter: dmitry(a)baikal.ru
CC: julliard(a)winehq.org
Regression SHA1: 9cc92365560f19c2fd2b9796f79aa75e02381bb1
Distribution: ---
If an application uses LB_FINDSTRING and provides a string that doesn't match
exactly then LB_FINDSTRING fails. This is a regression, and it's caused by
commit 9cc92365560f19c2fd2b9796f79aa75e02381bb1
Author: Alexandre Julliard <julliard(a)winehq.org>
Date: Mon Sep 21 13:53:21 2020 +0200
user32: Build with msvcrt.
Signed-off-by: Alexandre Julliard <julliard(a)winehq.org>
wcsnicmp() used by LB_FINDSTRING (in both user32 and comctl32) doesn't work
properly because it depends on LC_TYPE locale being correctly set, otherwise
_towlower_l() correctly handles only ASCII character range.
Relying on CRT locale being correctly initialized in a win32 core DLL seems
undesirable because an application may not use or care about C run-time at all.
Under Windows SendMessageW(LB_FINDSTRING) works just fine regardless of system
locale.
P.S.
This is a much more serious problem, and is not limited to user32/comctl32
because wcsnicmp()/wcsicmp() is used everywhere in the Wine codebase.
--
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=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=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=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.
https://bugs.winehq.org/show_bug.cgi?id=54381
Bug ID: 54381
Summary: tightvnc viewer crashes on incoming connection
Product: Wine
Version: 8.0-rc3
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: wine(a)axeitado.com
Distribution: ---
Created attachment 73948
--> https://bugs.winehq.org/attachment.cgi?id=73948
Backtrace, 64bits version.
$ wine --version
wine-8.0-rc3 (Debian 8.0~rc3~repack-1)
The crash happens when the connection is established and the remote screen is
about to appear on the viewer. For instance, when the remote server connects to
the viewer with a reverse connection:
$ wine tvnviewer.exe -listen
c:\> tvnserver.exe -run
c:\> tvnserver.exe -controlapp -connect <viewer-host-address>
wine: Unhandled page fault on write access to 0000000000000000 at address
000000014007D22D (thread 0110), starting debugger...
0108:err:sync:RtlpWaitForCriticalSection section 0000000001D77BF8 (null) wait
timed out in thread 0108, blocked by 010c, retrying (60 sec)
The above example uses the reverse connection method, which is straightforward
to setup. When the viewer connects to a listening remote server the same crash
occurs:
c:\> rem the server must be properly configured:
c:\> tvnserver.exe -run
$ wine tvnviewer.exe <remote-server-address>
wine: Unhandled page fault on write access to 0000000000000000 at address
000000014007D22D (thread 010c), starting debugger...
0108:err:sync:RtlpWaitForCriticalSection section 0000000001D77BF8 (null) wait
timed out in thread 0108, blocked by 010c, retrying (60 sec)
This worked until very recently, 7.0.1~repack-1 was fine (this is Debian
Testing).
The software is licensed under the GPL and binaries can be downloaded on the
author's homepage (currently at version 2.8.63):
https://www.tightvnc.com/download.php
The 32 bit version also crashes.
Backtrace attached. It looks like the problem is related to starting a thread.
--
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.