From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 28955] New: [r300g]: refresh/update/damage issues using compiz.
Date: Wed, 7 Jul 2010 17:00:05 -0700 (PDT) [thread overview]
Message-ID: <bug-28955-502@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=28955
Summary: [r300g]: refresh/update/damage issues using compiz.
Product: DRI
Version: unspecified
Platform: Other
OS/Version: All
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
AssignedTo: dri-devel@lists.freedesktop.org
ReportedBy: oreaus@gmail.com
Created an attachment (id=36846)
--> (https://bugs.freedesktop.org/attachment.cgi?id=36846)
example
Can reproduce reliably, running any compiz with r300g on rv350. While the
screen is not being damaged (you can see with showrepaint plugin) any change in
a window is not updated until some other window moves in front of it or
animation happens in the area. It used to work a few months ago as far as I can
remember, but I could not find a good commit to bisect with that would build
and wouldn't crash compiz when trying to start it.
Steps to reproduce:
1) Start compiz with r300g on rv350
2) Make sure the screen isn't already being damaged, then click on something in
ccsm or go to a different webpage in a browser or use an irc client with text
scrolling up (a terminal or any other window can also be affected)
3) Observe issue
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2010-07-08 0:00 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-08 0:00 bugzilla-daemon [this message]
2010-07-29 14:15 ` [Bug 28955] [r300g]: refresh/update/damage issues using compiz bugzilla-daemon
2010-07-29 22:38 ` bugzilla-daemon
2010-07-31 7:55 ` bugzilla-daemon
2010-07-31 21:28 ` bugzilla-daemon
2010-08-03 12:40 ` bugzilla-daemon
2010-08-04 6:19 ` bugzilla-daemon
2010-08-06 1:08 ` bugzilla-daemon
2010-08-06 1:18 ` bugzilla-daemon
2010-08-06 2:56 ` bugzilla-daemon
2010-08-06 15:37 ` bugzilla-daemon
2010-08-17 0:34 ` bugzilla-daemon
2010-08-26 23:57 ` bugzilla-daemon
2010-08-26 23:58 ` bugzilla-daemon
2010-08-28 12:02 ` bugzilla-daemon
2010-08-28 13:07 ` bugzilla-daemon
2010-08-28 13:42 ` 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-28955-502@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.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 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.