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

[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

[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 51882] New: Application using third party DLL can't use COM object (class not registered)
by WineHQ Bugzilla 26 Aug '22

26 Aug '22

https://bugs.winehq.org/show_bug.cgi?id=51882 Bug ID: 51882 Summary: Application using third party DLL can't use COM object (class not registered) Product: Wine Version: 6.18 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: dark.shadow4(a)web.de Distribution: --- Reported in the forums: https://forum.winehq.org/viewtopic.php?f=8&t=32385 -- 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 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