wine-bugs April 2022

wine-bugs@winehq.org

1 participants
4030 discussions

[Bug 52828] New: Incorrect instruments in MIDI playback over ALSA
by WineHQ Bugzilla 06 May '22

06 May '22

https://bugs.winehq.org/show_bug.cgi?id=52828 Bug ID: 52828 Summary: Incorrect instruments in MIDI playback over ALSA Product: Wine Version: 7.5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: dark(a)darkok.xyz Distribution: --- Created attachment 72216 --> https://bugs.winehq.org/attachment.cgi?id=72216 MIDI file that is played noticably wrong Starting from Wine 7.5, some MIDIs aren't played back properly as they have the incorrect instruments, at least when I've tried playing them using aplaymidi on a VST using SAVIHost. Downloads: https://www.hermannseib.com/programs/savihostx64.zip https://cdn.roland.com/assets/media/zip/scva_win_trial.zip Steps to reproduce: 1. Execute "winetricks mfc90" to get a required DLL 2. Extract scva_win_trial.zip and install the Roland Sound Canvas VA VST 3. Extract savihostx64.zip, and move savihost.exe to "C:\Program Files\Roland\Sound Canvas VA" 4. Rename savihost.exe to "Sound Canvas VA.exe" 5. Run the renamed executable 6. Go to Devices>MIDI, and set Input Port 1 to "Midi Through Port-0" 7. Run "aplaymidi -p 14:0 smr_101.mid" to start playing the MIDI 8. In the VST, click "PART", and the correct instruments should be Vibraphone for the first three, and "KICK&SNARE" for the 11th. However, starting from Wine 7.5, these instruments are incorrectly set to "Piano 1" for the first three, and "Syn. Strings 1" for the 11th. -- 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.

1 14

[Bug 48048] New: urlmon:protocol - The ftp test fail on Vista to Windows 8
by WineHQ Bugzilla 06 May '22

06 May '22

https://bugs.winehq.org/show_bug.cgi?id=48048 Bug ID: 48048 Summary: urlmon:protocol - The ftp test fail on Vista to Windows 8 Product: Wine Version: unspecified Hardware: x86 OS: Windows Status: NEW Severity: normal Priority: P2 Component: urlmon Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com The ftp protocol test in urlmon:protocol fails frequently on Windows from Vista to Windows 8: protocol.c:1188: Test failed: hrResult = 800c0006, expected E_PENDING or S_OK protocol.c:1193: Test failed: dwError = 12111, expected ERROR_SUCCESS protocol.c:3656: Test failed: wait timed out urlmon:protocol:0700 done (258) in 120s Test failed: timed out Note: 800c0006 is INET_E_OBJECT_NOT_FOUND See https://test.winehq.org/data/tests/urlmon:protocol.html -- 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.

1 5

[Bug 18635] New: Menu bar is hidden in Adobe Lightroom 2.3
by wine-bugs＠winehq.org 06 May '22

06 May '22

http://bugs.winehq.org/show_bug.cgi?id=18635 Summary: Menu bar is hidden in Adobe Lightroom 2.3 Product: Wine Version: 1.1.22 Platform: Other OS/Version: other Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: thomas+wine(a)stromberg.org With the Adobe Lightroom 2.3 demo, the menu bar titles (File, etc.) do not display. If you click on the area that they should be, the menu does appear however. Lightroom 2.3 can be downloaded from https://www.adobe.com/cfusion/tdrc/index.cfm?product=photoshop_lightroom (free Adobe login required) I'm not sure where to go about tracing the issue down to, but I did notice the following calls that show that it is calling DrawMenuBar(). 0009:Call user32.GetMenu(0002003c) ret=60030cbe 0009:Ret user32.GetMenu() retval=000000f0 ret=60030cbe 0009:Call user32.GetMenuBarInfo(0002003c,fffffffd,00000000,0032e1a4) ret=60030cec fixme:menu:GetMenuBarInfo (0x2003c,0xfffffffd,0x00000000,0x32e1a4) 0009:Ret user32.GetMenuBarInfo() retval=00000000 ret=60030cec 0009:Call user32.GetSystemMenu(0002003c,00000000) ret=60030beb 0009:Ret user32.GetSystemMenu() retval=00000280 ret=60030beb 0009:Call user32.GetSystemMenu(0002003c,00000000) ret=60030c06 0009:Ret user32.GetSystemMenu() retval=00000280 ret=60030c06 0009:Call user32.GetMenuItemInfoW(00000280,0000f060,00000000,0032e08c) ret=60030c22 0009:Ret user32.GetMenuItemInfoW() retval=00000001 ret=60030c22 0009:Call user32.DrawMenuBar(0002003c) ret=6008d171 -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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.

