wine-bugs February 2025

wine-bugs@winehq.org

1 participants
849 discussions

[Bug 57861] New: All wine runs fail with "failed to start wineboot"
by WineHQ Bugzilla 25 Feb '25

25 Feb '25

https://bugs.winehq.org/show_bug.cgi?id=57861 Bug ID: 57861 Summary: All wine runs fail with "failed to start wineboot" Product: Wine Version: 10.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: shtetldik(a)gmail.com Distribution: --- After upgrade to Wine 10.2 in Debian testing (using packages from Wine debian repo), any usage of that package wine (both regular and staging) fail with such error: wine winecfg wine: failed to open L"C:\\windows\\system32\\wineboot.exe": c0000135 0024:err:environ:run_wineboot failed to start wineboot c0000135 wine: could not load kernel32.dll, status c0000135 If I build Wine myself (new wow64 build), it works fine. -- 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 57877] New: CMD: Parsing issue: Mismatch in parentheses provoked by trailing tab
by WineHQ Bugzilla 25 Feb '25

25 Feb '25

https://bugs.winehq.org/show_bug.cgi?id=57877 Bug ID: 57877 Summary: CMD: Parsing issue: Mismatch in parentheses provoked by trailing tab Product: Wine Version: 10.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: cmd Assignee: wine-bugs(a)winehq.org Reporter: Dominik-Home(a)gmx.de Distribution: --- Wine has issues in parsing if-statements like the following: if not [%FOO:~-1%] == [True] ( <----- NOTE THE TRAILING TAB HERE echo ENTERED IF-EXPRESSION ) On Windows those kind of expressions execute as expected but on Wine it errors with a note 'Mismatch in parentheses.'. While playing around with this construct I realised that the trailing tab may cause this issue. As soon as I remove it, the code seems to work. See also the attached reproducers. For reference this, is the last issue to get the PlanAhead (part of Xilinx ISE) batch scripts to work. They are responsible for configuring the environment and starting the GUI. -- 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 57571] New: Zafehouse: Diaries garbage/black screen
by WineHQ Bugzilla 25 Feb '25

25 Feb '25

https://bugs.winehq.org/show_bug.cgi?id=57571 Bug ID: 57571 Summary: Zafehouse: Diaries garbage/black screen Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: blocker Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: rencer(a)euromail.hu Distribution: --- I have this game installed on my computer with it's own wineprefix. Never used that prefix for anything else, just to play this one game. Originally I created that wineprefix and installed the game inside that back at 2014. Also I tried to run the game with this wineprefix on the exact same computer as back then. It required lot of manual trickering to make it work. At that time nobody managed to run the game with sound on Linux, but I figured out and posted a how-to on the game's forum. Later even the developers shared that how-to on the Steam page of the game. See here: https://steamcommunity.com/app/249360/discussions/0/846963711048254058/#c61… Sadly that forum page doesn't exist anymore; possibly because the game is old and no longer supported. It doesn't really matter anyway, because it is no longer possible to make the game install and setup a wineprefix that way. Back then it was possible to install all the requirements manually because wine/winetricks wasn't blocking us to install them. (such as full DirectX9, .NET 3.5 SP1, etc.) As years passed, once in a while I played the game, everything was fine. But today, even that I try to run the game in that exact same wineprefix on the exact same computer, it doesn't work anymore. When I run the game it is starts loading; you can see as the game writes it on the bottom right corner. When the loading process finishes the game supposed to show the menu screen. There is the problem. I hear the music but the screen is just a mess. It somehow shows the content of whatever is in the background of the game; like any other window or the desktop itself. But it is all garbage; it looks like whatever is in the background is turned into a puzzle, shuffled and randomly put back on the screen. The reason I kept the wine version 'unspecified' because I also tried to run the game under different wine prefixes that uses different wine versions. Also tried to make fresh wineprefix with the current latest wine in my Manjaro XFCE, which is version 9.20. Creating a new one is impossible because of winetricks/wine. I have many winprefixes, so I find one or two that works.(One is version 9.20) With these different working prefixes the result is always the same as with the original old prefix; messed up 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.

1 11

