wine-bugs October 2020

wine-bugs@winehq.org

1 participants
6989 discussions

[Bug 49894] New: Regression in "kernelbase: Use conhost to handle Unix consoles."
by WineHQ Bugzilla 09 Oct '20

09 Oct '20

https://bugs.winehq.org/show_bug.cgi?id=49894 Bug ID: 49894 Summary: Regression in "kernelbase: Use conhost to handle Unix consoles." Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: martin(a)martin.st Distribution: --- Since 54e117018cd4cc58c258da92686bfad13946bde2, "kernelbase: Use conhost to handle Unix consoles.", the wine console misbehaves, when run within an existing unix terminal (in my case, ssh from a mac Terminal.app/bash shell to a linux host, running wine on linux within that ssh session) - i.e. when running "wine64 cmd" to get an interactive shell. On aarch64 on Debian 8, the effect is that typing individual chars do work, but when pressing enter, I get a ^M printed instead of executing the individual line. On x86_64 on Ubuntu 20.04, I get "wine: Unhandled page fault on write access to 00007F424DD5B2E0 at address 000000006EB8D3F0 (thread 0104), starting debugger..." directly when I type a single character. I.e., the testcase is to just run "wine64 cmd", then try to type "exit<enter>" to exit it. -- 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 49470] New: Silent Hill 4 crashes when a person is suppose to scream.
by WineHQ Bugzilla 09 Oct '20

09 Oct '20

https://bugs.winehq.org/show_bug.cgi?id=49470 Bug ID: 49470 Summary: Silent Hill 4 crashes when a person is suppose to scream. Product: Wine Version: 5.11 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: SolisX007(a)yahoo.com Distribution: --- Created attachment 67578 --> https://bugs.winehq.org/attachment.cgi?id=67578 SH4_wine-5.11_backtrace.txt Silent Hill 4 crashes when a person is suppose to scream. -- 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 46588] New: Cegid Business Line installer fails in custom script action installing " BLJNR.MSI" component.
by wine-bugs＠winehq.org 09 Oct '20

09 Oct '20

https://bugs.winehq.org/show_bug.cgi?id=46588 Bug ID: 46588 Summary: Cegid Business Line installer fails in custom script action installing "BLJNR.MSI" component. Product: Wine Version: 3.20 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: christian.briard(a)gmx.com Distribution: --- Created attachment 63482 --> https://bugs.winehq.org/attachment.cgi?id=63482 Setup.log Trying to Install Cegid Business Line (32 bits on Win XP works) fail to complete on a script launching BLJNR.MSI I'm running wine 3.20 under Play on Linux on an Ubuntu Machine 64 bits. I've uploaded a zip of the install package here : https://we.tl/t-AbRt4GFoOj Best regards, Christian. -- 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 16

[Bug 49946] New: Themida-packed application crashing on multi-hop import forward
by WineHQ Bugzilla 09 Oct '20

09 Oct '20

https://bugs.winehq.org/show_bug.cgi?id=49946 Bug ID: 49946 Summary: Themida-packed application crashing on multi-hop import forward Product: Wine Version: 5.18 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: oleaut32 Assignee: wine-bugs(a)winehq.org Reporter: heisenberg(a)croosade.com Regression SHA1: f26b1f0392714891bbd8c603de072818cc65e45f Distribution: ArchLinux I'm dealing with a packed application that imports functions from oleaut32.dll. Specifically, it uses GetErrorInfo and SetErrorInfo. In the commit mentioned in this issue, SetErrorInfo was moved from ole32.dll into combase.dll. This is fine, because Microsoft did the same in NT 6. However Wine now has the situation that we have a forward chain of oleaut32.SetErrorInfo -> ole32.SetErrorInfo -> combase.SetErrorInfo. I believe the packer that was applied to the application I'm trying to run cannot deal with this situation. The first hop goes fine, however for the next one, the actual function address is not resolved. It ends up literally jumping into the "combase.SetErrorInfo" string, which of course causes the program to crash unrecoverably. The application was running fine up until Wine 5.15. Wine 5.16 was the first version that incorporated the function move commits, and I've been experiencing this crash ever since. As a workaround, I tried recompiling oleaut32 with the forwards in oleaut32.spec replaced to directly point to combase instead of hopping through ole32 first. This immediately fixed the crash. Apart from SetErrorInfo this should also affect GetErrorInfo and CreateErrorInfo since they have the same chain now. I'm not submitting a patch because I'm not sure if simply changing them this way may have other side effects. -- 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 39123] New: Fairy Fencer F - Large number of FIXME ntdll NtQuerySystemInformation calls
by wine-bugs＠winehq.org 09 Oct '20

