From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 98266] Geforce GTX 960: display corruption under KDE Plasma
Date: Sat, 15 Oct 2016 19:32:32 +0000 [thread overview]
Message-ID: <bug-98266-8800-v2AonCUUnf@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-98266-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
[-- Attachment #1.1: Type: text/plain, Size: 500 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=98266
--- Comment #4 from Pablo Cholaky <waltercool-t2+aMKSqnzM@public.gmane.org> ---
(In reply to Pablo Cholaky from comment #3)
> I think this is related with all Maxwell2 cards. I have a 980m, and I also
> have a lot of artifacts on screen, and the mouse have a weird delay.
My bad, I meant a weird UI refresh delay for mouse.
--
You are receiving this mail because:
You are the assignee for the bug.
You are the QA Contact for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1360 bytes --]
[-- Attachment #2: Type: text/plain, Size: 154 bytes --]
_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/nouveau
next prev parent reply other threads:[~2016-10-15 19:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-14 18:49 [Bug 98266] New: Geforce GTX 960: display corruption under KDE Plasma bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
[not found] ` <bug-98266-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2016-10-14 18:52 ` [Bug 98266] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-10-15 3:57 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-10-15 19:31 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-10-15 19:32 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2016-10-17 2:09 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-10-26 5:46 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
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-98266-8800-v2AonCUUnf@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon-cc+yj3umiyqdupfqwhejaq@public.gmane.org \
--cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.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).