wine-bugs April 2022

wine-bugs@winehq.org

1 participants
3592 discussions

[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 39627] New: BreezeBrowser Pro 1.x crashes on start
by wine-bugs＠winehq.org 25 Aug '22

25 Aug '22

https://bugs.winehq.org/show_bug.cgi?id=39627 Bug ID: 39627 Summary: BreezeBrowser Pro 1.x crashes on start Product: Wine Version: 1.7.34 Hardware: x86 URL: http://www.breezesys.com/downloads/bbpro1987.exe OS: Linux Status: NEW Keywords: download, regression Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: gyebro69(a)gmail.com CC: erich.e.hoover(a)wine-staging.com Regression SHA1: ca51e113e4820f8b11016c13732b1a971d2b0054 Distribution: --- The application crashes immediately after starting (no backtrace is generated for me): fixme:heap:RtlSetHeapInformation (nil) 1 (nil) 0 stub fixme:ntdll:server_ioctl_file Unsupported ioctl 900a8 (device=9 access=0 func=2a method=0) fixme:ntdll:server_ioctl_file Unsupported ioctl 900a8 (device=9 access=0 func=2a method=0) wine: Unhandled exception 0x40000015 in thread 9 at address 0x80d930 (thread 0009), starting debugger... If you manually create an empty 'dbglogs' directory under ~/Documents, then the application starts properly.It seems the application fails to create that directory for some reason. Regression introduced by commit ca51e113e4820f8b11016c13732b1a971d2b0054 Author: Erich E. Hoover <erich.e.hoover(a)gmail.com> Date: Tue Aug 19 20:31:00 2014 -0600 ntdll: Unify retrieving the attributes of a file. The commit can't be reverted on git (Wine build failure), however the application starts properly with the previous commit (and dbglogs directory is created). Still present in wine-1.7.55-73-g39f2ed3. bbpro1987.exe sha1: ead99cf82bc8eeac4413ed4939891bbe57251058 -- 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 15

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

[Bug 51086] New: Could not load kernel32.dll
by WineHQ Bugzilla 22 Aug '22

22 Aug '22

https://bugs.winehq.org/show_bug.cgi?id=51086 Bug ID: 51086 Summary: Could not load kernel32.dll Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: blocker Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: johnallanlambert1(a)gmail.com Distribution: --- I can't open any wine or wine-related program, and when I type winecfg in terminal I get the following error: wine: could not load kernel32.dll, status c0000135 I have tried deleting the ~/.wine folder, reinstalling wine, and changing between 32-bit and 64-bit wine prefixes. This bug completely prevents me from using wine at all. Wine version: 6.7 Linux distribution: Manjaro KDE Everything on my system is up to date. -- 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 28

[Bug 29614] New: WinRAR viewer crashes on a particular file
by wine-bugs＠winehq.org 22 Aug '22

22 Aug '22

