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

[Bug 51289] New: ws2_32:sock has siocatmark failures on wvistau64
by WineHQ Bugzilla 27 Aug '22

27 Aug '22

https://bugs.winehq.org/show_bug.cgi?id=51289 Bug ID: 51289 Summary: ws2_32:sock has siocatmark failures on wvistau64 Product: Wine Version: 6.10 Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: winsock Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com ws2_32:sock fails quite consistently on wvistau64: https://test.winehq.org/data/patterns.html#ws2_32:sock sock.c:3838: Test failed: FIONBIO returned 0 sock.c:3838: Test failed: SIOCATMARK returned 1 sock.c:3848: Test failed: FIONBIO returned 0 These failures happen consistently for both 32- and 64-bit tests on wvistau64 but only the 64-bit WineTest is run daily. They don't happen at all on wvista though so there must be some difference between these two VMs. wvista has the older ws2_32 dll (6.0.6001.18000 vs. 6.0.6002.18005 for wvistau64), which means the failures happen on the more recent ws2_32. This makes no sense so the root cause is probably elsewhere. The failures look like they might be timing related but while adding a Sleep(50) before the failing lines avoid the first 3838 failure, it's not reliable and does nothing for the 3848 failure. The failing tests were introduced in this commit: commit 2795fa9c00338bfff6304c1b756d1a58f9f6ca60 Author: Zebediah Figura <z.figura12(a)gmail.com> Date: Thu May 27 18:57:31 2021 -0500 ws2_32/tests: Separate and expand tests for FIONREAD and SIOCATMARK. Signed-off-by: Zebediah Figura <z.figura12(a)gmail.com> Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> But the TestBot only reported the failures for the next patch in the series: https://www.winehq.org/pipermail/wine-devel/2021-May/187782.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 48851] New: WinSCP file transfer "The specified data could not be decrypted"
by WineHQ Bugzilla 27 Aug '22

27 Aug '22

https://bugs.winehq.org/show_bug.cgi?id=48851 Bug ID: 48851 Summary: WinSCP file transfer "The specified data could not be decrypted" Product: Wine Version: 4.0.3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: tim.c.quinn(a)gmail.com Distribution: --- Created attachment 66775 --> https://bugs.winehq.org/attachment.cgi?id=66775 This is the file that failes. Its from the Apache log4net project I've been using WinSCP on wine for years and just hit my first big issue and it appears to be a wine issue. I was trying to transfer an xml file to an IIS server on Windows Server 2019 and it fails on the client side with the error: - Copying files to remote side failed. - The specified data could not be decrypted. The version of WinSCP I am using is 5.17.2 portable. The same issue occurs with WinSCP 5.11.3 portable. The error on 5.11.3 is a bit more verbose: - Using TLSv1.2, cipher TLSv1/SSLv3: ECDHE-RSA-AES256-GCM-SHA384, 2048 bit RSA, ECDHE-RSA-AES256-GCM-SHA384 TLSv1.2 Kx=ECDH Au=RSA Enc=AESGCM(256) Mac=AEAD - Copying files to remote side failed. - The specified data could not be decrypted. To isolate if this is a WinSCP issue or a Windows issue, I deployed the exact same WinSCP 5.17.2 on Windows Server 2008R2 and the file transferred ok with no errors. I suspect this issue is related to TLS libraries deployed with Wine. -- 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 6

[Bug 52316] New: Windows Error
by WineHQ Bugzilla 27 Aug '22

27 Aug '22

https://bugs.winehq.org/show_bug.cgi?id=52316 Bug ID: 52316 Summary: Windows Error Product: Wine Version: 7.0-rc1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: api-ms-win-* Assignee: wine-bugs(a)winehq.org Reporter: liaolllll5(a)iCloud.com Distribution: --- Created attachment 71477 --> https://bugs.winehq.org/attachment.cgi?id=71477 The record $winecfg open a window in a strange shape -- 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 52742] New: Text in About windows is blacked out when running in 256-color Xephyr
by WineHQ Bugzilla 27 Aug '22

27 Aug '22

