-
-
Notifications
You must be signed in to change notification settings - Fork 64
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Mouse crashes into sides of screen on sway #174
Comments
I have similar problem on my system (fedora 37, KDE, Wayland) and latest flatpak version (update 23/05/03). Mouse crashes to edges and games are overall sluggish and unplayable. It may be related to fact, that I can no longer activate fullscreen with F11 (in Library - it solves some issues with escape key and mouse input), which i was used to in versions before. EDIT: Downgrading flatpak (2023-03-25) helped as a workaround. |
@pil-in-a I have the same issue on fedora 38 gnome wayland. What do you mean by downgrading flatpak? |
@rby-blackruby ... I downgraded |
Is this still an issue for you in the latest version? |
Fullscreen not working properly is still an issue in the lastest release (cannot manualy activate it via F11, mouse crashing to edge/going to second monitor). Performance seems to be lot better though - playable (still not as smooth as last working version). |
Same issue, trying to play genshin impact with the --spoof-windows flag enabled, I have very limited range of movement. Seems like the mouse locking isn't working, and I understand that it may be difficult to do that on linux. |
Yeah I've got the same issue since a month or so, have been using Chromium instead as well. |
Same here. Fedora 38 GNOME Wayland running latest gfn as of writing. |
Similar problem with Ubuntu 22.04 on Gnome42. Mouse seems to go over the edge and I can't rotate the characters anymore. Downgraded to the 5/3/23 package from flatpak and that version works just fine. |
Same problem here, on Ubuntu 23.10, Wayland, app version 2.0.0 . |
Also have this problem on KaOS with Wayland. |
I was able to fix this bug, like others, by downgrading the package. This command should work for everyone: And you should see this:
The fix works on both Fedora 38 and 39 for me. |
I discovered if you go to releases, download the AppImage and run it, the cursor issue is not a problem. |
This issue still isn't fixed, is it going to be fixed? |
Recently installed Debian 12 and this is no longer a possible fix as the version quoted is no longer found. Seems like everything before the version 2.0.0 update has been removed! ID: io.github.hmlendea.geforcenow-electron Commit: aa83ecbe154520416e0f8496d4beb81328c88444efa8fa51e07ef684572cf5a3 History: Commit: d41a1bf86bef70f0c8131cbf0041318de2726342770a74192cb9a670236ddbed Commit: 8c5e71e352e52c859bf3e3b302047634e414683c463666557df7aa309f86bfed Commit: 414a8a0394183d9f94b3ad422e963e02f998ec830186f72cd273ef44a7294e10 |
This issue is still not fixed, having the same problem with the latest version on my fresh KDE Neon with Wayland. |
Fedora 40 here with latest Electron version, fully reproducible as noted. ETA: launched 2.0.0 appimage and mouse stays within the game no problem. |
Thanks for that, I'll give it a go with AppImage. |
I just found a simple solution for this. The AppImage is good, but I don't like to sign in every single time because I need to do the 2FA this is the other alternative to install the 1.10 manually because the commit is no longer available. You just need to download the tar.gz file and install it, then you're good to go https://aur.archlinux.org/cgit/aur.git/commit/?h=geforcenow-electron&id=37c3cb1f787253529ae93eba52fd717fe8b9ada0 |
Describe the bug
I am running gfn-electron in sway. The cursor of the system continues to move even when it is captured by gfn-electron. When I move my view far enough, the cursor crashes into the sides of the screen and I am unable to continue moving my view any further.
To Reproduce
Screenshots
No response
Operating System
Arch Linux
Desktop Environment
sway 1.7
Display Server
Wayland
Installation method
AUR
Version
1.10.0
Is this a fresh install of the app or an update from a past version?
Fresh install
Did this issue appear right away upon installation/updating, or spontaneously?
Yes, right after installation
Additional context
This issue is not present when playing directly in the Chromium browser. I am using the
--enable-features=UseOzonePlatform --ozone-platform=wayland
flags to run gfn-electron and Chromium in Wayland directly.The text was updated successfully, but these errors were encountered: