wine-bugs April 2025

wine-bugs@winehq.org

1 participants
811 discussions

[Bug 32342] New: PlanetSide2 Error message and bugreport.txt and debug.log in Steam.
by wine-bugs＠winehq.org 23 May '25

23 May '25

http://bugs.winehq.org/show_bug.cgi?id=32342 Bug #: 32342 Summary: PlanetSide2 Error message and bugreport.txt and debug.log in Steam. Product: Wine Version: unspecified Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: linards.liepins(a)gmail.com Classification: Unclassified Created attachment 42683 --> http://bugs.winehq.org/attachment.cgi?id=42683 PlanetSide2 bugreport.txt Cannot run PlanetSide 2 on x64 Fedora 17. Popuing up three similar error log message with attached bugreport. Also attached debug.log is generated in Steam install dir. -- 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 143

[Bug 40584] New: DLTCEP: wrong window layout, buttons cannot be pressed
by wine-bugs＠winehq.org 23 May '25

23 May '25

https://bugs.winehq.org/show_bug.cgi?id=40584 Bug ID: 40584 Summary: DLTCEP: wrong window layout, buttons cannot be pressed Product: Wine Version: 1.9.9 Hardware: x86-64 OS: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: p1(a)devopsx.com Created attachment 54426 --> https://bugs.winehq.org/attachment.cgi?id=54426 how it looks in wine In a modal window, buttons at the bottom can't be pressed with mouse (presumably due to tabbed control are reaching too far down). But if focused with tab, pressing with enter or space works fine. This is a recurrence of https://bugs.winehq.org/show_bug.cgi?id=8522. I'm not sure if it's ever been fixed. -- 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 3

[Bug 58145] New: Out of Ctrl 1.2: game doesn't launch, gives error
by WineHQ Bugzilla 23 May '25

23 May '25

http://bugs.winehq.org/show_bug.cgi?id=58145 Bug ID: 58145 Summary: Out of Ctrl 1.2: game doesn't launch, gives error Product: Wine Version: 10.6 Hardware: x86-64 OS: MacOS Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: cemer99797(a)isorax.com Created attachment 78425 --> http://bugs.winehq.org/attachment.cgi?id=78425 Wine-devel 10.6 terminal log The game Out of Ctrl 1.2 doesn't launch and gives the following error in a pop-up window on launch: Error Failed to initialize player Details: Failed to initialize graphics. Make sure you have DirectX 11 installed, have up to date drivers for your graphics card and have not disabled 3D acceleration in display settings. InitializeEngineGraphics failed tested using Gcenx's wine-devel 10.6 build (https://github.com/Gcenx/macOS_Wine_builds/releases/tag/10.6) with GStreamer 1.26.0 download link (20 MB) (choose "OutOfCtrl_v1_2_EXE.zip"): https://miknugget.itch.io/out-of-ctrl shas256: 5d26c746c4e85b98af2f1f9fb4a4daeed837deb49427bf108935545f8958dba9 I'm using macOS 11 -- 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 15

[Bug 58156] New: Star Wars: Jedi Knight - Dark Forces II Demo: won't launch, "smackw32.DLL" failed to initialize
by WineHQ Bugzilla 23 May '25

23 May '25

http://bugs.winehq.org/show_bug.cgi?id=58156 Bug ID: 58156 Summary: Star Wars: Jedi Knight - Dark Forces II Demo: won't launch, "smackw32.DLL" failed to initialize Product: Wine Version: 10.6 Hardware: x86-64 OS: MacOS Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: cemer99797(a)isorax.com Created attachment 78437 --> http://bugs.winehq.org/attachment.cgi?id=78437 Wine-devel 10.6 log for "wine jkdemo.exe -windowgui" the Star Wars: Jedi Knight - Dark Forces II Demo: won't launch, it says "smackw32.DLL" failed to initialize. This is a Windows 95 game demo I tried setting the Windows Version to Windows 10, Windows 95, and Windows 98 in winecfg. I also tried launching the demo with and without the windowgui flag: `wine jkdemo.exe -windowgui` as mentioned in AppDB HowTo section. This is a regression because a lot of users report this game demo as Gold in AppDB, including on macOS (https://appdb.winehq.org/objectManager.php?sClass=version&iId=10948) The jedi.exe file is a launcher GUI which works fine, but when clicking "Play Jedi Knight Demo" it fails with the error: `file` command info for: jkdemo.exe PE32 executable (GUI) Intel 80386, for MS Windows Unable to start the Jedi Knight Demo game program. Try running JK.EXE where you installed the Demo directly. Also make sure you have the latest DirectX drivers installed on your system. The macOS terminal shows this error as one of the last things in the log: "err:module:loader_init "smackw32.DLL" failed to initialize, aborting" (the module is normally unzipped next to the jkdemo.exe executable) tested with Gcenx's Wine-devel 10.6 (https://github.com/Gcenx/macOS_Wine_builds/releases/tag/10.6) on macOS 11 and Wine-devel 9.21 (https://github.com/Gcenx/macOS_Wine_builds/releases/tag/9.21) and Gcenx's Wine CrossOverFOSS 23.7.1-1 based on Wine 8.0.1 (https://github.com/Gcenx/winecx/releases/tag/crossover-wine-23.7.1-1) download page (choose Download this File > Agree > Jedi Knight Demo.zip): https://community.pcgamingwiki.com/files/file/1308-jedi-knight-dark-forces-… sha256: 7bc013918cf79879a086a10c27306f2f3511852726f4b4a9fec09668ed221d18 -- 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 57954] New: Watch_Dogs black splash screen 10.3 rawinput:add_device Failed to open device
by WineHQ Bugzilla 23 May '25

