From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 104599] corrupted desktop graphics with latest git intel driver
Date: Tue, 16 Jan 2018 03:49:00 +0000 [thread overview]
Message-ID: <bug-104599-502-wZGbNemuGH@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-104599-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1412 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=104599
--- Comment #6 from Mario Kleiner <mario.kleiner@tuebingen.mpg.de> ---
(In reply to Tapani Pälli from comment #4)
> (In reply to Mario Kleiner from comment #3)
> > This is running the new GNOME based Ubuntu GUI with Gnome-Shell Wayland,
> > right?
> >
> > With "Windows control did not work" you mean it doesn't respond to
> > mouse-clicks?
> >
> > In that case it is known bugs/limitations in gnome-shell for depth 30/10bpc
> > mode. GNOME Shells picking code can't handle 10 bit per color channel.
> >
> > Additionally Gnome-Shells Wayland compositor doesn't handle anything but
> > bgrx8888 or bgra8888 framebuffers in its drm/kms backend. It takes 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 image during
> > scanout, which ends badly.
>
> Right, so this is NOTOURBUG. Zebulon, your issue should disappear when you
> do apt-get update again since allow_rgb10_configs defaults to 'false'.
>
> 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.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2445 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-01-16 3:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-12 12:03 [Bug 104599] corrupted desktop graphics with latest git intel driver bugzilla-daemon
2018-01-12 12:08 ` bugzilla-daemon
2018-01-12 13:01 ` bugzilla-daemon
2018-01-13 3:28 ` bugzilla-daemon
2018-01-15 6:41 ` bugzilla-daemon
2018-01-15 12:03 ` bugzilla-daemon
2018-01-16 3:49 ` bugzilla-daemon [this message]
2019-09-18 19:40 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-104599-502-wZGbNemuGH@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox