wine-bugs May 2025

wine-bugs@winehq.org

1 participants
986 discussions

[Bug 58229] New: _SH_SECURE sharing flag is not supported and causing _wfsopen to fail
by WineHQ Bugzilla 01 Jul '25

01 Jul '25

http://bugs.winehq.org/show_bug.cgi?id=58229 Bug ID: 58229 Summary: _SH_SECURE sharing flag is not supported and causing _wfsopen to fail Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: msvcrt Assignee: wine-bugs(a)winehq.org Reporter: bruvzg13(a)proton.me Distribution: --- Calling _wfsopen with _SH_SECURE sharing flag result in failure and "012c:err:msvcrt:_wsopen_dispatch Unhandled shflags 0x80" error in the terminal. 0x80 value correspond to _SH_SECURE Discovered while debugging Godot Engine - https://github.com/godotengine/godot/pull/106392 Seems like the case for this flag is missing: https://gitlab.winehq.org/wine/wine/-/blob/master/dlls/msvcrt/file.c?ref_ty… The flag is documented as "shared read, exclusive write access" (https://learn.microsoft.com/en-us/cpp/c-runtime-library/sharing-constants?v…), and the issue can be worked around by substituting it with "(mode_flags == READ) ? _SH_DENYWR : _SH_DENYRW", which result in the same behavior as on Windows (at least in our use case). -- 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 58271] New: Window decoration issues in Wine with Wayland driver
by WineHQ Bugzilla 01 Jul '25

01 Jul '25

http://bugs.winehq.org/show_bug.cgi?id=58271 Bug ID: 58271 Summary: Window decoration issues in Wine with Wayland driver Product: Wine Version: 10.8 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winewayland Assignee: wine-bugs(a)winehq.org Reporter: mexano222(a)gmail.com Distribution: --- Created attachment 78617 --> http://bugs.winehq.org/attachment.cgi?id=78617 default decorations When running applications through Wine using the native Wayland driver, windowed applications are not receiving proper window decorations (e.g., titlebars, borders) from the system window manager. Instead, Wine's default, minimal, and visually unappealing decorations are displayed. I have enabled option "Allow the window manager to decorate the windows" in winecfg and it's working fine on Xwayland. But this option does not appear to have any effect under native Wayland. -- 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 1

[Bug 58126] New: Display enumeration differs from winex11
by WineHQ Bugzilla 01 Jul '25

01 Jul '25

http://bugs.winehq.org/show_bug.cgi?id=58126 Bug ID: 58126 Summary: Display enumeration differs from winex11 Product: Wine Version: 10.5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winewayland Assignee: wine-bugs(a)winehq.org Reporter: oleg(a)np880.ru Distribution: --- Created attachment 78389 --> http://bugs.winehq.org/attachment.cgi?id=78389 Display enumeration in winewayland driver. Enumeration of displays in winewayland driver differs from winex11 and doesn't even follow order of reported wl_outputs. I have 3 displays: with middle one (1440p, primary) being the first display. My other displays are 1080p. In winex11 it's indeed the first, and it also reported as first wl_output by my compositor (KWin). But winewayland driver reports it the second and the leftmost display reported as the first. It causes problem in old games that don't have display selection and enumerate video modes only for primary (first) display, so I can't get resolution higher than 1080p on my 1440p display that is supposed to be primary. Although we don't have a way to determine primary screen on Wayland we can at least follow order of reported wl_outputs. Here is what my compositor is reporting and it doesn't correlate with order of winewayland driver. interface: 'wl_output', version: 4, name: 61 name: DP-1 description: Xiaomi Corporation Mi monitor x: 1920, y: 0, scale: 2, physical_width: 598 mm, physical_height: 336 mm, make: 'Xiaomi Corporation', model: 'Mi monitor', subpixel_orientation: unknown, output_transform: normal, mode: width: 2560 px, height: 1440 px, refresh: 180.000 Hz, flags: current interface: 'wl_output', version: 4, name: 62 name: DP-2 description: Philips Consumer Electronics Company Philips 226V4 x: 0, y: 0, scale: 1, physical_width: 477 mm, physical_height: 268 mm, make: 'Philips Consumer Electronics Company', model: 'Philips 226V4', subpixel_orientation: unknown, output_transform: normal, mode: width: 1920 px, height: 1080 px, refresh: 60.000 Hz, flags: current interface: 'wl_output', version: 4, name: 63 name: HDMI-A-1 description: Philips Consumer Electronics Company Philips 235PL x: 3968, y: 0, scale: 1, physical_width: 510 mm, physical_height: 287 mm, make: 'Philips Consumer Electronics Company', model: 'Philips 235PL', subpixel_orientation: unknown, output_transform: 90°, mode: width: 1920 px, height: 1080 px, refresh: 60.000 Hz, flags: current -- 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 57980] New: Adobe Creative Cloud requires unimplemented function KERNEL32.dll.SetThreadpoolTimerEx
by WineHQ Bugzilla 01 Jul '25

