Bug 7058 - incorrect mouse cursor when client is using wayland
Summary: incorrect mouse cursor when client is using wayland
Alias: None
Product: ThinLinc
Classification: Unclassified
Component: | rdesktop (deprecated) (show other bugs)
Version: 1.3.1
Hardware: PC Unknown
: P2 Normal
Target Milestone: 4.9.0
Assignee: Henrik Andersson
Depends on:
Blocks: 5646
  Show dependency treegraph
Reported: 2017-09-27 13:59 CEST by Pierre Ossman
Modified: 2017-10-03 13:11 CEST (History)
1 user (show)

See Also:
Acceptance Criteria:


Description Pierre Ossman cendio 2017-09-27 13:59:51 CEST
When the Linux client is on a Wayland system we sometimes get a bad mouse cursor. We've seen it with the standard I-beam cursor on Windows, but there might be others.

Instead of the correct cursor we get two thick vertical bars, not unlike a pause symbol. It doesn't seem to be a simple inverted version of the I-beam though as there isn't any pixels at the top and bottom.

The cursor starts working if any pixel is changed from alpha having 00 or ff, so there seems to be some heuristic somewhere that detects simple cursors like this.
Comment 1 Pierre Ossman cendio 2017-09-27 16:33:55 CEST
I can reproduce the same bug in Firefox using the same cursor. Not quite known why rdesktop is unaffected under the same circumstances.
Comment 2 Pierre Ossman cendio 2017-09-27 16:36:53 CEST
Seems to be related to the size. rdesktop has a lot of padding around the cursor, expanding it to 32x32 pixels. Doing the same in Firefox gets a working cursor.
Comment 3 Pierre Ossman cendio 2017-09-27 17:15:26 CEST
Found the bug in Xwayland:


So either we ignore it until they've fixed it, or we do a workaround (e.g. pad to 8 pixels wide).
Comment 4 Pierre Ossman cendio 2017-10-03 13:11:34 CEST
We trust that upstream will roll out the patch they have suggested on the upstream bug entry.

Note You need to log in before you can comment on or make changes to this bug.