wine-bugs

wine-bugs@winehq.org

1 participants
159310 discussions

[Bug 55218] New: Lotus Script "Print" macro crashes Lotus Approach
by WineHQ Bugzilla 24 Jul '25

24 Jul '25

https://bugs.winehq.org/show_bug.cgi?id=55218 Bug ID: 55218 Summary: Lotus Script "Print" macro crashes Lotus Approach Product: Wine-staging Version: 8.11 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: ToddAndMargo(a)zoho.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Created attachment 74832 --> https://bugs.winehq.org/attachment.cgi?id=74832 $ WINEDEBUG=seh,gdi,enhmetafile,winspool,localspl,psdrv wine approach.exe 2&>1 > WinePrintError.txt Fedora 38 Wine 8.11 Lotus Approach N99.8.0208.0800 (Smart Suite) In Lotus Approach, when you call the "Print" macro from a Lotus Script: RunApproachMacro("Print") Lotus Approach crashes. This happens about one out of every two print attempts. Occasionally, a "MEM_BAD_POINTER" will popup from Approach when it crashes. The attachment was created with: $ WINEDEBUG=seh,gdi,enhmetafile,winspool,localspl,psdrv wine approach.exe 2&>1 > WinePrintError.txt -- 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 17

[Bug 57723] New: 10 destroyed my column labels in Approach
by WineHQ Bugzilla 24 Jul '25

24 Jul '25

https://bugs.winehq.org/show_bug.cgi?id=57723 Bug ID: 57723 Summary: 10 destroyed my column labels in Approach Product: Wine-staging Version: 10.0-rc4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: ToddAndMargo(a)zoho.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Created attachment 77925 --> https://bugs.winehq.org/attachment.cgi?id=77925 mangled Approach column labels Lotus Approach N99.8.0208.0800 (Smart Suite) Fedora 41 Xfce 4.18 wine-10.0-0.7rc4.fc41.i686 (Staging) wine-10.0-0.7rc4.fc41.x86_64 (Staging 10 destroyed my ability to use my Approach business accounting. The labels on some column only show a single character. This is a DISASTER! Please fix! I will add a graphic of what it looks like under both wine and Windows 10 -- 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 58455] New: Word Pro loses path to a freshly opened file
by WineHQ Bugzilla 24 Jul '25

24 Jul '25

http://bugs.winehq.org/show_bug.cgi?id=58455 Bug ID: 58455 Summary: Word Pro loses path to a freshly opened file Product: Wine Version: 10.11 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: ToddAndMargo(a)zoho.com Distribution: --- SmartSuite-N99.8.0208.0800 Fedora 42 wine-devel-10.11-1.1.x86_64 Also reproducible under Fedora 41 wine-10.4-2.fc41.x86_64 (Staging from the Fedora repo) wine-10.4-2.fc41.i686 [1] open an existing .lwp file in Word Pro [2] make a change [3] press the save icons of file→save [4] you will be prompted for “Save As” instead of “Save” This is because Word Pro lost the path to your file [5] navigate back to your file and press “save” Okay the overwrite warning [6] make another change to your file [7] now press save. This time it will work. AND! this is not an issue under Fedroa 39 wine-9.1-1.fc39.i686 (staging from the Fedora repo) This is a complete pain-in-the-neck. Please fix. -- 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 53391] New: Unable to edit documents in Word Pro do to dictionary pop up
by WineHQ Bugzilla 24 Jul '25

24 Jul '25

https://bugs.winehq.org/show_bug.cgi?id=53391 Bug ID: 53391 Summary: Unable to edit documents in Word Pro do to dictionary pop up Product: Wine-staging Version: 7.12 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: ToddAndMargo(a)zoho.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Created attachment 72782 --> https://bugs.winehq.org/attachment.cgi?id=72782 User dictionary error Fedora 36 Wine 7.12-1 Word Pro N99.8.0208.0800 I am unable to edit document is work pro due to a constant pop up "Cannot load one or more user dictionaries" (see the attachment.) Reverting to wine-7.2-1 solves the issue, but brings back the bug where Approach crashes when printing to CUPS-PDF -- 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 58063] New: BeamNG Techdemo 0.3 crashes during HLSL compilation
by WineHQ Bugzilla 23 Jul '25

23 Jul '25

