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 28152] New: corruption in FVWM window decorations
Date: Mon, 17 May 2010 22:07:42 -0700 (PDT)	[thread overview]
Message-ID: <bug-28152-8800@http.bugs.freedesktop.org/> (raw)

https://bugs.freedesktop.org/show_bug.cgi?id=28152

           Summary: corruption in FVWM window decorations
           Product: xorg
           Version: git
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Driver/nouveau
        AssignedTo: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
        ReportedBy: nbowler-m3eOHSKbYRSw5LPnMra/2Q@public.gmane.org
         QAContact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org


Created an attachment (id=35718)
 --> (https://bugs.freedesktop.org/attachment.cgi?id=35718)
Screenshot (incorrectly rendered)

On an AGP fx5700 (NV36) card, I'm experiencing rendering glitches in FVWM's
window decorations on nouveau.  The artifacts are completely consistent:
exactly the same glitches occur on every single window.

These glitches do not occur with other drivers, and I'm certain they didn't
occur in nouveau last time I tried it (but this was well over a year ago).

Attaching screenshots since pictures say 1000 words.

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

             reply	other threads:[~2010-05-18  5:07 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-18  5:07 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
     [not found] ` <bug-28152-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2010-05-18  5:08   ` [Bug 28152] corruption in FVWM window decorations bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-05-18  5:09   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-05-18  5:12   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-18 18:10   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-18 18:29   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-18 18:33   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-18 19:22   ` [Bug 28152] [NV36] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-20 17:11   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-21  5:39   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-21  6:06   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-09-02  7:09   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-09-04 15:29   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-08-21 19:58   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-12-04  8:24   ` 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-28152-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.