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

[Bug 44434] New: Error: unsupported compressor 8
by wine-bugs＠winehq.org 12 Feb '22

12 Feb '22

https://bugs.winehq.org/show_bug.cgi?id=44434 Bug ID: 44434 Summary: Error: unsupported compressor 8 Product: Wine Version: 3.0 Hardware: x86 OS: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: wine_bz(a)ul-lange.de Created attachment 60376 --> https://bugs.winehq.org/attachment.cgi?id=60376 Error messages after typing command winecfg After a competed installation of Wine 3.0 on macOS 10.13.3, Kernel-Version: Darwin 17.4.0 and entering command of "winecfg" together with some other messages "Error: unsupported compressor 8" have been indicated (see attached 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.

2 7

[Bug 50477] New: Presonus Studio One 5: Browser windows won't update with scrolling (D2D-related debug)
by WineHQ Bugzilla 12 Feb '22

12 Feb '22

https://bugs.winehq.org/show_bug.cgi?id=50477 Bug ID: 50477 Summary: Presonus Studio One 5: Browser windows won't update with scrolling (D2D-related debug) Product: Wine Version: 6.0-rc6 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: d2d Assignee: wine-bugs(a)winehq.org Reporter: moseskim84(a)gmail.com Distribution: --- Created attachment 69113 --> https://bugs.winehq.org/attachment.cgi?id=69113 Images Hello, I'm running Ubuntu 20.10 (x64), Wine RC-6 (patched dcomp.dll) and have installed Studio One 5 Professional. There is a bug that renders it pretty useless, and that's lack of browser window updating whenever there is scrolling within a window. I have attached a screenshot showing the window on the left and the associated messages on the right. If you notice the scroll bar on the right, it continues to move but there is no update to the window. If you scroll back and forth enough it starts to distort, but the only way to get it back to normal is to go to another window and back. That just gets you back to the top of the window, without any scrolling. I have DVXK latest version installed, with esync enabled as well with no change. GDIplus_winxp is also installed, I cannot get gdiplus to install into a 64 bit prefix even with -q. Please let me know what else I can do to help resolve this issue. Thanks! -- 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 1

[Bug 52535] New: wine: Unhandled page fault on execute access to 00007FEBBDDFAA00 at address 00007FEBBDDFAA00 (thread 0148), starting debugger...
by WineHQ Bugzilla 12 Feb '22

12 Feb '22