https://bugs.winehq.org/show_bug.cgi?id=58063 Bug ID: 58063 Summary: BeamNG Techdemo 0.3 crashes during HLSL compilation Product: vkd3d Version: 1.15 Hardware: x86-64 URL: https://www.moddb.com/games/beamng/downloads/beamng-te chdemo-03 OS: Linux Status: NEW Keywords: download Severity: normal Priority: P2 Component: hlsl Assignee: wine-bugs(a)winehq.org Reporter: gijsvrm(a)gmail.com Distribution: --- Created attachment 78316 --> https://bugs.winehq.org/attachment.cgi?id=78316 log Continuation of bug 56353. 0024:trace:d3dx:D3DXCompileShader data "#line 1 \"C:/users/gverm/AppData/Local/BeamNG/BeamNG-Techdemo-0.3/shaders/common/lighting/advanced/pointLightP.hlsl\"\r\n//-----------------------------------------------------------------------------\r\n// Copyright (c) 2012 GarageGames, LLC\r\n//\r\n// Permission is hereby granted, free o"..., length 7900, defines 01700020, include 0534F2D8, function "main", profile "ps_3_0", flags 0, shader 00528810, error_msgs 00528814, constant_table 00528818. 0024:trace:d3dcompiler:D3DCompile data 01700088, data_size 7900, filename (null), defines 01700020, include 0534F2D8, entrypoint "main", target "ps_3_0", sflags 0, eflags 0, shader 00528810, error_messages 00528814. 0024:trace:d3dcompiler:D3DCompile2 data 01700088, data_size 7900, filename (null), macros 01700020, include 0534F2D8, entry_point "main", profile "ps_3_0", flags 0, effect_flags 0, secondary_flags 0, secondary_data 00000000, secondary_data_size 0, shader_blob 00528810, messages_blob 00528814. vkd3d:0024:fixme:preproc_yyparse #line directive. wine: Unhandled page fault on read access to 00000000 at address 1043ADF5 (thread 0024), starting debugger... -- 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 42232] New: Sort version list by version number
by wine-bugs＠winehq.org 23 Jul '25

23 Jul '25

https://bugs.winehq.org/show_bug.cgi?id=42232 Bug ID: 42232 Summary: Sort version list by version number Product: WineHQ Apps Database Version: unspecified Hardware: x86 URL: https://appdb.winehq.org/objectManager.php?sClass=appl ication&iId=13986 OS: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: appdb-unknown Assignee: wine-bugs(a)winehq.org Reporter: cges30901(a)gmail.com Distribution: --- Versions of LINE (Powered by Naver) is not sorted correctly. Version 4.10.x.x and 4.11.x.x is not at the bottom of the list. I guess this is because '1' in 10 is less than '3'? -- 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 58483] New: Burnout Paradise has rendering issues
by WineHQ Bugzilla 23 Jul '25

23 Jul '25

http://bugs.winehq.org/show_bug.cgi?id=58483 Bug ID: 58483 Summary: Burnout Paradise has rendering issues Product: Wine Version: 10.1 Hardware: x86-64 OS: Linux Status: NEW Keywords: regression Severity: normal Priority: P2 Component: d3d Assignee: wine-bugs(a)winehq.org Reporter: andrey.goosev(a)gmail.com CC: z.figura12(a)gmail.com Regression SHA1: 96fb128efdbf8d92f6b4d63a7db0346659b08969 Distribution: --- Created attachment 78933 --> http://bugs.winehq.org/attachment.cgi?id=78933 examples Some scenes are black rendered. -- 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 52092] New: game pass
by WineHQ Bugzilla 23 Jul '25

23 Jul '25

https://bugs.winehq.org/show_bug.cgi?id=52092 Bug ID: 52092 Summary: game pass Product: Wine Version: 6.21 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: master.zion(a)gmail.com Distribution: --- Hi everyone... it seems it is not possible to install the xbox application for PC using wine. It would be useful to play Windows games from xbox game pass, and it will be very useful on Steam deck. it fails during the installation startup. ------ Unhandled Exception: 0024:fixme:ntdll:EtwEventRegister ({8e9f5090-2d75-4d03-8a81-e5afbf85daf1}, 05E202EE, 00000000, 01EA96F4) stub. Unhandled Exception: System.IO.FileNotFoundException: Could not load file or assembly 'Windows.Foundation.UniversalApiContract, Version=7.0.0.0, Culture=neutral, PublicKeyToken=null, ContentType=WindowsRunt ime' or one of its dependencies. Module not found. at XboxInstaller.App..ctor() at XboxInstaller.App.Main() ------ https://www.xbox.com/en-IN/apps/xbox-app-for-pc -- 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 25

[Bug 58415] New: Wine msiexec behaviour deviates from MS msiexec for tables missing from .msi
by WineHQ Bugzilla 22 Jul '25

22 Jul '25

