Bug 1242322

Summary:	when running on wayland, mouse pointer does not remain stationary after scrolling map
Product:	[Fedora] Fedora	Reporter:	Jonathon Conte <anotherjonathon>
Component:	openttd	Assignee:	Felix Kaechele <felix>
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	22	CC:	atorkhov, dr4ke, felix, ofourdan, samuel-rhbugs
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-07-19 15:19:21 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Jonathon Conte 2015-07-13 04:28:40 UTC

This is an input handling bug that only occurs when running openttd on wayland.

When the secondary mouse button is held down in order to scroll on the map, the mouse pointer is supposed to remain in the same spot on the monitor. This works fine under xorg. However, when openttd is run under the GNOME wayland session and the mouse is used to scroll the map, the mouse pointer jumps in the direction the mouse was moved.

openttd depends on SDL 1.2 (which is not wayland compatible) so perhaps the bug is related to xwayland.

Comment 1 Olivier Fourdan 2015-07-20 13:51:16 UTC

I reckon to achieve this in Wayland, we'd need the relative pointer API:

http://lists.freedesktop.org/archives/wayland-devel/2014-December/018653.html

Which is still under discussion upstream and not merged yet.

Comment 2 Fedora End Of Life 2016-07-19 15:19:21 UTC

Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.