https://bugs.winehq.org/show_bug.cgi?id=52742 Bug ID: 52742 Summary: Text in About windows is blacked out when running in 256-color Xephyr Product: Wine Version: 7.5 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: winex11.drv Assignee: wine-bugs(a)winehq.org Reporter: alexhenrie24(a)gmail.com Distribution: --- Created attachment 72107 --> https://bugs.winehq.org/attachment.cgi?id=72107 Screenshot Steps to reproduce: 1. In one terminal, run `Xephyr :1 -ac -screen 800x600x8`. 2. In another terminal, run `DISPLAY=:1 wine notepad`. 3. Click Help, then click About Notepad. -- 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 40834] New: Steam for windows, used on a linux OS, using WINE to run, hardly works at all, I don't know why.
by wine-bugs＠winehq.org 27 Aug '22

27 Aug '22

https://bugs.winehq.org/show_bug.cgi?id=40834 Bug ID: 40834 Summary: Steam for windows, used on a linux OS, using WINE to run, hardly works at all, I don't know why. Product: Wine Version: 1.9.12 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: blocker Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: cherrytreesforever(a)yahoo.com Distribution: --- Created attachment 54796 --> https://bugs.winehq.org/attachment.cgi?id=54796 this is from the crash report I have no idea what it says Upon launching steam using WINE I get a crash report. I saved it, you can read up on it. Basically using Linux Zorin I am, the UI is horribly glitchy and the entire app is completely unusable. The only reason I need to use a windows version of steam should be obvious: Windows games and all. Anyways, I am not sure about this bug, nor do I know enough about linux to provide much more info, other than the saved doc with the error imprinted in it from the report itself. -- 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 19

[Bug 40104] New: ReplayGain by Foobar
by wine-bugs＠winehq.org 27 Aug '22

27 Aug '22

https://bugs.winehq.org/show_bug.cgi?id=40104 Bug ID: 40104 Summary: ReplayGain by Foobar Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: adl-88(a)posteo.de Distribution: --- ReplayGain by Foobar gains only with standardoptions and it ignores every change. So if I want to write with "+0.0db" to get "89db" on a track he will do this. But if I want to write with "+6,00" to get "95db" on a track he also writes with "0,0db". It seems that its a debian versions problem. Ubuntu versions works fine. But I dont use ubuntu anymore. -- 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 4

[Bug 52702] New: Old DLLs left in system32 and syswow
by WineHQ Bugzilla 27 Aug '22

27 Aug '22

https://bugs.winehq.org/show_bug.cgi?id=52702 Bug ID: 52702 Summary: Old DLLs left in system32 and syswow Product: Wine Version: 7.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: mikes(a)kuentos.guam.net Distribution: --- Noticed a difference with running wine under my regular user versus a new setup with root user for testing? Found my user had a number of dll files in directories were older recent install under the root user?? Moved old dll to dll.org and then copied the newer one from root? Fixed my problem, but not sure why the dlls hadn't been updated like most others? Some just a few months, but one was from 1998? 623771 Feb 22, 2022 ./system32/concrt140.dll 309136 Dec 3, 2021 ./system32/concrt140.dll.org 124624 Feb 22, 2022 ./system32/msvcp140_1.dll 23928 Dec 3, 2021 ./system32/msvcp140_1.dll.org 114163 Feb 22, 2022 ./system32/msvcp140_atomic_wait.dll 41360 Dec 3, 2021 ./system32/msvcp140_atomic_wait.dll.org 4228026 Feb 22, 2022 ./system32/msvcp140.dll 564088 Dec 3, 2021 ./system32/msvcp140.dll.org 217458 Feb 22, 2022 ./system32/vcruntime140_1.dll 36728 Dec 3, 2021 ./system32/vcruntime140_1.dll.org 111872 Feb 22, 2022 ./system32/vcruntime140.dll 96144 Dec 3, 2021 ./system32/vcruntime140.dll.org 721621 Feb 22, 2022 ./syswow64/atl.dll 73785 Feb 11, 2000 ./syswow64/atl.dll.org 82113 Feb 22, 2022 ./syswow64/comcat.dll 22288 Feb 11, 2000 ./syswow64/comcat.dll.org 498588 Feb 22, 2022 ./syswow64/concrt140.dll 243600 Dec 3, 2021 ./syswow64/concrt140.dll.org 586315 Feb 22, 2022 ./syswow64/msvcirt.dll 77878 Jun 16, 1998 ./syswow64/msvcirt.dll.org 95914 Feb 22, 2022 ./syswow64/msvcp140_1.dll 21368 Dec 3, 2021 ./syswow64/msvcp140_1.dll.org 101627 Feb 22, 2022 ./syswow64/msvcp140_atomic_wait.dll 39288 Dec 3, 2021 ./syswow64/msvcp140_atomic_wait.dll.org 3310918 Feb 22, 2022 ./syswow64/msvcp140.dll 436600 Dec 3, 2021 ./syswow64/msvcp140.dll.org 2807249 Feb 22, 2022 ./syswow64/msvcp60.dll 401462 Jun 16, 1998 ./syswow64/msvcp60.dll.org 4404513 Feb 22, 2022 ./syswow64/oleaut32.dll 598288 Feb 11, 2000 ./syswow64/oleaut32.dll.org 121449 Feb 22, 2022 ./syswow64/olepro32.dll 164112 Feb 11, 2000 ./syswow64/olepro32.dll.org 95194 Feb 22, 2022 ./syswow64/vcruntime140.dll 76152 Dec 3, 2021 ./syswow64/vcruntime140.dll.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 6

