https://bugs.winehq.org/show_bug.cgi?id=51930
Bug ID: 51930
Summary: Final Fantasy XIV audio broken in wine-6.20
Product: Wine
Version: 6.20
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: xaudio2
Assignee: wine-bugs(a)winehq.org
Reporter: achurch+wine(a)achurch.org
Regression SHA1: d8be85863fedf6982944d06ebd1ce5904cb3d4e1
Distribution: ---
Final Fantasy XIV (main game and Stormblood benchmark, which is the only
benchmark that currently seems to work in Wine) no longer plays audio in Wine
6.20. This is a regression from 6.19. XAudio-based audio output from other
applications seems to work fine.
git bisect blames d8be85863fedf6982944d06ebd1ce5904cb3d4e1 "xaudio: Use the
bundled FAudio and build with msvcrt." If I back out that commit against 6.20
and build with the FAudio 21.01 installed on my system, FFXIV audio works fine
again.
May I ask why you're removing options to build with external libraries? It
makes it much more difficult to work around problems like 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=51790
Bug ID: 51790
Summary: MSI is no longer able to detect correct architecture
for a custom action DLL
Product: Wine
Version: 6.17
Hardware: x86-64
OS: Linux
Status: NEW
Keywords: regression
Severity: normal
Priority: P2
Component: kernel32
Assignee: wine-bugs(a)winehq.org
Reporter: dmitry(a)baikal.ru
Regression SHA1: 02268cb290493c899b56996405ca7c65a8046e3c
Distribution: ---
MSI relies on GetBinaryType() to return correct architecture for a custom
action DLL, however GetBinaryType() started to intentionally fail for DLL
files. This for instance leads to inability to run a 32-bit action from a
64-bit installer process.
This essentially breaks any installer in a WoW64 Wine prefix. This bug should
probably have 'major' severity set.
--
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=51589
Bug ID: 51589
Summary: Buttons have no icons when using the Light Blue theme
Product: Wine-staging
Version: 6.14
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: oguilherme(a)protonmail.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
I noticed that buttons on the SUMo Update app have no icons on them after
setting the Wine theme to Light Blue in winecfg.
Steps to reproduce:
1. Set Wine theme to Light Blue using winecfg.
2. Download SUMo Update portable: https://www.kcsoftwares.com/files/sumo.zip
3. Run SUMo.exe
4. Notice the buttons have no icons
--
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=51500
Bug ID: 51500
Summary: ntdll:exception test_wow64_context() randomly fails on
Windows
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
test_wow64_context() regularly gets one of the following two failures on
Windows:
exception.c:4370: Test failed: cs32: ecx f6a10000 / 4EAECB33F6A10000
or
exception.c:4450: Test failed: cs64: rsp not inside 64-bit stack
0000000002B7F388 / 00000000009E0000-0000000000A1FD20
It looks like at most one failure happens in a given run. They happen on
Windows 8.1 to Windows 10 2009, only QEmu VMs so far.
But the failures only happen about 6.9% of the time so the above data is not
100% certain yet.
The tests were added in this commit:
commit 9ae2b046ef2f645b122a2554cc8e32d3a3d79ccc
Author: Alexandre Julliard <julliard(a)winehq.org>
AuthorDate: Tue Jun 22 17:08:11 2021 +0200
ntdll/tests: Add more tests for Wow64 contexts.
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=51282
Bug ID: 51282
Summary: Samurai Shodown Reboot 2019: low gpu usage around
5-10% and low fps around 9-20fps
Product: Wine
Version: 6.7
Hardware: x86-64
URL: https://store.steampowered.com/bundle/21032/SAMURAI_SH
ODOWN_STEAM_EDITION/
OS: Linux
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: user32
Assignee: wine-bugs(a)winehq.org
Reporter: rezzafri(a)gmail.com
Regression SHA1: c2c78a2fe0ac13e4fca7ab4c17977b65e358485c
Distribution: Other
Regression on commit c2c78a2fe0ac13e4fca7ab4c17977b65e358485c. normal gpu usage
and fps with this commit reverted.
--
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=52187
Bug ID: 52187
Summary: wine-mono's WPF tests hang
Product: Wine
Version: 6.23
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: madewokherd(a)gmail.com
Distribution: ---
The test
WineMono.Tests.System.Windows.Media.TextFormatting.TextFormatterTest:IndentTest
hangs on current Wine.
It seems it gets in a loop where dwritetextanalyzer_AnalyzeLineBreakpoints
requests data past the end of the range provided by the source, and the source
returns 0-length text.
This is our implementation of GetTextAtPosition:
https://github.com/madewokherd/wpf/blob/main/src/Microsoft.DotNet.Wpf/src/D…
Print statement debugging shows that the "else" path is being taken in that
function, but on the dwrite side checking for a length of 0 works around the
hang.
Bisecting gave me this:
909f7aa7c21f82114586e98a0a9e940b13bc386a is the first bad commit
commit 909f7aa7c21f82114586e98a0a9e940b13bc386a
Author: Nikolay Sivov <nsivov(a)codeweavers.com>
Date: Thu Dec 2 15:37:19 2021 +0300
dwrite: Use CRT allocation functions.
Nothing in that commit should change the behavior. I double-checked the result,
and it's consistent. I tried running with WINEDEBUG=warn+heap, both before and
after the bad commit, and that didn't change the behavior or print any warnings
while the test process was running.
Leaving component unknown because it's not clear to me that dwrite is doing
anything wrong.
--
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=52165
Bug ID: 52165
Summary: mfplat:mfplat has failures in
test_sample_allocator_d3d12() on Windows 10 1709
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: mfplat
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
mfplat:mfplat has failures in test_sample_allocator_d3d12() on Windows 10 1709:
mfplat.c:7365: Test failed: Failed to set a device, hr 0x80070057.
mfplat.c:7383: Test failed: Unexpected hr 0x80041000.
https://test.winehq.org/data/patterns.html#mfplat:mfplat
The failures happen on cw-rx460 and the TestBot's w1064v1709 VM. cw-gtx560 is
also impacted but it normally gets stuck before reaching this test (see bug
52164).
The failures started with the commit that introduced this set of tests:
commit f03933fbb73152c7a54383fba411a611af7aaa55
Author: Nikolay Sivov <nsivov(a)codeweavers.com>
Date: Sat Nov 27 00:03:59 2021 +0300
mfplat/tests: Add some tests for video sample allocator using D3D12 device.
Signed-off-by: Nikolay Sivov <nsivov(a)codeweavers.com>
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=52112
Bug ID: 52112
Summary: Final Fantasy XIV failing to boot
Product: Wine
Version: 6.22
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: blocker
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: meowsuke(a)gmail.com
Distribution: ---
Created attachment 71139
--> https://bugs.winehq.org/attachment.cgi?id=71139
terminal output
ubuntu 20.04.3 lts, wine staging 6.22.
the launcher runs, but the game will not launch. the game ran previously (maybe
under 6.20). i wasn't able to do a regression test because of errors i ran into
while compiling wine. the game has to be run under staging because it needs the
wine version to be hidden.
--
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=51910
Bug ID: 51910
Summary: Keyboard Input Partially Broken
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-dinput
Assignee: wine-bugs(a)winehq.org
Reporter: escomk3(a)hotmail.com
Distribution: ---
Here's an interesting one.
After 71ecc179aab [1], some keyboard keys no longer (completely) work as they
should in FINAL FANTASY XI Online.
For example, the arrow keys no longer navigate through menus, while they do
still move the cursor in chat.
Other keys that have become partially "mute" include:
- right ctrl
- insert
- delete
- home
- end
- page up
- page down
- / (numpad)
- Enter (numpad)
1.
https://source.winehq.org/git/wine.git/commit/71ecc179aab7ad103e06b52ea76ae…
--
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=51745
Bug ID: 51745
Summary: Xbox Controller no longer recognised
Product: Wine
Version: 6.17
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: xinput
Assignee: wine-bugs(a)winehq.org
Reporter: lemonzest(a)gmail.com
Distribution: ---
Created attachment 70631
--> https://bugs.winehq.org/attachment.cgi?id=70631
XinputTest.exe Test Program for Xinput Controllers
Hi
I just updated to WineHQ-Devel 6.17 and Xinput/Xbox controllers (Not sure about
others as don't own any) are no longer detected in games
I have tried Dragon's Dogma, Dead Cells and a couple of others and they no
longer react to Gamepad inputs and XinputTest.exe says its disconnected.
rolling back to WineHQ-Devel 6.16 all is working.
I am on Fedora 34 with a PDP Afterglow XBox One Controller which in many
previous versions worked correctly.
--
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.