wine-bugs December 2023

wine-bugs@winehq.org

1 participants
2841 discussions

[Bug 50484] New: Far Manager 3 crashes when Shift+Enter Execute in separate window pressed
by WineHQ Bugzilla 05 Jul '25

05 Jul '25

https://bugs.winehq.org/show_bug.cgi?id=50484 Bug ID: 50484 Summary: Far Manager 3 crashes when Shift+Enter Execute in separate window pressed Product: Wine Version: 5.0.3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: lanthruster(a)gmail.com Distribution: --- Far Manager 3 crashes when executing a file association. 1. Download and extract farmanager3 https://www.farmanager.com/download.php?l=en (zip archive) 2. Create a text file with no or arbitrary content test.txt 3. Select test.txt and press Shift + Enter Wine will crash. That bug was there for years, including Wine 2.3 and earlier releases. -- 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 39688] New: Crash in file browser dialog (probably because of > MAX_PATH)
by wine-bugs＠winehq.org 05 Jul '25

05 Jul '25

https://bugs.winehq.org/show_bug.cgi?id=39688 Bug ID: 39688 Summary: Crash in file browser dialog (probably because of > MAX_PATH) Product: Wine Version: 1.6.2 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: comdlg32 Assignee: wine-bugs(a)winehq.org Reporter: n296869(a)rtrtr.com Distribution: --- Wine's GetOpenFileNameW/GetSaveFileNameW seems to crash when encountering a very long path name (i.e. longer than MAX_PATH characters). -- 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 53008] New: When playing civilizatin2, winevdm crash
by WineHQ Bugzilla 05 Jul '25

05 Jul '25

https://bugs.winehq.org/show_bug.cgi?id=53008 Bug ID: 53008 Summary: When playing civilizatin2, winevdm crash Product: Wine Version: 7.8 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: clabbe.montjoie(a)gmail.com Distribution: --- Created attachment 72378 --> https://bugs.winehq.org/attachment.cgi?id=72378 backtrace of winevdm When playing civilization 2, game menu start, but after some time, game crash. I am sure that it worked before, but i need some time digging backup to find which version of wine I used. -- 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 50872] New: Greenshot doesn't start
by WineHQ Bugzilla 05 Jul '25

05 Jul '25

https://bugs.winehq.org/show_bug.cgi?id=50872 Bug ID: 50872 Summary: Greenshot doesn't start Product: Wine Version: 6.5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: t6zm3v62fkp7fe5(a)yandex.ru Distribution: --- Created attachment 69684 --> https://bugs.winehq.org/attachment.cgi?id=69684 Terminal output When running installed latest unstable Greenshot (https://github.com/greenshot/greenshot/releases/download/v1.3.178/Greenshot…) in terminal, it doesn't start and shows unhandled exception. Latest stable version (https://github.com/greenshot/greenshot/releases/download/Greenshot-RELEASE-…) works alright. Lubuntu 20.04.1, Wine 6.5 (official PPA). -- 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 52999] New: Redout fails to detect visual c++ runtimes
by WineHQ Bugzilla 04 Jul '25

04 Jul '25

https://bugs.winehq.org/show_bug.cgi?id=52999 Bug ID: 52999 Summary: Redout fails to detect visual c++ runtimes Product: Wine Version: 7.8 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: blue-t(a)web.de Distribution: --- Created attachment 72366 --> https://bugs.winehq.org/attachment.cgi?id=72366 Logfile When i try to run Redout, it says you need to install the c++ runtime. The log does not indicate anything going wrong: 002c:fixme:winediag:LdrInitializeThunk wine-staging 7.8 is a testing version containing experimental patches. 002c:fixme:winediag:LdrInitializeThunk Please mention your exact version when filing bug reports on winehq.org. 0118:fixme:imm:ImeSetActiveContext (0000000000CDB7F0, 1): stub 0118:fixme:imm:ImmReleaseContext (000000000001006C, 0000000000CDB7F0): stub 007c:fixme:imm:ImeSetActiveContext (0000000000356C10, 0): stub 007c:fixme:imm:ImmReleaseContext (0000000000010020, 0000000000356C10): stub 0118:fixme:kernelbase:AppPolicyGetProcessTerminationMethod FFFFFFFFFFFFFFFA, 0000000000B9FD70 -- 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 55979] New: Blizzard Battle.net Launcher: New Version Released On 11/30/2023 Hangs During Installation
by WineHQ Bugzilla 03 Jul '25

03 Jul '25

https://bugs.winehq.org/show_bug.cgi?id=55979 Bug ID: 55979 Summary: Blizzard Battle.net Launcher: New Version Released On 11/30/2023 Hangs During Installation Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: crashdance(a)charter.net Distribution: --- Created attachment 75569 --> https://bugs.winehq.org/attachment.cgi?id=75569 Terminal output when running the Battle.net client installer in a clean Wine prefix When attempting to install Battle.net in a clean 64-bit prefix on a clean install of Linux Mint 21.2 with all needed dependencies, I get the attached terminal output and the progress hangs at 45%. Also, I know the maintainers of Bugzilla encourage reporting only one problem per bug. That being said, the exact same time this started happening, my existing Wine prefix for Battle.net (and my Battle.net games) caused thread crashes when opening Battle.net after installing yesterday's update. The update was installed from within the Battle.net client by clicking the green icon to install the update. Prior to this update released yesterday on November 30, 2023, Battle.net and the games were running flawlessly. Because I can only add a single attachment, the Pastebin links below will give more detail on the related issue of thread crashes described above: Existing prefix terminal output when the thread crash occurs: https://pastebin.com/4UwxTsEP Here is my system information: https://pastebin.com/v3MVemgg Was able to save a crash report for the thread crash issue: https://pastebin.com/mYX68NrX -- 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 28

