https://bugs.kde.org/show_bug.cgi?id=473047
--- Comment #2 from ianwoodfor...@gmail.com --- (In reply to Aleix Pol from comment #1) > That is on wayland, can you confirm? Yes > A good way to confirm the issue, would be to provide the logs with > WAYLAND_DEBUG=1 enabled and see that the proximity events get lost. If it > came to it, providing a way to reproduce the problem with a piece of > software that is readily available would also make it easier to fix and test. I wasn't aware of that flag. `WAYLAND_DEBUG=1 systemsettings 2>&1 | grep "proximity_in\|proximity_out"` works well. I'm wondering if actually it's do with some kind of "half-initialised" state with my pen. I'm also struggling to reproduce it: it does still happen, but it's hard to pin down whether it's opengl windows or any window or fullscreen windows because sometimes when I launch that command the proximity_in events are generated, sometimes they aren't, and sometimes by playing with the pen it will stop or start working (but I can't pin down what is causing that). >From the log: [3584498.375] zwp_tablet_tool_v2@4278190081.proximity_in(1197, zwp_tablet_v2@4278190080, wl_surface@29) [3584498.424] zwp_tablet_tool_v2@4278190081.proximity_in(1198, zwp_tablet_v2@4278190080, wl_surface@29) ... [3585144.816] zwp_tablet_tool_v2@4278190081.proximity_out() ... [3587967.804] zwp_tablet_tool_v2@4278190081.proximity_out() I have the entire log file if that would be helpful, but I don't know how to upload it (pastebin?) -- You are receiving this mail because: You are watching all bug changes.