2 21

[Bug 52902] New: gdi32:font has specific failures on Windows 10 with the UTF-8 codepage
by WineHQ Bugzilla 02 May '22

02 May '22

https://bugs.winehq.org/show_bug.cgi?id=52902 Bug ID: 52902 Summary: gdi32:font has specific failures on Windows 10 with the UTF-8 codepage Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: gdi32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com The following gdi32:font failures are specific to UTF-8 on Windows 10: --- test_RealizationInfo(): font.c:4356: Test failed: info[0] = 103 for the system font --- test_GetCharacterPlacement(): font.c:4998: Test failed: Unexpected first glyph L":" font.c:5012: Test failed: GetCharacterPlacementA returned different result: 1048638 vs 1048637 font.c:5016: Test failed: GetCharacterPlacementA returned different result: 1048638 vs 1048637 font.c:5023: Test failed: GetCharacterPlacementA returned different result: 1048638 vs 1048637 font.c:5025: Test failed: Unexpected first glyph L":" --- test_GetCharWidthInfo(): font.c:7396: Test failed: expected 0, got -8 font.c:7397: Test failed: expected 0, got -9 font.c:7398: Test failed: expected 0, got 1 https://test.winehq.org/data/patterns.html#gdi32:font They can be reproduced on w10pro64-hi-u8. Note that w10pro64-hi which uses the Hindi locale too but not UTF-8 (so the system locale is English) has its own set of totally unrelated failures. -- 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.

1 2

[Bug 51365] New: wininet:http causes urlmon:protocol to time out
by WineHQ Bugzilla 01 May '22

01 May '22

https://bugs.winehq.org/show_bug.cgi?id=51365 Bug ID: 51365 Summary: wininet:http causes urlmon:protocol to time out Product: Wine Version: 6.10 Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: urlmon Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com If wininet:http is run before urlmon:url the latter will time out as follows: protocol.c:348: Test failed: unexpected call OnResponse protocol.c:839: Test failed: unexpected call ReportProgress_MIMETYPEAVAILABLE protocol.c:1101: Test failed: unexpected call ReportData protocol.c:3437: Test failed: wait timed out protocol.c:3439: Test failed: expected Switch protocol.c:3560: Testing http protocol (redirected, disable auto redirect)... protocol.c:469: QueryService(IID_IGetBindHandle) protocol.c:475: QueryService(IID_IWindowForBindingUI) protocol.c:1178: Test failed: unexpected call ReportResult protocol.c:1186: Test failed: hrResult = 800c0014, expected: 00000000 urlmon:protocol:0bd0 done (258) in 120s (0x800c0014 = INET_E_REDIRECT_FAILED) The timeout actually happens in test_http_protocol_url() on line 3437: ok( WaitForSingleObject(event_complete, 90000) == WAIT_OBJECT_0, "wait timed out\n" ); This actually happens on machines that use the wt-daily.bat script [1] because that script first runs the 32-bit tests (including wininet:http) and then the 64-bit tests and, obviously, no configuration 'reset' happens in between. Specifically this causes failures in the 64-bit urlmon:protocol results on cw-gtx560 and cw-rx460: https://test.winehq.org/data/patterns.html#urlmon:protocol [1] https://github.com/fgouget/wt-daily/blob/master/wt-daily.bat.template#L138 -- 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.

1 2

[Bug 50348] New: MFMEv20 Emulator crashes on start
by WineHQ Bugzilla 01 May '22

01 May '22

https://bugs.winehq.org/show_bug.cgi?id=50348 Bug ID: 50348 Summary: MFMEv20 Emulator crashes on start Product: Wine Version: 6.0-rc2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: adec2011.ac(a)gmail.com Distribution: --- Created attachment 68935 --> https://bugs.winehq.org/attachment.cgi?id=68935 Log file for crash MFMEv20 crashes on start. Log file attached -- 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.

1 10

