https://bugs.winehq.org/show_bug.cgi?id=52284
Bug ID: 52284
Summary: Factory I/O SPS-Software hangs
Product: Wine
Version: 7.0-rc2
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: maiktapwagner(a)aol.com
Distribution: ---
Hello everyone,
I got a request from the ubuntuusers.de forum that one user had problems
running this program and submitted an AppDB entry at
https://appdb.winehq.org/objectManager.php?sClass=version&iId=40486
providing tests for 7.0rc1 and 7.0rc2 (queued) where as the console is spammed
with
018c:fixme:d3d:wined3d_device_context_resolve_sub_resource Multisample resolve
is not fully supported for typeless formats (dst_format
WINED3DFMT_R8G8B8A8_TYPELESS, src_format WINED3DFMT_R8G8B8A8_TYPELESS, format
WINED3DFMT_R8G8B8A8_UNORM).
Steps to reproduce after installation:
New → File → Drivers → Control I/O (opens up a grey window but nothing happens)
--
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=57588
Bug ID: 57588
Summary: Guardant USB key drivers: grdkey.sys crashes
Product: Wine
Version: 10.0-rc3
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: ntoskrnl
Assignee: wine-bugs(a)winehq.org
Reporter: amorozov(a)etersoft.ru
Distribution: ---
Created attachment 77697
--> https://bugs.winehq.org/attachment.cgi?id=77697
Log with WINEDEBUG=+ntoskrnl,+plugplay and winedbg output
I installed Guardant USB key drivers 7.0.224 from here:
https://www.guardant.com/support/users/download/2238/
with WoW64 Wine build.
$ md5sum GrdDrivers.exe
731d388d2ee4c1a4f45d655e4b8c9163 GrdDrivers.exe
After installation windows/system32/drivers/grdkey.sys appears. And it crashes
at Wine start:
wine: Unhandled page fault on read access to 0000000000000008 at address
00006FFFFC8A295B (thread 00f0), starting debugger...
In AddDevice handler grdkey.sys calls IoOpenDeviceRegistryKey. This results in
calling get_device_instance_id -> get_device_id and sending
IRP_MJ_PNP/IRP_MN_QUERY_ID with BusQueryDeviceID to the driver which calls
IofCallDriver(NULL, ....) and crashes.
The crash can be avoided with commenting out this line:
device = IoGetAttachedDevice( device );
in get_device_id function in dlls/ntoskrnl.exe/pnp.c
But I assume that the correct fix should be in avoiding to send IRPs from
IoOpenDeviceRegistryKey. MSDN says that IRP_MN_QUERY_ID is sent before loading
driver and calling AddDevice:
https://learn.microsoft.com/en-us/windows-hardware/drivers/kernel/adding-a-…
--
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=58145
Bug ID: 58145
Summary: Out of Ctrl 1.2: game doesn't launch, gives error
Product: Wine
Version: 10.6
Hardware: x86-64
OS: MacOS
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: cemer99797(a)isorax.com
Created attachment 78425
--> http://bugs.winehq.org/attachment.cgi?id=78425
Wine-devel 10.6 terminal log
The game Out of Ctrl 1.2 doesn't launch and gives the following error in a
pop-up window on launch:
Error
Failed to initialize player
Details:
Failed to initialize graphics.
Make sure you have DirectX 11 installed, have up to date
drivers for your graphics card and have not disabled
3D acceleration in display settings.
InitializeEngineGraphics failed
tested using Gcenx's wine-devel 10.6 build
(https://github.com/Gcenx/macOS_Wine_builds/releases/tag/10.6) with GStreamer
1.26.0
download link (20 MB) (choose "OutOfCtrl_v1_2_EXE.zip"):
https://miknugget.itch.io/out-of-ctrl
shas256: 5d26c746c4e85b98af2f1f9fb4a4daeed837deb49427bf108935545f8958dba9
I'm using macOS 11
--
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=56681
Bug ID: 56681
Summary: 3d games continue receiving mouse input while not
focused
Product: Wine
Version: 9.8
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winewayland
Assignee: wine-bugs(a)winehq.org
Reporter: pmargeti34(a)gmail.com
Distribution: ---
Wine wayland windows seem to get the mouse input even if the application window
is not focused. 3D game world continues to respond to mouse input as if the
game still had focus.
To reproduce:
-launch a 3d game in wayland mode (warframe in my example)
-open another application and make sure it has focus
-observe that when the mouse cursor is over the game window, game still
receives input
--
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=30853
Bug #: 30853
Summary: Wine doesn’t always handle "right alt" properly
Product: Wine
Version: 1.5.5
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winex11.drv
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: sloonz(a)gmail.com
Classification: Unclassified
Created attachment 40410
--> http://bugs.winehq.org/attachment.cgi?id=40410
workaround/quick and dirty fix
I’m trying to get World of Warcraft working under Wine. However, I have huge
trouble with key bindings (I use unusual key bindings : I use the right half of
my keyboard, whereas most players use the left half).
After investigation, I found 3 bugs (different behaviors between Wine and my
Windows installation). The first one is the management of the right "Alt" key
(labeled "Alt-Gr" on my keyboard). When I press AltGr+l under Windows with
Spy++, I get the followings events :
<03637> 0007045A P WM_KEYDOWN nVirtKey:VK_CONTROL cRepeat:1 ScanCode:1D
fExtended:0 fAltDown:0 fRepeat:0 fUp:0
<03638> 0007045A P WM_KEYDOWN nVirtKey:VK_MENU cRepeat:1 ScanCode:38
fExtended:1 fAltDown:1 fRepeat:0 fUp:0
<03639> 0007045A P WM_KEYDOWN nVirtKey:'L' cRepeat:1 ScanCode:18
fExtended:0 fAltDown:1 fRepeat:0 fUp:0
<03640> 0007045A P WM_DEADCHAR chCharCode:'002F' (47) cRepeat:1 ScanCode:18
fExtended:0 fAltDown:1 fRepeat:0 fUp:0
<03641> 0007045A P WM_KEYUP nVirtKey:'L' cRepeat:1 ScanCode:18 fExtended:0
fAltDown:1 fRepeat:1 fUp:1
<03642> 0007045A P WM_SYSKEYUP nVirtKey:VK_CONTROL cRepeat:1 ScanCode:1D
fExtended:0 fAltDown:1 fRepeat:1 fUp:1
<03643> 0007045A P WM_KEYUP nVirtKey:VK_MENU cRepeat:1 ScanCode:38
fExtended:1 fAltDown:0 fRepeat:1 fUp:1
Under Wine 1.5.5 however (WINEDEBUG=+msg), I get those :
trace:msg:peek_message got type 7 msg 100 (WM_KEYDOWN) hwnd 0x6007e wp eb
lp 760001 [note: wp = VK_OEM_PA2]
trace:msg:peek_message got type 7 msg 101 (WM_KEYUP) hwnd 0x6007e wp 4c lp
c0260001 [note: wp = 'L']
trace:msg:peek_message got type 7 msg 101 (WM_KEYUP) hwnd 0x6007e wp eb lp
c0760001 [note: wp = VK_OEM_PA2]
With xev, I get :
KeyPress event, serial 93, synthetic NO, window 0x4000001,
root 0xbc, subw 0x0, time 5086996, (1585,410), root:(2578,425),
state 0x0, keycode 108 (keysym 0xfe03, ISO_Level3_Shift), same_screen
YES,
XKeysymToKeycode returns keycode: 92
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False
KeyRelease event, serial 93, synthetic NO, window 0x4000001,
root 0xbc, subw 0x0, time 5087052, (1585,410), root:(2578,425),
state 0x80, keycode 108 (keysym 0xfe03, ISO_Level3_Shift), same_screen
YES,
XKeysymToKeycode returns keycode: 92
XLookupString gives 0 bytes:
XFilterEvent returns: False
After "setxkbmap us", AltGr is bound to Alt_R under X (checked with xev), and I
get this under Wine :
trace:msg:peek_message got type 7 msg 104 (WM_SYSKEYDOWN) hwnd 0x10046 wp
a5 lp 21380001 [wp = VK_RMENU]
trace:msg:peek_message got type 7 msg 104 (WM_SYSKEYDOWN) hwnd 0x10046 wp
4c lp 20260001 [wp = 'L']
trace:msg:peek_message got type 6 msg 106 (WM_SYSCHAR) hwnd 0x10046 wp 6c
lp 20260001 [wp = 'l']
trace:msg:peek_message got type 7 msg 105 (WM_SYSKEYUP) hwnd 0x10046 wp 4c
lp e0260001 [wp = 'L']
trace:msg:peek_message got type 7 msg 101 (WM_KEYUP) hwnd 0x10046 wp a5 lp
c1380001 [wp = VK_RMENU]
(yes, I have a KEYUP without KEYDOWN)
Wich is still not the same as Windows. So I think there is two problems here :
- ISO_Level3_Shift is not properly recognized by Wine
- "AltGr" doesn't have the same behavior under Wine and Windows
FYI, attached patch is a workaround to have the same behavior than Windows.
With it, I get this under Wine :
trace:msg:peek_message got type 7 msg 100 (WM_KEYDOWN) hwnd 0x10062 wp a2
lp 1d0001 [note: wp = VK_LCONTROL]
trace:msg:peek_message got type 7 msg 100 (WM_KEYDOWN) hwnd 0x10062 wp a4
lp 20380001 [note: wp = VK_LMENU]
trace:msg:peek_message got type 7 msg 100 (WM_KEYDOWN) hwnd 0x10062 wp 4c
lp 20260001 [note: wp = 'L']
trace:msg:peek_message got type 7 msg 101 (WM_KEYUP) hwnd 0x10062 wp 4c lp
e0260001
trace:msg:peek_message got type 7 msg 105 (WM_SYSKEYUP) hwnd 0x10062 wp a2
lp e01d0001
trace:msg:peek_message got type 7 msg 101 (WM_KEYUP) hwnd 0x10062 wp a4 lp
c0380001
Which is still not the same as Windows :
- Windows uses (right) control + menu (with fExtended flag for menu) whereas
Wine uses left control + left menu. Not investigated if this is related to
TranslateMessage.
- AltGr+L is a dead symbol on my keymap. Windows send a DEADCHAR message,
wheras Wine send nothing. Note that I had to disable the XFilterEvent test in
event.c to have those messages, otherwise nothing is sent to the program (but
that’s another story for another bug report)
But it suffice for my use case (WoW key bindings with right alt)
--
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=57925
Bug ID: 57925
Summary: winewayland.drv: Games are not filled to my monitor's
resolution
Product: Wine
Version: 10.2
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winewayland
Assignee: wine-bugs(a)winehq.org
Reporter: daniel.penalized(a)proton.me
Distribution: ArchLinux
Created attachment 78178
--> https://bugs.winehq.org/attachment.cgi?id=78178
SWAT 4 output log (in this log I opened the settings and tried to set the
maximum resolution that the game supports)
Old games (specifically Ghost Recon, Splinter Cell 1, Splinter Cell 2 and SWAT
4) won't fill to my monitor's resolution, even if I switch to a higher
resolution in the game settings.
This MR (https://gitlab.winehq.org/wine/wine/-/merge_requests/6804) was
supposed to work with winewayland.drv and fix this issue, but it doesn't work
or fix it. However, this MR
(https://gitlab.winehq.org/wine/wine/-/merge_requests/5057) does work and fixes
that issue.
There is a workaround (at least for SWAT 4): which is to take the game window
out of fullscreen, then toggle the maximization state of the game window and
put the game window back into fullscreen (In labwc/openbox terms:
ToggleFullscreen > ToggleMaximize > ToggleFullscreen). I think it also works
for Ghost Recon.
Splinter Cell 1 even supports 16:9 resolutions, but only in game (in the menus,
loadings and cut-scenes are still not filled in for my monitor's resolution)
and Splinter Cell 2 is worse, there's no support for 16:9 resolutions or even a
workaround.
- I use labwc/wlroots as WM.
- I'm using the new WoW64 mode. I did some tests with normal wine, but it's
been a few weeks or months, so I'm not sure if the new WoW64 mode has any
impact here, but I don't think so.
(Sorry if the paraphrases seem disconnected from each other, if I'm not very
clear or if I'm giving too little information. I've been doing a lot of testing
over the last few hours and my mind isn't in a good place to come up with a
good text here :/)
--
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=57584
Bug ID: 57584
Summary: 8-bit color mode is broken in Wine 9.11 and later
Product: Wine
Version: 9.11
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: winex11.drv
Assignee: wine-bugs(a)winehq.org
Reporter: alexhenrie24(a)gmail.com
Distribution: ---
Created attachment 77694
--> https://bugs.winehq.org/attachment.cgi?id=77694
Regedit on Wine 9.22 in Xephyr
Similar to Bug 48088, palette colors are being mapped incorrectly again. Steps
to reproduce:
1. In one terminal, run `Xephyr :2 -ac -screen 800x600x8`
2. In a second terminal, run `DISPLAY=:2 openbox`
3. In a third terminal, run `DISPLAY=:2 wine regedit`
`git bisect` says:
commit 6ace92e0cafcc381f324fc831f3006fb15db4b4e (HEAD)
Author: Rémi Bernon <rbernon(a)codeweavers.com>
AuthorDate: Mon Jun 3 17:48:30 2024 +0200
Commit: Alexandre Julliard <julliard(a)winehq.org>
CommitDate: Mon Jun 3 23:24:59 2024 +0200
winex11: Create a HBITMAP for the allocated surface pixels.
dlls/winex11.drv/bitblt.c | 77
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++-------------------
1 file changed, 58 insertions(+), 19 deletions(-)
--
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=51546
Bug ID: 51546
Summary: ran a application and it gave an error
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: mrtbryanonlinux(a)gmail.com
Distribution: ---
Created attachment 70389
--> https://bugs.winehq.org/attachment.cgi?id=70389
Im trying to run Xenos64.exe for gta v and then that happened plz help
tried to run a application called xenos64.exe i use it for gta v so i wined it
then that happened. plz try and fix ASAP
--
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=44901
Bug ID: 44901
Summary: DS4Windows crashes DS4 Driver
Product: Wine
Version: 3.5
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: romulasry(a)gmail.com
Distribution: ---
Created attachment 60984
--> https://bugs.winehq.org/attachment.cgi?id=60984
backtrace
Crashes on the latest Version 1.4.52 of the 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=45063
Bug ID: 45063
Summary: win64 / 64-bit .NET 4.0 - c0000005 from
ntdll:RtlGetDaclSecurityDescriptor
Product: Wine
Version: 3.6
Hardware: x86-64
OS: Mac OS X
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: pembertona(a)gmail.com
After fighting for some to get .NET 4.0 running on 64 bit (great progress here
after overcoming multiple msi/msiexec/installer issues), I've hit an access
violation exception running a very basic 'hello world' 64-bit console app. This
is on `portable-winehq-staging-3.6-osx64` - but almost certainly the devel and
stable branches as well.
136984.882:0008:0041:Call
advapi32.ConvertStringSecurityDescriptorToSecurityDescriptorW(19e1f7f8
L"D:P(A;;GRGW;;;BA)(A;;GRGW;;;S-1-5-21-0-0-0-1000)",00000001,19e1f780,19e1f7c8)
ret=6447f2c4d3e
136984.884:0008:0041:trace:advapi:ConvertStringSecurityDescriptorToSecurityDescriptorW
L"D:P(A;;GRGW;;;BA)(A;;GRGW;;;S-1-5-21-0-0-0-1000)", 1, 0x19e1f780, 0x19e1f7c8
136984.884:0008:0041:trace:heap:RtlAllocateHeap (0x10000,70000062,00000062):
returning 0xf60b0
136984.885:0008:0041:trace:advapi:ParseStringAclToAcl
L"P(A;;GRGW;;;BA)(A;;GRGW;;;S-1-5-21-0-0-0-1000)"
136984.885:0008:0041:trace:advapi:ParseStringSidToSid
L"BA)(A;;GRGW;;;S-1-5-21-0-0-0-1000)", 0x0, 0x19e1f514
136984.885:0008:0041:trace:advapi:ParseStringSidToSid only size requested,
returning TRUE with 16
136984.885:0008:0041:trace:advapi:ParseStringSidToSid L"S-1-5-21-0-0-0-1000)",
0x0, 0x19e1f514
136984.885:0008:0041:trace:advapi:ParseStringSidToSid only size requested,
returning TRUE with 28
136984.885:0008:0041:trace:heap:RtlFreeHeap (0x10000,70000062,0xf60b0):
returning TRUE
136984.886:0008:0041:trace:heap:RtlAllocateHeap (0x10000,7000006a,00000058):
returning 0x46340
136984.886:0008:0041:trace:heap:LocalAlloc (flags=0040) returning 0x46340
136984.886:0008:0041:trace:heap:RtlAllocateHeap (0x10000,70000062,00000062):
returning 0x46420
136984.886:0008:0041:trace:advapi:ParseStringAclToAcl
L"P(A;;GRGW;;;BA)(A;;GRGW;;;S-1-5-21-0-0-0-1000)"
136984.886:0008:0041:trace:advapi:ParseStringSidToSid
L"BA)(A;;GRGW;;;S-1-5-21-0-0-0-1000)", 0x46364, 0x19e1f514
136984.886:0008:0041:trace:advapi:ParseStringSidToSid returning TRUE
136984.886:0008:0041:trace:advapi:ParseStringSidToSid L"S-1-5-21-0-0-0-1000)",
0x4637c, 0x19e1f514
136984.886:0008:0041:trace:advapi:ParseStringSidToSid returning TRUE
136984.887:0008:0041:trace:heap:RtlFreeHeap (0x10000,70000062,0x46420):
returning TRUE
136984.887:0008:0041:trace:advapi:ConvertStringSecurityDescriptorToSecurityDescriptorW
ret=1
136984.887:0008:0041:Ret
advapi32.ConvertStringSecurityDescriptorToSecurityDescriptorW() retval=00000001
ret=6447f2c4d3e
136984.887:0008:0041:Call ntdll.RtlFreeHeap(00010000,00000000,000f5f30)
ret=6447f2c4dc8
136984.887:0008:0041:trace:heap:RtlFreeHeap (0x10000,70000062,0xf5f30):
returning TRUE
136984.887:0008:0041:Ret ntdll.RtlFreeHeap() retval=00000001 ret=6447f2c4dc8
136984.887:0008:0041:trace:ntdll:RtlGetSaclSecurityDescriptor
(0x46340,0x19e1f716,0x19e1f718,0x19e1f715)
136984.887:0008:0041:trace:ntdll:RtlGetDaclSecurityDescriptor
(0x46340,0x19e1f717,0x19e1f720,0x19e1f715)
136984.887:0008:0041:trace:heap:RtlAllocateHeap (0x10000,7000006a,0000009c):
returning 0x46570
136984.888:0008:0041:trace:heap:RtlFreeHeap (0x10000,70000062,0x46570):
returning TRUE
136984.888:0008:0041:trace:seh:NtRaiseException code=c0000005 flags=0
addr=0x6447f1d6f19 ip=6447f1d6f19 tid=0041
136984.888:0008:0041:trace:seh:NtRaiseException info[0]=0000000000000000
136984.888:0008:0041:trace:seh:NtRaiseException info[1]=0000000000000010
136984.888:0008:0041:trace:seh:NtRaiseException rax=0000000000000000
rbx=000006447f27fd30 rcx=0000000019e1fce0 rdx=0000000019e21ad0
136984.888:0008:0041:trace:seh:NtRaiseException rsi=0000000019e1fce0
rdi=0000000000000000 rbp=0000000019e1fe00 rsp=0000000019e1fc20
136984.888:0008:0041:trace:seh:NtRaiseException r8=0000000019e1f298
r9=0000000000000010 r10=0000000019e21b25 r11=ffffffffffffffa9
136984.888:0008:0041:trace:seh:NtRaiseException r12=0000000000000000
r13=0000000000000000 r14=0000000000044860 r15=0000000000000000
136984.888:0008:0041:trace:seh:call_vectored_handlers calling handler at
0x6447f30a954 code=c0000005 flags=0
...
136984.967:0008:0041:err:eventlog:ReportEventW L"Application:
Console64.exe\nFramework Version: v4.0.30319\nDescription: The process was
terminated due to an internal error in the .NET Runtime at IP 000006447F1D6F19
(000006447F100000) with exit code 80131506.\n"
Possibly related to https://bugs.winehq.org/show_bug.cgi?id=27680?
--
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.