wine-bugs February 2022

wine-bugs@winehq.org

1 participants
4037 discussions

[Bug 45103] New: FlixGrab: Crashes on launch after showing the splash screen
by wine-bugs＠winehq.org 07 Apr '22

07 Apr '22

https://bugs.winehq.org/show_bug.cgi?id=45103 Bug ID: 45103 Summary: FlixGrab: Crashes on launch after showing the splash screen Product: Wine Version: 3.7 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: lucas.halbig(a)gmail.com Distribution: --- Created attachment 61276 --> https://bugs.winehq.org/attachment.cgi?id=61276 backtrace file when app crashed When attempting to launch https://www.freegrabapp.com/flixgrab after installation it failes to go past the splash screen. -- 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 8

[Bug 50460] New: Regression on installing mdac28 on 6.0-rc5 was ok in 5.0.4
by WineHQ Bugzilla 07 Apr '22

07 Apr '22

https://bugs.winehq.org/show_bug.cgi?id=50460 Bug ID: 50460 Summary: Regression on installing mdac28 on 6.0-rc5 was ok in 5.0.4 Product: Wine Version: 6.0-rc5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: pierre(a)couderc.eu Distribution: --- Created attachment 69085 --> https://bugs.winehq.org/attachment.cgi?id=69085 log of the trial Using : sudo rm -rI .wine/ WINEARCH=win32 winecfg winetricks mdac28 wine .wine/drive_c/windows/system32/odbcad32.exe fails on last version (from winehq-devel from deb https://dl.winehq.org/wine-builds/debian/ bullseye main debian) and is ok with default bullseye release (5.0.4). odbcad32.exe box is not displayed. Full (small...) listing in attachment I am not able to know if the problem is wine or winetricks. But I am surprised that msado15 is installed as ado is not needed for mdac adn odbs... -- 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 52530] New: dowonline: Crash at start with multiple error messages (needs dotnet452)
by WineHQ Bugzilla 06 Apr '22

06 Apr '22

https://bugs.winehq.org/show_bug.cgi?id=52530 Bug ID: 52530 Summary: dowonline: Crash at start with multiple error messages (needs dotnet452) Product: Wine Version: 7.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: mscoree Assignee: wine-bugs(a)winehq.org Reporter: joseskvolpe(a)gmail.com Distribution: --- Created attachment 71830 --> https://bugs.winehq.org/attachment.cgi?id=71830 Screenshots and log This application crashes from beginning on Wine Mono 7.0.0, installing dotnet452 with winetricks is a working workaround I've used the ZIP version of the application. Version 2.8 Procedure: 1 - Run DowOnline.exe Download (Version v. 2.8): https://dowonline.ru SHA1 (ZIP): 101a1bf896b834cd8653127a985ae10c080dbeba SHA1 (Installer): f47f7a529f5fcb0449fad0a5d497f667292accea Note: I had TLS package decode errors during download, so i was unable to download it from a browser, use wget instead to download the file if that occurs -- 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 52532] New: SDL 2.0.20 doesn't restore fullscreen mode when restoring a window
by WineHQ Bugzilla 06 Apr '22

06 Apr '22

https://bugs.winehq.org/show_bug.cgi?id=52532 Bug ID: 52532 Summary: SDL 2.0.20 doesn't restore fullscreen mode when restoring a window Product: Wine Version: 7.1 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: winex11.drv Assignee: wine-bugs(a)winehq.org Reporter: madewokherd(a)gmail.com Distribution: --- Same testcase as bug 52519. SDL will, in some cases, minimize fullscreen windows when they are deactivated. If this happens in SDL 2.0.20, the window will not be fullscreen when it is restored. To reproduce the bug: * Run the test program in Wine with SDL_EVENT_LOGGING=1 * Click the window to fullscreen it. * Alt+tab to another window. * Restore the test program's window. * It appears with a windowed size rather than fullscreen. Based on logs, I believe that SDL is requesting a fullscreen size and position, but Wine never requests NET_WM_STATE_FULLSCREEN. I'm not sure why. -- 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 10

[Bug 52519] New: SDL 2.0.20 reports wrong FOCUS_GAINED event when minimizing an inactive fullscreen window
by WineHQ Bugzilla 06 Apr '22

06 Apr '22

