wacom invisible mouse pointer in wayland

[Timokl]

After upgrading to Ubuntu 17.10, I connected my Wacom Intuos tablet, which has touch and pen functionality.

Controlling the mouse pointer through the touch functionality seems to work fine, but using the stylus produced very strange behaviour, depending the program.

- With Firefox there there are two pointers - one that is moving in accordance with the stylus movements, and one stays put at the position, when the stylus movement was detected.

- With Darktable the mouse pointer becomes invisible, once it's moved inside of the application window (it registers clicks though). Once the pointer is moved outside of the application window, it appears again.

I'm running Ubuntu inside of a wayland session.

libwacom2: 0.24-1

[Timokl (timokl)]

The stylus pointer seems to work fine in a X.org session.

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1726224/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[Alessandro (alessandro-oliviero)]

I have the same issue. After upgrading to 17.10 with Wayland, connecting my Wacom graphic tablet results in two independent pointers: one for the mouse and the other for the tablet pen. In the Gnome shell and in certain programs, i.e. Firefox (Firefox Quantum beta version), My Paint 1.2, the pen pointer become invisible but the pen can still draw or click buttons. I tried to check the system settings of Wacom and, when in focus of the settings window, the pointer turns visible, but if I leave the focus, it disappears again.

[Daniel van Vugt (vanvugt)]

Assigned also to xorg-server in case Xwayland needs a fix here.

[Sebastien Bacher (seb128)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance.

[Alessandro (alessandro-oliviero)]

After log-in with Wacom tablet connected Gnome shows two cursors, one for the mouse and the other for the tablet's pen. I can normally control the pen's cursor. After a while the pen's cursor disappears (it is invisible, but I can still control it with the pen).
If I reset the shell with "killall -HUP gnome-shell" and I log in again the cursor is back.

Thanks

[Alessandro (alessandro-oliviero)]

Additional info: the pen cursor disappears when I move in the same time both mouse and pen.

[Alessandro (alessandro-oliviero)]

Upstream bug: https://bugzilla.gnome.org/show_bug.cgi?id=789754

[Sebastien Bacher (seb128)]

thanks

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Kostas (sokos-deactivatedaccount)]

I wanted to add that I have the same problem too.
Additionally if I press any of the Wacom Intuos Pen and Touch buttons the screen freezes completely and I have to restart the PC.
( Using Wayland Ubuntu 17.10 )

[Alessandro (alessandro-oliviero)]

I confirm the same behaviour reported by Kostas, the system freezes if I press the buttons of the tablet.

[Alessandro (alessandro-oliviero)]

Additionally if I press any of the Wacom Intuos Pen and Touch buttons the screen freezes completely and I have to restart the PC.

[Schatzkin-o (schatzkin-o)]

I'm having these problems too. In addition, I cannot open a dropdown menu using the pen.

[André (afsverissimo)]

Confirm Kostas and Alessandro. Here is the output of `journalctl -e /usr/bin/gnome-shell`

[Erwyn (lordmartinus)]

Hello, Here to confirm cursor disappearance and system freeze. I have a Wacom Intuos Comic Small. Also buttons are not properly detected I have some mismatching in there (between what is shown in the settings and the one actually pressed on the tablet). Funny thing is, mismatched is not the same on Wayland and Xorg....

Also, on Xorg the touch detection (right click/scrolling) is really awful while it works pretty well on Wayland...

[Erwyn (lordmartinus)]

Just to add some information on this on the cursor disappearance topic. If I hit the "windows" button the one that open the application/windows browsing of gnome shell and I move the stylus on the tablet the pointer is there. Same thing if I Alt+Tab. But I soon as I leave one or the other, cursor is not there and the only quickfix yet is unplugging and plugging back the tablet as suggested before.

[Casey (casey-jao)]

This seems to happen with applications running under XWayland. For pure Wayland applications the Wacom tablet's cursor behaves correctly.