https://bugs.winehq.org/show_bug.cgi?id=52535 Bug ID: 52535 Summary: wine: Unhandled page fault on execute access to 00007FEBBDDFAA00 at address 00007FEBBDDFAA00 (thread 0148), starting debugger... Product: Wine Version: 7.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: alois.schloegl(a)gmail.com Distribution: --- After installing wine-7.1 (staging) according to these instructions https://wiki.winehq.org/Debian on new, powerful machine, and start a new wineprefix, I see this error message. ... 0088:fixme:msi:internal_ui_handler internal UI not implemented for message 0x0b000000 (UI level = 1) 00ec:err:winediag:nodrv_CreateWindow Application tried to create a window, but no driver could be loaded. 00ec:err:winediag:nodrv_CreateWindow The explorer process failed to start. wine: configuration in L"/nfs/scistore/schloegl/.wine" has been updated. wine: Unhandled page fault on execute access to 00007FEBBDDFAA00 at address 00007FEBBDDFAA00 (thread 0148), starting debugger... wine: Unhandled page fault on execute access to 00007F95DEDBDA00 at address 00007F95DEDBDA00 (thread 015c), starting debugger... and than waits, an there is no obvious progress. No dialog window about "wine configuration of .wine is being updated, please wait" is shown. When I stop the session, and login in again, ~/.wine is partially generated. and "wineboot -i" the following is shown: $ wineboot -i 002c:fixme:winediag:LdrInitializeThunk wine-staging 7.1 is a testing version containing experimental patches. 002c:fixme:winediag:LdrInitializeThunk Please mention your exact version when filing bug reports on winehq.org. wine: Unhandled page fault on execute access to 00007F7D0A5A3A00 at address 00007F7D0A5A3A00 (thread 0068), starting debugger... wine: Unhandled page fault on execute access to 00007F9AF9D15510 at address 00007F9AF9D15510 (thread 00c4), starting debugger... wine: Unhandled page fault on execute access to 00007FD301331A00 at address 00007FD301331A00 (thread 00d8), starting debugger... wine: Unhandled page fault on execute access to 00007FBED1E63510 at address 00007FBED1E63510 (thread 00ec), starting debugger... 0108:err:sync:RtlpWaitForCriticalSection section 0000000170067620 "dlls/ntdll/loader.c: loader_section" wait timed out in thread 0108, blocked by 0100, retrying (60 sec) 0110:err:sync:RtlpWaitForCriticalSection section 0000000170067620 "dlls/ntdll/loader.c: loader_section" wait timed out in thread 0110, blocked by 00e0, retrying (60 sec) 0114:err:sync:RtlpWaitForCriticalSection section 0000000170067620 "dlls/ntdll/loader.c: loader_section" wait timed out in thread 0114, blocked by 0034, retrying (60 sec) 010c:err:sync:RtlpWaitForCriticalSection section 0000000170067620 "dlls/ntdll/loader.c: loader_section" wait timed out in thread 010c, blocked by 00f4, retrying (60 sec) I tried also wine-devel (7.1) and wine-stable(7.0) with the same result. The software is Debian11 with cuda Driver Version: 470.103, like we have it installed on several other machines as well. The main difference is that this is a rather powerful machine: (128 threads, 1 TB RAM, 8xA40 GPU's). $ lscpu Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian Address sizes: 43 bits physical, 48 bits virtual CPU(s): 128 On-line CPU(s) list: 0-127 Thread(s) per core: 2 Core(s) per socket: 32 Socket(s): 2 NUMA node(s): 2 Vendor ID: AuthenticAMD CPU family: 23 Model: 49 Model name: AMD EPYC 7452 32-Core Processor Stepping: 0 Frequency boost: enabled CPU MHz: 1497.039 CPU max MHz: 3364.3550 CPU min MHz: 1500.0000 BogoMIPS: 4700.33 Virtualization: AMD-V L1d cache: 2 MiB L1i cache: 2 MiB L2 cache: 32 MiB L3 cache: 256 MiB NUMA node0 CPU(s): 0-31,64-95 NUMA node1 CPU(s): 32-63,96-127 Vulnerability Itlb multihit: Not affected Vulnerability L1tf: Not affected Vulnerability Mds: Not affected Vulnerability Meltdown: Not affected Vulnerability Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl and seccomp Vulnerability Spectre v1: Mitigation; usercopy/swapgs barriers and __user pointer sanitization Vulnerability Spectre v2: Mitigation; Full AMD retpoline, IBPB conditional, IBRS_FW, STIBP conditional, RSB filling Vulnerability Srbds: Not affected Vulnerability Tsx async abort: Not affected Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_ts c rep_good nopl nonstop_tsc cpuid extd_apicid aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cm p_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt tce topoext perfctr_core perfctr_nb bpext perfctr_llc mwaitx cpb cat_ l3 cdp_l3 hw_pstate sme ssbd mba sev ibrs ibpb stibp vmmcall sev_es fsgsbase bmi1 avx2 smep bmi2 cqm rdt_a rdseed adx smap clflushopt clwb sha_ni xsaveopt xs avec xgetbv1 xsaves cqm_llc cqm_occup_llc cqm_mbm_total cqm_mbm_local clzero irperf xsaveerptr rdpru wbnoinvd amd_ppin arat npt lbrv svm_lock nrip_save tsc_s cale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic v_vmsave_vmload vgif umip rdpid overflow_recov succor smca root(a)gpu230:~# nvidia-smi Thu Feb 10 18:08:21 2022 +-----------------------------------------------------------------------------+ | NVIDIA-SMI 470.103.01 Driver Version: 470.103.01 CUDA Version: 11.4 | |-------------------------------+----------------------+----------------------+ | GPU Name Persistence-M| Bus-Id Disp.A | Volatile Uncorr. ECC | | Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. | | | | MIG M. | |===============================+======================+======================| | 0 NVIDIA A40 On | 00000000:01:00.0 Off | 0 | | 0% 25C P8 11W / 300W | 36MiB / 45634MiB | 0% Default | | | | N/A | +-------------------------------+----------------------+----------------------+ | 1 NVIDIA A40 On | 00000000:25:00.0 Off | 0 | | 0% 25C P8 11W / 300W | 4MiB / 45634MiB | 0% Default | | | | N/A | +-------------------------------+----------------------+----------------------+ | 2 NVIDIA A40 On | 00000000:41:00.0 Off | 0 | | 0% 23C P8 11W / 300W | 4MiB / 45634MiB | 0% Default | | | | N/A | +-------------------------------+----------------------+----------------------+ | 3 NVIDIA A40 On | 00000000:61:00.0 Off | 0 | | 0% 23C P8 11W / 300W | 4MiB / 45634MiB | 0% Default | | | | N/A | +-------------------------------+----------------------+----------------------+ | 4 NVIDIA A40 On | 00000000:81:00.0 Off | 0 | | 0% 23C P8 11W / 300W | 4MiB / 45634MiB | 0% Default | | | | N/A | +-------------------------------+----------------------+----------------------+ | 5 NVIDIA A40 On | 00000000:A1:00.0 Off | 0 | | 0% 23C P8 11W / 300W | 4MiB / 45634MiB | 0% Default | | | | N/A | +-------------------------------+----------------------+----------------------+ | 6 NVIDIA A40 On | 00000000:C1:00.0 Off | 0 | | 0% 23C P8 19W / 300W | 4MiB / 45634MiB | 0% Default | | | | N/A | +-------------------------------+----------------------+----------------------+ | 7 NVIDIA A40 On | 00000000:E1:00.0 Off | 0 | | 0% 23C P8 20W / 300W | 4MiB / 45634MiB | 0% Default | | | | N/A | +-------------------------------+----------------------+----------------------+ Do you have any idea what is wrong here ? Let me know if I should run further tests. -- 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 52540] New: iTunes crashes with page fault on read access to 0x00000000 in 32-bit code (0x021b40b2)
by WineHQ Bugzilla 12 Feb '22