https://bugs.winehq.org/show_bug.cgi?id=52519 Bug ID: 52519 Summary: SDL 2.0.20 reports wrong FOCUS_GAINED event when minimizing an inactive fullscreen window Product: Wine Version: 7.1 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: madewokherd(a)gmail.com Distribution: --- Created attachment 71817 --> https://bugs.winehq.org/attachment.cgi?id=71817 test case (C source) SDL will, in some cases, minimize fullscreen windows when they are deactivated. If this happens in SDL 2.0.20, it will report a FOCUS_LOST event followed by a FOCUS_GAINED event. It should only report the FOCUS_GAINED event when the window is restored, which is what happens on Windows. Also reported here: https://github.com/libsdl-org/SDL/issues/5316 Test program attached. This requires SDL. To reproduce the bug: * Run the test program in Wine with SDL_EVENT_LOGGING=1 * Click the window to fullscreen it. * Alt+tab to another window. * The last focus event logged was FOCUS_GAINED. I know this happens because SDL receives a WM_ACTIVATE message indicating that the window is minimized, but GetForegroundWindow reports that the application is still in the foreground. SDL responds to WM_ACTIVATE by "resyncing" focus, so it responds to this by reporting FOCUS_GAINED. I haven't been able to figure out the exact set of circumstances that cause this behavior in Wine, so I couldn't make a test case that doesn't require SDL. -- 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

[Bug 52529] New: Black screen in Zork: Grand Inquisitor
by WineHQ Bugzilla 06 Apr '22

06 Apr '22

https://bugs.winehq.org/show_bug.cgi?id=52529 Bug ID: 52529 Summary: Black screen in Zork: Grand Inquisitor 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: jhansonxi(a)gmail.com Distribution: --- Zork: Grand Inquisitor (CD and demo version) installs without problems but launching the game results in a black screen. This may be related to bug 1347, bug 2082, etc. but needs to be reviewed to determine if it is a duplicate of those or not. Demo: https://archive.org/details/ZGIDEMO GoG: https://www.gog.com/game/zork_grand_inquisitor The CD version of the game is playable on ScummVM and the GoG version includes it. The demo doesn't work (cursor only) so the other versions are more reliable examples of expected behavior. https://wiki.scummvm.org/index.php?title=Zork:_Grand_Inquisitor The game requires 640x480x16. I tried it in a virtual desktop and Xephyr. Game music requires MIDI (I used TiMidity++). Xubuntu 20.04.3 x86_64 AMD Phenom 9550 GeForce GTX 750 Ti using Nvidia 470.57.02 driver -- 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 51901] New: Warcraft 3 disconnects Randomly when using bonjour service and w3champions
by WineHQ Bugzilla 05 Apr '22

05 Apr '22

https://bugs.winehq.org/show_bug.cgi?id=51901 Bug ID: 51901 Summary: Warcraft 3 disconnects Randomly when using bonjour service and w3champions Product: Wine Version: 6.19 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: kostile(a)gmail.com Distribution: --- I didn't get a full trace log, but below is the output I get when the game disconnects randomly: npacked/flo-worker.exe: /home/ubuntu/buildbot/runners/wine/wine-src/dlls/ntdll/unix/thread.c:1773: ntdll_set_exception_jmp_buf: Assertion `!jmp || !ntdll_get_thread_data()->jmp_buf' failed. 0630:err:virtual:virtual_setup_exception nested exception on signal stack in thread 0630 addr 0x7fd6118a5d22 stack 0x67fbddb0 There doesn't seem to be any reason, it just randomly disconnects. Could be 2 minutes into a game or 30 minutes into a game. -- 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 48758] New: ConEmu Ctrl+c has different behavior
by WineHQ Bugzilla 30 Mar '22

30 Mar '22

https://bugs.winehq.org/show_bug.cgi?id=48758 Bug ID: 48758 Summary: ConEmu Ctrl+c has different behavior Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: rpisl(a)seznam.cz Distribution: --- In ConEmu, Ctrl+c behavior is different on Wine and Windows. ConEmu+Cmd on Windows: Ctrl+c breaks current command and starts new empty prompt Ctrl+C shows ^C ConEmu+Cmd on Wine: Ctrl+c shows 'c' Ctrl+C terminates ConEmu completely ConEmu+Far Manager+console application on Windows: Ctrl+c terminates the application Ctrl+C shows ^C ConEmu+Far Manager+console application on Wine: Ctrl+c does nothing or shows 'c' Ctrl+C terminates the application -- 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 21936] New: rtld mmap failed mapping on OpenBSD
by wine-bugs＠winehq.org 27 Mar '22

27 Mar '22

http://bugs.winehq.org/show_bug.cgi?id=21936 Summary: rtld mmap failed mapping on OpenBSD Product: Wine Version: 1.1.40 Platform: x86 URL: http://www.openbsd.org/cgi-bin/cvsweb/ports/emulators/ wine/patches/patch-libs_wine_mmap.c?rev=1.1;content-ty pe=text%2Fplain OS/Version: OpenBSD Status: NEW Keywords: download, patch, source Severity: blocker Priority: P2 Component: loader AssignedTo: wine-bugs(a)winehq.org ReportedBy: austinenglish(a)gmail.com /home/austin/wine-git/loader/wine: rtld mmap failed mapping /home/austin/wine-git/dlls/ntdll/ntdll.dll.so. wine: failed to initialize: File not found Patch in url fixes the loader on OpenBSD. Need to test on other OS's before submitting to wine-patches. Review of the patch in the meantime is appreciated. -- 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 25