[Bug 57875] New: wine cannot load/use system faudio PE library
by WineHQ Bugzilla 25 Feb '25

25 Feb '25

https://bugs.winehq.org/show_bug.cgi?id=57875 Bug ID: 57875 Summary: wine cannot load/use system faudio PE library Product: Wine Version: 10.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: build-env Assignee: wine-bugs(a)winehq.org Reporter: arusanu.bu(a)gmail.com Distribution: --- Wine fails to use the system PE FAudio library for FAudio version 25.02, and it falls back on the bundled FAudio library. Wine can still load/accept older system FAudio libraries, but something must have changed in FAudio that makes Wine fail to identify the newer versions of FAudio libraries as valid versions. Config output snippet when Wine is checking faudio-25.02: ' checking for x86_64-w64-mingw32-pkg-config... x86_64-w64-mingw32-pkg-config checking for MinGW FAudio.h... yes checking for FAudio_CommitOperationSet in MinGW -lFAudio... no checking for MinGW fluidsynth.h... yes checking for new_fluid_synth in MinGW -lfluidsynth... yes ' I've tested this behavior on Wine 10.0 and up, with the older and newer versions of the MinGW-FAudio libraries built under the same environment. -- 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 57809] New: cmd: Incorrect substring expansion of last character (e.g. `!MY_STR:~1!`)
by WineHQ Bugzilla 25 Feb '25

25 Feb '25

https://bugs.winehq.org/show_bug.cgi?id=57809 Bug ID: 57809 Summary: cmd: Incorrect substring expansion of last character (e.g. `!MY_STR:~1!`) Product: Wine Version: 10.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: cmd Assignee: wine-bugs(a)winehq.org Reporter: Dominik-Home(a)gmx.de Distribution: --- Call the following script and observe the different output on Windows and Wine. Substring expansion seems to work in general except the last character, therefore MY_STR is set to 1 character to trigger the issue immediately. Note that I've focused on the issue at hand and haven't tried out other variations of substring-expansion. issue_substring_expansion.bat ```cmd @echo off setlocal enableextensions enabledelayedexpansion set MY_STR=R echo "!MY_STR:~1!" REM Prints "" on Windows REM Prints "R" on Wine ``` This issue is blocking to get PlanAhead (part of Xilinx ISE 14.7) to work. Multiple batch scripts set-up the environment before starting the GUI. Because of this issue, they end up in an endless loop while iterating over all characters in a variable similar to PATH. My version: ```console $ wine --version wine-10.0 (Staging) ``` -- 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 57804] New: cmd: CALL instruction freezes
by WineHQ Bugzilla 25 Feb '25

25 Feb '25

https://bugs.winehq.org/show_bug.cgi?id=57804 Bug ID: 57804 Summary: cmd: CALL instruction freezes Product: Wine Version: 10.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: cmd Assignee: wine-bugs(a)winehq.org Reporter: Dominik-Home(a)gmx.de Distribution: --- Executing the 'CALL'-instruction on a *.bat file may causes freezes when using e.g. '@echo off' in the called script. ```console $ wine --version wine-10.0 (Staging) ``` I inserted two minimal reproducers below that are used in the following examples. Note that I marked the output of the scripts as comment with the REM command as well as my own descriptions. ```cmd C:\>C:\working.bat REM C:\>echo Test REM Test REM Command returns immediately. No issue here C:\>C:\issue.bat REM Test REM Command returns immediately. No issue here C:\>CALL C:\working.bat REM C:\>echo Test REM Test REM Command returns immediately. No issue here C:\>CALL C:\issue.bat REM Test REM ISSUE: Command freezes here and never returns ``` working.bat: ```cmd @echo on echo Test ``` issue.bat: ```cmd @echo off echo Test ``` This issue was encountered while trying out PlanAhead, a tool included in the Xilinx ISE design package. They use multiple batch scripts to configure the environment before starting the GUI application. Because the batch files do not work properly the GUI does not start at all. I.e. the application (PlanAhead) is completely unusable. -- 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 12

[Bug 18959] New: MetaTrader 4 installer hangs at the very end of file extraction
by wine-bugs＠winehq.org 25 Feb '25

