August 2021 - 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 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 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 9901] New: GetMonitorInfo returns wrong work area
by wine-bugs＠winehq.org 27 Aug '22

27 Aug '22

http://bugs.winehq.org/show_bug.cgi?id=9901 Summary: GetMonitorInfo returns wrong work area Product: Wine Version: CVS/GIT Platform: Other OS/Version: other Status: UNCONFIRMED Severity: normal Priority: P2 Component: wine-x11driver AssignedTo: wine-bugs(a)winehq.org ReportedBy: lich(a)math.spbu.ru GetMontorInfo always returns rcWork equal to rcMonitor, but it must take panels and taskbars into account. The only solution I can see is to use SystemParametersInfo(SPI_SETWORKAREA) during initialization time, but I do not know how to deal with different monitors. P.S. It is needed to properly implement maximum dimensions of console window. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

2 30

[Bug 47618] New: Required gstreamer plugins not installed by Debian packages
by wine-bugs＠winehq.org 25 Aug '22

25 Aug '22

https://bugs.winehq.org/show_bug.cgi?id=47618 Bug ID: 47618 Summary: Required gstreamer plugins not installed by Debian packages Product: Packaging Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: wine-packages Assignee: wine-bugs(a)winehq.org Reporter: jre.winesim(a)gmail.com CC: dimesio(a)earthlink.net, michael(a)fds-team.de, sebastian(a)fds-team.de Distribution: --- Hi, from https://bugs.launchpad.net/ubuntu/+source/wine/+bug/1817244 and followup reading at winehq I learned that several gstreamer plugins are required for some media, but the Debian packages don't install them. In this specific case I couldn't reproduce the issue as long as libmpg123-0:i386 was installed. But I assume current Wine still generally needs them!? Please comment. Unless you have some other input, I'm going to fix this in the debian.org packages, and suggest you do something similar in the winehq -i386 and -amd64 packages: Recommends: gstreamer1.0-libav, gstreamer1.0-plugins-good, gstreamer1.0-plugins-ugly, This works on Debian unstable. gstreamer1.0-plugins-bad still has non multi-arch'd dependencies. I'll try to get those fixed. I assume some other distros don't support multi-arch for the previous 3 packages, so you might have to add this conditionally. Also some distros might still use gstreamer 0.10. Greets! jre -- 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 43193] New: MinGW-w64 GUI installer fails 66 per cent through its file-installation page.
by wine-bugs＠winehq.org 25 Aug '22

25 Aug '22

https://bugs.winehq.org/show_bug.cgi?id=43193 Bug ID: 43193 Summary: MinGW-w64 GUI installer fails 66 per cent through its file-installation page. Product: Wine-staging Version: 2.10 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: irwin(a)beluga.phys.uvic.ca CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de, sebastian(a)fds-team.de Distribution: --- My platform is Debian Jessie, and I am using the WineHQ repository for that distro following the advice at <https://wine-staging.com/installation.html>. I installed the latest version (2.10) of winehq-staging and set the environment variables export WINEVERSION=2.10_jessie_wine_staging export WINEPREFIX=/home/wine/wine_staging/.wine-$WINEVERSION export WINEDEBUG='fixme-all' and ran winecfg taking defaults for everything. Then wine(a)raven> wine --version wine-2.10 (Staging) wineserver -p nice -19 wine msys2-x86_64-20161025.exe Welcome screen, set prefix (added date string to default location), start menu shortcuts left as they were, then install page went to the 66 per cent level and then generated a Program Error GUI box with the message The program bash.exe has encountered a serious error and needs to close. We are sorry for the inconvenience. Program error details page on GUI was empty. stderr (or stdout) had the following messages on the konsole instance I was running: err:ole:CoCreateInstanceEx apartment not initialised err:ole:CoCreateInstanceEx apartment not initialised err:ole:CoCreateInstanceEx apartment not initialised wine: Unhandled page fault on read access to 0x00000020 at address 0x7bc4b478 (thread 0045), starting debugger... The installer GUI details showed the install failed (at the ~66 per cent mark) while installing nansi.sys. This is definitely a wine-staging bug because the equivalent experiment with vanilla wine-2.10 (obtained by purging winehq-staging and installing winehq-devel) had no troubles with that install page of the GUI (although the above "apartment" warnings were produced), but failed in other ways on the final page of that GUI. Note it is likely this current wine-staging bug with the initial file installation has been introduced in the past year since <https://github.com/TeaCI/tea-ci/wiki/Msys2-on-Wine> implies MSYS2 works on Wine-staging, and that page was last updated in July last year. However, introduction of this wine-staging bug is not extremely recent because I replicated this bug also for wine-staging 2.4 (the earliest version [released March 2017] currently available for the winehq Debian Jessie repository. -- 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 47922] New: Speech synthesis does not start in Logos Bible Software
by WineHQ Bugzilla 22 Aug '22

22 Aug '22

https://bugs.winehq.org/show_bug.cgi?id=47922 Bug ID: 47922 Summary: Speech synthesis does not start in Logos Bible Software Product: Wine Version: 4.17 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: sapi Assignee: wine-bugs(a)winehq.org Reporter: johnpgoodman(a)gmail.com Distribution: --- Logos Bible Software will read audio using sapi from almost any of the books except those published by Zondervan. Using wine starting speech causes a crash. Installing sapi there is no long a crash but there is no audio. 0040:fixme:path:parse_url failed to parse L"System.Speech" 0040:fixme:wtsapi:WTSUnRegisterSessionNotification Stub 00030084 -- 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 32