From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 109548] Seeing visual corruption in totem after installing amdgpu 18.50 in Ubuntu 18.04.1
Date: Tue, 05 Feb 2019 09:00:44 +0000 [thread overview]
Message-ID: <bug-109548-502-Nw4Pnx2G2B@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-109548-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1255 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=109548
Michel Dänzer <michel@daenzer.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
Product|DRI |Mesa
Component|DRM/AMDgpu |Mesa core
Assignee|dri-devel@lists.freedesktop |mesa-dev@lists.freedesktop.
|.org |org
QA Contact| |mesa-dev@lists.freedesktop.
| |org
--- Comment #3 from Michel Dänzer <michel@daenzer.net> ---
Most of the time, if disabling allow_rgb10_configs works around an issue like
this, it's a bug in the application or a higher level library above Mesa.
However, some people are claiming this is a Mesa issue (something about not
(correctly) supporting some VA-API functionality, resulting in the application
using a pixel format that can't work).
It most certainly isn't a kernel driver issue, so reassigning to Mesa for now.
Please attach the output of vainfo when the problem occurs.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2964 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
prev parent reply other threads:[~2019-02-05 9:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-04 23:58 [Bug 109548] Seeing visual corruption in totem after installing amdgpu 18.50 in Ubuntu 18.04.1 bugzilla-daemon
2019-02-04 23:59 ` bugzilla-daemon
2019-02-05 0:04 ` bugzilla-daemon
2019-02-05 9:00 ` bugzilla-daemon [this message]
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-109548-502-Nw4Pnx2G2B@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