July 2020 - Wine-Bugs - list.winehq.org

[Bug 48410] New: The "Add syscall thunks for 64 bit" patch partly breaks USVFS
by WineHQ Bugzilla Aug. 15, 2020

Aug. 15, 2020

https://bugs.winehq.org/show_bug.cgi?id=48410 Bug ID: 48410 Summary: The "Add syscall thunks for 64 bit" patch partly breaks USVFS Product: Wine-staging Version: 5.0-rc3 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: qsniyg(a)mail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- This is the patch that breaks USVFS: https://github.com/wine-staging/wine-staging/blob/d36d63ac848dadbc2c8ffc933… (discussion: https://github.com/ModOrganizer2/modorganizer/issues/372) I've only tested 64-bit, so it's possible https://github.com/wine-staging/wine-staging/blob/master/patches/winebuild-… also affects it. Although USVFS works for the most part, loading DLLs fails, because LdrLoadDll (within ntdll) calls NtOpenFile (through open_dll_file), but for some reason, USVFS doesn't recognize that specific NtOpenFile call (even though it hooks other NtOpenFile calls that aren't called from ntdll without issue). I haven't looked through the patch in much detail, but from what I can tell I believe the reason why this patch breaks USVFS is because the calls to NtOpenFile from within ntdll use the direct function address, whereas with the patch, USVFS now hooks a new "wrapper" around the function, instead of the same address that ntdll calls internally. -- 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 9

[Bug 44571] New: Unable to build cue sheets with IMGBurn
by wine-bugs＠winehq.org Aug. 15, 2020

Aug. 15, 2020

https://bugs.winehq.org/show_bug.cgi?id=44571 Bug ID: 44571 Summary: Unable to build cue sheets with IMGBurn Product: Wine-staging Version: 3.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: halo117nachos(a)gmail.com CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de, sebastian(a)fds-team.de Distribution: --- Created attachment 60538 --> https://bugs.winehq.org/attachment.cgi?id=60538 stderr and stdout Everytime I try to build a cue sheet out of MP3 files with IMGBurn, the program crashes. Building a cue sheet is the first step in burning MP3 (and other audio files) to standard red book audio discs, so if one can't build a cue sheet, one can't burn music. Of course, I made a new wine prefix to test this, and found that it didn't solve the problem at all. :( Here's what happens: If I click the tools menu, and select "Create Cue File... ", and I start manually adding MP3s, first the program hangs, and then it says the following: "Potential Direct Show Error! - No data has been received for 10 seconds file name: C:\blablabla\file.mp3 Decoding Progress: 9,999,999 bytes" It then gives me three options: "Cancel", "Try Again", and "Continue". BTW, that number (9,999,999) seems to very with each MP3 file. It's possible that whatever number it lands on is the end of the file. I also tend to get a more generic error, although this one is harder to reproduce. IDK if this is the same bug or not. The error is: "An error occured in the application There might be an updated version available that fixes the pr [the rest of this line seems to be cut off by some buttons on the right] Please check the website for updates - http://www.imgburn.co [once again, the message is cut off]" There are three buttons on the bottom, and three on the right (the ones on the right are the ones that cut off the text). The ones on the bottom are "send bug report", "save bug report", and "show bug report". The buttons on the right are "Continue application", "Restart application", and "Close application". If I click "Continue application", the program seems to continue working. PS: I've just run IMGBurn from the terminal, and redirected both stdout and stderr to a file, which I've attached to this report. When the aformentioned "generic" error message appeared. I tried to click "Close application", but the program froze, forcing me to kill it. That error happened on the second file. BTW, I'm running Ubuntu 16.04, and I've installed winehq-devel 3.2 from the official repositories. Also, I didn't modify the prefix at all, except to install IMGBurn, and to change the default version of Windows to XP (otherwise IMGBurn doesn't start). -- 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 49514] New: Wine-staging 5.12 package building fails
by WineHQ Bugzilla Aug. 15, 2020

Aug. 15, 2020

https://bugs.winehq.org/show_bug.cgi?id=49514 Bug ID: 49514 Summary: Wine-staging 5.12 package building fails Product: Wine-staging Version: 5.12 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: dimesio(a)earthlink.net CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- The wine-devel 5.12 packages built without any problem, but most of the wine-staging 5.12 packages failed. The only ones that successfully built were for the two oldest distros we package for, Debian 9.0 and Ubuntu 16.04. What those two distros have in common is that they can't be built with FAudio support. I've attached the failed build log from Fedora 32 here; logs for the other distros we build for are on https://build.opensuse.org/package/show/Emulators:Wine:Fedora/wine-staging and https://build.opensuse.org/package/show/Emulators:Wine:Debian/wine-staging. -- 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 8

[Bug 48883] New: Cygwin installation
by WineHQ Bugzilla Aug. 15, 2020

Aug. 15, 2020

https://bugs.winehq.org/show_bug.cgi?id=48883 Bug ID: 48883 Summary: Cygwin installation Product: Wine Version: 5.5 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: megastallman(a)gmail.com Distribution: --- Created attachment 66827 --> https://bugs.winehq.org/attachment.cgi?id=66827 wine client error:34: read: Bad file descriptor I'm trying to install 32-bit Cygwin. The installer starts, downloads tarballs, then just hangs with the "wine client error:34: read: Bad file descriptor". Wineboot doesn't help. Download link: https://cygwin.com/setup-x86.exe My current wine installation is done into a 32-bit Xubuntu18.04 chroot, where the latest wine-staging is built and used. So I can update/rebuild any time required. Doing "~/.wine", build and installation directories deletion every rebuild. The host system - is Opensuse Thumbleweed x86_64. Choot allows X11 and OpenGL throughput, e.g. - I can run glxgears. See the crashlog in attachment. -- 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 49577] New: Segmentation fault when running winecfg in Staging
by WineHQ Bugzilla Aug. 15, 2020

Aug. 15, 2020

https://bugs.winehq.org/show_bug.cgi?id=49577 Bug ID: 49577 Summary: Segmentation fault when running winecfg in Staging Product: Wine-staging Version: 5.12 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: gyebro69(a)gmail.com CC: leslie_alistair(a)hotmail.com, pgofman(a)codeweavers.com, z.figura12(a)gmail.com Distribution: ArchLinux I'm using a mingw-enabled Wine build now. Vanilla Wine doesn't have this problem, but Staging does. When I issue either winecfg or wineboot -u to create or update a wineprefix, I 'm getting only "Segmentation Fault (core dumped)" in the terminal. WINEDEBUG=+all wine winecfg: trace:virtual:free_ranges_remove_range view 0x7bc00000-0x7bf60000 (0x7bc00000). trace:module:map_image_into_view mapped PE file at 0x7bc00000-0x7bf5b000 trace:module:map_image_into_view mapping section .text at 0x7bc01000 off 600 size 68e00 virt 68d7c flags 60500020 trace:module:map_image_into_view clearing 0x7bc69e00 - 0x7bc6a000 Due to lack of time I couldn't perform a regression test yet. What I see is that Wine-Staging 5.11 works, Staging 5.12.1 and Staging/master are equally broken. Maybe this has already been reported here on bugzilla and I just couldn't find the corresponding bug report. -- 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 8

[Bug 40958] New: Toontown Rewritten has major lag on wine-staging on FreeBSD and GNOME 3
by wine-bugs＠winehq.org Aug. 15, 2020

Aug. 15, 2020

https://bugs.winehq.org/show_bug.cgi?id=40958 Bug ID: 40958 Summary: Toontown Rewritten has major lag on wine-staging on FreeBSD and GNOME 3 Product: Wine-staging Version: 1.9.13 Hardware: x86-64 OS: FreeBSD Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: neel(a)neelc.org CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de, sebastian(a)fds-team.de Toontown Rewritten (http://toontownrewritten.com/) has major lag with keystrokes on wine-staging when I use FreeBSD and GNOME 3. TTR is a online game, and using keyboard controls often results in the display lagging by a few seconds. Other desktop environments don't have this lag to as great of an extent (I also tested TTR on Mate and Fluxbox). Is there a reason for 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.

2 4

[Bug 49555] New: Wine-Staging compilation fails after 046f6604b763ca494bece1ff16a0919077ecb9d4 (../ntdll/unix/file.c)
by WineHQ Bugzilla Aug. 15, 2020

Aug. 15, 2020

