Repository navigation
Any support for Wayland? #37
Replies: 3 comments 7 replies
|
What does wayland have to do with spacenavd? What kind of support would you like? |
|
well, it complains that it can't connect to display ":0", for starters. |
|
As I stated, I'm not running X11/Xorg directly. I don't have .Xauthority file in home dir as it looks like spacenavd can't reach or talk to my Xorg server that runs within wayland. Given that majority of distros are migrating to Wayland these days (with MANY good reasons!), this seems as something that should be looked into... |
|
Regardless of how the X server is running, be it standalone or rootless on some other window system, applications still need to authenticate to connect to it, and certainly it will be running as a certain display number, and that number will have to be specified in the DISPLAY environment variable. There might be some other cause to your problem, but these two are the only ones I can think of right now. Here's a list of questions, and things to try:
For the sake of expediency, I'll try to take a blind stab at a probable cause before waiting for your answers: I assume you're running spacenavd from init (as you should, it is a daemon after all). I also assume (because I remember reading something to that effect by another wayland user) that wayland is not running the X server as display 0 which is the usual case, but as some larger number instead. During init the DISPLAY environment variable is probably not set, since the X server is not running yet, which causes spacenavd to fallback to assuming display 0. When the X server starts as a different display number spacenavd fails to connect to it. If the above assumption turns out to be correct, and further assuming the display number X starts as is predictable and doesn't change from one session to the next, you can edit your init script and make sure to manually define |
|
OK, here we go: INFO:I'm running Gentoo, with wayland+sway with enabled xwayland support. AD 1: Yes. I've just installed sci-electronics/pcb as test example. Runs fine with ("xwayland on") in sway config file, it doesn't start with ("xwayland off"). Notice: |
|
I apologize, my mistake, the command is |
|
I tried that and now spacenavd stops complaining about authorization. So I've ran it manually and it seems that the daemon can't find the device it would recognise: Spacenav daemon 1.2 I have latest kernel 6.3.7, compiled from sources. Do I hjave to have some special support for Space Navigator ? "lsusb -v" does list the device as: Bus 003 Device 012: ID 046d:c626 Logitech, Inc. 3Dconnexion Space Navigator 3D Mouse Also, "udevadm -u monitor" doesn't show any creation of the device in the /dev, just the map in the /sys: UDEV [165248.277356] add /devices/pci0000:00/0000:00:08.1/0000:06:00.4/usb3/3-1/3-1.1 (usb) So I've opened the file "dev" in that map and it lists the char device as 189,268 I tried creating it manually: "mknod --mode=777 /dev/input/mouse1 b 189 268" "cat /dev/input/mouse1" doesn't work. I get the response as "non-existing device" Also, running the daemon manually in verbose mode shows that the daemon doesn't like it either. |
|
I think I got it. Good part of the problem is that the daemon fails if usbguard ( USB bus event filter daemon) blocks it after plugin, even if it is allowed later. spacenavd daemon finds and recognizes its event device and connects to it. Space Navigator's LED lights up and test_cube example works. Thanks. |
|
Glad to hear you figured it out. To be clear, the X authentication issue has nothing to do with device detection. If you want to solve that, I'd look into where xwayland puts the authentication cookie, and make XAUTHORITY point to it, or symlink it to your home directory. |
Uh oh!
There was an error while loading. Please reload this page.
I am on Ubuntu 20.04 and having issues when not running in X11 comp mode.
Any thoughts?
Thanks
S
All reactions