[kwin] [Bug 386954] Pointer locking/confinement issues

2018-02-08 Thread Yannick
https://bugs.kde.org/show_bug.cgi?id=386954 --- Comment #14 from Yannick --- The issue is still here with Plasma 5.12.0. When I start Neverball with both the X11 and Wayland SDL backends, pressing "Escape" in the game will not unlock the cursor. I have to Alt+tab out

[kwin] [Bug 386954] Pointer locking/confinement issues

2018-01-04 Thread Yannick
https://bugs.kde.org/show_bug.cgi?id=386954 --- Comment #13 from Yannick --- I applied the patch on top of Kwin 5.11.5. I'm not sure if it's the right thing to do, but building kwin-git and all its *-git dependencies would take ages on my computer. I still had issues

[kwin] [Bug 386954] Pointer locking/confinement issues

2018-01-03 Thread Martin Flöser
https://bugs.kde.org/show_bug.cgi?id=386954 Martin Flöser changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Latest

[kwin] [Bug 386954] Pointer locking/confinement issues

2018-01-03 Thread Martin Flöser
https://bugs.kde.org/show_bug.cgi?id=386954 Martin Flöser changed: What|Removed |Added URL||https://phabricator.kde.org

[kwin] [Bug 386954] Pointer locking/confinement issues

2017-11-16 Thread Martin Flöser
https://bugs.kde.org/show_bug.cgi?id=386954 --- Comment #9 from Martin Flöser --- It might be that XWayland assumes a bug in the Wayland compositor. I read the documentation of pointer locking again and looked at the source code of XWayland and that doesn't fit. We have in

[kwin] [Bug 386954] Pointer locking/confinement issues

2017-11-15 Thread Yannick
https://bugs.kde.org/show_bug.cgi?id=386954 --- Comment #8 from Yannick --- I tried Neverball and Xonotic on a Weston session, and didn't have any of the problems I encountered with Plasma. The pointer is correctly locked/unlocked on Weston. I made sure to run both

[kwin] [Bug 386954] Pointer locking/confinement issues

2017-11-15 Thread Martin Flöser
https://bugs.kde.org/show_bug.cgi?id=386954 --- Comment #7 from Martin Flöser --- the other problem is the locking. Well, that looks like an xwayland bug to me. Obviously the mouse doesn't move when locked. That's the idea behind it. -- You are receiving this mail because:

[kwin] [Bug 386954] Pointer locking/confinement issues

2017-11-15 Thread Martin Flöser
https://bugs.kde.org/show_bug.cgi?id=386954 --- Comment #6 from Martin Flöser --- Ok, I just installed neverball to see what's going on. The main problem is that neverball acts on repeated key press events for escape key and do to that the breaking of the confinement doesn't

[kwin] [Bug 386954] Pointer locking/confinement issues

2017-11-15 Thread Yannick
https://bugs.kde.org/show_bug.cgi?id=386954 --- Comment #5 from Yannick --- Sorry, my bad: I made another test with Neverball. When I press "Escape", the mouse pointer remains visible. It just won't move. I noticed a few more things: - I can also unlock the pointer

[kwin] [Bug 386954] Pointer locking/confinement issues

2017-11-15 Thread Yannick
https://bugs.kde.org/show_bug.cgi?id=386954 --- Comment #4 from Yannick --- Hi, 1. I use xorg-server-xwayland 1.19.5 2. There should be a mouse cursor on the neverball screenshot -- You are receiving this mail because: You are watching all bug changes.

[kwin] [Bug 386954] Pointer locking/confinement issues

2017-11-15 Thread Martin Flöser
https://bugs.kde.org/show_bug.cgi?id=386954 Martin Flöser changed: What|Removed |Added Component|wayland-generic |input Flags|

[kwin] [Bug 386954] Pointer locking/confinement issues

2017-11-15 Thread Yannick
https://bugs.kde.org/show_bug.cgi?id=386954 --- Comment #2 from Yannick --- I am aware that the issue with NetRadiant is not easily reproducible, because this application is quite specific and requires a special setup, sorry for that :( But maybe other applications

[kwin] [Bug 386954] Pointer locking/confinement issues

2017-11-15 Thread Yannick
https://bugs.kde.org/show_bug.cgi?id=386954 --- Comment #1 from Yannick --- Created attachment 108881 --> https://bugs.kde.org/attachment.cgi?id=108881=edit NetRadiant layout, with 3D and 2D views -- You are receiving this mail because: You are watching all bug