https://bugs.winehq.org/show_bug.cgi?id=49555 Bug ID: 49555 Summary: Wine-Staging compilation fails after 046f6604b763ca494bece1ff16a0919077ecb9d4 (../ntdll/unix/file.c) Product: Wine-staging Version: unspecified Hardware: x86 OS: Linux Status: NEW Keywords: download, regression, source Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: gyebro69(a)gmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Since yesterday's rebase compiling Wine-Staging fails somewhere in ../ntdll/unix/file.c. https://github.com/wine-staging/wine-staging/commit/046f6604b763ca494bece1f… gcc -m64 -c -o unix/file.o ../../../dlls/ntdll/unix/file.c -I. -I../../../dlls/ntdll -I../../include \ -I../../../include -D__WINESRC__ -D_NTSYSTEM_ -D_ACRTIMP= -D_MSVCR_VER=0 -D_REENTRANT -fPIC \ -fasynchronous-unwind-tables -Wall -pipe -fcf-protection=none -fno-stack-protector \ -fno-strict-aliasing -Wdeclaration-after-statement -Wempty-body -Wignored-qualifiers \ -Wno-packed-not-aligned -Wshift-overflow=2 -Wstrict-prototypes -Wtype-limits \ -Wunused-but-set-parameter -Wvla -Wwrite-strings -Wpointer-arith -Wlogical-op -pipe -O2 -ftree-vectorize ../../../dlls/ntdll/unix/file.c:3566:16: error: conflicting types for ‘nt_to_unix_file_name’ 3566 | NTSTATUS CDECL nt_to_unix_file_name( const UNICODE_STRING *nameW, char **unix_name_ret, | ^~~~~~~~~~~~~~~~~~~~ In file included from ../../../dlls/ntdll/unix/file.c:128: ../../../dlls/ntdll/unix/unix_private.h:243:17: note: previous declaration of ‘nt_to_unix_file_name’ was here 243 | extern NTSTATUS nt_to_unix_file_name( const UNICODE_STRING *nameW, char **name_ret, UINT disposition ) DECLSPEC_HIDDEN; | ^~~~~~~~~~~~~~~~~~~~ ../../../dlls/ntdll/unix/file.c: In function ‘NtCreateFile’: ../../../dlls/ntdll/unix/file.c:3790:31: warning: unused variable ‘objattr’ [-Wunused-variable] 3790 | struct object_attributes *objattr; | ^~~~~~~ ../../../dlls/ntdll/unix/file.c:3789:17: warning: unused variable ‘len’ [-Wunused-variable] 3789 | data_size_t len; | ^~~ ../../../dlls/ntdll/unix/file.c:3788:23: warning: unused variable ‘unix_attr’ [-Wunused-variable] 3788 | OBJECT_ATTRIBUTES unix_attr; | ^~~~~~~~~ ../../../dlls/ntdll/unix/file.c:3787:27: warning: unused variable ‘empty_string’ [-Wunused-variable] 3787 | static UNICODE_STRING empty_string; | ^~~~~~~~~~~~ At top level: ../../../dlls/ntdll/unix/file.c:3787:27: warning: ‘empty_string’ defined but not used [-Wunused-variable] make[1]: *** [Makefile:1287: unix/file.o] Error 1 make[1]: Leaving directory '/home/gyebro/sources/test/wine-staging/wine64-build/dlls/ntdll' make: *** [Makefile:8823: dlls/ntdll] Error 2 -- 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 7

[Bug 49463] New: wineserver segfaulting on exit
by WineHQ Bugzilla Aug. 15, 2020

Aug. 15, 2020

https://bugs.winehq.org/show_bug.cgi?id=49463 Bug ID: 49463 Summary: wineserver segfaulting on exit Product: Wine-staging Version: unspecified Hardware: x86 OS: Linux Status: NEW Keywords: regression Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: gyebro69(a)gmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- I don't see anything unusual in the terminal, but my systemd journal is full of these whenever wineserver quits: kernel: wineserver[1140]: segfault at 0 ip 0000000000000000 sp 00000000ffb4794c error 14 in wineserver[5f9a7000+7000] kernel: Code: Bad RIP value. To reproduce the problem run 'winecfg' then close the window by clicking <OK>. This is after today's rebase, https://github.com/wine-staging/wine-staging/commit/37fc290f7786687b95a90b5… wine-5.11-179-g13b2587d4f (Staging) on Arch Linux -- 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 45437] New: Readme' s installation instructions link leads to winehq page with no installation instructions
by wine-bugs＠winehq.org Aug. 15, 2020

