Fedora 29 Mouse not working (Wayland ?)

[FloThinksPi]

• 0.60
• 1.11-1
• 8.2.1-4
• Fedora 29 64Bit
• 4k
• Can you reproduce the bug at Examples:
  • [X] Yes (provide example code)
  • [ ] No
  • [ ] Not relevant
• Provide example code:

package main

import (
	"github.com/go-vgo/robotgo"
)

func main() {
	robotgo.ScrollMouse(10, "up")
	robotgo.MouseClick("left", true)
	robotgo.MoveMouseSmooth(100, 200, 1.0, 100.0)
}

• Log gist:

Description

So it seems like the mouse features are not working straight away on fedora 29. The Curser or buttons below the cursor just flicker. No mouse movement whatsoever. Maybe this is related to Wayland Support ? However i also tested Keyboard functionality wich seems to work fine.

Any ideas ? ...

[vcaesar]

Robotgo uses x11, please try to run xlsclients or check the x11 environment. Since the Fedora 29 version is stuck and splashed in the virtual machine, I will not continue testing it. There is no problem with Fedora 25 testing. Welcome feedback any situation.

[FloThinksPi]

@vcaesar Fedora 25 is not maintained and supported since 2017. The only Maintained versions of Fedora are 28 and 29 now(Which both work without issues in a VM). Fedora 27 Support ends Today, what a coincidence, see https://en.wikipedia.org/wiki/Fedora_(operating_system) 😄 . However both , 28 and 29, use Wayland as default, like many other new Distros now do or will do. X-Server will be vanishing away. So one should considder how to handle this, as robotgo gets more and more incompatible to the Operating System Defaults.

[vcaesar]

You can try to disable Wayland:

/etc/gdm/custom.conf
[daemon]
WaylandEnable=false

Currently, robotgo works fine on Ubuntu and Fedora XX; there are no plans to migrate yet, because the amount of engineering and testing is large, and this is a huge update.

Welcome to contribute code that can switch between x11 and Wayland.

[pwhelan]

The reality of wayland has changed substantially since this issue was first opened.