From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 51144] significant pixel corruption in text ; driver nouveau - GF116 [GeForce GTS 450]
Date: Sat, 16 Jun 2012 12:51:03 +0000 [thread overview]
Message-ID: <bug-51144-8800-7NwolpV1NL@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-51144-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
https://bugs.freedesktop.org/show_bug.cgi?id=51144
--- Comment #5 from Basile Starynkevitch <basile-VdE74OAlGqnvXjIo7pOF+l6hYfS7NtTn@public.gmane.org> 2012-06-16 05:51:03 PDT ---
Some pixels are also corrupted perhaps unrelated to text, e.g. in
iceweasel/firefox tab titles.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next prev parent reply other threads:[~2012-06-16 12:51 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-15 23:26 [Bug 51144] New: significant pixel corruption in text bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
[not found] ` <bug-51144-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2012-06-15 23:33 ` [Bug 51144] significant pixel corruption in text ; driver nouveau - GF116 [GeForce GTS 450] bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-06-16 6:28 ` [Bug 51144] significant pixel corruption in text bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-06-16 6:31 ` [Bug 51144] significant pixel corruption in text nouveau - GF116 [GeForce GTS 450] bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-06-16 6:32 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-06-16 6:37 ` [Bug 51144] significant pixel corruption in text ; driver " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-06-16 6:41 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-06-16 10:34 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-06-16 10:34 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-06-16 12:51 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2012-06-17 22:52 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-06-18 5:55 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-06-28 11:00 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-06-28 17:51 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-07-03 8:51 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-07-03 14:47 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-07-03 15:00 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-07-03 15:19 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-07-05 11:52 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-07-12 1:29 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-26 2:52 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-09-27 2:00 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-09-27 5:32 ` 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-51144-8800-7NwolpV1NL@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