After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 795748 - Totem has problems with AMD cards (clutter does not support HDR colors /rgb10/).
Totem has problems with AMD cards (clutter does not support HDR colors /rgb10/).
Status: RESOLVED OBSOLETE
Product: cogl
Classification: Platform
Component: GL
1.22.x
Other Linux
: Normal normal
: ---
Assigned To: Cogl maintainer(s)
Cogl maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2018-05-02 09:51 UTC by Lukáš Růžička
Modified: 2021-06-10 11:19 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Lukáš Růžička 2018-05-02 09:51:19 UTC
When you try to run Totem on a computer using an AMD graphic card, the application starts, but fails to respond to controlling buttons and looks like a frozen application, although it is not frozen. Alternatively, it starts but is unable to create a main window at all. The problem was discussed in this bug here https://bugzilla.redhat.com/show_bug.cgi?id=1560481, where you can find more info.

To highlight at least some if the findings. It has been identified, that the AMD cards now support HDR colours (rgb10) which causes some application to behave in a weird way. The problem has been located to clutter (Comment 26 of the RHBZ) and a temporary solution was proposed in Comment 33 detto. The solution worked and the support could be switched off. After that, Totem is working without issues.

In one of the meetings, Matthias Clasen stated: "... the only clutter we care about is the one inside mutter. Anything else using clutter is living on borrowed time."

However, we would like to support these features (HDR colours) in Fedora 29 and core applications, such as Totem, should be ready for this step.
Comment 1 Bastien Nocera 2018-05-02 09:54:30 UTC
Nothing I can do in totem either for now.
Comment 2 Lukáš Růžička 2018-05-02 10:14:32 UTC
Hello Bastien,
can you please provide a more detailed info on this?

* Why is, you cannot do anything about it for Totem?
* Will it be possible to do anything about it in the future? If yes, when?

I think that it is highly important for us, the Fedora QA Team, that Totem works as expected with rgb10 flag on, because Totem is a release blocking feature for Fedora and we do not want to switch off the rgb10 support for everybody on a long term basis.
Comment 3 Emmanuele Bassi (:ebassi) 2018-05-02 11:03:51 UTC
Totem is not involved in choosing the visual, so it cannot do anything.

Additionally Cogl/Clutter are in deep maintenance mode, and won't support 10-bit depth RGB visuals.

It should be possible to allow Cogl to discard a 10 bit depth visual when creating a GL context, and I'll gladly review the patch for it, as I don't have the hardware capable of returning such a visual.

Alternatively, somebody could port Totem away from Clutter and Clutter-GTK, and use the gtksink GStreamer element. Of course, that is a larger piece of work, and won't really happen on a stable branch.

(Re-assigning to Cogl, which is the component in charge of creating the GL context for Clutter)
Comment 4 Jonas Ådahl 2018-05-02 11:29:39 UTC
Changing cogl to ignore rgb10 configs didn't actually help though. I don't know if there are more things to fix, or if mesa is broken is some way, but just doing that was not enough. As far as I could tell, I selected the same glconfig as if no rgb10 configs were advertised.

See patch on https://bugzilla.redhat.com/show_bug.cgi?id=1560481 for the change that ignored rgb10 configs.
Comment 5 Lukáš Růžička 2018-05-02 12:33:23 UTC
(In reply to Jonas Ådahl from comment #4)
> Changing cogl to ignore rgb10 configs didn't actually help though. I don't
> know if there are more things to fix, or if mesa is broken is some way, but
> just doing that was not enough. As far as I could tell, I selected the same
> glconfig as if no rgb10 configs were advertised.
> 
> See patch on https://bugzilla.redhat.com/show_bug.cgi?id=1560481 for the
> change that ignored rgb10 configs.

I am aware of the original bug 1560481. We were told that clutter will not support the rgb10 features, but we'd like to have them available in Fedora 29. There will be problems when features we want will break apps we want.
Comment 6 Emmanuele Bassi (:ebassi) 2018-05-02 13:17:58 UTC
(In reply to Jonas Ådahl from comment #4)
> Changing cogl to ignore rgb10 configs didn't actually help though. I don't
> know if there are more things to fix, or if mesa is broken is some way, but
> just doing that was not enough. As far as I could tell, I selected the same
> glconfig as if no rgb10 configs were advertised.
> 
> See patch on https://bugzilla.redhat.com/show_bug.cgi?id=1560481 for the
> change that ignored rgb10 configs.

Clutter-GTK has the additional messy interaction between:

 - which windowing system you're running under (x11, wayland)
 - which Clutter windowing system backend you're using (x11, wayland, gdk)

and the fact that, under X11, GDK preselects and caches GLX visuals, and Clutter needs to reuse the same GDK visual everywhere to avoid more breakage.

Under Wayland and GDK we can, at least, rely on EGL, but more things can utterly break in there as well.
Comment 7 André Klapper 2021-06-10 11:19:29 UTC
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org.
As part of that, we are mass-closing older open tickets in bugzilla.gnome.org
which have not seen updates for a longer time (resources are unfortunately
quite limited so not every ticket can get handled).

If you can still reproduce the situation described in this ticket in a recent
and supported software version of cogl, then please follow
  https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines
and create a ticket at
  https://gitlab.gnome.org/GNOME/cogl/-/issues/

Thank you for your understanding and your help.