[Bug 48746] New: Null_DC stops with error on Emulator Startup (not opening the application)
by WineHQ Bugzilla 29 Jun '25

29 Jun '25

https://bugs.winehq.org/show_bug.cgi?id=48746 Bug ID: 48746 Summary: Null_DC stops with error on Emulator Startup (not opening the application) Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: apphelp Assignee: wine-bugs(a)winehq.org Reporter: starfirehyper(a)gmail.com Distribution: --- Hello, I am having issues with Wine and Null DC I do have Crossover on a Chromebook, but whatever I start the emulator (not opening the application) I get a error that tells me " The program (the full name of the exe) has encountered a serious problem and needs to close." The link on the error wasn't very helpful. (I am running nullDC 1.0.4 and I don't know what is causing it) Thank you and good bye. Have a nice day! :) -- 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

[Bug 48771] New: SoulWorker from Official Launcher
by WineHQ Bugzilla 29 Jun '25

29 Jun '25

https://bugs.winehq.org/show_bug.cgi?id=48771 Bug ID: 48771 Summary: SoulWorker from Official Launcher Product: Wine Version: 5.4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: full01(a)linuxmail.org Distribution: --- I can't start the game from the Official Launcher. The launcher starts with Wine-staging but I get the error (The Directory is Invalid) when I try to start the game client. The game worked flawlessly before they changed the launcher. I think the problem is the second launcher called "Soulworkerlauncher.exe". The game is free to play: https://en.soulworker.gameforge.com/landingpage/ -- 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 53407] New: Hogia Hemekonomi Missing date picker widget
by WineHQ Bugzilla 28 Jun '25

28 Jun '25

https://bugs.winehq.org/show_bug.cgi?id=53407 Bug ID: 53407 Summary: Hogia Hemekonomi Missing date picker widget Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: winehq(a)jonass.user.lysator.liu.se Distribution: --- Created attachment 72799 --> https://bugs.winehq.org/attachment.cgi?id=72799 How the calendar widget looks when run on Windows XP. When showing transactions there is a date entry field where the user can enter a date. Or press "enter" to get a date picker widget. The widget seems to be missing in Wine. To reproduce: - Run the software like "wine Hemeko.exe" - There will be dialogue asking about number format, click Yes. - On first run you get an intro (or error see Bug 53384). If error, just dismiss. If intro, press "Återgå till Hemekonomi" to dismiss. - Click "Arkiv" and "Ny" to create a new database to work with. When asked "Ange namnet på den nya databasen" enter something like "foo.mdb" and click OK. - Click "Fortsätt med Hemekonomi" to dismiss setup wizard. - Press CTRL-K or click on icon Kontoutdrag. - Click OK. - Use mouse to set focus on entry field in lower right corner called "Fr o m" - Press enter. - See Program Error. On subsequent runs click Arkiv/Öppna instead to use the existing foo.mdb database. -- 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 13

[Bug 55138] New: msys2: bash.exe is not able to fork/start another process.
by WineHQ Bugzilla 27 Jun '25

27 Jun '25

https://bugs.winehq.org/show_bug.cgi?id=55138 Bug ID: 55138 Summary: msys2: bash.exe is not able to fork/start another process. Product: Wine Version: 8.10 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: bernhardu(a)mailbox.org Distribution: --- Created attachment 74697 --> https://bugs.winehq.org/attachment.cgi?id=74697 allocation stacks in parent and child bash.exe This is a followup to bug 47808. If I understand it right, bug 47808 was primarily about native libraries getting called at a win32 stack which was not yet committed. Those native libraries then jumped over the guard page, therefore the stack got not grown, instead a crash reported. This aspect was fixed by using the syscall interface and therefore bug 47808 was closed. But there is another issue that causes a msys2-forked process crashing, because after the stack was grown it still misses the PAGE_READWRITE flags. For this Zeb Figura included in the first attachement to bug 47808 "always expand the stack if within the stack reserve" a line adding the flags "VPROT_COMMITTED | VPROT_READ | VPROT_WRITE" to the page that gets the VPROT_GUARD removed in grow_thread_stack. This modification still enables a forked process to run. The issue can be reproduced with an unmodified wine by just - running msys2 bash.exe interactively - then trying to start e.g. notepad from it. Attached file shows the stack when the stack gets allocated - in a working msys2-parent process and - in a failing msys2-forked child process. Therefore it looks like the forked stack get really setup differently, but it is still not clear if or when this memory gets the READ/WRITE added in native windows. -- 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

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 December 2023