25 Feb '25

http://bugs.winehq.org/show_bug.cgi?id=18959 Summary: MetaTrader 4 installer hangs at the very end of file extraction Product: Wine Version: 1.1.23 Platform: PC URL: http://www.metatrader4.com/files/mt4setup.exe OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: msvcrt AssignedTo: wine-bugs(a)winehq.org ReportedBy: arethusa26(a)gmail.com CC: julliard(a)winehq.org With today's Git (wine-1.1.23-221-gafce86b), the MetaTrader installer hangs at the very end of file extraction at "C:\Program Files\MetaTrader 4\mailbox\1190736044.english" with sufficient responsiveness to handle the Cancel button being pressed, which merely hides the installer window until a Ctrl+C interrupt is sent to the installer. The installer worked properly in 1.0.1, and the regression test revealed: 1c91d54503f9b2afa513dc4dd79bf19bc9bad51a is first bad commit commit 1c91d54503f9b2afa513dc4dd79bf19bc9bad51a Author: Alexandre Julliard <julliard(a)winehq.org> Date: Wed Feb 18 14:44:17 2009 +0100 msvcrt: Don't try to duplicate invalid handles. Don't reset std handles if we didn't set them. :040000 040000 2abf5f9a82de1d29b1fccadc658fc3a956388ac4 86464380dfe4aca4c5c11ea2a539a1fc5def03b8 M dlls Reverting the commit in HEAD allows the installer to start. -- 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 32

[Bug 52714] New: Richard Burns Rally (RallySimFans): Logitech G29 Force Feedback doesn't work
by WineHQ Bugzilla 24 Feb '25

24 Feb '25