To see this, open for instance gnome-terminal (which uses Wayland) and Xournal (which uses XWayland) side by side. When moving the cursor from gnome-terminal to Xournal, the cursor does not change to a pen but instead remains whatever it was when it left the gnome-terminal window, such as an arrow or a text cursor.

[Ian (imyxhuang)]

Aside from the drop-down menu and pen button problems, I have all of the issues above while using digimend drivers and a Huion tablet; this is probably not a problem with the Gnome Wacom drivers but rather an issue with XWayland, as Casey pointed out.
Another thing worth mentioning is that on my system, after I switch off my pen with a button on the top, my regular pointer can't click anything. I need to either press alt-tab, change workspaces and switch back, or a few other options to restore the normal cursor.

[WarrenSensei (warren-sensei)]

I am not sure if I have the same bug with worse symptoms, or a whole different problem, but here goes:
My Intuos3 PTX-930 will not work in Ubuntu 17.10.
Under Wayland, the cursor flies randomly across the screen whenever the stylus or mouse are near the tablet, often "collecting" in the top left corner. It also leaves a second cursor under the control of the normal mouse/touchpad on my laptop.
Under XOrg, location is stable. BUT with either Wayland or Xorg, all input seems to include a "touch" or left-click action! So literally everything the cursor passes over is clicked! Programs opening, windows being opened and closed, CHAOS! In XOrg, clicking stops when I remove the stylus/mouse from the tablet's field, but in Wayland once the stylus/mouse has been near, the chaos never ends until I reboot.

The internet has not been helpful with this, as most solutions are for older versions and refer to repositories that don't exist anymore (doctormo, for one).

[Fillchiam (fillchiam)]

I am also experiencing this bug with my Intuos4 M. When I connect the tablet, one cursor remains where I last had the mouse, and another appears where I put down the stylus. The one where the stylus is changes appearance from arrow to "crosshairs" to disappearing depending on where on screen it is and over which applications.

[Vadim Andreyev (kolobast)]

Still not fixed in 2020. Gnome-shell and Wayland = Wacom cursor dissapears.

[Daniel van Vugt (vanvugt)]

Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed.

[Daniel van Vugt (vanvugt)]

Note also this bug is about Wayland sessions so comment #17 should probably go somewhere else.

[Maksim Yu.Semenov (rasmiy)]

I have Ubuntu 20.04.1 LTS. Window interface is Wayland. And described solution didn't work long. After half an hour cursor disappeared again. So it is obviously just coincidence that it worked.

Here is detailed description of what I did before this bug happened:
1. First of all my device worked good. Pointer was visible when stylus was used.
2. I've installed chrome-remote-desktop and found that I can't log to X locally anymore because some conflict between gnome and chrome-remote-desktop. (I used https://remotedesktop.google.com/headless/ setup).
3. I've purged chrome-remote-desktop and found this bug. Pointer of mouse became independent and stylus pointer isn't visible anymore in programs (firefox for example) but visible on desktop as separate cursor or cross.

[Daniel van Vugt (vanvugt)]

That's a little bit obscure. If it takes chrome-remote-desktop to trigger problems then perhaps open a new bug for that, by running:

  ubuntu-bug gnome-shell

Unless other people find this bug is still occurring for them with basic gnome-shell in 20.04...

[Maksim Yu.Semenov (rasmiy)]

Opened new bug: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1898880

[Daniel van Vugt (vanvugt)]

This bug should have expired last year per comment #18. If anyone still experiences similar issues then please open a new bug by running:

  ubuntu-bug gnome-shell

[Gnome-sysadmin (gnome-sysadmin)]

GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org.
As part of that, we are mass-closing older open tickets in bugzilla.gnome.org
which have not seen updates for a longer time (resources are unfortunately
quite limited so not every ticket can get handled).

If you can still reproduce the situation described in this ticket in a recent
and supported software version, then please follow
  https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines
and create a new ticket at
  https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/

Thank you for your understanding and your help.