http://bugs.winehq.org/show_bug.cgi?id=34045
Bug #: 34045
Summary: Gray Matter demo needs .NET Framework and DirectX for
launching
Product: Wine
Version: 1.6-rc5
Platform: x86
URL: http://www.fileplanet.com/217641/210000/fileinfo/Gray-
Matter-Demo
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: andrey.goosev(a)gmail.com
CC: andrey.goosev(a)gmail.com
Classification: Unclassified
Created attachment 45246
--> http://bugs.winehq.org/attachment.cgi?id=45246
config-log
Demo installs .NET Framework. No version showing. At the end of installation
has failed with that. I did installation manually from winetricks ver. 2.0 and
run config.exe
(see config log and pic)
I can't change the settings because of text in drop-down menus is missing.
Installation of Directx is solving this only partially.
--
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.
https://bugs.winehq.org/show_bug.cgi?id=50793
Bug ID: 50793
Summary: Regression: Far Cry crashes on launch
Product: Wine
Version: 6.3
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: alasky(a)codeweavers.com
Distribution: ---
Far Cry (running through Steam, steam app id:13520) crashes on launch with the
latest wine master (9107f591d3d73a3b4040db2e13ef51d9846591c9 from 20210309). I
ran a git bisect which blamed the following commit:
e341d1f695311725752c287057f6c6ab60fdf2a3
ntdll: Restore all non-volatile i386 registers in syscall dispatcher
I reverted the commit on the latest wine tip (which was messy and I had to
resolve a conflict, so treat with mild suspicion), and confirmed that the Far
Cry crash on launch was fixed with the commit reverted.
Attached is a +tid,+seh log of the crash on the latest wine master.
--
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=50506
Bug ID: 50506
Summary: Do not receive WM_INPUT messages for game controllers
registered with RegisterRawInputDevices
Product: Wine
Version: 6.0
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: blocker
Priority: P2
Component: user32
Assignee: wine-bugs(a)winehq.org
Reporter: lunarlambda(a)gmail.com
Distribution: ---
I am using RegisterRawInputDevices with HID_USAGE_PAGE_GENERIC,
HID_USAGE_GENERIC_JOYSTICK, and HID_USAGE_GENERIC_GAMEPAD.
My controller (Nintendo Switch Pro Controller) shows up in joy.cpl, and input
works.
The controller shows up in GetRawInputDeviceList, I can query it with
GetRawInputDeviceInfo, and opening it and getting the product name via
HidD_GetProductString also works.
However, my window simply never receives any WM_INPUT messages.
If I register a keyboard instead (HID_USAGE_GENERIC_KEYBOARD), using the same
code, I do get WM_INPUT messages.
I was hopeful that this had been fixed in 6.0, but I was looking through
dlls/user32/rawinput.c, but I cannot find anything indicative of a lack of
support.
--
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=33421
Bug #: 33421
Summary: Cypress PSoCCreator Installer fails with "You have
insufficient privileges to run CyInstaller..."
Product: Wine
Version: unspecified
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: terry(a)maximatcher.com
Classification: Unclassified
wine-1.5.28-114-g60faef8
PSoCCreatorSetup_2.2_cp5.exe
wine runs the extractor, starts the PSoCCreator InstallShield Wizard, then
throws the error window with "You have insufficient privileges to run
CyInstaller. Please contact you(sic) administrator. CyInstaller will now exit"
--
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.
https://bugs.winehq.org/show_bug.cgi?id=49457
Bug ID: 49457
Summary: Simple command in powershell 6 (pwsh) containing "$"
only works for me if the dollar sign is escaped
Product: Wine
Version: 5.11
Hardware: x86
URL: https://github.com/PowerShell/PowerShell/releases/down
load/v6.1.6/PowerShell-6.1.6-win-x64.msi
OS: Linux
Status: NEW
Keywords: download
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: xerox.xerox2000x(a)gmail.com
Distribution: ---
I tried simple command like
wine pwsh.exe /c $env:username
and it gives ":username"
If one escapes the dollarsign it works correctly:
wine pwsh.exe /c \$env:username
gives "louis"
When you first start powershell console like "wine start pwsh", and type in the
console it works correctly (without the escape character)
I tried 1st command in Windows 7 cmd, and it works correctly (so without having
to add the escape character)
(The same story above holds for powershell 2.0 in wine too, but that is more
troublesome to get installed due to few bugs in bugilla, so i files it here for
pwsh.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.
https://bugs.winehq.org/show_bug.cgi?id=48256
Bug ID: 48256
Summary: pwsh.exe (powershell) crashes after 20~50 sec:
System.EntryPointNotFoundException: Unable to find an
entry point named 'FreeAddrInfoEx' in DLL
'ws2_32.dll'.
Product: Wine
Version: 4.21
Hardware: x86
URL: https://github.com/PowerShell/PowerShell/releases/down
load/v6.1.6/PowerShell-6.1.6-win-x64.zip
OS: Linux
Status: NEW
Keywords: download
Severity: normal
Priority: P2
Component: winsock
Assignee: wine-bugs(a)winehq.org
Reporter: xerox.xerox2000x(a)gmail.com
Distribution: Debian
See below. Just start pswh.exe and wait a while (or type anything)
I don`t know if FreeAddrInfoEx is exactly same as FreeAddrInfoExW so if it can
just be forwarded, so if anyone who knows more about winsock could fix this bug
that would be nice (note: FreeAddrInfoEx entry is present in win7 ws2_32)
Error in console:
An error has occurred that was not properly handled. Additional information is
shown below. The PowerShell process will exit.
Unhandled Exception: System.EntryPointNotFoundException: Unable to find an
entry point named 'FreeAddrInfoEx' in DLL 'ws2_32.dll'.
at Interop.Winsock.FreeAddrInfoEx(AddressInfoEx* pAddrInfo)
at
System.Net.NameResolutionPal.GetAddrInfoExContext.FreeContext(GetAddrInfoExContext*
context)
at System.Net.NameResolutionPal.ProcessResult(SocketError errorCode,
GetAddrInfoExContext* context)
at System.Net.NameResolutionPal.GetAddressInfoExCallback(Int32 error, Int32
bytes, NativeOverlapped* overlapped)
003c:fixme:advapi:RegisterEventSourceW ((null),L".NET Runtime"): stub
003c:fixme:advapi:ReportEventW
(0xcafe4242,0x0001,0x0000,0x00000402,(nil),0x0001,0x00000000,0x1ba0d600,(nil)):
stub
003c:err:eventlog:ReportEventW L"Application: pwsh.exe\nCoreCLR Version:
4.6.28008.1\nDescription: The process was terminated due to an unhandled
exception.\nException Info: System.EntryPointNotFoundException: Unable to find
an entry point named 'FreeAddrInfoEx' in DLL 'ws2_32.dll'.\r\n at
Interop.Winsock.FreeAddrInfoE"...
--
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=49351
Bug ID: 49351
Summary: PowerShell-7.0.1-win-x64.msi fails to install
Product: Wine
Version: 5.10
Hardware: x86
URL: https://github.com/PowerShell/PowerShell/releases/down
load/v7.0.1/PowerShell-7.0.1-win-x64.msi
OS: Linux
Status: NEW
Keywords: download
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: xerox.xerox2000x(a)gmail.com
Distribution: Debian
Created attachment 67388
--> https://bugs.winehq.org/attachment.cgi?id=67388
patch
>From the forum https://forum.winehq.org/viewtopic.php?f=2&t=33963
It pops up messagebox
"PowerShell requires the Windows Management Framework 4.0 or newer to be
installed to enable remoting over WinRM."
It checks for version of pwrshlplugin.dll; one could copy some wine system-dll
with high enough version resource to pwrshlplugin.dll, like i said in forum,
but as this dll is present on my win7, I guess we should just add it to wine.
Attached patch , will send to wine-devel.
Note: Check seems to come from
(https://github.com/PowerShell/PowerShell/blob/master/assets/Product.wxs)
<!-- Prerequisite check for Windows Management Framework -->
<Property Id="PWRSHPLUGIN_VERSION" Secure="yes">
<DirectorySearchRef Id="System32" Parent="WindowsDirectory"
Path="System32">
<FileSearch Id="pwrshplugin" Name="pwrshplugin.dll"
MinVersion="6.3.9600.16383"/>
</DirectorySearchRef>
</Property>
--
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=50026
Bug ID: 50026
Summary: Powershell Core errors (in win10 mode) with:
Attempting to perform the Start operation on the
'FileSystem' provider failed. Unable to find an entry
point named
'RtlQueryProcessPlaceholderCompatibilityMode' in DLL
'ntd ll.dll'.
Product: Wine
Version: 5.19
Hardware: x86-64
URL: https://github.com/PowerShell/PowerShell/releases/down
load/v7.0.3/PowerShell-7.0.3-win-x64.msi
OS: Linux
Status: NEW
Keywords: download, patch
Severity: normal
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: xerox.xerox2000x(a)gmail.com
Regression SHA1: download
Distribution: Debian
Created attachment 68458
--> https://bugs.winehq.org/attachment.cgi?id=68458
patch with stub
This happens on every command if win10 version is set, i.e.
wine pwsh.exe -c Write-Host "Hello"
Attempting to perform the Start operation on the 'FileSystem' provider failed.
Unable to find an entry point named
'RtlQueryProcessPlaceholderCompatibilityMode' in DLL 'ntdll.dll'.
Though it continues happily further and the command(s) work, this actually
prevents Waves Central from starting in win10 mode
I`ll send attached patch (that fixes this) later.
Relevant code from Powershell Core:
#if !UNIX
// The placeholder mode management APIs
Rtl(Set|Query)(Process|Thread)PlaceholderCompatibilityMode
// are only supported starting with Windows 10 version 1803 (build
17134)
Version minBuildForPlaceHolderAPIs = new Version(10, 0, 17134, 0);
if (Environment.OSVersion.Version >= minBuildForPlaceHolderAPIs)
{
// let's be safe, don't change the PlaceHolderCompatibilityMode
if the current one is not what we expect
if (NativeMethods.PHCM_DISGUISE_PLACEHOLDER ==
NativeMethods.RtlQueryProcessPlaceholderCompatibilityMode())
{
NativeMethods.RtlSetProcessPlaceholderCompatibilityMode(NativeMethods.PHCM_EXPOSE_PLACEHOLDERS);
}
}
#endif
--
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.