http://bugs.winehq.org/show_bug.cgi?id=58415 Bug ID: 58415 Summary: Wine msiexec behaviour deviates from MS msiexec for tables missing from .msi Product: Wine Version: 10.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: msi Assignee: wine-bugs(a)winehq.org Reporter: depaoli.renzo(a)gmail.com Distribution: --- While investigating a problematic .msi file, I noticed the following: The .msi file in its InstallExecuteSequence calls functions that depend on tables in the msi. However these tables do not exit. Examples found: "LaunchConditions", but no "LaunchCondition Table" "IsolateComponents", but no "IsolatedComponent Table" "PublishComponents/UnpublishComponents", but no "PublishComponent Table" "RegisterMIMEInfo/UnregisterMIMEInfo", but no "MIME table" "RegisterTypeLibraries/UnregisterTypeLibraries", but no "TypeLib table" "RegisterComPlus/UnregisterComPlus", but no "Complus table" When MS msiexec processes the .msi, it reports "Return value 0" in these cases. However when Wine msiexec does the same, it reports "Return value 1" instead. When modifying the .msi with the Orca MSI editor adding the missing tables (left empty), then MS msiexec reports "Return value 1", and Wine msiexec does the same. So there is a mismatch between the two implementations; I would conclude that Wine msiexec is missing a check for missing tables. Whether there are problems resulting from this difference in behaviour I cannot say, but it is at least not making investigations of .msi-issues any easier. -- 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 8

[Bug 58326] New: SetupDiGetClassDevs does not enumerate USB devices
by WineHQ Bugzilla 22 Jul '25

22 Jul '25

http://bugs.winehq.org/show_bug.cgi?id=58326 Bug ID: 58326 Summary: SetupDiGetClassDevs does not enumerate USB devices Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: setupapi Assignee: wine-bugs(a)winehq.org Reporter: mail(a)3v1n0.net Distribution: --- Created attachment 78694 --> http://bugs.winehq.org/attachment.cgi?id=78694 Example device enumerator In order to enumerate the USB devices in the system, a window application is expected (https://github.com/microsoft/Windows-driver-samples/blob/main/usb/usbview/e…) to use SetupDiGetClassDevs with the `GUID_DEVINTERFACE_USB_DEVICE` GUID, however this returns nothing in WINE. Running a simpler example (attached) of the enumerator that extends to all the device types, I get in fact: ``` Device info is 0x7ffffe8d4760 Device info Date is 1 {4D36E96E-E325-11CE-BFC1-08002BE10318} Device desc name is Generic Non-PnP Monitor Device driver name is {4D36E96E-E325-11CE-BFC1-08002BE10318}\0000 Failed at 186 Device info Date is 1 {745A17A0-74D3-11D0-B6FE-00A0C90F57DA} Device desc name is Wine HID device Device driver name is {745A17A0-74D3-11D0-B6FE-00A0C90F57DA}\0003 Failed at 186 Device info Date is 1 {745A17A0-74D3-11D0-B6FE-00A0C90F57DA} Device desc name is Wine HID device Device driver name is {745A17A0-74D3-11D0-B6FE-00A0C90F57DA}\0002 Failed at 186 Device info Date is 1 {4D36E968-E325-11CE-BFC1-08002BE10318} Device desc name is Wine Adapter Device driver name is {4D36E968-E325-11CE-BFC1-08002BE10318}\0000 Failed at 186 Device info Date is 1 {4D36E97D-E325-11CE-BFC1-08002BE10318} Device desc name is Wine HID bus driver Device driver name is {4D36E97D-E325-11CE-BFC1-08002BE10318}\0000 Failed at 186 Device info Date is 1 {4D36E97D-E325-11CE-BFC1-08002BE10318} Device desc name is Wine USB bus driver Device driver name is {4D36E97D-E325-11CE-BFC1-08002BE10318}\0001 Failed at 186 Device info Date is 1 {00000000-0000-0000-0000-000000000000} Failed at 159 Device info Date is 1 {745A17A0-74D3-11D0-B6FE-00A0C90F57DA} Device desc name is Wine HID compatible device Device driver name is {745A17A0-74D3-11D0-B6FE-00A0C90F57DA}\0000 Failed at 186 Device info Date is 1 {745A17A0-74D3-11D0-B6FE-00A0C90F57DA} Device desc name is Wine HID compatible device Device driver name is {745A17A0-74D3-11D0-B6FE-00A0C90F57DA}\0001 Failed at 186 Device info Date is 0 {00000000-0000-0000-0000-000000000000} ``` While under a windows VM the same code also returns (for example): Device info Date is 1 {CA3E7AB9-B4C3-4AE6-8251-579EF933890F} Device desc name is USB Video Device Device driver name is {ca3e7ab9-b4c3-4ae6-8251-579ef933890f}\0001 As per this it's not possible to find out the device ID that it could be used via `WinUsb_Initialize(deviceHandle, &winusbHandle)` (even though this doesn't seem to work even passing an hardcoded path). -- 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

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