wine-bugs January 2022

wine-bugs@winehq.org

1 participants
4413 discussions

[Bug 51632] New: Downloading Wine-Mono through appwiz hangs/fails
by WineHQ Bugzilla 02 Mar '22

02 Mar '22

https://bugs.winehq.org/show_bug.cgi?id=51632 Bug ID: 51632 Summary: Downloading Wine-Mono through appwiz hangs/fails Product: Wine Version: 6.15 Hardware: x86-64 OS: Mac OS X Status: NEW Keywords: download, regression, source Severity: normal Priority: P2 Component: winsock Assignee: wine-bugs(a)winehq.org Reporter: gijsvrm(a)gmail.com CC: julliard(a)winehq.org Regression SHA1: d327527cec22c1123781e6c5a637032a31698b91 This only happens on macOS. Clicking 'Install' works, but it stays on 'Downloading...' forever. Cancelling to skip works. The only output is: 0068:err:appwizcpl:InstallCallback_OnStopBinding Binding failed 800c0008 Bisection revealed: d327527cec22c1123781e6c5a637032a31698b91 is the first bad commit commit d327527cec22c1123781e6c5a637032a31698b91 Author: Alexandre Julliard <julliard(a)winehq.org> Date: Wed Aug 11 20:40:23 2021 +0200 ws2_32: Convert the Unix library to the __wine_unix_call interface. Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> I'm running macOS 10.14, compiling with mingw and the 10.13 SDK. -- 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 52374] New: compiling on Cygwin fails: error: ‘S_IRUSR’ undeclared (in libs/mpg123)
by WineHQ Bugzilla 28 Feb '22

28 Feb '22

https://bugs.winehq.org/show_bug.cgi?id=52374 Bug ID: 52374 Summary: compiling on Cygwin fails: error: ‘S_IRUSR’ undeclared (in libs/mpg123) Product: Wine Version: 7.0-rc5 Hardware: x86-64 OS: Windows Status: UNCONFIRMED Severity: normal Priority: P2 Component: l3codeca.acm Assignee: wine-bugs(a)winehq.org Reporter: saulius2(a)gmail.com (This is continuation from the bug 52370) After faking some dlls from there, make then fails in libs/mpg123. Other defines are missing too: S_IWUSR, S_IRGRP, S_IWGRP, S_IROTH, S_IWOTH. --- snip --- $ make gcc -c -o libs/mpg123/src/compat/compat.o libs/mpg123/src/compat/compat.c -Ilibs/mpg123 -Iinclude -Iinclude/msvcrt \ -Ilibs/mpg123/src -Ilibs/mpg123/src/compat -Ilibs/mpg123/src/libmpg123 -DOPT_GENERIC_DITHER \ -DREAL_IS_FLOAT -DNO_CATCHSIGNAL -DMPG123_NO_LARGENAME -D_UCRT -fasynchronous-unwind-tables \ -D_WIN32 -fno-builtin -fshort-wchar -D__WINE_PE_BUILD -pipe -fcf-protection=none \ -fno-stack-protector -fno-strict-aliasing -Wno-packed-not-aligned -gdwarf-4 \ -fno-omit-frame-pointer -g -O2 libs/mpg123/src/compat/compat.c: In function ‘INT123_compat_open’: libs/mpg123/src/compat/compat.c:96:37: error: ‘S_IRUSR’ undeclared (first use in this function) 96 | ret = open(filename, flags, S_IRUSR|S_IWUSR|S_IRGRP|S_IWGRP|S_IROTH|S_IWOTH); | ^~~~~~~ libs/mpg123/src/compat/compat.c:96:37: note: each undeclared identifier is reported only once for each function it appears in libs/mpg123/src/compat/compat.c:96:45: error: ‘S_IWUSR’ undeclared (first use in this function) 96 | ret = open(filename, flags, S_IRUSR|S_IWUSR|S_IRGRP|S_IWGRP|S_IROTH|S_IWOTH); | ^~~~~~~ libs/mpg123/src/compat/compat.c:96:53: error: ‘S_IRGRP’ undeclared (first use in this function) 96 | ret = open(filename, flags, S_IRUSR|S_IWUSR|S_IRGRP|S_IWGRP|S_IROTH|S_IWOTH); | ^~~~~~~ libs/mpg123/src/compat/compat.c:96:61: error: ‘S_IWGRP’ undeclared (first use in this function) 96 | ret = open(filename, flags, S_IRUSR|S_IWUSR|S_IRGRP|S_IWGRP|S_IROTH|S_IWOTH); | ^~~~~~~ libs/mpg123/src/compat/compat.c:96:69: error: ‘S_IROTH’ undeclared (first use in this function) 96 | ret = open(filename, flags, S_IRUSR|S_IWUSR|S_IRGRP|S_IWGRP|S_IROTH|S_IWOTH); | ^~~~~~~ libs/mpg123/src/compat/compat.c:96:77: error: ‘S_IWOTH’ undeclared (first use in this function) 96 | ret = open(filename, flags, S_IRUSR|S_IWUSR|S_IRGRP|S_IWGRP|S_IROTH|S_IWOTH); | ^~~~~~~ make: *** [Makefile:160889: libs/mpg123/src/compat/compat.o] Error 1 --- snip --- This then leads to dlls/l3codeca.acm/l3codeca.acm build failure. -- 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 51687] New: GetMappedFileNameA/W implementation breaks RiotClient updates.
by WineHQ Bugzilla 27 Feb '22

