wine-bugs

wine-bugs@winehq.org

1 participants
159488 discussions

[Bug 59046] New: wine: Call to unimplemented function icu.dll.ulocdata_getCLDRVersion, aborting wine: Call to unimplemented function icu.dll.uloc_canonicalize, aborting
by WineHQ Bugzilla 02 Dec '25

02 Dec '25

http://bugs.winehq.org/show_bug.cgi?id=59046 Bug ID: 59046 Summary: wine: Call to unimplemented function icu.dll.ulocdata_getCLDRVersion, aborting wine: Call to unimplemented function icu.dll.uloc_canonicalize, aborting Product: Wine Version: 10.19 Hardware: x86-64 URL: https://builds.dotnet.microsoft.com/dotnet/WindowsDesk top/10.0.0/windowsdesktop-runtime-10.0.0-win-x64.exe OS: Linux Status: NEW Keywords: download Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)list.winehq.org Reporter: xerox.xerox2000x(a)gmail.com Distribution: Debian Followup of bugreport https://bugs.winehq.org/show_bug.cgi?id=59041 in current git-wine: Just install dotnet10 and run the simple app from that bugreoprt: https://github.com/dreamsyntax/net10-bug-ookii-wine-repro/releases/download… -- 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 58261] New: Ys Origin: videos playing upside down
by WineHQ Bugzilla 02 Dec '25

02 Dec '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 2

[Bug 56790] New: wine binds my application to "lo" adapter
by WineHQ Bugzilla 02 Dec '25

02 Dec '25

https://bugs.winehq.org/show_bug.cgi?id=56790 Bug ID: 56790 Summary: wine binds my application to "lo" adapter Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winsock Assignee: wine-bugs(a)winehq.org Reporter: contact(a)msteinbusch.nl Distribution: ArchLinux Created attachment 76596 --> https://bugs.winehq.org/attachment.cgi?id=76596 A full wine trace Issue: Farming Simulator 2022 dedicated webserver binds application to "lo" adapter Wine doesn't run my program the same way as Windows does, for some reason it binds to the "lo" adapter. I suspect the application is selecting the first interface. Sadly there is no way to override this. I included a full trace, keywords to look trough are winsock, 127.0.0.1, winsock:bind socket etc. Any help is welcome and if more info is needed let me know. Wine: 9.10-1 and < Archlinux, Kernel 6.9.3. X68_64 A VNC instance where the issue can be reproduced is available on request. A license key for Farming Simulator 2022 can be provided by me on request. The download of the game/server can be found at: https://eshop.giants-software.com/downloads.php This docker container is using nginx to get around the issue: https://github.com/wine-gameservers/arch-wine-fs22 Screenshot and logs included in zip. -- 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 30

[Bug 58790] New: specops the line doesnt get past splash screen
by WineHQ Bugzilla 02 Dec '25

02 Dec '25

http://bugs.winehq.org/show_bug.cgi?id=58790 Bug ID: 58790 Summary: specops the line doesnt get past splash screen Product: Wine Version: 10.16 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winex11.drv Assignee: wine-bugs(a)winehq.org Reporter: zlice(a)crtdrift.us Distribution: --- JWM, fluxbox and openbox do not start "specops: the line" - they are stuck on splash screen. my fork of fluxbox (shynebox) does pass the splash screen, but, alt-tabbing breaks the window, at first it will be a 'smooshed' version of the fullscreen window, then alt-tabbing back and forward again will make a 1/4 of the screen window that isnt usable. -- 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 57954] New: Watch_Dogs black splash screen 10.3 rawinput:add_device Failed to open device
by WineHQ Bugzilla 02 Dec '25

02 Dec '25

https://bugs.winehq.org/show_bug.cgi?id=57954 Bug ID: 57954 Summary: Watch_Dogs black splash screen 10.3 rawinput:add_device Failed to open device Product: Wine Version: 10.3 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: --- Created attachment 78201 --> https://bugs.winehq.org/attachment.cgi?id=78201 wd-winedbg 10.2 seems to work fine, 10.3 gives an error about rawinput and the splash screen that should have the main character and game title is a black box and hangs using wow64 build, other 32bit games seem to work fine. running with WINEDBEUG ends in multiple varying lines of `0158:warn:rawinput:add_device Failed to open device file L"\\??\\HID#some-device-name#{hex-hash-id}", status 0xc0000034.` -- 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 14

[Bug 59073] New: Washed out colors in OpenGL
by WineHQ Bugzilla 02 Dec '25

02 Dec '25

http://bugs.winehq.org/show_bug.cgi?id=59073 Bug ID: 59073 Summary: Washed out colors in OpenGL Product: Wine Version: 10.19 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: opengl Assignee: wine-bugs(a)list.winehq.org Reporter: tpaniaki(a)protonmail.com Distribution: --- Created attachment 79862 --> http://bugs.winehq.org/attachment.cgi?id=79862 glxinfo A recent update in a wine component makes my OpenGL apps all washed out (see screenshot). This affects both X11 and wayland. I'm running qtile on wayland with wlroots0.19. -- 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 59071] New: Roblox Studio flickering when resizing docked child windows on winex11 and winevulkan driver
by WineHQ Bugzilla 02 Dec '25

02 Dec '25

