#486 [mutter] Mouse cursor offset in GNOME VMs with Wayland (but not X11), due to use of Atomic API | rhbz#2009304
Closed by blockerbot. Opened by blockerbot.

Bug details: ** https://bugzilla.redhat.com/show_bug.cgi?id=2009304 **
Information from BlockerBugs App:
2009304

Current vote summary

Commented but haven't voted yet: frantisekz, geraldosimiao

The votes have been last counted at 2021-10-06 14:07 UTC and the last processed comment was #comment-756671

To learn how to vote, see:
https://pagure.io/fedora-qa/blocker-review
A quick example: BetaBlocker +1 (where the tracker name is one of BetaBlocker/FinalBlocker/BetaFE/FinalFE/0Day/PreviousRelease and the vote is one of +1/0/-1)


My personal take on this is that a mouse cursor which clicks on a different location than I pointed it at is a serious issue. While the offset is small and the desktop mostly works as usual, it is large enough to be noticeable e.g. when selecting text or drawing. I wouldn't want to use such a desktop. Yes, it only occurs in a VM, but we have the same criteria for bare metal and self-hosted VMs. For me, this violates fundamental desktop criteria, e.g. interacting with (mostly any) apps. And it definitely violates basic functionality of all drawing apps.

FinalBlocker +1

FinalBlocker +1

In agreement with kparal, a mouse that clicks elsewhere to where I put it is a big enough issue to warrant blocker status. Seems like it would break basic functionality of many default installed applications.

AGREED AcceptedFinalBlocker

See https://meetbot-raw.fedoraproject.org/fedora-blocker-review/2021-10-04/f35-blocker-review.2021-10-04-16.02.html .

The following votes have been closed:

Fix (mutter-41.0-3.fc35.x86_64) worked fine for me :D

Metadata Update from @blockerbot:
- Issue status updated to: Closed (was: Open)

Release F35 is no longer tracked by BlockerBugs, closing this ticket.

Log in to comment on this ticket.

Metadata