go-vgo/robotgo

Fedora 29 Mouse not working (Wayland ?)

Open

#178 opened on Nov 5, 2018

View on GitHub
 (5 comments) (1 reaction) (0 assignees)C (7,142 stars) (673 forks)batch import
LinuxProposalenhancementhelp wanted

Description

  • 0.60
  • 1.11-1
  • 8.2.1-4
  • Fedora 29 64Bit
  • 4k
  • Can you reproduce the bug at Examples:
    • 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 ? ...

Contributor guide

Tech stack
go
Domain
desktop
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
needs investigation
Prerequisites
Go programmingLinux desktop environmentsWayland basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
10
Research direction
The issue is likely related to Wayland vs X11 compatibility. The robotgo library uses C bindings for mouse control under the hood. Check the robotgo source code for mouse functions in services/ directory, particularly any Wayland specific code. Look for existing discussions in the issue comments or linked issues about Wayland. Consider testing on X11 to isolate the problem. Maintainer input is needed to confirm if Wayland support is intended.