Description of problem:
Some Gnome applications, such as Totem, Cheese, and Maps, are not working properly on AMD cards. Supposedly, the problem is caused by a missing support for 10-bit depth RGB colours as described in bug #1560481, because cogl/clutter does not support it.
According to https://bugzilla.gnome.org/show_bug.cgi?id=795748, cogl/clutter neither does support rgb10 nor will do it in the future because it is in deep maintenance mode.
The problem has been workarounded by switching off the rgb10 support in the Mesa library to unblock a release blocker for Fedora 28. Now, it is switched off.
However, the feature should not remain switched off. It should be enabled for people who want to use it, so the situation with those Gnome application would be great to fix until Fedora 29.
I am proposing this bug as a blocker for Fedora 29 and also as a Prioritized Bug in order to track it properly, so that it gets good care in the upcoming time.
Version-Release number of selected component (if applicable):
Fedora 28 Beta
Always in Fedora 28 Beta
Steps to Reproduce:
1. Install Fedora Workstation 28 Beta
2. Log onto Gnome session
3. Run Totem, Maps, Cheese ...
The above mentioned applications are not responsive because of the described missing support.
The application should either override the rgb10 feature and stay responsive or, for the better, they should make use of the rgb10 feature.
The rgb10 support should be switched ON in Fedora 29.
Proposed as a Blocker for 29-beta by Fedora user lruzicka using the blocker tracking app because:
The bug affects using the functionality of Totem and other Gnome apps. Although workarounded, the functionality should be introduced back into Fedora.
Bugs were also reported upstream for Totem, Cheese and Maps, so that their developers could think how they will deal with that.
I don't see any grounds on which this currently constitutes a Beta blocker. It's only violating the criteria if the apps aren't working. So long as the issue is worked around, it's not breaking the release criteria. Of course it'd be nice to fix things 'properly', but we don't have to block the Beta on it, IMO.
I don't understand enough about exactly where there should be rgb8 to 10 conversion to support legacy 8 bit per channel programs, so that all apps can just work. I know this has been done some time ago on Windows and a bit more recently on macOS, and they did account for legacy programs. For sure the programs that want 10 bit per channel precision should get access and can't remain at a lower precision indefinitely.
Instead of using blocker process, I suggest gathering all the relevant bugs with a summary, and put it into a Workstation WG ticket.
CCing Mesa and Workstation folks: basically what we want to keep track of here is that things stay in sync. The 10-bit support should ultimately be re-enabled in mesa, but only when the apps that were broken by enabling it have been fixed to work with it. So, trying to make sure everyone's on this bug.
(In reply to Adam Williamson from comment #5)
> CCing Mesa and Workstation folks: basically what we want to keep track of
> here is that things stay in sync. The 10-bit support should ultimately be
> re-enabled in mesa, but only when the apps that were broken by enabling it
> have been fixed to work with it. So, trying to make sure everyone's on this
So a brief discussion with various people at the GNOME perf hackfest this week they've indicated it's likely a bug/issue in mesa so will probably have to be fixed there, just noting that here for reference before I forget.
Discussed during the 2018-05-14 blocker review meeting: 
The decision to classify this bug as an RejectedBlocker was made:
"As things stand, nothing is broken for F29 Beta. There is no blocker bug here. If the 10-bit support is reintroduced in Mesa without affected applications being fixed, we will revisit this."
Rejected as a PrioritizedBug. We have a workaround in place and there are several upstream changes that need to land before this can be addressed in Fedora.
This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. 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 '28'.
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 28 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 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 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
Thank you for reporting this bug and we are sorry it could not be fixed.