http://bugs.winehq.org/show_bug.cgi?id=29614 Bug #: 29614 Summary: WinRAR viewer crashes on a particular file Product: Wine Version: 1.3.37 Platform: x86 URL: http://www.rarlabs.com/rar/wrar401.exe OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: richedit AssignedTo: wine-bugs(a)winehq.org ReportedBy: t.artem(a)mailcity.com Classification: Unclassified Created attachment 38365 --> http://bugs.winehq.org/attachment.cgi?id=38365 Test file When trying to view the attached file, WinRAR crashes. Steps to reproduce, download the file, install and run WinRAR, click Commands -> View File (Alt + V). (Viewer settings: view as Windows text, word wrap enabled). caret.c:208: ME_GetCursorCoordinates: Assertion `~para->member.para.nFlags & 0x01' failed. wine: Assertion failed at address 0xb776f424 (thread 0046), starting debugger... Unhandled exception: assertion failed in 32-bit code (0xb776f424). Register dump: CS:0073 SS:007b DS:007b ES:007b FS:0033 GS:003b EIP:b776f424 ESP:00322904 EBP:0032291c EFLAGS:00000202( - -- I - - - ) EAX:00000000 EBX:00006589 ECX:00006589 EDX:00000006 ESI:b758b74a EDI:b75c7ff4 Stack dump: 0x00322904: 0032291c 00000006 00006589 b746d2f1 0x00322914: b75c7ff4 00322a3c 00322a44 b746ed5e 0x00322924: 00000006 003229bc 00000000 b75c7ff4 0x00322934: 00000060 00000001 00322a54 00322980 0x00322944: 00000000 00000068 0000005c b75c93a0 0x00322954: b75c7ff4 0000005c 0000005b 00322a2c Backtrace: =>0 0xb776f424 __kernel_vsyscall+0x10() in [vdso].so (0x0032291c) 1 0xb746d2f1 gsignal+0x50() in libc.so.6 (0x0032291c) 2 0xb746ed5e abort+0x17d() in libc.so.6 (0x00322a44) 3 0xb7465c08 __assert_fail+0xf7() in libc.so.6 (0x00322a8c) 4 0x7dbc5657 ME_MoveCaret+0x496() in riched20 (0x00322b5c) 5 0x7dbd79c2 ME_PaintContent+0xc1() in riched20 (0x00322c0c) 6 0x7dbd399d RichEditWndProc_common+0x3bc() in riched20 (0x00322ccc) 7 0x7dbd3ccc RichEditWndProcW+0x2b() in riched20 (0x00322cfc) 8 0x7ec2b4ea WINPROC_wrapper+0x19() in user32 (0x00322d2c) 9 0x7ec2bc3c call_window_proc+0x5b() in user32 (0x00322d7c) 10 0x7ec2e10d WINPROC_call_window+0x10c() in user32 (0x00322dcc) 11 0x7ebf0b0e DispatchMessageW+0x9d() in user32 (0x00322ebc) 12 0x0049aa76 in winrar (+0x9aa75) (0x00328308) 13 0x7dbcf53b ME_HandleMessage+0xcba() in riched20 (0x00328c48) 14 0x7dbd3764 RichEditWndProc_common+0x183() in riched20 (0x00328d08) 15 0x7dbd3ccc RichEditWndProcW+0x2b() in riched20 (0x00328d38) 16 0x7ec2b4ea WINPROC_wrapper+0x19() in user32 (0x00328d68) 17 0x7ec2bc3c call_window_proc+0x5b() in user32 (0x00328db8) 18 0x7ec2e10d WINPROC_call_window+0x10c() in user32 (0x00328e08) 19 0x7ebeec61 call_window_proc+0x90() in user32 (0x00328e78) 20 0x7ebf5456 send_message+0x205() in user32 (0x00328ef8) 21 0x7ebf58cc SendMessageW+0x4b() in user32 (0x00328f48) 22 0x0049dbf5 in winrar (+0x9dbf4) (0x7ebf5880) 23 0x458b48ec (0x83e58955) 0xb776f424 __kernel_vsyscall+0x10 in [vdso].so: popl %ebp Modules: ... Backtrace: =>0 0xb776f424 __kernel_vsyscall+0x10() in [vdso].so (0x0032291c) 1 0xb746d2f1 gsignal+0x50() in libc.so.6 (0x0032291c) 2 0xb746ed5e abort+0x17d() in libc.so.6 (0x00322a44) 3 0xb7465c08 __assert_fail+0xf7() in libc.so.6 (0x00322a8c) 4 0x7dbc5657 ME_MoveCaret+0x496() in riched20 (0x00322b5c) 5 0x7dbd79c2 ME_PaintContent+0xc1() in riched20 (0x00322c0c) 6 0x7dbd399d RichEditWndProc_common+0x3bc() in riched20 (0x00322ccc) 7 0x7dbd3ccc RichEditWndProcW+0x2b() in riched20 (0x00322cfc) 8 0x7ec2b4ea WINPROC_wrapper+0x19() in user32 (0x00322d2c) 9 0x7ec2bc3c call_window_proc+0x5b() in user32 (0x00322d7c) 10 0x7ec2e10d WINPROC_call_window+0x10c() in user32 (0x00322dcc) 11 0x7ebf0b0e DispatchMessageW+0x9d() in user32 (0x00322ebc) 12 0x0049aa76 in winrar (+0x9aa75) (0x00328308) 13 0x7dbcf53b ME_HandleMessage+0xcba() in riched20 (0x00328c48) 14 0x7dbd3764 RichEditWndProc_common+0x183() in riched20 (0x00328d08) 15 0x7dbd3ccc RichEditWndProcW+0x2b() in riched20 (0x00328d38) 16 0x7ec2b4ea WINPROC_wrapper+0x19() in user32 (0x00328d68) 17 0x7ec2bc3c call_window_proc+0x5b() in user32 (0x00328db8) 18 0x7ec2e10d WINPROC_call_window+0x10c() in user32 (0x00328e08) 19 0x7ebeec61 call_window_proc+0x90() in user32 (0x00328e78) 20 0x7ebf5456 send_message+0x205() in user32 (0x00328ef8) 21 0x7ebf58cc SendMessageW+0x4b() in user32 (0x00328f48) 22 0x0049dbf5 in winrar (+0x9dbf4) (0x7ebf5880) 23 0x458b48ec (0x83e58955) -- 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 32

[Bug 37873] New: Pokemon TCGO version 4.5.5 crashes during startup
by wine-bugs＠winehq.org 21 Aug '22

21 Aug '22

https://bugs.winehq.org/show_bug.cgi?id=37873 Bug ID: 37873 Summary: Pokemon TCGO version 4.5.5 crashes during startup Product: Wine Version: 1.7.3 Hardware: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: lppoulin(a)gmail.com Distribution: --- Pokemon TCGO version 4.X.X used to work perfectly. In December 2014, after an auto-update to version 4.5.5 it started to crash at startup. Has anyone been able to make it 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 13

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-bugs April 2022