https://bugs.winehq.org/show_bug.cgi?id=45432
Bug ID: 45432
Summary: Implement Windows Native Firewall Rules for Lightwave
Software Licensing - netfw_rules
Product: Wine
Version: 3.11
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: blocker
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: newel.anderson(a)gmail.com
Distribution: ---
Created attachment 61753
--> https://bugs.winehq.org/attachment.cgi?id=61753
Terminal logs installing and launching Lightwave under WIne 3.11 in Linux
Lightwave requires Windows Native Firewall Inbound/Outbound Rules in order to
register/activate one's license.
For reference, please see:
https://forum.winehq.org/viewtopic.php?f=8&t=30847&p=116945#p116945 (I'm
wineink)
Towards the end of the above thread I posted terminal output as well as
screenshots. Disabling Windows Firewall, as well as deleting the
inbound/outbound rules in Windows, deactivates my license. Re-enabling the
rules and Windows Firewall reactivates my license. Since this functionality
doesn't exist in Wine, Wine hasn't to my knowledge implemented Windows Native
Firewall Rules, it's impossible to register/activate my legally purchased
license in Wine.
Thank you for your time and consideration.
***Please note, the above applies only to a FULL license of Lightwave. The
trial, which is node-locked, works as designed. Unfortunately, the FULL license
is not node-locked.
--
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=33621
Bug #: 33621
Summary: [UWIN] ksh93 from UWIN generates a lot of fixme
warnings
Product: Wine
Version: 1.5.30
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: simon.toedt(a)gmail.com
Classification: Unclassified
Running ksh93 (Korn Shell 93) from the UWIN (Unix emulation on Windows) toolkit
generates a lot of "fixme" warnings and the shell is generally not useable.
The goal is to use WINE for automated testing without having to fire up a full
blown Windows system each time in VMware or real iron.
Steps to test:
1. Install UWIN:
> wget --http-user="I accept www.opensource.org/licenses/eclipse"
--http-passwd="."
'http://www2.research.att.com/~gsf/download/beta/uwin-base.2013-02-08.win32.…'
> wine uwin-base.2013-02-08.win32.i386.exe
2. Run Windows/UWIN version of ksh93:
wine64 'C:\Program Files/UWIN/usr/bin/ksh.exe'
fixme:process:SetProcessShutdownParameters (00000300, 00000001): partial stub.
fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented
fixme:ntdll:NtSetInformationToken unimplemented class 4
fixme:process:SetProcessShutdownParameters (00000300, 00000001): partial stub.
fixme:ntdll:NtSetInformationToken unimplemented class 4
fixme:ntdll:NtSetInformationToken unimplemented class 4
fixme:process:SetProcessShutdownParameters (00000000, 00000001): partial stub.
fixme:ntdll:NtSetInformationToken unimplemented class 4
fixme:ntdll:NtSetInformationToken unimplemented class 4
fixme:advapi:LsaOpenPolicy ((null),0x23f980,0x00000001,0x23f950) stub
fixme:advapi:LsaClose (0xcafe) stub
fixme:netbios:NetServerEnum Stub ((null) 100 0x23f440 -1 0x23fbb8 0x23fbc8 24
(null) (nil))
fixme:netapi32:NetGetDCName ((null), (null), 0x23f448) stub!
fixme:dbghelp_dwarf:dwarf2_parse_subprogram Unhandled Tag type 0x26 at
ctx(0x8834c0,L"libc.so.6"), for debug_info(abbrev:0xf70850,symt:0xfce150)
fixme:dbghelp_dwarf:compute_location Only supporting one breg (r10/338 ->
r8/336)
fixme:dbghelp_dwarf:compute_location Only supporting one breg (r10/338 ->
r8/336)
fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented
fixme:dbghelp_dwarf:dwarf2_parse_subprogram Unhandled Tag type 0x26 at
ctx(0x8834c0,L"libc.so.6"), for debug_info(abbrev:0x20e2370,symt:0x2140480)
fixme:dbghelp_dwarf:dwarf2_parse_subprogram_block Unhandled Tag type 0xf at
ctx(0x8834c0,L"libc.so.6"), for debug_info(abbrev:0x21926b8,symt:(nil))
fixme:dbghelp_dwarf:dwarf2_parse_subprogram_block Unhandled Tag type 0xf at
ctx(0x8834c0,L"libc.so.6"), for debug_info(abbrev:0x21926b8,symt:(nil))
fixme:dbghelp_dwarf:dwarf2_parse_subprogram_block Unhandled Tag type 0xf at
ctx(0x8834c0,L"libc.so.6"), for debug_info(abbrev:0x21926b8,symt:(nil))
fixme:dbghelp_dwarf:dwarf2_parse_subprogram_block Unhandled Tag type 0xf at
ctx(0x8834c0,L"libc.so.6"), for debug_info(abbrev:0x21926b8,symt:(nil))
fixme:dbghelp_dwarf:dwarf2_parse_subprogram Unhandled Tag type 0x26 at
ctx(0x8834c0,L"ld-linux-x86-64.so.2"), for
debug_info(abbrev:0x2914e98,symt:0x2970264)
fixme:dbghelp_dwarf:dwarf2_parse_subprogram_block Unhandled Tag type 0x26 at
ctx(0x8834c0,L"ld-linux-x86-64.so.2"), for
debug_info(abbrev:0x2943cb0,symt:(nil))
fixme:dbghelp_dwarf:dwarf2_parse_subprogram_block Unhandled Tag type 0x26 at
ctx(0x8834c0,L"ld-linux-x86-64.so.2"), for
debug_info(abbrev:0x2914e90,symt:(nil))
fixme:dbghelp_dwarf:compute_location Only supporting one breg (rdx/331 ->
rax/328)
fixme:dbghelp_dwarf:compute_location Only supporting one breg (rdx/331 ->
rax/328)
fixme:dbghelp_dwarf:compute_location Only supporting one breg (rdx/331 ->
rax/328)
fixme:dbghelp_dwarf:compute_location Only supporting one breg (rdx/331 ->
rax/328)
fixme:dbghelp_dwarf:compute_location Only supporting one breg (rdx/331 ->
rax/328)
fixme:dbghelp_dwarf:dwarf2_parse_subprogram Unhandled Tag type 0x26 at
ctx(0x8834c0,L"libgcc_s.so.1"), for debug_info(abbrev:0x36b3448,symt:0x378fa1c)
fixme:dbghelp_dwarf:dwarf2_parse_subprogram Unhandled Tag type 0x26 at
ctx(0x8834c0,L"libgcc_s.so.1"), for debug_info(abbrev:0x3743718,symt:0x37781b4)
fixme:dbghelp_dwarf:dwarf2_parse_subprogram_block Unhandled Tag type 0x26 at
ctx(0x8834c0,L"libgcc_s.so.1"), for debug_info(abbrev:0x3743658,symt:(nil))
fixme:dbghelp_dwarf:dwarf2_parse_subprogram Unhandled Tag type 0x26 at
ctx(0x8834c0,L"libgcc_s.so.1"), for debug_info(abbrev:0x37425a0,symt:0x3754e38)
fixme:dbghelp_dwarf:dwarf2_parse_subprogram_block Unhandled Tag type 0x15 at
ctx(0x8834c0,L"kernel32<elf>"), for debug_info(abbrev:0x3824860,symt:(nil))
fixme:dbghelp_dwarf:dwarf2_parse_subprogram_block Unhandled Tag type 0xf at
ctx(0x8834c0,L"kernel32<elf>"), for debug_info(abbrev:0x3824860,symt:(nil))
fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented
fixme:netapi32:NetUserGetInfo Level 3 is not implemented
fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented
fixme:netapi32:NetUserGetInfo Level 3 is not implemented
fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented
fixme:netapi32:NetUserGetInfo Level 3 is not implemented
fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented
fixme:netapi32:NetUserGetInfo Level 3 is not implemented
fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented
fixme:netapi32:NetUserGetInfo Level 3 is not implemented
fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented
fixme:netapi32:NetUserGetInfo Level 3 is not implemented
fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented
fixme:netapi32:NetUserGetInfo Level 3 is not implemented
fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented
fixme:netapi32:NetUserGetInfo Level 3 is not implemented
fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented
fixme:netapi32:NetUserGetInfo Level 3 is not implemented
fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented
fixme:netapi32:NetUserGetInfo Level 3 is not implemented
fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented
fixme:netapi32:NetUserGetInfo Level 3 is not implemented
fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented
fixme:netapi32:NetUserGetInfo Level 3 is not implemented
fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented
fixme:netapi32:NetUserGetInfo Level 3 is not implemented
fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented
fixme:netapi32:NetUserGetInfo Level 3 is not implemented
fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented
fixme:netapi32:NetUserGetInfo Level 3 is not implemented
fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented
fixme:netapi32:NetUserGetInfo Level 3 is not implemented
fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented
fixme:netapi32:NetUserGetInfo Level 3 is not implemented
fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented
fixme:netapi32:NetUserGetInfo Level 3 is not implemented
fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented
fixme:netapi32:NetUserGetInfo Level 3 is not implemented
fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented
fixme:netapi32:NetUserGetInfo Level 3 is not implemented
fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented
fixme:netapi32:NetUserGetInfo Level 3 is not implemented
fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented
fixme:netapi32:NetUserGetInfo Level 3 is not implemented
fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented
fixme:netapi32:NetUserGetInfo Level 3 is not implemented
fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented
fixme:netapi32:NetUserGetInfo Level 3 is not implemented
fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented
fixme:netapi32:NetUserGetInfo Level 3 is not implemented
fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented
fixme:netapi32:NetUserGetInfo Level 3 is not implemented
fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented
fixme:netapi32:NetUserGetInfo Level 3 is not implemented
fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented
fixme:netapi32:NetUserGetInfo Level 3 is not implemented
fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented
fixme:netapi32:NetUserGetInfo Level 3 is not implemented
fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented
fixme:netapi32:NetUserGetInfo Level 3 is not implemented
fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented
fixme:netapi32:NetUserGetInfo Level 3 is not implemented
fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented
fixme:netapi32:NetUserGetInfo Level 3 is not implemented
fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented
fixme:netapi32:NetUserGetInfo Level 3 is not implemented
fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented
fixme:netapi32:NetUserGetInfo Level 3 is not implemented
fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented
fixme:netapi32:NetUserGetInfo Level 3 is not implemented
fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented
fixme:netapi32:NetUserGetInfo Level 3 is not implemented
fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented
fixme:netapi32:NetUserGetInfo Level 3 is not implemented
fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented
fixme:netapi32:NetUserGetInfo Level 3 is not implemented
wine version is wine-1.5.30. Wine versions older than wine-1.5.30 may not work
as described in bug 33619.
IMO the most pressing problems are:
1. fixme:process:SetProcessShutdownParameters (00000300, 00000001): partial
stub.
2. fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented
3. fixme:netapi32:NetUserGetInfo Level 3 is not implemented
4. fixme:ntdll:NtSetInformationToken unimplemented class 4
5. fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented
--
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=45098
Bug ID: 45098
Summary: FrostPunk: multiple graphical glitches
Product: Wine
Version: 3.7
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: winehq(a)embed.me.uk
Distribution: ---
Created attachment 61268
--> https://bugs.winehq.org/attachment.cgi?id=61268
FrostPunk log
With patch posted in https://bugs.winehq.org/show_bug.cgi?id=45080 the game
sucessfully starts however there are severe graphical glitches which render it
unplayable. Log 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=45388
Bug ID: 45388
Summary: user32:edit fails on Traditional Chinese and Korean
locales
Product: Wine
Version: unspecified
Hardware: x86
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: user32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
user32:edit fails with the following errors on Traditional Chinese and Korean
locales:
edit.c:1489: Test failed: 0: got 1, 1
edit.c:1510: Test failed: 0: got 1, 1
edit.c:1524: Test failed: 0: got 1, 1
edit.c:1538: Test failed: 0: got 1, 1
See:
* Source matching the above
https://source.winehq.org/git/wine.git/?a=blob;f=dlls/user32/tests/edit.c;h…
* user32:edit WineTest failures
https://test.winehq.org/data/tests/user32:edit.html
The errors can be reproduced on the newtb-wvistau64-zh-cn TestBot VM, and also
happen on fg-win7u64-1spie9-ko.
--
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=43995
Bug ID: 43995
Summary: Uplay - Assassin's Creed 4 Black Flag won't start
Product: Wine-staging
Version: 2.20
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: mi.bar.2001(a)gmail.com
CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de,
sebastian(a)fds-team.de
Distribution: ---
Created attachment 59652
--> https://bugs.winehq.org/attachment.cgi?id=59652
Terminal log from `wine AC4BFSP.exe`
After clicking the "Play" button in Ubisoft Game Launcher (or launching `wine
AC4BFSP.exe`), a window pops up informing, that the game is starting, but it
disappears and the game doesn't launch. I don't have the Steam version, just
the Uplay one.
I've set Windows version to XP, wineprefix is 32-bit.
Wine version will probably be visible when I post this, but I'm going to
mention it just to be safe. Using Wine 2.20 staging
--
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=43208
Bug ID: 43208
Summary: Assassin's Creed IV - Black Flag Hangs tightly
Product: Wine-staging
Version: 2.10
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: tall89(a)mail.ru
CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de,
sebastian(a)fds-team.de
Distribution: ---
When you switch to the Big Inagua location, the game hangs tight, you have to
do Cntrl + Atl + Delete to remove the task, then the game closes, then you
receive an error message, the program ACBF.exe has a serious error, the
application will be closed, we apologize for the inconvenience
WINEDEBUG=fixme-all,err+loaddll,err+dll,err+file,err+reg
------ Program AC4BFSP.exe ------
err:winsock:WSAIoctl -> SIO_ADDRESS_LIST_CHANGE request failed with status
0x2733
err:winedevice:async_create_driver failed to create driver L"ps6ajtsb":
c0000135
err:eventlog:ReportEventW L"mDNSCoreReceiveResponse: Received from
192.168.0.102:5353 16 aspire89-P55A-UD4.local. AAAA
FE80:0000:0000:0000:0A12:F0CA:1A84:437A"
err:eventlog:ReportEventW L"mDNSCoreReceiveResponse: ProbeCount 2; will
deregister 4 aspire89-P55A-UD4.local. Addr 192.168.0.102"
err:eventlog:ReportEventW L"Local Hostname aspire89-P55A-UD4.local already in
use; will try aspire89-P55A-UD4-2.local instead"
err:eventlog:ReportEventW L"mDNSCoreReceiveResponse: Received from
192.168.0.102:5353 25 102.0.168.192.in-addr.arpa. PTR
aspire89-P55A-UD4.local."
err:eventlog:ReportEventW L"mDNSCoreReceiveResponse: Unexpected conflict
discarding 27 102.0.168.192.in-addr.arpa. PTR aspire89-P55A-UD4-2.local."
err:ole:CoInitializeEx Attempt to change threading model of this apartment from
multi-threaded to apartment threaded
err:d3d:wined3d_debug_callback 0x721acb8: "GL_INVALID_OPERATION error
generated. <program> has not been linked, or is not a program object.".
err:d3d:wined3d_debug_callback 0x721acb8: "GL_INVALID_OPERATION error
generated. <program> object is not successfully linked, or is not a program
object.".
err:d3d:wined3d_debug_callback 0x721acb8: "GL_INVALID_OPERATION error
generated. <program> has not been linked, or is not a program object.".
err:d3d:wined3d_debug_callback 0x721acb8: "GL_INVALID_OPERATION error
generated. <program> object is not successfully linked, or is not a program
object.".
err:d3d:wined3d_debug_callback 0x721acb8: "GL_INVALID_OPERATION error
generated. <program> has not been linked, or is not a program object.".
err:d3d:wined3d_debug_callback 0x721acb8: "GL_INVALID_OPERATION error
generated. <program> object is not successfully linked, or is not a program
object.".
wine: Unhandled page fault on read access to 0x00000063 at address 0x8cfb7f
(thread 0047), starting debugger...
wine: Unhandled page fault at address 0x7bc5d590 (thread 0012), starting
debugger...
err:seh:start_debugger Couldn't start debugger ("winedbg --auto 14 168") (1115)
Read the Wine Developers Guide on how to set up winedbg or another debugger
--
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=18635
Summary: Menu bar is hidden in Adobe Lightroom 2.3
Product: Wine
Version: 1.1.22
Platform: Other
OS/Version: other
Status: UNCONFIRMED
Severity: enhancement
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: thomas+wine(a)stromberg.org
With the Adobe Lightroom 2.3 demo, the menu bar titles (File, etc.) do not
display. If you click on the area that they should be, the menu does appear
however. Lightroom 2.3 can be downloaded from
https://www.adobe.com/cfusion/tdrc/index.cfm?product=photoshop_lightroom (free
Adobe login required)
I'm not sure where to go about tracing the issue down to, but I did notice the
following calls that show that it is calling DrawMenuBar().
0009:Call user32.GetMenu(0002003c) ret=60030cbe
0009:Ret user32.GetMenu() retval=000000f0 ret=60030cbe
0009:Call user32.GetMenuBarInfo(0002003c,fffffffd,00000000,0032e1a4)
ret=60030cec
fixme:menu:GetMenuBarInfo (0x2003c,0xfffffffd,0x00000000,0x32e1a4)
0009:Ret user32.GetMenuBarInfo() retval=00000000 ret=60030cec
0009:Call user32.GetSystemMenu(0002003c,00000000) ret=60030beb
0009:Ret user32.GetSystemMenu() retval=00000280 ret=60030beb
0009:Call user32.GetSystemMenu(0002003c,00000000) ret=60030c06
0009:Ret user32.GetSystemMenu() retval=00000280 ret=60030c06
0009:Call user32.GetMenuItemInfoW(00000280,0000f060,00000000,0032e08c)
ret=60030c22
0009:Ret user32.GetMenuItemInfoW() retval=00000001 ret=60030c22
0009:Call user32.DrawMenuBar(0002003c) ret=6008d171
--
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=46330
Bug ID: 46330
Summary: [Feature Request] Enable winelib on ppc64el
Product: Wine
Version: unspecified
Hardware: Other
OS: Linux
Status: UNCONFIRMED
Severity: enhancement
Priority: P2
Component: winelib
Assignee: wine-bugs(a)winehq.org
Reporter: tpearson(a)raptorengineering.com
Distribution: ---
With the resurgence in POWER hardware support and interest centering around the
POWER8/POWER9 chips, it would be great to get winelib support for the ppc64el
architecture. This would allow Windows open source applications to be used on
these powerful machines (e.g. FEMM, SQLYog, etc.).
--
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=46694
Bug ID: 46694
Summary: widl crashes in dlls/atl during build on ppc64el
Product: Wine
Version: 4.2
Hardware: Other
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: tpearson(a)raptorengineering.com
Distribution: ---
Created attachment 63657
--> https://bugs.winehq.org/attachment.cgi?id=63657
Backtrace
Building on ppc64el fails with a segmentation fault in widl while attempting to
build dlls/atl. Backtrace 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=45385
Bug ID: 45385
Summary: Wrong state of virtual keys after cycling windows.
Usually VK_MENU, VK_SHIFT and VK_CONTROL, but every
key can be affected.
Product: Wine
Version: 3.9
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: wineserver
Assignee: wine-bugs(a)winehq.org
Reporter: johnfound(a)asm32.info
Distribution: ---
I noticed that the state of the keys sometimes sticks in pressed state.
This happens when cycling windows with some shortcut key combination.
For example if cycling with Alt+Tab, on pressing Alt, the program gets
WM_KEYDOWN and the state of the VK_MENU becomes pressed. But after cycling
windows, the program does not get WM_KEYUP because the window is not focused
and VK_MENU (and the respective VK_LMENU or VK_RMENU) remain in pressed state.
When cycling back to the program window, the window get focused only after
releasing Alt key, so it does not get this event as well.
If cycling windows with another shortcut key combination (for example
Alt+Shift+Tab - for backward cycling) both VK_MENU and VK_SHIFT keys stick.
In the same time, GetAsyncKeyState returns the proper state of the keys.
Note1: The problem is obviously in the wineserver code, because it handles the
key state tables for the different threads.
Note2: The effect happens only sometimes. It seems the code for proper
processing is already there, but some racing conditions have place.
Note3: There is some probability that the effect is in result of my application
code, but it never happens on real Windows, so I considered it a bug.
Note4: I tried to workaround this problem by reading the whole table by
GetAsyncKeyState and setting it then with SetKeyboardState on WM_ACTIVATE
message of the main window. This workaround actually works, but is too ugly
IMO.
The same trick on WM_ACTIVATEAPP does not work.
--
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.