12 Feb '22

https://bugs.winehq.org/show_bug.cgi?id=52540 Bug ID: 52540 Summary: iTunes crashes with page fault on read access to 0x00000000 in 32-bit code (0x021b40b2) Product: Wine Version: 7.0-rc6 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: robertect(a)gmail.com Distribution: --- Created attachment 71847 --> https://bugs.winehq.org/attachment.cgi?id=71847 error log describing the actions failed before the crash of iTunes itunes first reports insufficient disk space and then reports the attached error and has to close -- 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 47448] New: Homeworld Remastered Collection: Fullscreen broken
by wine-bugs＠winehq.org 12 Feb '22

12 Feb '22

https://bugs.winehq.org/show_bug.cgi?id=47448 Bug ID: 47448 Summary: Homeworld Remastered Collection: Fullscreen broken Product: Wine-staging Version: 4.11 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: linards.liepins(a)gmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Created attachment 64805 --> https://bugs.winehq.org/attachment.cgi?id=64805 Game log file 1 As of wine-4.11, the game is not launching anymore properly and is giving following behavior: - Sound starts from the intro video(s) - Intro video ( gearbox ) ends and I hear the game is opened in the Main menu level - No video is being shown ('nothing happens') and the desktop is still showing I have tried with no success the following: - using official latest versions of Fedora 30 x64 packages and also Mesa 19.1.1 - using Wayland session - changing all configs in winecfg ( resolution, decoration, staging settings) - using Steam command launch options ( '-fakeFullscreen -window[ed] -w 1920 -h 1080' ) in different combinations - running game from Nautilus by directly running the executable I expect that game runs properly in full-screen same way it was working in wine-4.9. My config: $ wine --version wine-4.11 (Staging) $ inxi -Gxxx Graphics: Device-1: AMD Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] vendor: XFX Pine driver: amdgpu v: kernel bus ID: 01:00.0 chip ID: 1002:67df Display: x11 server: Fedora Project X.org 1.20.5 driver: amdgpu compositor: gnome-shell v: 3.32.2 tty: N/A OpenGL: renderer: Radeon RX 580 Series (POLARIS10 DRM 3.30.0 5.1.15-300.fc30.x86_64 LLVM 8.0.0) v: 4.5 Mesa 19.1.1 direct render: Yes P.S. Similar issue has been noticed for StepMania 5 and Age of Mythology: Extended, but these games have ways to enforce windowed mode both from Steam Launch Options or from configuring config files. -- 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 46247] New: BF2 Complete Collection 1.50 Crashes when using Anti-Aliasing 8x
by wine-bugs＠winehq.org 12 Feb '22

