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.
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.
https://bugs.winehq.org/show_bug.cgi?id=55578
Bug ID: 55578
Summary: kernel32:loader - The 64-bit test_section_access()
sometimes fails on Windows 8
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: kernel32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
kernel32:loader - The 64-bit test_section_access() sometimes fails on Windows
8:
loader.c:2075: Test failed: DeleteFile error 32
loader.c:2075: Test failed: DeleteFile error 32
loader.c:2075: Test failed: DeleteFile error 32
See https://test.winehq.org/data/patterns.html#kernel32:loader
This started on 2023-09-04 and happens in about 50% of the WineTest runs and is
most likely caused by the commit below:
commit d64200805b1848f782c8a4ce1fdbcb9292fffe51
Author: Alexandre Julliard <julliard(a)winehq.org>
AuthorDate: Thu Aug 31 18:08:50 2023 +0200
kernel32/tests: Remove some workarounds for old Windows versions.
--
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=55439
Bug ID: 55439
Summary: RPG Maker game crashes
Product: Wine
Version: 8.13
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: beta60sensei(a)mail.ru
Distribution: ---
Created attachment 74999
--> https://bugs.winehq.org/attachment.cgi?id=74999
WINEDEBUG=+seh,+tid
Hi. I'm playing RPG Maker game and it crashes in some specific places with
errors like:
Script 'Flash' line 112: Errno::EBADF occurred. Bad file descriptor - <STDUOT>
The developer of the game says: "seams to be a problem with wine running ingame
scripts ... it looks like wine crashes every time I use console output for
debugging in scripts".
But, if i run the game with WINEDEBUG, then it works fine without crashes.
There is no errors in terminal when crash occurs, but i will attach log of
WINEDEBUG=+seh,+tid of the moment, when the game would crash if it were not
running in the debug mode.
I'm using wine-staging 8.13
--
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.