June 2025 - Wine-Bugs - list.winehq.org

[Bug 55218] New: Lotus Script "Print" macro crashes Lotus Approach
by WineHQ Bugzilla July 24, 2025

July 24, 2025

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 July 24, 2025

July 24, 2025

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 42232] New: Sort version list by version number
by wine-bugs＠winehq.org July 23, 2025

July 23, 2025

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 58415] New: Wine msiexec behaviour deviates from MS msiexec for tables missing from .msi
by WineHQ Bugzilla July 22, 2025

July 22, 2025

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 July 22, 2025

July 22, 2025

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

[Bug 58430] New: Clip Studio Paint 4.0 EX Crashes when trying to save or export a project
by WineHQ Bugzilla July 21, 2025

July 21, 2025

http://bugs.winehq.org/show_bug.cgi?id=58430 Bug ID: 58430 Summary: Clip Studio Paint 4.0 EX Crashes when trying to save or export a project Product: Wine Version: 10.11 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: dalister07(a)gmail.com Distribution: --- Created attachment 78852 --> http://bugs.winehq.org/attachment.cgi?id=78852 A Crash Log Created by wine after trying to save the project. After applying all the needed workarounds to launch the program, trying to save a project or export it with the file menu causes it to hard crash, completely killing the program and triggering the wine debugger. Tried to save the project, export it into 3 different formats, and use save as in the file menu, all of which yielded the same result of hard crashing. Distro is CatchyOS (Arch-based), With the wine version being from wine-git. Log is Attached. -- 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 57113] New: File open dialog doesn't show all the filtered file types
by WineHQ Bugzilla July 21, 2025

July 21, 2025

https://bugs.winehq.org/show_bug.cgi?id=57113 Bug ID: 57113 Summary: File open dialog doesn't show all the filtered file types Product: Wine Version: 9.16 Hardware: x86-64 URL: https://cef-builds.spotifycdn.com/cef_binary_127.3.5%2 Bg114ea2a%2Bchromium-127.0.6533.120_windows64_client.t ar.bz2 OS: Linux Status: NEW Keywords: download, source Severity: trivial Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: imwellcushtymelike(a)gmail.com Distribution: Ubuntu Created attachment 77003 --> https://bugs.winehq.org/attachment.cgi?id=77003 Wine 9.16 console output Under Windows 10 the file open dialog shows a list of the filtered file types. As it is such a small area its only use is to let you know that more than one file type has been filtered. Under Wine the same area only lists one file type, although the filter itself does seem to work as expected. Noticed when trying the "input types - multiple files" test in the CEF sample application. -- 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 37541] New: Request for Enhancement: first time opening a program, give the window some size
by wine-bugs＠winehq.org July 20, 2025

July 20, 2025

https://bugs.winehq.org/show_bug.cgi?id=37541 Bug ID: 37541 Summary: Request for Enhancement: first time opening a program, give the window some size Product: Wine Version: 1.7.30 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: ToddAndMargo(a)zoho.com Distribution: --- Created attachment 49957 --> https://bugs.winehq.org/attachment.cgi?id=49957 first window Hi All, Wine 1.7.30 and Smart Suite. Request for Enhancement: Currently the first time you open a window (like Word Pro), the window has horizontal length, but no vertical length, just the decoration bar. The decoration says you are in Windowed mode. If you click on the Window mode decoration, you get a full screen window. Click again and you just get the decoration bar back. This is really confusing as your thing you have click on the "roll up / roll down" in the upper left of the decoration. The tip off that you did not, is the arrow is pointing up. (That doesn't stop yo from clicking it anyway.) The cure is to drag the line at the bottom of decoration downward, then you get a windowed window back. That is unless the Role Up/Down arrow is now pointing down from your clicking on it. This is really confusing. Makes you think Wine is broken (again). Would your please consider giving the first time a windows is open some size? I have attached a picture of what the weird opening screen looks like. Many thanks, -T -- 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 10

[Bug 57044] New: Cannot open ZFS mounted directories if in root "/"
by WineHQ Bugzilla July 20, 2025

July 20, 2025

https://bugs.winehq.org/show_bug.cgi?id=57044 Bug ID: 57044 Summary: Cannot open ZFS mounted directories if in root "/" Product: Wine Version: 8.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: jklaas(a)klaashome.org Distribution: --- I was checking on the status of using Lotus WordPro and was quite happy with the progress. I did find an oddity. I have my "/home" directory mounted from a ZFS mount. When I browse for files and go to root "/", I cannot see "/home". However any subdirectories with a ZFS mount can be seen. Additionally, if I create a link to "/home" (ln -s /home /newhome/home), I can see "/newhome/home" and easily browse the files from there. I also cannot see direct links at the root level. I noticed this in WordPro, but I also found this behavior running "Program Files (x86)/Windows NT/Accessories/wordpad.exe" -- 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 40762] New: Approach 97: Error Message When Opening From Network Path
by wine-bugs＠winehq.org July 20, 2025

July 20, 2025

https://bugs.winehq.org/show_bug.cgi?id=40762 Bug ID: 40762 Summary: Approach 97: Error Message When Opening From Network Path Product: Wine Version: 1.9.11 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: crashdance(a)charter.net Distribution: Mint When opening a database (APR) file from a CIFS mapped Windows network share using a drive letter in dosdevices Approach fails to open the file. The error message is "Cannot open database "Z:\examplefile.dbf" because it is encrypted." This problem persists regardless of the compatibility mode in the Wine config. The program works correctly in a modern version of Windows and a Windows virtual machine connected to the same LAN. -- 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