SpacingBat3
Webcord causes gesture daemon, lisgd, to sometimes not recieve inputs
Aknowledgements
-
[X] I have checked that there's no other issue describing the same or similar problem that I currently have, regardless if it has been closed or open.
-
[X] I can confirm that this is not an issue with the Discord website, but it is a problem specific to the WebCord itself. I have tested if this bug occurs on Chromium/Chrome or any other Chromium-based browser that uses unpatched/upstream Chromium engine.
-
[X] I have tried running the build from the
masterbranch and it does not have any fixes implemented according to my issue. -
[ ] My issue describes one of the unstable and/or not fully implemented features.
-
[X] I have found a workaround to mitigate or temporarily fix this issue in affected releases (please write it in Additional context section below).
Operating System / Platform
🐧️ Linux
Operating system architecture
aarch64 (64-bit ARM)
Electron version
v20.1.0
Application version
v3.8.1
Bug description
While WebCord is running on PostmarketOS with Sway window manager, sometimes my gesture daemon called lisgd won't recieve gesture inputs. This happens on both X11 and Wayland.
Additional context
Sometimes closing and restarting WebCord fixes it other times not.
Officially, Electron does not support the touch devices and therefore its API is not prepared for the touch among many other web-based software with Linux support. However, maybe this could be resolved on side of lisgd developers, if not Electron's?
It's definitely not a bug specific to WebCord, there's no API to control how gestures would behave, at least designed to work on Linux mobile devices.
It just strange because other electron apps running in the background don't stop the gestures from working. If WebCord is running (even just in the tray) gestures just stop working.
It just strange because other electron apps running in the background don't stop the gestures from working. If WebCord is running (even just in the tray) gestures just stop working.
Out of the curiousity, it this issue still reproducible on the newer WebCord versions? It would be useful to know that, considering there was a major Electron update and WebCord's now on 21.x.y.