Bug 1879303
| Summary: | Duplicate cursor when using Wacom tablet in Wayland | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Henrique Campos <henriquecamposrj> | ||||||||
| Component: | mutter | Assignee: | Florian Müllner <fmuellner> | ||||||||
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
| Severity: | unspecified | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | 33 | CC: | contact.matti, fmuellner, gnome-sig, jadahl, otaylor, peter.hutterer, philip.wyett, walters | ||||||||
| Target Milestone: | --- | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | x86_64 | ||||||||||
| OS: | Linux | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2021-11-30 19:01:51 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: | |||||||||||
| Attachments: |
|
||||||||||
Also affects Fedora 34.
> the mouse's cursor gets images from tablet cursor
To reproduce:
1. Open Firefox with MOZ_ENABLE_WAYLAND=1
2. Move mouse pointer over text for it to become the "text selection cursor"
3. Hover tablet cursor over some other part of the page
Actual results: two cursors that share the icon of the tablet cursor. Moving the mouse pointer makes both flicker between the two icons.
Expected results: only the cursor last moved would show up (or maybe both if moved simultaneously, in which case their icons should be independent (which sounds app-specific).
Created attachment 1802263 [details]
The invisible cursor can keep things focused
Created attachment 1802270 [details]
Two cursors confuse apps to no end
I'd like to add that making inactive cursors invisible isn't enough to prevent confusing apps. In these two pictures you can see why either one should de-spawn while the other is in use:
"The invisible cursor can keep things focused" shows the tablet cursor keeping the Dash to Dock dock open, even though the dock should close due to the focused calendar window on top of it. Similar effects can be reproduced with a plethora of apps, this being the most annoying one to me personally.
"Two cursors confuse apps to no end" shows the Draw on Your Screen extension getting confused by the two cursors, making it impossible to drawn on the screen using the tablet pen (though drawing with the mouse cursor works as expected). This makes a case for de-spawning the mouse cursor while the tablet pen is being used, as all apps aren't built to handle multiple cursors.
Requesting review from Peter Hutterer: do these qualify for "specific examples of bugs"?
I recommend filing this issue in the upstream gitlab instance, it has a higher chance of being seen by the respective developers there: https://gitlab.gnome.org/GNOME/mutter/ > When tablet is in use has two cursors on screen, one for the mouse and another for the tablet (that cursor only show when tablet is in use), in Gnome Shell interface the cursor becomes a cross and in the interface of krita that cursor becomes invisible after the resize. This sounds like a bug. I would accept this for a in-screen tablet (since the cursor is underneath the pen) but not for an external tablet where the cursor is needed to determine where it is. Same with the cursor focus issue, there's clearly something missing in mutter to handle this correctly. Having two separate cursors however was a conscious decision by the GNOME team - presumably with the assumption that users don't use mice and tablets at the same time. It sounds like some of the issues you have are caused by this but this wouldn't work even if both shared the same cursor. So my guess is that the last issue is less likely to be fixed. Either way, it's also unlikely to get fixed here in bugzilla, please do get involved with upstream GNOME in GitLab, Fedora will pick up any changes through the normal release procedures. This message is a reminder that Fedora 33 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '33'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 33 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. This message is a reminder that Fedora 33 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '33'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 33 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. This message is a reminder that Fedora 33 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '33'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 33 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 33 changed to end-of-life (EOL) status on 2021-11-30. Fedora 33 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. |
Created attachment 1715004 [details] Video recorded by native gnome sreen recorder (Shift+Ctrl+Alt+R); shows the bug Description of problem: I have a Wacom pen-tablet and a mouse both pluged into my machine. When start a Gnome Wayland session I get two cursors using the tablet, and the mouse's cursor gets images from tablet cursor, except the cross image (that one show in Gnome Shell interface,in windows aplications has normal cursors images). And when I resize Krita whith shortcut keys the tablet's cursor becomes invisible in this aplication window (in Shell interface and another aplications windows still visible) and only show the cursor on canvas. To make the cursor visible again, open another aplication click on it and go back to krita. Version-Release number of selected component: #1 OS: Fedora 33.20200914.n.0 (Silverblue Prerelease) ; Gnome 3.37.90 ; #2 OS: Fedora 32.20200824.0 (Silverblue) Gnome 3.36.5 ; Krita is a flatpak from Flathub, version 4.3.0; How reproducible: 100% reproducible in all attempts Steps to Reproduce: 1. Plug a Wacom tablet and a mouse to the same macine 2. Log into a Gnome Wayland session 3. Use the tablet in Gnome Shell interface 4. Open a Krita project 5. Resize Krita window with the shortcut keys (super + up or down) 4. Use the tablet in Krita interface Actual results: When tablet is in use has two cursors on screen, one for the mouse and another for the tablet (that cursor only show when tablet is in use), in Gnome Shell interface the cursor becomes a cross and in the interface of krita that cursor becomes invisible after the resize. Expected results: When tablet is in use have only one cursor on screen, when stop to use a tablet that cursor still where stop and become the mouse cursor (like Gnome Xorg session's behavior),and that cursor don't become invisible in krita interface when resize the windows and in Gnome Shell interface have a normal cursor image. Additional data: One by Wacom, tablet model:CTL-472 PS: this same bug was found in a past version (Bug ID 1683844), but it was closed by EOL and I'm not able to reopen that report.