12 Feb '22

https://bugs.winehq.org/show_bug.cgi?id=46247 Bug ID: 46247 Summary: BF2 Complete Collection 1.50 Crashes when using Anti-Aliasing 8x Product: Wine-staging Version: 3.20 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: linards.liepins(a)gmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- All settings are Maxed Out; I tried with 2x and 4x and no crashes/issues noted. Wine details: sh winetricks list-installed ------------------------------------------------------ You are using a 64-bit WINEPREFIX. Note that many verbs only install 32-bit versions of packages. If you encounter problems, please retest in a clean 32-bit WINEPREFIX before reporting a bug. ------------------------------------------------------ Using winetricks 20181203-next - sha256sum: 90643712034ccea3dad530e2e33761d872fd532c3f6018919b21ae006ecba680 with wine-3.20 (Staging) and WINEARCH=win64 binkw32 d3dx9_42 gmdls l3codecx lucida mfc40 mfc42 physx tahoma w_workaround_wine_bug-30713 vcrun2008 w_workaround_wine_bug-30713 vcrun2012 w_workaround_wine_bug-37781 w_workaround_wine_bug-30713 vcrun2015 w_workaround_wine_bug-22053 steam w_workaround_wine_bug-30713 vcrun2010 d3dx9_36 win7 setupapi w_workaround_wine_bug-30713 vcrun2005 corefonts msls31 w_workaround_wine_bug-25648 ie8 vulkanrt msscript vulkansdk -- 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 14

[Bug 50183] New: GetCurrentConsoleFontEx - returns wrong dwFontSize
by WineHQ Bugzilla 12 Feb '22

12 Feb '22

https://bugs.winehq.org/show_bug.cgi?id=50183 Bug ID: 50183 Summary: GetCurrentConsoleFontEx - returns wrong dwFontSize Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: vladimir.kokovic(a)gmail.com Distribution: --- wine version=wine-5.17-1657-g92fb63d7754 code snippet: ------------- { CONSOLE_FONT_INFO pfi; bSuccess = GetCurrentConsoleFont( myStdOut, true, &pfi ); COORD fCoord = GetConsoleFontSize( myStdOut, pfi.nFont ); vkLog( "GetConsoleFontSize X=%d Y=%d\n", fCoord.X, fCoord.Y ); CONSOLE_FONT_INFOEX Font = { sizeof( Font ) }; GetCurrentConsoleFontEx( myStdOut, FALSE, &Font ); vkLog( "GetCurrentConsoleFontEx 1 nFont=%d dwFontSize={X=%d Y=%d} FontFamily=%d FontWeight=%d FaceName='%ls'\n", Font.nFont, Font.dwFontSize.X, Font.dwFontSize.Y, Font.FontFamily, Font.FontFamily, Font.FaceName ); //dwFontSize: //A COORD structure that contains the width and height of each character in the font, in logical units. //The X member contains the width, while the Y member contains the height. Font.dwFontSize.X = fCoord.X; Font.dwFontSize.Y = fCoord.Y; SetCurrentConsoleFontEx(myStdOut, FALSE, &Font); GetCurrentConsoleFontEx( myStdOut, FALSE, &Font ); vkLog( "GetCurrentConsoleFontEx 2 nFont=%d dwFontSize={X=%d Y=%d} FontFamily=%d FontWeight=%d FaceName='%ls'\n", Font.nFont, Font.dwFontSize.X, Font.dwFontSize.Y, Font.FontFamily, Font.FontFamily, Font.FaceName ); } log result: ----------- 2020-11-25 10:22:29 - GetConsoleFontSize X=8 Y=16 2020-11-25 10:22:29 - GetCurrentConsoleFontEx 1 nFont=0 dwFontSize={X=200 Y=58} FontFamily=1 FontWeight=1 FaceName='Liberation Mono' 2020-11-25 10:22:29 - GetCurrentConsoleFontEx 2 nFont=0 dwFontSize={X=200 Y=58} FontFamily=1 FontWeight=1 FaceName='Liberation Mono' Vladimir Koković, DP senior(70), Serbia, Belgrade, 25.November 2020 -- 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 1

