From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 205049] garbled graphics
Date: Tue, 19 Nov 2019 18:05:57 +0000 [thread overview]
Message-ID: <bug-205049-2300-HaXBQQ9VxK@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-205049-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=205049
--- Comment #12 from lechp@onet.pl ---
Is anyone actually working on this problem?
I just upgraded from Fedora 30 to 31, hoping that the upgrade might include
other miscellaneous changes that fix the problem, but the problem is EXACTLY
THE SAME.
Nothing has changed. I'm starting to lose my mind with this chronic lack of
progress.
Support for the Lenovo Ideapad 330 has been been severely broken for at least
the last 6-7 kernel versions!
Can you bisect the people supposedly working on the kernel???
--
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 prev parent reply other threads:[~2019-11-19 18:05 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-30 11:26 [Bug 205049] New: garbled graphics bugzilla-daemon
2019-09-30 11:28 ` [Bug 205049] " 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 [this message]
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-HaXBQQ9VxK@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).