[Bug 47953] New: Adobe Reader is DC fails to load files
by WineHQ Bugzilla 27 Aug '22

27 Aug '22

https://bugs.winehq.org/show_bug.cgi?id=47953 Bug ID: 47953 Summary: Adobe Reader is DC fails to load files Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: varia.3(a)osu.edu Distribution: --- This issues happens in multiple versions of Wine. Starting with Adobe Reader DC version 19.012.20034 and onward I am unable to open a PDF file in Adobe reader on wine. If you go one version before to Reader DC version 19.010.20100 then Adobe reader installs and opens PDFs just fine. Something changed in 19.012.x onward that has broken 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.

1 5

[Bug 48028] New: Error trying to install instanlling Adobe ADE 4.5
by WineHQ Bugzilla 27 Aug '22

27 Aug '22

https://bugs.winehq.org/show_bug.cgi?id=48028 Bug ID: 48028 Summary: Error trying to install instanlling Adobe ADE 4.5 Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: carlosm1979(a)gmail.com Distribution: --- Error trying to install instanlling Adobe ADE 4.5 -- 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 6

[Bug 52647] New: wine-staging 7.3 fails to run on debian11 (but work on Debian10)
by WineHQ Bugzilla 27 Aug '22

27 Aug '22

https://bugs.winehq.org/show_bug.cgi?id=52647 Bug ID: 52647 Summary: wine-staging 7.3 fails to run on debian11 (but work on Debian10) Product: Wine-staging Version: unspecified 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 CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- I'm try to run some CUDA application (Cuda-Z, Warpem) on Debian11. Both appliations are running find under wine-staging 7.3 on some Debian10 machines. When trying to install wine-staging on some Debian11 machines (either upgraded from Debian10, or installed Debian11 from scratch) and following the these instructions [1] of installing wine, wine fails to run, and switches into debug mode. Here is the short log, when the WINEPREFIX did alreay exist. 002c:fixme:winediag:LdrInitializeThunk wine-staging 7.3 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 00007FB4D8B485C0 at address 00007FB4D8B485C0 (thread 0068), starting debugger... wine: Unhandled page fault on execute access to 00007FDE04B370D0 at address 00007FDE04B370D0 (thread 00c8), starting debugger... wine: Unhandled page fault on execute access to 00007FAD3A6C05C0 at address 00007FAD3A6C05C0 (thread 00dc), starting debugger... wine: Unhandled page fault on execute access to 00007F12CA1970D0 at address 00007F12CA1970D0 (thread 00f0), starting debugger... I remember that a few weeks ago, I could make wine-staging (v7.1?) running on Debian11. But I can not reproduce this anymore. I'm suspecting that some dependencies on libraries have changed, or some dependencies are not correct in the debian/control file. Or that some some differences in the build environment and my setup is in place I tried checking finding differences in the packages installed, and fixed a number of difference, but there are too many. And I've not been successful so far. Do you have any ideas how to proceed and identify what the problem might be ? [1] https://wiki.winehq.org/Debian -- 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 21