23 May '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 10

[Bug 56486] New: Battle.net App Crash Cycle on Startup
by WineHQ Bugzilla 23 May '25

23 May '25

https://bugs.winehq.org/show_bug.cgi?id=56486 Bug ID: 56486 Summary: Battle.net App Crash Cycle on Startup Product: Wine Version: 9.5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: wschmrdr(a)gmail.com Distribution: --- Created attachment 76256 --> https://bugs.winehq.org/attachment.cgi?id=76256 Backtrace from the Program Error Starting up Battle.net App. Login screen shows with a loading circle as if it's trying to use a saved password to login. I receive a notice that there's an error and Battle.net has to shut down. I close it, and the error shows up again. This continues in a cycle until I use "wineserver -k" to exit. The backtrace saved from this has been attached. I am able to use the Settings button on the login screen for the Battle.net app, as well as typing in a username/password, but I cannot go any farther than that because there is no submit button and it doesn't seem to want to load. Be aware that I had previously been loading Starcraft II directly using the SC2Switcher.exe executable, but because a new version needs to be downloaded, I'm needing to get into the Battle.net app. Not sure if not using the app is a side effect. For the heck of it, I tried running the setup to update Battle.net, and the same thing occurred. -- 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 57936] New: Incorrect audio volume level read by app from the system - 100% all the time.
by WineHQ Bugzilla 22 May '25

22 May '25

https://bugs.winehq.org/show_bug.cgi?id=57936 Bug ID: 57936 Summary: Incorrect audio volume level read by app from the system - 100% all the time. 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: greblus(a)gmail.com Distribution: --- Hi guys. I'm trying to use Yousician on Linux and it works amazingly well, maybe even smoother than on W11, but there is one small problem: It's impossible to preform latency calibration as the app is checking global system volume, if it's too high, it disallows calibration to prevent hearing damage if the sounds it produces are too loud. On wine and wine-staging the volume in Yousician is always 100%. I use pipewire-pulse backend and plasma-pa, I'm changing volume from plasma settings or alsamixer, or pulsemixer but it stays 100% in Yousician. Hope there's an easy fix for it :). Regards, W. -- 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 58126] New: Display enumeration differs from winex11
by WineHQ Bugzilla 22 May '25

22 May '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 3

[Bug 19410] New: Personal Stock Monitor: tooltip text not visible
by wine-bugs＠winehq.org 22 May '25

22 May '25

http://bugs.winehq.org/show_bug.cgi?id=19410 Summary: Personal Stock Monitor: tooltip text not visible Product: Wine Version: 1.1.26 Platform: PC-x86-64 URL: http://www.personalstockmonitor.com/downloads.html OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: comctl32 AssignedTo: wine-bugs(a)winehq.org ReportedBy: Andrew.Talbot(a)talbotville.com In Personal Stock Monitor (see URL for download), if one hovers over a truncated entry a tooltip pops up, but there is no visible text on it. -- 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 11

[Bug 49097] New: Treeview unduly handles WM_SYSKEYDOWN
by WineHQ Bugzilla 22 May '25

22 May '25

https://bugs.winehq.org/show_bug.cgi?id=49097 Bug ID: 49097 Summary: Treeview unduly handles WM_SYSKEYDOWN Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: comctl32 Assignee: wine-bugs(a)winehq.org Reporter: contact(a)kcsoftwares.com Distribution: --- Treeview unduly handles WM_SYSKEYDOWN Refer to treeview.c case WM_KEYDOWN: case WM_SYSKEYDOWN: return TREEVIEW_KeyDown(infoPtr, wParam); No such processing on Listview : case WM_KEYDOWN: return LISTVIEW_KeyDown(infoPtr, (INT)wParam, (LONG)lParam); As a consequence, WM_SYSKEYDOWN not correctly passed to parent Wnd if focus is on a Treeview control. Proof of concept : Use ReactOS. Open Regedit or Event Viewer. Put focus on treeview. Alt+F4 does nothing (WM_SYSKEYDOWN "stuck" at Treeview component level) Suggested patch : change case WM_KEYDOWN: case WM_SYSKEYDOWN: return TREEVIEW_KeyDown(infoPtr, wParam); into case WM_KEYDOWN: return TREEVIEW_KeyDown(infoPtr, wParam); as no reason to handle WM_SYSKEYDOWN at component level. -- 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

← Newer
1
...
24
25
26
27
28
29
30
...
82
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 April 2025