27 Feb '22

https://bugs.winehq.org/show_bug.cgi?id=51687 Bug ID: 51687 Summary: GetMappedFileNameA/W implementation breaks RiotClient updates. Product: Wine Version: 6.15 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: matias.nicolas.zc(a)gmail.com Distribution: --- Created attachment 70554 --> https://bugs.winehq.org/attachment.cgi?id=70554 trace log Since wine (vanilla or staging) 6.2, the Riot Client Launcher fails when updating itself. This worked fine with wine 6.1 (vanilla and staging) This wasn't much of a problem since LoL players used a lutris versions based on wine 5.x. Starting with the last League Of Legends Client update, the CEF upgrade requires a patched wine 6.15, so users will begin getting this error on the next Launcher update. The launcher throws the following error when starting the update process: ``` Update failed: Failed getting path to current executable: File path could not be found in a mapped drive: \??\c:\Riot Games\Riot Client\RiotClientServices.exe ``` I bisected the problem to commit bd0a3c1a59db9e75500db6df0f3598c981abf44e. For some reason the launcher worked with the stub implementation of GetMappedFileNameA/W, but not with a "real" one. I can confirm that reverting the commit on 6.15 makes the update work. Attached is a trace log of the execution (from wine staging 6.15, with the most frequent calls removed). The interesting part should start in line 546, when the debug message says that it will start the update, and end in line 1705, when the update process ends. In line 1361 there is a call to GetMappedFileNameW, which should be where the error begins. -- 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 19757] New: Nota Bene: Crashes upon installation
by wine-bugs＠winehq.org 26 Feb '22

26 Feb '22

http://bugs.winehq.org/show_bug.cgi?id=19757 Summary: Nota Bene: Crashes upon installation Product: Wine Version: 1.1.27 Platform: PC URL: https://www.notabene.com/download/demos/nbdemo80.exe OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: jekwas(a)gmail.com Created an attachment (id=23127) --> (http://bugs.winehq.org/attachment.cgi?id=23127) Crash log in 1.1.27 I discovered this while trying to reproduce 5255. During installation, the Nota Bene Demo reports that AUTOEXE.NT and CONFIG.NT have been removed from the system, and won't continue unless you allow it to restore them. If you agree, the installation starts. However, when the installation bar reaches 100%, the installer crashes. The files appear to have been installed. But on running nblaunch.exe, the program crashes immediately. I have attached a log. -- 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 5

[Bug 52502] New: Mupen64-RR-Lua: Title and menu bar are not refreshed properly
by WineHQ Bugzilla 26 Feb '22

26 Feb '22

https://bugs.winehq.org/show_bug.cgi?id=52502 Bug ID: 52502 Summary: Mupen64-RR-Lua: Title and menu bar are not refreshed properly Product: Wine Version: 7.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: jackyguo18(a)hotmail.com Distribution: --- source code: https://github.com/mkdasher/mupen64-rr-lua- The title and menu bar of the emulator don't refresh properly, leading to two different, but likely related graphical glitches. Wine version: 7.0 (winehq-stable) Linux distro: Ubuntu 21.10 (impish) Display server: Wayland, GNOME Mutter To reproduce, download the package from https://repack.skazzy3.com, then simply unzip to a folder and run mupen64.exe. From there: - Try resizing the window. The title/menubar are cleared, but not redrawn. - run an N64 ROM - File > Close ROM - Try resizing the window again. The title/menubar are not cleared, but are redrawn. -- 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 52155] New: kernel32:pipe times out on 64-bit Wine
by WineHQ Bugzilla 25 Feb '22

25 Feb '22

https://bugs.winehq.org/show_bug.cgi?id=52155 Bug ID: 52155 Summary: kernel32:pipe times out on 64-bit Wine Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- kernel32:pipe now times out on 64-bit Wine: pipe.c:3218: testing message mode, byte read client->server writes... pipe.c:3148: Test failed: WriteFile returned 0(6) kernel32:pipe:0520 done (258) in 120s https://test.winehq.org/data/patterns.html#kernel32:pipe The timeout only happens on WoW64 wineprefixes but impacts both real machines (cw-gtx560, cw-rx460) and VMs (notably the TestBot's debiant2 VM). A bisect shows that this started with the commit below: commit a041075cd2c26874757e0b6e1449c23c1326241c Author: Alexandre Julliard <julliard(a)winehq.org> Date: Thu Dec 2 09:59:49 2021 +0100 makefiles: Support per-platform values for EXTRADLLFLAGS. Signed-off-by: Alexandre Julliard <julliard(a)winehq.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 7

[Bug 52290] New: Playground Sessions crashes on startup
by WineHQ Bugzilla 25 Feb '22

