March 2022 - Wine-bugs - list.winehq.org

[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 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 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 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

[Bug 52612] New: Build Error on macOS 12.2.1 with M1 mac
by WineHQ Bugzilla 30 Apr '22

30 Apr '22

https://bugs.winehq.org/show_bug.cgi?id=52612 Bug ID: 52612 Summary: Build Error on macOS 12.2.1 with M1 mac Product: Wine Version: 7.3 Hardware: arm OS: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: syurin.nagatuki(a)gmail.com Created attachment 71939 --> https://bugs.winehq.org/attachment.cgi?id=71939 log Build Error on macOS 12.2.1 with M1 Mac Error Message : clang: error: unable to execute command: Segmentation fault: 11 clang: error: clang frontend command failed due to signal (use -v to see invocation) Apple clang version 13.0.0 (clang-1300.0.29.30) Target: arm64-apple-darwin21.3.0 Thread model: posix InstalledDir: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin clang: note: diagnostic msg: ******************** PLEASE ATTACH THE FOLLOWING FILES TO THE BUG REPORT: Preprocessed source(s) and associated run script(s) are located at: clang: note: diagnostic msg: /var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/T/cmslut-db7957.c clang: note: diagnostic msg: /var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/T/cmslut-db7957.sh clang: note: diagnostic msg: Crash backtrace is located in clang: note: diagnostic msg: /Users/syurin/Library/Logs/DiagnosticReports/clang_<YYYY-MM-DD-HHMMSS>_<hostname>.crash clang: note: diagnostic msg: (choose the .crash file that corresponds to your crash) clang: note: diagnostic msg: ******************** make: *** [libs/lcms2/src/cmslut.o] Error 254 -- 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 45385] New: Wrong state of virtual keys after cycling windows. Usually VK_MENU, VK_SHIFT and VK_CONTROL, but every key can be affected.
by wine-bugs＠winehq.org 27 Apr '22

27 Apr '22

https://bugs.winehq.org/show_bug.cgi?id=45385 Bug ID: 45385 Summary: Wrong state of virtual keys after cycling windows. Usually VK_MENU, VK_SHIFT and VK_CONTROL, but every key can be affected. Product: Wine Version: 3.9 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: wineserver Assignee: wine-bugs(a)winehq.org Reporter: johnfound(a)asm32.info Distribution: --- I noticed that the state of the keys sometimes sticks in pressed state. This happens when cycling windows with some shortcut key combination. For example if cycling with Alt+Tab, on pressing Alt, the program gets WM_KEYDOWN and the state of the VK_MENU becomes pressed. But after cycling windows, the program does not get WM_KEYUP because the window is not focused and VK_MENU (and the respective VK_LMENU or VK_RMENU) remain in pressed state. When cycling back to the program window, the window get focused only after releasing Alt key, so it does not get this event as well. If cycling windows with another shortcut key combination (for example Alt+Shift+Tab - for backward cycling) both VK_MENU and VK_SHIFT keys stick. In the same time, GetAsyncKeyState returns the proper state of the keys. Note1: The problem is obviously in the wineserver code, because it handles the key state tables for the different threads. Note2: The effect happens only sometimes. It seems the code for proper processing is already there, but some racing conditions have place. Note3: There is some probability that the effect is in result of my application code, but it never happens on real Windows, so I considered it a bug. Note4: I tried to workaround this problem by reading the whole table by GetAsyncKeyState and setting it then with SetKeyboardState on WM_ACTIVATE message of the main window. This workaround actually works, but is too ugly IMO. The same trick on WM_ACTIVATEAPP does not work. -- 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 3

[Bug 52737] New: winecfg not open
by WineHQ Bugzilla 27 Apr '22

27 Apr '22

https://bugs.winehq.org/show_bug.cgi?id=52737 Bug ID: 52737 Summary: winecfg not open 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: jayjameshlw(a)gmail.com Distribution: --- archkubi(a)GnuChanOS ~> winecfg MESA-INTEL: warning: Haswell Vulkan support is incomplete MESA-INTEL: warning: Haswell Vulkan support is incomplete MESA-INTEL: warning: Haswell Vulkan support is incomplete MESA-INTEL: warning: Haswell Vulkan support is incomplete MESA-INTEL: warning: Haswell Vulkan support is incomplete MESA-INTEL: warning: Haswell Vulkan support is incomplete MESA-INTEL: warning: Haswell Vulkan support is incomplete 0120:err:winediag:nodrv_CreateWindow Application tried to create a window, but no driver could be loaded. 0120:err:winediag:nodrv_CreateWindow The explorer process failed to start. -- 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