[Bug 34326] New: uplive.exe from TypeEasy crashes
by wine-bugs＠winehq.org 11 Feb '22

11 Feb '22

http://bugs.winehq.org/show_bug.cgi?id=34326 Bug #: 34326 Summary: uplive.exe from TypeEasy crashes Product: Wine Version: 1.7.0 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: wininet AssignedTo: wine-bugs(a)winehq.org ReportedBy: jactry92(a)gmail.com Classification: Unclassified Created attachment 45694 --> http://bugs.winehq.org/attachment.cgi?id=45694 backtrace.txt reproduce it follow this: 0. download and install TypeEasy. Sorry for there is not a english version, you can install by click the button which with those word: "下一步(N)" -> "我接受(N)" -> "下一步(N)" -> "安装(I)" -> "完成(F)"; 1. TypeEasy will starup after the installation, the exit it. And uplive.exe will crash as soon as you exit TypeEasy. -- 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 7

[Bug 51130] New: user32:win test_SetActiveWindow() has 2 failures on Vista to Windows 8.1
by WineHQ Bugzilla 11 Feb '22

11 Feb '22

https://bugs.winehq.org/show_bug.cgi?id=51130 Bug ID: 51130 Summary: user32:win test_SetActiveWindow() has 2 failures on Vista to Windows 8.1 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:win test_SetActiveWindow() has 2 systematic failures on Vista to Windows 8.1 which don't happen on Windows 10: https://test.winehq.org/data/patterns.html#user32:win win.c:3191: Test failed: GetActiveWindow() = 00000000 win.c:3191: Test failed: GetFocus() = 00000000 The failing test was introduced by this commit: commit e188d66251e6f9693629fe3e1bfa4bd2e9a534cf Author: Zebediah Figura <z.figura12(a)gmail.com> AuthorDate: Tue Dec 19 18:29:30 2017 -0600 Commit: Alexandre Julliard <julliard(a)winehq.org> CommitDate: Wed Dec 20 17:48:57 2017 +0100 user32/tests: Add more tests for SetActiveWindow(). Signed-off-by: Zebediah Figura <z.figura12(a)gmail.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.

1 11

[Bug 48815] New: user32:win "unexpected 0x738 message" Windows 10 failures
by WineHQ Bugzilla 11 Feb '22

11 Feb '22

https://bugs.winehq.org/show_bug.cgi?id=48815 Bug ID: 48815 Summary: user32:win "unexpected 0x738 message" Windows 10 failures Product: Wine Version: unspecified Hardware: x86 OS: Windows Status: NEW Severity: major Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com user32:win sometimes fails complaining about an unexpected 0x738 message: win.c:3858: Test failed: message 0738 available or win.c:3852: Test failed: hwnd 00210500 message 0738 This second message includes the window handle which means it is "always new", which can cause the TestBot to mistakenly attribute the failure to the patch being tested. So I bumped the priority on this bug. >From what I gathered the 0x738 message was introduced in Windows 10 1703 which is why this failure only happens on our 1709+ test configurations (we don't have 1703). Also nobody seems to know what this message is, only that it seems to be related to windows belonging to the UserAdapterWindowClass: https://forums.zimbra.org/viewtopic.php?t=63188 https://stackoverflow.com/questions/44395364/windows-creators-update-crashe… https://github.com/otya128/winevdm/issues/114 -- 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 4