09 Oct '20

https://bugs.winehq.org/show_bug.cgi?id=39123 Bug ID: 39123 Summary: Fairy Fencer F - Large number of FIXME ntdll NtQuerySystemInformation calls Product: Wine Version: 1.7.49 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: chaos.kagami(a)gmail.com Distribution: --- Created attachment 52131 --> https://bugs.winehq.org/attachment.cgi?id=52131 Replaces SYSTEM_INTERRUPT_INFORMATION returning zeroed array with rand() filled array The following messages are repeated through the log during gameplay of Fairy Fencer F, over and over: fixme:ntdll:NtQuerySystemInformation info_class SYSTEM_INTERRUPT_INFORMATION fixme:ntdll:NtQuerySystemInformation (0x00000021,0x5dd43a80,0x00000010,0x6fcdd00) stub fixme:ntdll:NtQuerySystemInformation (0x0000002d,0x5dd43a80,0x00000020,0x6fcdd00) stub Looking through WINE's source, as well as various internet resources - SYSTEM_INTERRUPT_INFORMATION and another two-ish unimplemented queries can be used to seed RNG, or just be used as random numbers. Wine returns a zero-filled array in all of these cases, which results in oddly crippled RNG ranges in Fairy Fencer F. I've observed a whole battle where every attach hit and as long as the same attack was used, it did exactly the same damage every time. Also, in general, the game appears to lack some randomness with these stubs versus windows. Replacing the zero-filled array with a rand() filled one improves the situation, but I'm rather sure it isn't what windows does. A rather hackish patch is attached. The difference in random numbers in-game should be easily and immediately observable. I'm also aware the patch doesn't meet submission guidelines - it's not meant to be a real fix. I'm not entirely sure what the 'correct' fix is. -- 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 11

[Bug 49873] New: Warzone 2100 crashes when starting the game.
by WineHQ Bugzilla 09 Oct '20

09 Oct '20

https://bugs.winehq.org/show_bug.cgi?id=49873 Bug ID: 49873 Summary: Warzone 2100 crashes when starting the game. Product: Wine Version: 5.17 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: cedric.dewijs(a)eclipso.eu Distribution: --- Created attachment 68212 --> https://bugs.winehq.org/attachment.cgi?id=68212 The last part of the console messages during the crash Download location https://github.com/Warzone2100/warzone2100/releases/download/3.4.1/warzone2… Steps to reproduce 1) install the game 2) start the game: $ wine ~/.wine/drive_c/Program\ Files\ $x86$/Warzone\ 2100-3.4.1/bin/warzone2100.exe 3) after a few seconds, this error comes up: "Warzone crashed unexpectedly, would you like to save a mini-dump diagnostic file? (A standard report log .RPT will always be saved)" Click Yes. 4) Now the error "The program Warzone2100.exe has encountered a serious problem and needs to close" Click show details My versions: $ wine --version wine-5.17 (Staging) $ uname -a Linux cedric-p4 5.8.10-arch1-1 #1 SMP PREEMPT Thu, 17 Sep 2020 18:01:06 +0000 x86_64 GNU/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 8

[Bug 49968] New: Resident Evil 3 crashes on loading
by WineHQ Bugzilla 09 Oct '20

09 Oct '20

https://bugs.winehq.org/show_bug.cgi?id=49968 Bug ID: 49968 Summary: Resident Evil 3 crashes on loading Product: Wine Version: 5.0.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: aadityavikram628(a)gmail.com Distribution: --- Created attachment 68365 --> https://bugs.winehq.org/attachment.cgi?id=68365 Crash Report Resident Evil 3 crashes on loading -- 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 0

[Bug 46736] New: Doom 3: BFG Edition freezes when using gnome shortcut or fails with error when running from terminal
by wine-bugs＠winehq.org 09 Oct '20

09 Oct '20

