wine-bugs June 2025

wine-bugs@winehq.org

1 participants
966 discussions

[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

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

21 Jul '25

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 57828] New: Approach Smart Icons do not show
by WineHQ Bugzilla 21 Jul '25

21 Jul '25

https://bugs.winehq.org/show_bug.cgi?id=57828 Bug ID: 57828 Summary: Approach Smart Icons do not show Product: Wine Version: 10.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: win32u Assignee: wine-bugs(a)winehq.org Reporter: ToddAndMargo(a)zoho.com Distribution: --- Created attachment 78036 --> https://bugs.winehq.org/attachment.cgi?id=78036 Smart Icon in Windows 10 and Wine SmartSuite-N99.8.0208.0800 Fedora 41 wine-devel-10.1-1.1.x86_64 and wine-stable-10.0.0-1.1.x86_64 winehq-stable-10.0.0-1.1.x86_64 In Approach, the View pull down, Smart Icon setting does not active. This makes Approach very difficult to use. -- 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 32

[Bug 57113] New: File open dialog doesn't show all the filtered file types
by WineHQ Bugzilla 21 Jul '25

21 Jul '25

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 50220] New: 1-2-3 installs OK but closes on run before any info entered
by WineHQ Bugzilla 20 Jul '25

20 Jul '25

https://bugs.winehq.org/show_bug.cgi?id=50220 Bug ID: 50220 Summary: 1-2-3 installs OK but closes on run before any info entered Product: Wine Version: 4.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: jlee27(a)btinternet.com Distribution: --- Created attachment 68726 --> https://bugs.winehq.org/attachment.cgi?id=68726 plain text report from Wine when 1-2-3 closes itself Smartsuite installs OK from local CD (selected 1-2-3 + Approach only). 1-2-3 opens, looks OK, then closes itself before entry of any data. backtrace output attached. Approach not tied yet. -- 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 57330] New: NtQueryVolumeInformationFile does not work on Z: drive on default configuration
by WineHQ Bugzilla 20 Jul '25

20 Jul '25

https://bugs.winehq.org/show_bug.cgi?id=57330 Bug ID: 57330 Summary: NtQueryVolumeInformationFile does not work on Z: drive on default configuration Product: Wine Version: 9.19 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: joshudson(a)gmail.com Distribution: --- Calling NtQueryVolumeInformationFile on an open handle that's opened from the Z: drive returns Invalid Function. I tried to run the test harness for my .NET File Systems DLL on Wine, and it didn't get very far. Almost nothing works because it wants the volume serial number, which on actual Windows is a cheap call. Source code line of failure: https://github.com/joshudson/Emet/blob/302fe61d0b8614e2a57930fc75cffa034ba3… What's interesting is this code *doesn't want* the volume serial number; it *wants* any unique volume identifier given a handle where all handles on the same handle get the same result. I could in theory detect wine here if I had a good way to implement the problem elsehow on Wine; say by one of the wine specific IOCTL calls. (The obvious solution is if I get back Invalid Function here; make the wine-specific call before giving up.) If you actually run the test battery https://github.com/joshudson/Emet/blob/302fe61d0b8614e2a57930fc75cffa034ba3… it should be a pretty good supplemental test battery for Wine's filesystem layer. -- 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 37541] New: Request for Enhancement: first time opening a program, give the window some size
by wine-bugs＠winehq.org 20 Jul '25

20 Jul '25

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 53878] New: Lotus SmartSuite 9.8 (Millenium Edition)'s installer creates broken shortcuts
by WineHQ Bugzilla 20 Jul '25

20 Jul '25

https://bugs.winehq.org/show_bug.cgi?id=53878 Bug ID: 53878 Summary: Lotus SmartSuite 9.8 (Millenium Edition)'s installer creates broken shortcuts Product: Wine Version: 7.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: msi Assignee: wine-bugs(a)winehq.org Reporter: Zero3K(a)teknik.io Distribution: --- Created attachment 73405 --> https://bugs.winehq.org/attachment.cgi?id=73405 Archive of a log made under ReactOS 0.4.15 which contains WINE's MSI debug output When I install it, broken shortcuts (along with shortcuts that are not made under Windows Server 2003) are being made. The broken shortcuts are missing the C:\lotus part of the path. I have tried installing it under the latest ReactOS (which uses the MSI code from WineStaging-7.3), under Wine-Stable 7.0 and under Wine-Devel 7.20. All of them encounter the issue. You can find more info about the issue at https://jira.reactos.org/browse/CORE-15204 and can download the ISO containing the setup program at https://winworldpc.com/product/lotus-smartsuite/9-8. I am also attaching an archive of the log I made under ReactOS 0.4.15 which contains the debug output of WINE's MSI component. -- 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 57044] New: Cannot open ZFS mounted directories if in root "/"
by WineHQ Bugzilla 20 Jul '25

20 Jul '25

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

← Newer
1
...
25
26
27
28
29
30
31
...
97
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 June 2025