Commen=
t # 6
on bug 10459=
9
from Mario Kleiner
(In reply to Tapani P=C3=A4lli from comment #4)
> (In reply to Mario Kleiner from comment #3)
> > This is running the new GNOME based Ubuntu GUI with Gnome-Shell W=
ayland,
> > right?
> >=20
> > With "Windows control did not work" you mean it doesn't=
respond to
> > mouse-clicks?
> >=20
> > In that case it is known bugs/limitations in gnome-shell for dept=
h 30/10bpc
> > mode. GNOME Shells picking code can't handle 10 bit per color cha=
nnel.
> >=20
> > Additionally Gnome-Shells Wayland compositor doesn't handle anyth=
ing but
> > bgrx8888 or bgra8888 framebuffers in its drm/kms backend. It take=
s whatever
> > framebuffer format it gets, e.g., bgrx1010102 and hands it to the=
kernel as
> > bgrx8888, so the gpu misinterprets a 10 bit image as a 8 bit imag=
e during
> > scanout, which ends badly.
>=20
> Right, so this is NOTOURBUG. Zebulon, your issue should disappear when=
you
> do apt-get update again since allow_rgb10_configs defaults to 'false'.
>=20
> Mario, do you know if there us existing Gnome bug about this? (did not=
find
> such) Maybe easiest workaround for them would be to ignore 10bpc until
> picking and kms backend is fixed.
None that i would know of. I haven't filed one so far.