Skip to content
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

Wayland/xwayland issue #41

Open
severin-lemaignan opened this issue Nov 6, 2020 · 13 comments
Open

Wayland/xwayland issue #41

severin-lemaignan opened this issue Nov 6, 2020 · 13 comments

Comments

@severin-lemaignan
Copy link

Starting remouse (commit 89505ec) this morning on Ubuntu 20.04 on a wayland session, I get these errors:

$ sudo remouse --address 192.168.0.23 --key ~/.ssh/remarkable --monitor 1 --evdev
connected to 192.168.0.23
Created virtual input device '/dev/input/event25'
Error setting orientation: b'WARNING: running xinput against an Xwayland server. See the xinput man page for details.\nunable to find device reMarkable tablet stylus\n'
Error setting monitor: b"WARNING: running xinput against an Xwayland server. See the xinput man page for details.\nunable to find device 'reMarkable tablet stylus'\n"
Error setting pressure threshold: b'WARNING: running xinput against an Xwayland server. See the xinput man page for details.\nunable to find device reMarkable tablet stylus\n'
Error setting fit: b'WARNING: running xinput against an Xwayland server. See the xinput man page for details.\nunable to find device reMarkable tablet stylus\n'

and indeed, the monitor is not properly selected.

...not sure why xinput and xwayland are triggered here... any idea?

libinput list-devices does list the tablet, as expect.

@tuxPT
Copy link

tuxPT commented Jan 21, 2021

can confirm, can't get it working on sway

@Evidlo
Copy link
Owner

Evidlo commented Jan 22, 2021 via email

@Evidlo
Copy link
Owner

Evidlo commented Jan 22, 2021

I'm guessing that screeninfo doesn't support Wayland yet.

edit: screeninfo does support Wayland

@Evidlo
Copy link
Owner

Evidlo commented Jan 22, 2021

I just tested this on Sway/Debian 10 and the problem seems to be that 'xinput' doesn't work as root.

Normally this is because $DISPLAY is set incorrectly, but in my case it seems correct.

@tuxPT
Copy link

tuxPT commented Jan 24, 2021

btw, my libinput list-devices does not list the tablet either with evdev or without, and root/non root

@tuxPT
Copy link

tuxPT commented Jan 24, 2021

It does however receive positional info from the pen when I put --debug flag
image
image

@tuxPT
Copy link

tuxPT commented Feb 8, 2021

After seeing various forks, this fork works on sway, but it still has errors.
Basically he replaced /dev/event with /dev/touchscreen

@tsmithe
Copy link

tsmithe commented May 13, 2021

@tuxPT Is it worth trying that fork? (What errors do you refer to?) I'm looking for a way to get something like remouse working on Sway!

Edit to say that: I did try remouse upstream (ie., from this repo), but couldn't get any response from libinput, whether I used --evdev or not, whether I used the udev quirk or not, and whether I ran as root or not...

@tuxPT
Copy link

tuxPT commented May 13, 2021

@tsmithe I use sway on archlinux. The errors I don't remember but I think it was the same as upstream. Besides console printing errors, the remouse worked fine, I don't use it in a while.

Edit: I think you have to use the evdev flag in the fork

Edit2: I think I have run with sudo -EH remouse --evdev . Because of some environment variable problem.

@tsmithe
Copy link

tsmithe commented May 13, 2021

Amazing, thanks, that works! I'm very grateful :-)

@Evidlo
Copy link
Owner

Evidlo commented May 15, 2021

BTW, sudo -EH ... doesn't work on some distributions because -E specifically excludes PATH.

sudo --preserve-env=PATH ... should work everywhere.

@7RST1
Copy link

7RST1 commented Jun 6, 2022

I got this working through the fix mentioned here, however the virtual pointer only affects XWayland windows, meaning I can't use it with any drawing applications I have installed.

I'm guessing there's nothing to do about it in this project, and we just have to wait for upstream pyinput wayland support? Looks like the necessary Wayland protocols still aren't implemented.

@Evidlo
Copy link
Owner

Evidlo commented Nov 11, 2024

@7RST1 I would just use it with the --evdev option, which bypasses pynput entirely.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants