wine-bugs May 2024

wine-bugs@winehq.org

1 participants
1345 discussions

[Bug 49543] New: Several games require bcrypt DH support
by WineHQ Bugzilla 01 Dec '24

01 Dec '24

https://bugs.winehq.org/show_bug.cgi?id=49543 Bug ID: 49543 Summary: Several games require bcrypt DH support Product: Wine Version: 5.12 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: bcrypt Assignee: wine-bugs(a)winehq.org Reporter: bshanks(a)codeweavers.com Distribution: --- There are a few games that need DH support in bcrypt. - The Rockstar Games Launcher, GTA V, and RDR 2 all open DH and generate+export a public key. With DH unimplemented, the only effect I know of is that RDR 2's online mode fails to load. - Astroneer dedicated server (see https://www.reddit.com/r/wine_gaming/comments/gvaa9a/bcryptopenalgorithmpro…). >From a disassembler, it looks like the server imports/exports public/private keys, and uses BCryptDeriveKey() with the "HASH" KDF and SHA256. Microsoft has sample code which tests (some of) the functionality: https://github.com/microsoft/Windows-classic-samples/blob/master/Samples/Se… Unfortunately GnuTLS doesn't currently export the needed functionality. There's an issue open: https://gitlab.com/gnutls/gnutls/-/issues/894 -- 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 48175] New: AION (64 bit) - crashes in CrySystem32.dll.CryFree() due to high memory pointers allocated
by WineHQ Bugzilla 01 Dec '24

01 Dec '24

https://bugs.winehq.org/show_bug.cgi?id=48175 Bug ID: 48175 Summary: AION (64 bit) - crashes in CrySystem32.dll.CryFree() due to high memory pointers allocated Product: Wine Version: 4.20 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: gofmanp(a)gmail.com Distribution: --- Created attachment 65809 --> https://bugs.winehq.org/attachment.cgi?id=65809 Force down-top memory allocation Split off from bug #40334. The crash happens after the original issue in Bug #40334 is solved, after the loading screen or very soon after login. The game expects memory pointers from HeapAlloc and VirtualAlloc to fit in the certain range. It is fine with ~16GB range as per my observations, that is, up to 0x3ffffffff address. I am attaching the patch which is confirmed to fix the issue with AION. The patch consists of two, the first one is not exactly related but the second one depends on it. At the present moment the first one is passing the review upstream. The solution in the second patch is to force virtual memory allocation return lower addresses when they are available (unless top-down allocation is explicitly requested), that's how it seem to work on Windows. The patch does it essentially the same way as the allocation with zero_bits mask is performed. -- 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 54314] New: my eprom programmer software can't recognize the hardware anymore.
by WineHQ Bugzilla 01 Dec '24

01 Dec '24

https://bugs.winehq.org/show_bug.cgi?id=54314 Bug ID: 54314 Summary: my eprom programmer software can't recognize the hardware anymore. Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: jacek.zmudzki(a)gmail.com Distribution: --- I used WINE for a long Time to program EPROMS with my Parallel-Port bases Programmer: http://www.conitec.net/english/galep4.php After an Update to Ubuntu 22.04 (with WINE 6.0.3) the Software https://appdb.winehq.org/objectManager.php?sClass=application&iId=2240 can't access the hardware anymore. I used the Runners from Lutris to investigate further: It seems that the Last Wine Version that works is WINE 5.4. -- 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 16

[Bug 56676] New: native wayland resolution with 32bit games on wow64 grabs input
by WineHQ Bugzilla 30 Nov '24

30 Nov '24

https://bugs.winehq.org/show_bug.cgi?id=56676 Bug ID: 56676 Summary: native wayland resolution with 32bit games on wow64 grabs input Product: Wine Version: 9.8 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: zlice(a)crtdrift.us Distribution: --- Enabling wow64 (64bit wine without separate 32bit) to get native wayland wine running seems to have issues when rescaling input. Fallout 3 and KOTOR have similar related issues. Fallout 3 - if you are at a different resolution than what is set in the ini, the game opens a popup saying to run the launcher because your input does not support the resolution. This popup seems to freeze all input related to the window manager (labwc), where the mouse is locked and keyboard shortcuts will not work. You can use tab/arrows to press the 'ok' button which will close the popup. Changing to the resolution with wlr-randr to match the ini file runs fine afaict. KOTOR - this game changes resolution a lot for startup and cutscenes. It also has a lower resolution compared to most games and does not hit 1080p. Similarly input is trashed and does not work as expected. The game does not start. I assume if the game did start it would constantly want to change resolution for cutscenes. Using XWayland does not appear to have the same issues. But it does not change resolution appropriatey (and with it, refresh rate). I was only able to get 32bit games running under native wine+wayland with the wow64 mode. Not sure if I missed something with the build or if 32bit is not properly set up yet. KOTOR had an error about using the null/noa(?) driver. Fallout 3 just didn't run, assert(!status) for vkCreateInstance at winevulkanloader.c:271 I can file separate bug for resolution scaling in wayland vs the input grab. System - kernel 6.9.0 - wine 9.8 - void linux - labwc 0.7.2 (wayland wlroots) -- 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 40500] New: Scrap Mechanic : Unable to launch
by wine-bugs＠winehq.org 30 Nov '24

30 Nov '24

