From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 102004] Graphics renders only random black and white artifacts after boot. GUI mode unusable. Padoka ppa update Aug 1/2017
Date: Tue, 01 Aug 2017 15:31:54 +0000 [thread overview]
Message-ID: <bug-102004-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1058 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=102004
Bug ID: 102004
Summary: Graphics renders only random black and white artifacts
after boot. GUI mode unusable. Padoka ppa update Aug
1/2017
Product: Mesa
Version: git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/radeonsi
Assignee: dri-devel@lists.freedesktop.org
Reporter: lesserbrute@gmail.com
QA Contact: dri-devel@lists.freedesktop.org
Created attachment 133174
--> https://bugs.freedesktop.org/attachment.cgi?id=133174&action=edit
Screen photo just after boot. This is a login screen that works but failed to
display
GUI mode is completely unusable due to massive graphics corruption. Looks like
libllvm5.0 -> libllvm6.0 is the point of failure.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2720 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 reply other threads:[~2017-08-01 15:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-01 15:31 bugzilla-daemon [this message]
2017-08-01 15:35 ` [Bug 102004] Graphics renders only random black and white artifacts after boot. GUI mode unusable. Padoka ppa update Aug 1/2017 bugzilla-daemon
2017-08-01 15:39 ` bugzilla-daemon
2017-08-02 1:50 ` bugzilla-daemon
2018-03-31 22:21 ` 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-102004-502@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.