[Bug 48385] New: Rising Lands freezes when navigating back by pressing ESC key on main menu
https://bugs.winehq.org/show_bug.cgi?id=48385 Bug ID: 48385 Summary: Rising Lands freezes when navigating back by pressing ESC key on main menu Product: Wine Version: 4.11 Hardware: x86 URL: https://appdb.winehq.org/objectManager.php?sClass=appl ication&iId=19674 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winex11.drv Assignee: wine-bugs(a)winehq.org Reporter: vyproyects(a)gmail.com CC: z.figura12(a)gmail.com Regression SHA1: 1bc9c4fdb2e6c2762105c14cdafb7d4ea3370625 Distribution: Ubuntu Created attachment 66145 --> https://bugs.winehq.org/attachment.cgi?id=66145 Rising Lands navigating back output This is NOT a regression but a still not working at all bug resulting of a previous bugfix. I mean, before Wine 4.11 in Rising Lads game (a Win95 game that uses wine 32 bit configuring it with Windows 95 compatibility), it was impossible at all to navigate back from a secondary menu at main menu by pressing ESC key. This is, if you clicked on "load game" from main menu and then pressed ESC key to go back to main menu, all texts were cleared and animations stopped resulting in a freezed screen. Same happens during gameplay in order to save the game. As of a bugfix in wine 4.11 now is possible to go back but just in a certain situation: being in windowed mode (due to another bug) you have to which to any other app by pressing Alt+TAB. At the very moment wine loses the focus main menu is refreshed. No need to go back again to wine, though. As you can see if dragged apart the new appearing window. I've made a regression testing to find out which exact commit had fixed this bug this way, and this is the output: 1bc9c4fdb2e6c2762105c14cdafb7d4ea3370625 is the first fixed commit commit 1bc9c4fdb2e6c2762105c14cdafb7d4ea3370625 Author: Zebediah Figura <zfigura(a)codeweavers.com> Date: Mon Jun 17 14:46:20 2019 -0500 winex11: Update the state of all keys on KeymapNotify. The Binding of Isaac transitions in and out of fullscreen when the "F" key is pressed. Specifically, it will swap states when receiving WM_KEYDOWN, provided that the previous key state was not pressed (i.e. bit 30 is 0). However, as part of the process of transitioning, it hides and shows its window, causing it to temporarily lose focus. If the F key is released while the window does not have focus, Wine misses this fact, and thinks that the key was already pressed the next time it is pressed, causing the game to refuse to change focus. Windows will not deliver WM_KEYUP messages to a window that does not have focus, but it will always report the true previous state of any key on the keyboard when requested. Signed-off-by: Zebediah Figura <zfigura(a)codeweavers.com> Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> :040000 040000 2348a78ab9f7e1c7abfa45606b769dc0d28986ee 056dbd175d366ab2ee50c4d1f3674a01307a718d M dlls Although I use spanish version this also happen on english version even without installing the patch update. A download url is available on AppDB: https://appdb.winehq.org/objectManager.php?sClass=application&iId=19674 VGA compatible controller: Intel Corporation HD Graphics 5500 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330 / M430 / R7 M520] (rev 83) Subsystem: Lenovo Radeon R5 M330 Kernel driver in use: radeon Kernel modules: radeon, amdgpu Hope this help to find out the real problem. -- 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=48385 Gijs Vermeulen <gijsvrm(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |regression -- 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=48385 Zebediah Figura <z.figura12(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Regression SHA1|1bc9c4fdb2e6c2762105c14cdaf | |b7d4ea3370625 | Keywords|regression |download --- Comment #1 from Zebediah Figura <z.figura12(a)gmail.com> --- Thanks for the bisect. I'm not sure whether it'll end up helping, but I'll take a shot at debugging this anyway. -- 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=48385 --- Comment #2 from Zebediah Figura <z.figura12(a)gmail.com> --- I can't seem to reproduce this with 5.0-rc3, whether using a virtual desktop or not. What graphics driver are you using? -- 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=48385 --- Comment #3 from vyproyects(a)gmail.com --- lspci -v | less 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 5500 (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 5500 Flags: bus master, fast devsel, latency 0, IRQ 50 Memory at d0000000 (64-bit, non-prefetchable) [size=16M] Memory at c0000000 (64-bit, prefetchable) [size=256M] I/O ports at 5000 [size=64] [virtual] Expansion ROM at 000c0000 [disabled] [size=128K] Capabilities: <access denied> Kernel driver in use: i915 Kernel modules: i915 04:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330 / M430 / R7 M520] (rev 83) Subsystem: Lenovo Radeon R5 M330 Flags: bus master, fast devsel, latency 0, IRQ 54 Memory at b0000000 (64-bit, prefetchable) [size=256M] Memory at d1000000 (64-bit, non-prefetchable) [size=256K] I/O ports at 3000 [size=256] Expansion ROM at d1040000 [disabled] [size=128K] Capabilities: <access denied> Kernel driver in use: radeon Kernel modules: radeon, amdgpu -- 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=48385 --- Comment #4 from Zebediah Figura <z.figura12(a)gmail.com> --- This is probably a WM-specific bug rather than a GPU driver-specific bug. I can't reproduce it with wine 6.0-rc4, though, in any of KWin, Mutter, xfwm4, fvwm2 (all but the first running in Xnest). Can you please retest with wine 6.0-rc4, and specify your WM version? -- 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=48385 vyproyects(a)gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |NOTOURBUG Status|UNCONFIRMED |RESOLVED --- Comment #5 from vyproyects(a)gmail.com --- Hi I'm happy to say that this bug is finally fixed. As I told, the problem seem to be related with another bug I had on a different game caused by a failing video card driver (Intel). Finally I had the time to upgrade my distro to the latest version and the bug was automatically fixed. Same Wine version, same pc, same distro, same copy of the game. Simply different distro version and the latest version of my video card driver. I already upgraded my distro in the past but this time was different. Thanks for your time and effort anyway. -- 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.
participants (1)
-
WineHQ Bugzilla