[Bug 29354] New: Microsoft Virtual PC 2007 SP1 installer fails to get past the "Product Key" dialog
by wine-bugs＠winehq.org 27 Mar '22

27 Mar '22

http://bugs.winehq.org/show_bug.cgi?id=29354 Bug #: 29354 Summary: Microsoft Virtual PC 2007 SP1 installer fails to get past the "Product Key" dialog Product: Wine Version: 1.3.34 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: msi AssignedTo: wine-bugs(a)winehq.org ReportedBy: focht(a)gmx.net Classification: Unclassified Hello, split off bug mentioned in http://bugs.winehq.org/show_bug.cgi?id=17512#c3 to track what is most likely a regression ... --- quote --- Tested in 1.3.19 Didn't crash but I couldn't get past the "Product Key" screen. The "Next" button didn't seem to do anything. --- quote --- The problem in Microsoft Virtual PC 2007 SP1 installer is the "ValidateProductID" standard action. Dump using ORCA: --- snip --- CustomerInformationDialog NextButton NewDialog ReadyToInstallDialog PIDRET = 0 4 CustomerInformationDialog NextButton DoAction CA_ValidatePID NOT ProductID AND PIDKEY AND PIDKEY<>" " 1 CustomerInformationDialog NextButton DoAction CA_InstallForAllUsers NOT VPC2004INSTALLED 2 CustomerInformationDialog NextButton DoAction CA_SetTargetPathOnUpgrade VPC2004INSTALLED 3 --- snip --- First condition, if true -> CA_ValidatePID gets executed. --- snip --- 0023:trace:msi:MSI_EvaluateConditionW L"NOT ProductID AND PIDKEY AND PIDKEY<>\" \"" ... 0023:trace:msi:msi_get_property returning L"PWCVDGDPM7P23VYG6QM4R8Y8T" for property L"ProductID" ... 0023:trace:msi:msi_get_property returning L"PWCVDGDPM7P23VYG6QM4R8Y8T" for property L"PIDKEY" ... 0023:trace:msi:MSI_EvaluateConditionW 0 <- L"NOT ProductID AND PIDKEY AND PIDKEY<>\" \"" --- snip --- (not fulfilled) Another condition to reach "ReadyToInstallDialog" is "PIDRET = 0". --- snip --- 0023:trace:msi:MSI_ProcessMessage (nil) (nil) (nil) 0 10 L"Action start 18:26:06: ValidateProductID." 0023:trace:msi:msi_get_property returning L"74216<````=````=````=````=`````>@@@@@" for property L"PIDTemplate" 0023:fixme:msi:ACTION_ValidateProductID partial stub: template L"74216<````=````=````=````=`````>@@@@@" key L"PWCVDGDPM7P23VYG6QM4R8Y8T" 0023:trace:msi:msi_set_property 0x13ce60 L"ProductID" L"PWCVDGDPM7P23VYG6QM4R8Y8T" 0023:trace:msi:MSI_ProcessMessage (nil) (nil) (nil) 0 10 L"Action ended 18:26:06: ValidateProductID. Return value 0." ... 0023:trace:msi:MSI_EvaluateConditionW L"PIDRET = 0" 0023:trace:msi:msi_get_property property L"PIDRET" not found 0023:trace:msi:MSI_EvaluateConditionW 0 <- L"PIDRET = 0" --- snip --- The "PIDRET" property never exists hence the installation is stuck in "CustomerInformationDialog". If you google for "Adding PIDRET property" you will find many similar looking msi logs, suggesting that this property is added during ValidatePID custom action: --- snip --- MSI (c) (DC:20) [17:55:05:750]: Doing action: ValidatePID MSI (c) (DC:20) [17:55:05:750]: Note: 1: 2205 2: 3: ActionText Action 17:55:05: ValidatePID. Action start 17:55:05: ValidatePID. ... MSI (c) (DC!3C) [17:55:05:875]: PROPERTY CHANGE: Adding PID property. Its value is '58730-000-0000007-05734'. MSI (c) (DC!3C) [17:55:05:875]: PROPERTY CHANGE: Adding ProductID property. Its value is '58730-000-0000007-05734'. ... MSI (c) (DC!3C) [17:55:05:875]: PROPERTY CHANGE: Adding PIDRET property. Its value is '0'. Action ended 17:55:05: ValidatePID. Return value 1. --- snip --- Because ProductID was set earlier during ValidateProductID standard action, CA_ValidatePID is never executed. http://source.winehq.org/git/wine.git/blob/8cc5561fbf9f3250fbd2d986390e4013… If you remove line 6891 the installer executes the custom action which allows to proceed and let the installation finally succeed. You need 'winetricks mfc42' for CA_ValidatePID. Regards -- 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 21

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