https://bugs.winehq.org/show_bug.cgi?id=40500 Bug ID: 40500 Summary: Scrap Mechanic : Unable to launch Product: Wine Version: 1.9.8 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: arionrina(a)verizon.net Distribution: --- Created attachment 54281 --> https://bugs.winehq.org/attachment.cgi?id=54281 Crash log Scrap Mechanic doesn't open up the first window, then crashes. -- 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 20

[Bug 49981] New: Doom Eternal Killed
by WineHQ Bugzilla 30 Nov '24

30 Nov '24

https://bugs.winehq.org/show_bug.cgi?id=49981 Bug ID: 49981 Summary: Doom Eternal Killed Product: Wine Version: 5.19 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: shagooserver(a)gmail.com Distribution: --- Created attachment 68382 --> https://bugs.winehq.org/attachment.cgi?id=68382 Terminal output when launching On launch the game is killed before it starts. -- 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 52212] New: Doom Eternal - Crash on Launch
by WineHQ Bugzilla 30 Nov '24

30 Nov '24

https://bugs.winehq.org/show_bug.cgi?id=52212 Bug ID: 52212 Summary: Doom Eternal - Crash on Launch Product: Wine-staging Version: 6.23 Hardware: x86-64 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 71270 --> https://bugs.winehq.org/attachment.cgi?id=71270 report_1 See attached bugreports for various wine and launch options. -- 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 18

[Bug 46803] New: Diablo 1 GOG.com crash
by wine-bugs＠winehq.org 30 Nov '24

30 Nov '24

https://bugs.winehq.org/show_bug.cgi?id=46803 Bug ID: 46803 Summary: Diablo 1 GOG.com crash Product: Wine Version: 4.3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: xzgamertag(a)mail.com Distribution: --- Created attachment 63823 --> https://bugs.winehq.org/attachment.cgi?id=63823 Log Diablo crashes immidiately after skipping intro, while using hi-res, latest version. When I try to run Diablo (Classic) version, it requires original CD to proceed. -- 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

[Bug 49780] New: wineconsole reports VT sequence support when it does not
by WineHQ Bugzilla 29 Nov '24

29 Nov '24

https://bugs.winehq.org/show_bug.cgi?id=49780 Bug ID: 49780 Summary: wineconsole reports VT sequence support when it does not Product: Wine Version: 5.16 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: cmd Assignee: wine-bugs(a)winehq.org Reporter: magiblot(a)hotmail.com Distribution: --- Created attachment 68092 --> https://bugs.winehq.org/attachment.cgi?id=68092 Demo application to reproduce the issue Wineconsole does not support applications writing Virtual Terminal sequences through the Console API. That's fine. However, when enabling the console ENABLE_VIRTUAL_TERMINAL_PROCESSING mode on stdout with SetConsoleMode, no error is returned, so the application has no way to detect whether VT sequences are supported or not. This is documented in https://docs.microsoft.com/en-us/windows/console/setconsolemode. The port of Turbo Vision at https://github.com/magiblot/tvision is affected by this. When using the Console API, Turbo Vision prefers VT sequences over SetConsoleCursorPosition/SetConsoleTextAttribute for code reusability and performance. Nevertheless, it can fall back to the latter method when SetConsoleMode fails to enable either ENABLE_VIRTUAL_TERMINAL_PROCESSING or DISABLE_NEWLINE_AUTO_RETURN. Since SetConsoleMode does not return error on wineconsole, garbage is shown instead of a colorful interface. STEPS TO REPRODUCE To reproduce the issue on Turbo Vision: (A) - Using the attached 'tvdemo.exe' 1. Run the application on wineconsole. You should see a black-and-white background and escape sequences drawn on the console. 2. Press Alt+F, then D. You should see the command prompt, and the message "VT enabled" at the top, which demonstrates the issue in SetConsoleMode. (B) - Compiling from source code (requires up-to-date CMake and MSVC). 1. Insert the following code after line 63 in source/linux/win32con.cpp (https://github.com/magiblot/tvision/blob/dd4e410e60a34e08053399e346d4ed4e63…): ``` if (supportsVT) cerr << "VT enabled" << endl; else cerr << "VT not enabled: " << GetLastError() << endl; ``` 2. Follow the build instructions at https://github.com/magiblot/tvision/blob/dd4e410e60a34e08053399e346d4ed4e63… 3. Follow the steps in (A). EXPECTED BEHAVIOUR On Windows, support for VT sequences can be disabled by turning on the "Legacy Console" mode. If tvdemo.exe is ran in these conditions, the interface is displayed properly. If entering the command prompt by pressing Alt+F, then D, the message "VT not enabled: 87" is displayed (error 87 stands for ERROR_INVALID_PARAMETER), which is what should be shown on wineconsole as well, since it clearly does not support VT sequences. Thank you! -- 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 56539] New: Ableton Live 12 Suite Crashes Whenever Max Instruments Startup
by WineHQ Bugzilla 28 Nov '24

28 Nov '24

https://bugs.winehq.org/show_bug.cgi?id=56539 Bug ID: 56539 Summary: Ableton Live 12 Suite Crashes Whenever Max Instruments Startup Product: Wine Version: 9.4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: numono(a)yahoo.com Distribution: Other Created attachment 76295 --> https://bugs.winehq.org/attachment.cgi?id=76295 Ableton 12 Wine Command Line Output Live 12 crashes Whenever Max For Live Instruments Startup. Here's the Free Download - https://www.ableton.com/en/download/archive/ -- 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 6

Jump to page:

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 May 2024