01 Jul '25

https://bugs.winehq.org/show_bug.cgi?id=57980 Bug ID: 57980 Summary: Adobe Creative Cloud requires unimplemented function KERNEL32.dll.SetThreadpoolTimerEx Product: Wine Version: 10.3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: asdfghrbljzmkd(a)outlook.com Distribution: --- Every so often I test installing Adobe CC on Wine to see if it will work. With the recent fixes relating to libcef/edge/chromium sandboxing, I gave it another go. Seems like this is now an issue: ``` wine: Call from 00006FFFFFC75D38 to unimplemented function KERNEL32.dll.SetThreadpoolTimerEx, aborting ``` -- 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 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 58261] New: Ys Origin: videos playing upside down
by WineHQ Bugzilla 28 Jun '25

28 Jun '25

http://bugs.winehq.org/show_bug.cgi?id=58261 Bug ID: 58261 Summary: Ys Origin: videos playing upside down Product: Wine Version: unspecified Hardware: x86-64 URL: https://store.steampowered.com/app/207350/Ys_Origin/ OS: Linux Status: NEW Keywords: regression Severity: normal Priority: P2 Component: quartz Assignee: wine-bugs(a)winehq.org Reporter: gyebro69(a)gmail.com CC: z.figura12(a)gmail.com Regression SHA1: 2f180106471a41fa3d95f21919b87b94d8e13e63 Distribution: --- Created attachment 78600 --> http://bugs.winehq.org/attachment.cgi?id=78600 terminal output Intro and in-game videos are playing upside down in Ys:Origin. Tested with the Steam and GOG.com versions. Demo is available on Steam but it is not affected (the demo uses different video format for videos). This is after commit 2f180106471a41fa3d95f21919b87b94d8e13e63 amstream: Implement the custom ddraw stream allocator. The allocator has a lot of custom behaviour that is very visible in how it interacts with Update(). Naturally this has the benefit of writing directly into the mapped surfaces. The gstreamer errors in my log were present before that commit too. wine-10.8-103-g8f91df4c4e4 -- 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 1

[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

[Bug 37131] New: Clang Static Analyzer: Division by zero
by wine-bugs＠winehq.org 27 Jun '25

27 Jun '25

https://bugs.winehq.org/show_bug.cgi?id=37131 Bug ID: 37131 Summary: Clang Static Analyzer: Division by zero Product: Wine Version: 1.7.22 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: lukebenes(a)hotmail.com Clang Static Analyzer identifies Division by zero File: dlls/winex11.drv/palette.c Location: line 601, column 43 Description: Division by zero #define NB_RESERVED_COLORS 20 ... static void X11DRV_PALETTE_FillDefaultColors(....) { ... int i = 0, idx = 0; int red, no_r, inc_r; ... if (palette_size <= NB_RESERVED_COLORS) return; while (i*i*i < (palette_size - NB_RESERVED_COLORS)) i++; no_r = no_g = no_b = --i; ... inc_r = (255 - NB_COLORCUBE_START_INDEX)/no_r; //Clang: Division by zero ... } The code will continue executing if the palette_size variable is larger than or equal to 21. With the value 21, the 'i' variable will be first incremented by one and then decremented by one. As a result, the 'i' variable will remain equal to zero, which will cause the division-by-zero error. -- 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 5

← Newer
1
...
31
32
33
34
35
36
37
...
99
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 May 2025