From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 65254] opengl flicker in xbmc / glxgears
Date: Mon, 07 Oct 2013 00:27:27 +0000 [thread overview]
Message-ID: <bug-65254-502-FmUyNvs3KB@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-65254-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 324 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=65254
--- Comment #22 from bgunteriv@gmail.com ---
setting:
"NoAccel" "true"
solves the problem, but the menu is super slow, and with the dual processor,
they both peak at 90-100%
not a solid option.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1066 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2013-10-07 0:27 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-02 2:48 [Bug 65254] New: opengl flicker in xbmc / glxgears bugzilla-daemon
2013-06-02 14:14 ` [Bug 65254] " bugzilla-daemon
2013-06-02 18:37 ` bugzilla-daemon
2013-06-02 18:40 ` bugzilla-daemon
2013-06-02 18:43 ` bugzilla-daemon
2013-06-02 18:44 ` bugzilla-daemon
2013-06-03 14:51 ` bugzilla-daemon
2013-06-03 18:51 ` bugzilla-daemon
2013-06-04 17:13 ` bugzilla-daemon
2013-06-06 2:33 ` bugzilla-daemon
2013-06-09 6:25 ` bugzilla-daemon
2013-06-10 3:59 ` bugzilla-daemon
2013-06-10 17:50 ` bugzilla-daemon
2013-06-10 18:14 ` bugzilla-daemon
2013-08-15 22:04 ` bugzilla-daemon
2013-08-15 22:08 ` bugzilla-daemon
2013-08-16 2:17 ` bugzilla-daemon
2013-08-21 18:06 ` bugzilla-daemon
2013-09-18 8:35 ` bugzilla-daemon
2013-09-21 17:22 ` bugzilla-daemon
2013-10-05 20:48 ` bugzilla-daemon
2013-10-07 0:17 ` bugzilla-daemon
2013-10-07 0:27 ` bugzilla-daemon [this message]
2013-10-07 15:23 ` 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-65254-502-FmUyNvs3KB@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.