http://bugs.winehq.org/show_bug.cgi?id=59071 Bug ID: 59071 Summary: Roblox Studio flickering when resizing docked child windows on winex11 and winevulkan driver Product: Wine Version: 10.20 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: trivial Priority: P2 Component: winevulkan Assignee: wine-bugs(a)list.winehq.org Reporter: eff3ctsb0t(a)gmail.com Distribution: --- Created attachment 79856 --> http://bugs.winehq.org/attachment.cgi?id=79856 Wine debugging log when using Studio's native Vulkan renderer When resizing one of the docked child windows inside of Roblox Studio with its renderer set to Vulkan (or using DXVK with the default) and while using the X11 driver, the contents of the parent window appear to flicker rapidly. This only occurs under this combination and does not happen under WineD3D/OpenGL or winewayland. Steps to reproduce: 1. Create an account on roblox.com. 2. Download the installer for Roblox Studio. 3. Create a desktop entry named "Roblox_Studio.desktop" with the following contents. Replace <user> with the name of your user. [Desktop] Name=Roblox Studio (modified) Exec=env "WINEPREFIX=/home/<user>/.wine" wine "C:\\\\users\\\\<user>\\\\AppData\\\\Roaming\\\\Microsoft\\\\Windows\\\\Start Menu\\\\Programs\\\\Roblox\\\\Roblox Studio.lnk" %u Type=Application StartupNotify=true Icon=2C11_RobloxStudioBeta.0 StartupWMClass=robloxstudiobeta.exe MimeType=x-scheme-handler/roblox-studio-auth 4. Run the installer through Wine. This should also launch Roblox Studio itself once the installation is complete. If not, run the RobloxStudioBeta.exe executable that is located inside the Wineprefix. 5. Upon launching Roblox Studio, you will be greeted by an error prompting you to login via your browser. Follow its instructions. 6. Once you reached the place templates selection, click on the "File" menu on the top left, then on "Studio Settings" and then on "Rendering" in the newly spawned window, where you should change the "Graphics Mode" from "Automatic" to "Vulkan" (or just leave it as the default and copy the DXVK DLLs into the Wineprefix). After that, relaunch Studio. 7. Load one of the place templates, then try resizing one of the docked child windows (the "Explorer" window for instance). System Information: OS: Arch Linux x86_64 Kernel: Linux 6.17.9-arch1-1 Display Server: Wayland (Niri) GPU: AMD Radeon RX 6650 XT [Discrete] Driver: Mesa 25.2.7-1 -- 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 59038] New: wow64 mode and Unhandled exception: The type initializer for 'Microsoft.DotNet.Installer.Windows.InstallerBase' threw an exception.
by WineHQ Bugzilla 02 Dec '25

02 Dec '25

http://bugs.winehq.org/show_bug.cgi?id=59038 Bug ID: 59038 Summary: wow64 mode and Unhandled exception: The type initializer for 'Microsoft.DotNet.Installer.Windows.InstallerBase' threw an exception. Product: Wine Version: 10.18 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)list.winehq.org Reporter: info(a)fernandolucas.info Distribution: --- Created attachment 79802 --> http://bugs.winehq.org/attachment.cgi?id=79802 wine console output I am using the new packages for Debian Wine 10.18 - 10.19 with the new wow64 mode. Installing .net 10 after initializing the prefix works well. Additional installations of a previous .net core version or running C:\Program Files\dotnet\dotnet.exe workload install wasm-tools fails with 0150:fixme:crypt:CertAddCertificateLinkToStore (00007FFFFED4B850, 00007FFFFE8A3DF8, 00000004, 0000000000000000): semi-stub Unhandled exception: The type initializer for 'Microsoft.DotNet.Installer.Windows.InstallerBase' threw an exception 0130:fixme:unwind:call_user_apc_dispatcher flags 0x3 are not supported. -- 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 59070] New: vkGetPhysicalDeviceProperties2 gives incorrect results in wow64 mode
by WineHQ Bugzilla 02 Dec '25

02 Dec '25

http://bugs.winehq.org/show_bug.cgi?id=59070 Bug ID: 59070 Summary: vkGetPhysicalDeviceProperties2 gives incorrect results in wow64 mode Product: Wine Version: 10.20 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winevulkan Assignee: wine-bugs(a)list.winehq.org Reporter: m101010a(a)gmail.com Distribution: --- Created attachment 79853 --> http://bugs.winehq.org/attachment.cgi?id=79853 vkGetPhysicalDeviceProperties2 test program When running the attached C++ program on Linux, and as a 64-bit program on wine, it prints 29 different image layouts. When run as a 32-bit program on wine (under wow64), it sometimes prints "Undefined" 29 times, and sometimes prints no image layouts at all. vkGetPhysicalDeviceProperties2 should consistently give the same results regardless of whether it is called from a 32-bit or 64-bit program. -- 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 59016] New: Directdraw games get black screen
by WineHQ Bugzilla 02 Dec '25

02 Dec '25

http://bugs.winehq.org/show_bug.cgi?id=59016 Bug ID: 59016 Summary: Directdraw games get black screen Product: Wine Version: 10.15 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: d3d Assignee: wine-bugs(a)list.winehq.org Reporter: i(a)xuzhao.net Distribution: --- Created attachment 79755 --> http://bugs.winehq.org/attachment.cgi?id=79755 Black screen, with directdraw render method Hi Wine Community, I want to ask about a regression I observed on my desktop (openSUSE Tumbleweed, KDE, NVIDIA 3080 Ti). A few old Japanese Galgames have blackscreen starting from a few months ago. To be specific, I am running Ebenbourg no Kaze (by Studio e-go!). The game screen is black, but with `WINEDEBUG=+ddraw` I can see logs being printed out: https://pastebin.com/s5m0i3AK I am testing on other applications, e.g., VisualBoyAdvance (the GameBoyAdvance simulator). I found that when I switch the render method to "DirectDraw" it shows black screen, but when I switch to "GDI", "OpenGL" or "Direct3D", the screen is normal. I have tried changing [HKCU/Wine/Direct3D] -> "renderer" from "gl" to "gdi", but the game/application will crash/black screen. I suspect there is a regression in DirectDraw support in Wine. -- 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

← Newer
1
...
4
5
6
7
8
9
10
...
15949
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