https://bugs.winehq.org/show_bug.cgi?id=46736 Bug ID: 46736 Summary: Doom 3: BFG Edition freezes when using gnome shortcut or fails with error when running from terminal Product: Wine-staging Version: 4.2 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: linards.liepins(a)gmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Created attachment 63734 --> https://bugs.winehq.org/attachment.cgi?id=63734 terminal log doom3bfg114 gog Game crashes with ID error window. Error message similar to the one. as shown in the following thread(s): https://steamcommunity.com/app/208200/discussions/0/864949037819880093/ https://www.gog.com/forum/doom_series/doom_3_bfg_edition_is_not_working_wit… Attaching error logs for both steam and GOG versions. -- 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 11

[Bug 40735] New: Midnight Mysteries: The Edgar Allan Poe Conspiracy (Steam ) fails to start (probably needs msscript)
by wine-bugs＠winehq.org 09 Oct '20

09 Oct '20

https://bugs.winehq.org/show_bug.cgi?id=40735 Bug ID: 40735 Summary: Midnight Mysteries: The Edgar Allan Poe Conspiracy (Steam) fails to start (probably needs msscript) Product: Wine Version: 1.9.11 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: gyebro69(a)gmail.com Distribution: --- This is the only game from the Midnight Mysteries series on Steam which refuses to start. The game displays an error message after start: 'Exception EOleSysError in module Midnight Mysteries - Edgar Allan Poe Conspiracy.exe at 0008B9AD. OLE error 80004002.' In the terminal: >fixme:msscript:ScriptControl_QueryInterface (0x177000)->({00000112-0000-0000-c000-000000000046} 0x33fca8) >fixme:ole:CoCreateInstanceEx no instance created for interface {00000112-0000-0000-c000-000000000046} of class {0e59f1d5-1fbe-11d0-8ff2-00a0d10038bc}, hres is 0x80004002 I installed msscript.ocx with winetricks, and now the game window is opened and sound begins to play for a second then the game throws a different error: 'Access violation error at address....'. The error dialog box can't be dismissed, it's popping up continuously. This is the terminal output with native msscript.ocx: >err:ole:CoCreateInstanceEx apartment not initialised >fixme:jscript:JScript_SetScriptState unimplemented SCRIPTSTATE_INITIALIZED >fixme:win:EnumDisplayDevicesW ((null),0,0x33f7e8,0x00000000), stub! >fixme:win:EnumDisplayDevicesW ((null),0,0x33f638,0x00000000), stub! wine-1.9.11-112-gd864119 -- 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 52

[Bug 48233] New: In a 64-bit app, GetSyscolor(COLOR_BTNSHADOW) returns a darker value than on windows
by WineHQ Bugzilla 09 Oct '20

09 Oct '20

https://bugs.winehq.org/show_bug.cgi?id=48233 Bug ID: 48233 Summary: In a 64-bit app, GetSyscolor(COLOR_BTNSHADOW) returns a darker value than on windows Product: Wine Version: 3.6 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdi32 Assignee: wine-bugs(a)winehq.org Reporter: ryampolsky(a)yahoo.com Distribution: --- Created attachment 65879 --> https://bugs.winehq.org/attachment.cgi?id=65879 Screenshot, showing shadow drawn with GetSysColor(COLOR_BTNSHADOW) I recently converted my 32-bit app to 64-bits, and when I run either the 32-bit version or the 64-bit version under a wine64 WINEPREFIX, the only difference I notice is the value returned by GetSyscolor(COLOR_BTNSHADOW). On Windows in both the WIN32 and WIN64 versions of my app, it returns 0xa0a0a0, but on WINE64, it returns 0x4c4c4c. On WINE, I'm using the Ubuntu Light theme. With that theme in effect, on WINE32, GetSysColor(COLOR_BTNSHADOW) returns 0xa5a9ad. But on WINE64, both the WIN32 and WIN64 versions get 0x4c4c4c. So the shadow looks too dark. Again, the WIN32 exe gets the right color under WINE32, but the same wrong color as the WIN64 exe under WINE64 - which is why I think it's a WINE64 bug and not my app. Everything else seems to look the same between WINE32 and WINE64. The attached screenshot shows the About dialog from my app. There's a 3D frame around the logo at the top - BTNSHADOW on top and left, BTNHIGHLIGHT on bottom and right. The text below it shows that this is the X64 version of the app, and prints out the value returned by GetSysColor(COLOR_BTNSHADOW). -- 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

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 October 2020