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.
https://bugs.winehq.org/show_bug.cgi?id=53573
Bug ID: 53573
Summary: Warcraft III Reforged 1.33.0.19194 has black main menu
Product: Wine
Version: 7.15
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: kolAflash(a)kolahilft.de
Distribution: ---
Created attachment 72950
--> https://bugs.winehq.org/attachment.cgi?id=72950
STDOUT/STDERR log when warcraft-iii-reforged-1.33.0.19194 is starting an
switching to black main menu
Last night (2022-08-18) Blizzard released an update for Warcraft III Reforged
from version 1.32.x to 1.33.0.19194.
Since then the main menu of the game is just black!
But I can hear the sound of the main menu.
I attached a STDOUT/STDERR log.
Version 1.32.x of the game was running fine using wine-staging-7.14.
(didn't test any other wine version before)
Wine versions I just tried:
wine-staging-7.14
wine-staging-7.15
wine-devel-7.15
OS: Debian-11
Wine: https://dl.winehq.org/wine-builds/debian/
GPU: Radeon RX 590
Neither standard Wine D3D11 OpenGL based implementation (WineD3D) nor DXVK is
working.
Maybe slightly related:
Warcraft III: staying in menus quickly gobs all system memory
https://github.com/doitsujin/dxvk/issues/1866
--
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.
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.
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.
https://bugs.winehq.org/show_bug.cgi?id=56614
Bug ID: 56614
Summary: Videos are not player in The Signifier (GOG)
Product: Wine
Version: 9.7
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: mfplat
Assignee: wine-bugs(a)winehq.org
Reporter: titan.costa(a)gmail.com
Distribution: ---
Created attachment 76371
--> https://bugs.winehq.org/attachment.cgi?id=76371
console log
Videos are not played. Observable during menu and on the computer at the
beginning. Console output attached.
wine-9.7-100-g7641124d07a
--
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.
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.
https://bugs.winehq.org/show_bug.cgi?id=54157
Bug ID: 54157
Summary: dir command of cmd fails on Z: on Ubuntu under WSL
Product: Wine
Version: 8.0-rc1
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: mterrisse(a)free.fr
Distribution: ---
Wine 8.0 rc1, Ubuntu 22.10 under WSL (Windows SubSystem for Linux, Windows 11
22H2)
Hello,
You will probably think it is a weird idea running Wine in Ubuntu under WSL.
I tried it to avoid copying many files with my program to test it under Wine.
I noticed this:
wine64 cmd.exe
dir
This works fine on C:
But if I do
Z:
dir
I receive
Invalid function.
I tried this
WINEDEBUG=warn+file wine64 cmd.exe
Z:
dir
and there is something more explicit
0108:warn:file:get_mountmgr_fs_info failed to retrieve filesystem type from
mountmgr, status 0xc000000e
Invalid function.
Do you know what is wrong?
Regards,
Michel Terrisse
--
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.
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.
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.
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.