25 Feb '22

https://bugs.winehq.org/show_bug.cgi?id=52290 Bug ID: 52290 Summary: Playground Sessions crashes on startup Product: Wine Version: 7.0-rc2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: install1ball(a)gmail.com Distribution: --- Created attachment 71431 --> https://bugs.winehq.org/attachment.cgi?id=71431 Playground Sessions crash backtrace The Playground Sessions piano teaching app crashes during startup before the splash page and audio introduction are displayed. My Environment: CPU - x86_64 O/S - Fedora 35 - Kernel 5.15.10-200.fc35.x86_64 Wine - wine-7.0-rc2 (Staging) Playground Sessions - Version 2.5 (Their only version) Backtrace uploaded The problem started after a dnf update command that brought wine to version 6.21-staging. Tried downgrading wine as far as I could but the problem persists. Created new wine prefix (32-bit) and no luck. I am about at the limit of my skill here. This is the only app I use with wine so I do not have a lot of experience with it. The program can be downloaded here. https://www.playgroundsessions.com/windows The software is proprietary and subscription-based, but it crashes well before the authentication screen is presented. My personal feeling is that I am missing a library but I have no idea how to check that. -- 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 14

[Bug 51103] New: d3d11:d3d11 crashes on Windows + NVidia
by WineHQ Bugzilla 25 Feb '22

25 Feb '22

https://bugs.winehq.org/show_bug.cgi?id=51103 Bug ID: 51103 Summary: d3d11:d3d11 crashes on Windows + NVidia Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Created attachment 69968 --> https://bugs.winehq.org/attachment.cgi?id=69968 Traces for the crash on cw-gtx560 d3d11:d3d11 crashes on the cw-gtx560 machine which has an NVidia graphics card. The crash happens from Windows 8.1 to Windows 10 2009 so it seems to be related to the graphics driver rather than to the Windows version. https://test.winehq.org/data/patterns.html#d3d11:d3d11 The crash shows no backtrace but I added traces and found that the crash happens on the final release in test_device_context_state(): refcount = ID3D11Device1_Release(device); Adding a trace on the previous line shows that the refcount before that call is 1. So it's not a case of a one-too-many release calls. Without test_device_context_state() d3d11:d3d11 does not crash. According to a bisect the commit causing this crash is: commit ccffc06c6df30aa8b4ea487b868c419b9c7f5a9a Author: Rémi Bernon <rbernon(a)codeweavers.com> Date: Tue Feb 2 16:41:00 2021 +0100 d3d11/tests: Add more tests for ID3D11DeviceContext1_SwapDeviceContextState. Better checking multiple context swap side effects. Signed-off-by: Rémi Bernon <rbernon(a)codeweavers.com> Signed-off-by: Henri Verbeet <hverbeet(a)codeweavers.com> Signed-off-by: Alexandre Julliard <julliard(a)winehq.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 7

[Bug 48096] New: Mulle Meck: Unhandled exception when starting game
by WineHQ Bugzilla 25 Feb '22

25 Feb '22

https://bugs.winehq.org/show_bug.cgi?id=48096 Bug ID: 48096 Summary: Mulle Meck: Unhandled exception when starting game Product: Wine Version: 4.19 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: odecif(a)gmail.com Distribution: --- Created attachment 65654 --> https://bugs.winehq.org/attachment.cgi?id=65654 warn+all debug log When running the game w/o any debug flags one receive the following: wine: Unhandled exception 0x80000004 in thread 9 at address 0040986D (thread 0009), starting debugger... Attached is a pretty short debug log. Some specs: Manjaro Linux 18.1.2 (clean prefix) wine-4.19-251-g292b728908 Windows 2000-mode (also tried with 95/98/Me/XP/7) No overrides 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 530 (rev 06) The game is protected by SafeDisc 1 (old game), but running from CD gets pass the "Please insert the correct CD"-error message so it's probably nothing to do with that. -- 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 17

[Bug 38210] New: WshScriptExec's StdIn StdOut and StdErr are missing.
by wine-bugs＠winehq.org 25 Feb '22

25 Feb '22

https://bugs.winehq.org/show_bug.cgi?id=38210 Bug ID: 38210 Summary: WshScriptExec's StdIn StdOut and StdErr are missing. Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: wshom.ocx Assignee: wine-bugs(a)winehq.org Reporter: ptubbytaylor(a)gmail.com Distribution: --- Created attachment 51003 --> https://bugs.winehq.org/attachment.cgi?id=51003 Example.ahk Here's the documentation for the WshScriptExec object: https://msdn.microsoft.com/en-us/library/2f38xsxe(v=vs.84).aspx The Std properties appear to have the same interface as TextStream objects, which are documented here: https://msdn.microsoft.com/en-us/library/312a5kbt(v=vs.84).aspx Attached is an AutoHotkey v1.1.20.00 script that demonstrates using the StdIn property. Note that this problem isn't limited to just AutoHotkey scripts, I'm just using this property primarily from AutoHotkey. -- 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

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 January 2022