All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 101229] Global screen tearing (scrolling, Hz miss-match?)
Date: Tue, 06 Jun 2017 03:51:57 +0000	[thread overview]
Message-ID: <bug-101229-502-17niP31VKN@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-101229-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 908 bytes --]

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

--- Comment #11 from Paul <Paul.Hancock.17041993@live.com> ---
(In reply to Michel Dänzer from comment #10)
> (In reply to Paul from comment #9)
> > it's less obvious, but there still appears to be screen tearing
> 
> How does that manifest, and when you do what?

Use the system and run OpenGL applications, is there an option to enable
triple-buffering or is it enabled by default?

> FWIW, since DRI3 is enabled, "Re-use screen content" is the most efficient
> setting.

I did have this enabled for a while, but plasma got super erratic after I had
launched a game, I'll give it another shot and see if it does it again.

I'm also going to try with 'allow applications to disable composition'
unchecked in case something was disabling the compositor...

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 1863 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2017-06-06  3:51 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-30  6:31 [Bug 101229] Global screen tearing (scrolling, Hz miss-match?) bugzilla-daemon
2017-05-30  7:47 ` bugzilla-daemon
2017-05-30 22:27 ` bugzilla-daemon
2017-05-30 22:28 ` bugzilla-daemon
2017-05-30 22:28 ` bugzilla-daemon
2017-05-30 22:41 ` bugzilla-daemon
2017-05-31  3:30 ` bugzilla-daemon
2017-05-31 22:16 ` bugzilla-daemon
2017-06-01  3:13 ` bugzilla-daemon
2017-06-06  1:06 ` bugzilla-daemon
2017-06-06  1:19 ` bugzilla-daemon
2017-06-06  3:51 ` bugzilla-daemon [this message]
2017-06-06  7:17 ` bugzilla-daemon
2017-09-08 23:43 ` bugzilla-daemon
2017-09-08 23:45 ` bugzilla-daemon
2017-09-09  6:58 ` bugzilla-daemon
2017-09-09  6:59 ` bugzilla-daemon
2017-09-09 16:07 ` bugzilla-daemon
2017-09-09 23:11 ` bugzilla-daemon
2017-09-10  2:41 ` bugzilla-daemon
2019-09-25 17:59 ` 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-101229-502-17niP31VKN@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.