From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 205049] New: garbled graphics
Date: Mon, 30 Sep 2019 11:26:01 +0000 [thread overview]
Message-ID: <bug-205049-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=205049
Bug ID: 205049
Summary: garbled graphics
Product: Drivers
Version: 2.5
Kernel Version: 5.2.15-200
Hardware: x86-64
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Video(DRI - non Intel)
Assignee: drivers_video-dri@kernel-bugs.osdl.org
Reporter: lechp@onet.pl
Regression: No
I'm getting severe graphics glitches in the desktop environment (XFCE, Fedora
30, on Lenovo Ideapad 330-15ARR with Ryzen 3), including text, text cursor,
images, buttons and other GUI elements including screen brightness pop-ups.
The annoyance level is severe, and usability is also affected. As can be seen
in the attachment, the output of "uname -a" is partly garbled. In this case I
know roughly what the output should have been, but I would be wary of doing
extensive debugging if I can't trust what I see on the screen.
Some of the errors last for about a second before self-correcting. Others
persist until some activity like clicking on a button with the mouse 'prompts'
the affected area of the display to be refreshed.
How to reproduce:
Normal interaction with D.E. using mouse and keyboard.
Temporary workaround:
Select kernel version 5.1.20x or older when restarting.
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2019-09-30 11:26 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-30 11:26 bugzilla-daemon [this message]
2019-09-30 11:28 ` [Bug 205049] garbled graphics bugzilla-daemon
2019-10-01 13:57 ` bugzilla-daemon
2019-10-07 11:25 ` bugzilla-daemon
2019-10-07 13:21 ` bugzilla-daemon
2019-10-08 10:22 ` bugzilla-daemon
2019-10-08 11:52 ` bugzilla-daemon
2019-10-08 11:58 ` bugzilla-daemon
2019-10-08 13:12 ` bugzilla-daemon
2019-10-12 9:40 ` bugzilla-daemon
2019-10-18 9:36 ` bugzilla-daemon
2019-10-18 13:36 ` bugzilla-daemon
2019-11-19 18:05 ` bugzilla-daemon
2019-11-19 18:16 ` bugzilla-daemon
2019-11-19 20:01 ` bugzilla-daemon
2019-11-21 13:45 ` bugzilla-daemon
2020-01-02 15:29 ` bugzilla-daemon
2020-01-02 15:41 ` 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-205049-2300@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.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.