Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1816761
Summary: | in Wayland VM text is selected from line above pointer | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Jens Petersen <petersen> |
Component: | mutter | Assignee: | Florian Müllner <fmuellner> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 32 | CC: | awilliam, fmuellner, gmarr, gnome-sig, jadahl, jonha87, kparal, otaylor, philip.wyett, robatino, sshedmak, walters |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | AcceptedBlocker | ||
Fixed In Version: | mutter-3.36.1-3.fc32 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2020-04-02 00:31:55 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: | |||
Bug Depends On: | |||
Bug Blocks: | 1705305 |
Description
Jens Petersen
2020-03-24 16:35:59 UTC
Yep, could reproduce the reported problem on a F32 WorkStation KVM box (post a week from 2020-03-10 I18N Test Day) I found the upstream links via this discussion on desktop list: https://lists.fedoraproject.org/archives/list/desktop@lists.fedoraproject.org/thread/IGI7WS4JA24WGLNJU7OVTZCPH5HQ444U/ Jens: you linked a PR. I linked an issue report. The issue report reports this same issue. The PR is the fix for it. There can be more than upstream link :) Note, I did a mutter build yesterday, but didn't include this PR as it is still under review upstream. Proposed as a Blocker for 32-final by Fedora user jonha using the blocker tracking app because: The release must be able host virtual guest instances of the same release. All elements of the default panel (or equivalent) configuration in all release-blocking desktops must function correctly in typical use. Not fixing this would result in bad user experience when installing Fedora in a VM, for example resizing windows is awkward as the resize cursor is offset from the expected position, focusing textboxes inside the installer is also potentially problematic. Discussed during the 2020-03-30 blocker review meeting: [0] The decision to classify this bug as an "AcceptedBlocker" was made as it violates the following criterion: "All elements of the default panel (or equivalent) configuration in all release-blocking desktops must function correctly in typical use" and other desktop criteria when running in a VM using 'seamless mouse pointer' mode (which virt-manager and Boxes use by default). [0] https://meetbot.fedoraproject.org/fedora-blocker-review/2020-03-30/f32-blocker-review.2020-03-30-16.00.txt FEDORA-2020-ed25e0cdcb has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-ed25e0cdcb I believe mutter 3.36.1 (included in the megaupdate) has the fix for this. Jens, can you confirm? Thanks! FEDORA-2020-ed25e0cdcb has been pushed to the Fedora 32 stable repository. If problem still persists, please make note of it in this bug report. Thanks a lot, Adam! I think this issue already improved a bit with your earlier upstream patches (ie it fixed the line offset). Sorry, I think I had misinterpreted https://gitlab.gnome.org/GNOME/mutter/-/issues/1094 as a different issue, apologies. (Because I could only see the problem on text selection.) Yep, with mutter-3.36.1 this looks completely fixed to me, awesome! Thanks as always for going the extra mile on this one too. I really didn't do anything for the megaupdate, just tagged the bug! But thanks anyway :) I can confirm that this problem is fixed now. |