Aug. 15, 2020

https://bugs.winehq.org/show_bug.cgi?id=45437 Bug ID: 45437 Summary: Readme's installation instructions link leads to winehq page with no installation instructions Product: Wine-staging Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: root(a)swooshalicio.us CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- The readme in the wine-staging repository links to https://wine-staging.com/installation.html which redirects to https://wiki.winehq.org/Wine-Staging which contains no information for installing wine-staging. -- 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 3

[Bug 48188] New: wine fails to load, "kernelbase.dll" failed to initialize, aborting
by WineHQ Bugzilla Aug. 15, 2020

Aug. 15, 2020

https://bugs.winehq.org/show_bug.cgi?id=48188 Bug ID: 48188 Summary: wine fails to load, "kernelbase.dll" failed to initialize, aborting Product: Wine Version: 4.20 Hardware: x86 OS: Linux Status: NEW Keywords: download, regression Severity: critical Priority: P2 Component: kernelbase Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com CC: julliard(a)winehq.org Distribution: --- 000b:err:module:LdrInitializeThunk "kernelbase.dll" failed to initialize, aborting 000b:err:module:LdrInitializeThunk Initializing dlls for L"C:\\windows\\system32\\wineboot.exe" failed, status c0000005 0009:err:module:LdrInitializeThunk "kernelbase.dll" failed to initialize, aborting 0009:err:module:LdrInitializeThunk Initializing dlls for L"C:\\windows\\system32\\wineboot.exe" failed, status c0000005 d05c9f12fb9409e2bc65bb59fa596c9872915d40 is the first bad commit commit d05c9f12fb9409e2bc65bb59fa596c9872915d40 Author: Alexandre Julliard <julliard(a)winehq.org> Date: Wed Nov 27 09:54:51 2019 +0100 kernelbase: Initialize codepage data using ntdll functions. Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> :040000 040000 46104b3961726d8c6d83abb04a7619008d88aad1 bedb6cb4be88dc3711d75909d60ca4d89dfb6702 M dlls mingw is enabled: austin(a)laptop ~/wine-git ((no branch, bisect started on master)) $ i686-w64-mingw32-gcc -v Using built-in specs. COLLECT_GCC=i686-w64-mingw32-gcc COLLECT_LTO_WRAPPER=/usr/libexec/gcc/i686-w64-mingw32/9.2.0/lto-wrapper Target: i686-w64-mingw32 Configured with: /var/tmp/portage/cross-i686-w64-mingw32/gcc-9.2.0-r2/work/gcc-9.2.0/configure --host=x86_64-pc-linux-gnu --target=i686-w64-mingw32 --build=x86_64-pc-linux-gnu --prefix=/usr --bindir=/usr/x86_64-pc-linux-gnu/i686-w64-mingw32/gcc-bin/9.2.0 --includedir=/usr/lib/gcc/i686-w64-mingw32/9.2.0/include --datadir=/usr/share/gcc-data/i686-w64-mingw32/9.2.0 --mandir=/usr/share/gcc-data/i686-w64-mingw32/9.2.0/man --infodir=/usr/share/gcc-data/i686-w64-mingw32/9.2.0/info --with-gxx-include-dir=/usr/lib/gcc/i686-w64-mingw32/9.2.0/include/g++-v9 --with-python-dir=/share/gcc-data/i686-w64-mingw32/9.2.0/python --enable-languages=c,c++ --enable-obsolete --enable-secureplt --disable-werror --with-system-zlib --disable-nls --enable-checking=release --with-bugurl=https://bugs.gentoo.org/ --with-pkgversion='Gentoo 9.2.0-r2 p3' --disable-esp --enable-libstdcxx-time --disable-libstdcxx-pch --enable-poison-system-directories --with-sysroot=/usr/i686-w64-mingw32 --disable-bootstrap --disable-multilib --disable-altivec --disable-fixed-point --with-arch=i686 --enable-targets=all --disable-libgomp --disable-libmudflap --disable-systemtap --disable-vtable-verify --disable-libvtv --disable-libquadmath --enable-lto --without-isl --disable-libsanitizer --disable-default-pie --enable-default-ssp Thread model: win32 gcc version 9.2.0 (Gentoo 9.2.0-r2 p3) -- 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