All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 16961] New: 3298249d8267c27235653f17379f8c breaks Xv overlay ( display corruption)
Date: Sat,  2 Aug 2008 10:55:43 -0700 (PDT)	[thread overview]
Message-ID: <bug-16961-8800@http.bugs.freedesktop.org/> (raw)

http://bugs.freedesktop.org/show_bug.cgi?id=16961

           Summary: 3298249d8267c27235653f17379f8c breaks Xv overlay
                    (display corruption)
           Product: xorg
           Version: unspecified
          Platform: x86 (IA32)
        OS/Version: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Driver/nouveau
        AssignedTo: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
        ReportedBy: mathieu.berard-S9djqSf+cojYtjvyW6yDsg@public.gmane.org
         QAContact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org


Hi,
Xv overlay has a pretty major display corruption bug which
was bisected down to commit 3298249d8267c27235653f17379f8c
(xv: reformat source so mere mortals can understand it)

Visually I see flashing bands of alternatively greed/purple colors
that seems mixed with the normal image
The corruption the not seems to affect every frame,
It more looks like something like 1 frame over 2 are corrupted, which
visually create a flashing effect.

A (bad) screenshot on a CRT monitor is attached.

The hardware is a NV20 GeForce 2 Ti 500


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

             reply	other threads:[~2008-08-02 17:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-02 17:55 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
     [not found] ` <bug-16961-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2008-08-02 17:57   ` [Bug 16961] 3298249d8267c27235653f17379f8c breaks Xv overlay ( display corruption) bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-08-02 19:43   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-08-02 20:25   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-08-04  5:22   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-08-04 13:12   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-08-05 12:57   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-08-05 21:40   ` 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-16961-8800@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 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.