[Bug 46330] New: [Feature Request] Enable winelib on ppc64el
by wine-bugs＠winehq.org 01 May '22

01 May '22

https://bugs.winehq.org/show_bug.cgi?id=46330 Bug ID: 46330 Summary: [Feature Request] Enable winelib on ppc64el Product: Wine Version: unspecified Hardware: Other OS: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: winelib Assignee: wine-bugs(a)winehq.org Reporter: tpearson(a)raptorengineering.com Distribution: --- With the resurgence in POWER hardware support and interest centering around the POWER8/POWER9 chips, it would be great to get winelib support for the ppc64el architecture. This would allow Windows open source applications to be used on these powerful machines (e.g. FEMM, SQLYog, etc.). -- 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.

2 9

[Bug 52430] New: Ubi Connect Launcher forever shows a black window
by WineHQ Bugzilla 01 May '22

01 May '22

https://bugs.winehq.org/show_bug.cgi?id=52430 Bug ID: 52430 Summary: Ubi Connect Launcher forever shows a black window Product: Wine Version: 7.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: blue-t(a)web.de Distribution: --- Created attachment 71690 --> https://bugs.winehq.org/attachment.cgi?id=71690 Console Log When you try to run the Ubi Connect Launcher, it never finishes the start sequence. Instead of showing the "Ubisoft Connect" Text alongside a logo inside a frame with small status updates in the lower left corner before displaying news and installed games, it just shows an empty black window that never vanishes and never gets content. On the console variuous notes about shaders are repeated. The AppDB says using corefonts via winetricks should make it boot, but it doesn't. The Card is an amd rtx480 on a Kubuntu 21.10. -- 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.

1 3

[Bug 46694] New: widl crashes in dlls/atl during build on ppc64el
by wine-bugs＠winehq.org 30 Apr '22

30 Apr '22

https://bugs.winehq.org/show_bug.cgi?id=46694 Bug ID: 46694 Summary: widl crashes in dlls/atl during build on ppc64el Product: Wine Version: 4.2 Hardware: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: tpearson(a)raptorengineering.com Distribution: --- Created attachment 63657 --> https://bugs.winehq.org/attachment.cgi?id=63657 Backtrace Building on ppc64el fails with a segmentation fault in widl while attempting to build dlls/atl. Backtrace attached. -- 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.

2 6

[Bug 48398] New: [PATCH] build failure on arm64 with new gcc
by WineHQ Bugzilla 30 Apr '22

30 Apr '22

https://bugs.winehq.org/show_bug.cgi?id=48398 Bug ID: 48398 Summary: [PATCH] build failure on arm64 with new gcc Product: Wine Version: 5.0-rc1 Hardware: aarch64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: costamagnagianfranco(a)yahoo.it Distribution: --- Description: ../../tools/winegcc/winegcc -o d3dcompiler_47.dll.so --wine-objdir ../.. -fPIC -fasynchronous-unwind-tables -shared d3dcompiler_47.spec -mno-cygwin asmparser.o blob.o bytecodewriter.o compiler.o main.o preproc.o reflection.o utils.o asmshader.tab.o hlsl.tab.o ppy.tab.o asmshader.yy.o hlsl.yy.o ppl.yy.o version.res ../../dlls/dxguid/libdxguid.a ../../dlls/uuid/libuuid.a -Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,-z,now -Wl,-rpath,/usr/lib/aarch64-linux-gnu/wine ../d3dx9_36/effect.c:1472:12: error: result of comparison of unsigned enum expression < 0 is always false [-Werror,-Wtautological-unsigned-enum-zero-compare] if (op < 0 || op > SCT_PSINT) ~~ ^ ~ 1 error generated. Author: Gianfranco Costamagna <locutusofborg(a)debian.org> Forwarded: pending Last-Update: 2019-12-31 --- wine-5.0~rc1.orig/dlls/d3dx9_36/effect.c +++ wine-5.0~rc1/dlls/d3dx9_36/effect.c @@ -1469,7 +1469,7 @@ static HRESULT d3dx_set_shader_const_sta D3DXVECTOR4 value; HRESULT ret; - if (op < 0 || op > SCT_PSINT) + if (op > SCT_PSINT) { FIXME("Unknown op %u.\n", op); return D3DERR_INVALIDCALL; An enum starting with 0 can't obviously assume negative values... -- 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.

1 12

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-bugs April 2022