Bug 1823678
| Summary: | Tiled (usually 5k) monitors doesn't work properly | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Jonas Ådahl <jadahl> |
| Component: | mutter | Assignee: | Jonas Ådahl <jadahl> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 32 | CC: | awilliam, bcotton, carl, fmuellner, gmarr, gnome-sig, hdegoede, jadahl, lruzicka, otaylor, philip.wyett, sgallagh, walters |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | AcceptedFreezeException | ||
| Fixed In Version: | mutter-3.36.1-5.fc32 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-04-23 18:02:38 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: | 1705306 | ||
|
Description
Jonas Ådahl
2020-04-14 09:09:48 UTC
Attempted fix: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1199 Scratch build available at https://koji.fedoraproject.org/koji/taskinfo?taskID=43379125 (In reply to Jonas Ådahl from comment #2) > Scratch build available at > https://koji.fedoraproject.org/koji/taskinfo?taskID=43379125 Hans, could you check that this build doesn't break anything with a panel orientation? (In reply to Jonas Ådahl from comment #3) > Hans, could you check that this build doesn't break anything with a panel > orientation? Just tested this, works fine for me, including using an external (unrotated) monitor. Thank you for checking with me that this did not break. (In reply to Hans de Goede from comment #4) > (In reply to Jonas Ådahl from comment #3) > > Hans, could you check that this build doesn't break anything with a panel > > orientation? > > Just tested this, works fine for me, including using an external (unrotated) > monitor. > > Thank you for checking with me that this did not break. The merge request is verified to fix the immediate issue, but was not complete, thus I gave it a second try to fix more edge cases. Could you sanity test this as well? Scratch build available here: https://koji.fedoraproject.org/koji/taskinfo?taskID=43397439 Proposed as a Freeze Exception for 32-final by Fedora user jadahl using the blocker tracking app because: High end 5K monitors sometimes are constructed as multiple display panels "tiled" inside a physical monitor. To the operating system they appear as multiple separate monitors with some metadata that tie them together. in GNOME this metadata is constructed to create a single monitor for multiple tiled monitor outputs. This functionality broke with GNOME 3.36, where booting into a system which used such a high end monitor would result in an unusable desktop. Bug 1823678 contains a fix that verified by a bug reporter upstream to fix the issue. An early version of the fix has been verified to not regress on another relatively rare hardware setup that share the same code paths, and it has been regression with a more common hardware setup (laptop and external monitor) tested by me. Note that these high end monitors are rare and usually expensive, but do exist, and we've seen bug reports about them in Fedora in the past. -1 FE for now. It seems like the fix is still in progress and would be better off landing as a post-release update. I might change to +1 FE if the release slips and a fully-formed fix is available. I'm +1 FE as I trust the devs not to send an update till the fix is complete and properly reviewed, they have a good process upstream for this. Of course, if RC 1.3 is approved this can't go in. (In reply to Ben Cotton from comment #7) > -1 FE for now. It seems like the fix is still in progress and would be > better off landing as a post-release update. I might change to +1 FE if the > release slips and a fully-formed fix is available. The upstream fix has been verified and reviewed and is about to land, so it should be considered finished. (In reply to Jonas Ådahl from comment #5) > The merge request is verified to fix the immediate issue, but was not > complete, thus I gave it a second try to fix more edge cases. Could you > sanity test this as well? Scratch build available here: > https://koji.fedoraproject.org/koji/taskinfo?taskID=43397439 I've out this build through the same tests as before, everything still works fine for me. I'm +1 FE for this, but whether it goes in will depend on the Go/No-Go decision tomorrow on RC 1.3 As we were No-Go last week, I am +1 for FE now. FEDORA-2020-beac641efe has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-beac641efe Discussed during the 2020-04-20 blocker review meeting: [0] The decision to classify this bug as an "AcceptedFreezeException" was made as it is a noticeable issue that cannot be fixed with an update. [0] https://meetbot.fedoraproject.org/fedora-blocker-review/2020-04-20/f32-blocker-review.2020-04-20-16.01.txt FEDORA-2020-beac641efe has been pushed to the Fedora 32 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-beac641efe` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-beac641efe See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2020-beac641efe has been pushed to the Fedora 32 stable repository. If problem still persists, please make note of it in this bug report. |