https://bugs.winehq.org/show_bug.cgi?id=52714 Bug ID: 52714 Summary: Richard Burns Rally (RallySimFans): Logitech G29 Force Feedback doesn't work Product: Wine Version: 7.4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: groovestomp+winehq(a)getgoogleoff.me Distribution: --- Install the RallySimFans distribution of Richard Burns Rally in a new wine prefix: https://rallysimfans.hu/rbr/index.php Run: "wine control" with the prefix and verify the racing wheel inputs all work correctly and force feedback works. Now go into the game, configure the wheel and notice force feedback does not work. Downgrading to Wine 5 (The latest previous version available before 7 on my system) works without issue. Here's a mention of this issue that led me to isolate that 7 is the problem: https://forum.winehq.org/viewtopic.php?t=36110 And that thread refers to another here: http://srmz.net/index.php?showtopic=14451#entry162706 Output of lshw -short: H/W path Device Class Description ============================================================= system Oryx Pro (Not Applicable) /0 bus Oryx Pro /0/0 memory 64KiB BIOS /0/1d memory 32GiB System Memory /0/1d/0 memory 16GiB SODIMM DDR4 Synchronous 2400 MHz (0.4 ns) /0/1d/1 memory [empty] /0/1d/2 memory 16GiB SODIMM DDR4 Synchronous 2400 MHz (0.4 ns) /0/1d/3 memory [empty] /0/23 memory 256KiB L1 cache /0/24 memory 1MiB L2 cache /0/25 memory 6MiB L3 cache /0/26 processor Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz /0/100 bridge Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers /0/100/1 bridge 6th-10th Gen Core Processor PCIe Controller (x16) /0/100/1/0 display GP104BM [GeForce GTX 1070 Mobile] /0/100/1/0.1 multimedia GP104 High Definition Audio Controller /0/100/14 bus 100 Series/C230 Series Chipset Family USB 3.0 xHCI Controller /0/100/14/0 usb1 bus xHCI Host Controller /0/100/14/0/1 input G29 Driving Force Racing Wheel /0/100/14/0/4 multimedia Turtle Beach P11 Headset /0/100/14/0/5 communication Arduino Leonardo /0/100/14/0/7 generic EgisTec_ES603 /0/100/14/0/8 communication Bluetooth wireless interface /0/100/14/0/9 multimedia Chicony USB 2.0 Camera /0/100/14/1 usb2 bus xHCI Host Controller /0/100/14.2 generic 100 Series/C230 Series Chipset Family Thermal Subsystem /0/100/16 communication 100 Series/C230 Series Chipset Family MEI Controller #1 /0/100/17 storage HM170/QM170 Chipset SATA Controller [AHCI Mode] /0/100/1c bridge 100 Series/C230 Series Chipset Family PCI Express Root Port #1 /0/100/1c.4 bridge 100 Series/C230 Series Chipset Family PCI Express Root Port #5 /0/100/1c.4/0 generic RTL8411B PCI Express Card Reader /0/100/1c.4/0.1 enp109s0f1 network RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller /0/100/1c.6 bridge 100 Series/C230 Series Chipset Family PCI Express Root Port #7 /0/100/1c.6/0 wlp110s0 network Wireless 8265 / 8275 /0/100/1d bridge 100 Series/C230 Series Chipset Family PCI Express Root Port #9 /0/100/1d/0 storage NVMe SSD Controller SM961/PM961/SM963 /0/100/1d/0/0 /dev/nvme0 storage Samsung SSD 960 EVO 250GB /0/100/1d/0/0/1 /dev/nvme0n1 disk 250GB NVMe namespace /0/100/1d/0/0/1/1 /dev/nvme0n1p1 volume 497MiB Windows FAT volume /0/100/1d/0/0/1/2 /dev/nvme0n1p2 volume 4095MiB Windows FAT volume /0/100/1d/0/0/1/3 /dev/nvme0n1p3 volume 224GiB EFI partition /0/100/1d/0/0/1/4 /dev/nvme0n1p4 volume 4095MiB Linux swap volume /0/100/1f bridge HM175 Chipset LPC/eSPI Controller /0/100/1f.2 memory Memory controller /0/100/1f.3 multimedia CM238 HD Audio Controller /0/100/1f.4 bus 100 Series/C230 Series Chipset Family SMBus /0/1 input PnP device PNP0303 /0/2 generic PnP device SYN1219 /0/3 system PnP device PNP0c02 /0/4 system PnP device PNP0c02 /0/5 system PnP device PNP0b00 /0/6 generic PnP device INT3f0d /0/7 system PnP device PNP0c02 /0/8 system PnP device PNP0c02 /0/9 system PnP device PNP0c02 /0/a scsi3 storage /0/a/0.0.0 /dev/sda disk 1TB WDC WD10SPZX-00Z /0/a/0.0.0/0 /dev/sda volume 931GiB Linux Unified Key Setup volume -- 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 57871] New: InteleViewer appears to crash on quitting.
by WineHQ Bugzilla 24 Feb '25

24 Feb '25

https://bugs.winehq.org/show_bug.cgi?id=57871 Bug ID: 57871 Summary: InteleViewer appears to crash on quitting. Product: Wine Version: 10.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: neurofire80(a)gmail.com Distribution: --- Created attachment 78091 --> https://bugs.winehq.org/attachment.cgi?id=78091 The log produced by wine When quitting InteleViewer (radiology application), the program produces an error window. Full size windows also do not work, although that may be a separate issue. I'm on Manjaro i3, on the latest stable kernel on a Ryzen 7 with plenty of RAM (128gb). -- 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 56246] New: Regarding the color depth of BMP in the SavePicture method: the value is unstable.
by WineHQ Bugzilla 24 Feb '25

24 Feb '25

https://bugs.winehq.org/show_bug.cgi?id=56246 Bug ID: 56246 Summary: Regarding the color depth of BMP in the SavePicture method: the value is unstable. Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: win32u Assignee: wine-bugs(a)winehq.org Reporter: taka(a)bahamut7.com Distribution: --- Created attachment 75953 --> https://bugs.winehq.org/attachment.cgi?id=75953 Difference in color depth between Wine and Windows Thank you for the great software. In Windows 10/11, the SavePicture method saves in "24-bit color" even if the display's color setting is "32-bit color". In Wine, if the display's color setting is "32bit color", the picture is saved in "32bit color" and the Windows software throws an error. In Debian, for some reason, it is saved with the value "0". Due to this difference, some software may not work. -- 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

← Newer
1
...
54
55
56
57
58
59
60
...
85
Older →

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 2025