From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 98146] DRI_PRIME=1 and fullscreen issues
Date: Sun, 25 Jun 2017 06:42:38 +0000 [thread overview]
Message-ID: <bug-98146-502-Uvsudd6RpG@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-98146-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1035 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=98146
--- Comment #20 from Darek Deoniziak <darekdeoniziak@gmail.com> ---
After switching on the same system from Unity, compiz and lightdm to gnome3 and
gdm3, updating drivers (oibaf ppa) the remaining issues are almost gone.
1. I do not notice not drawing content in the windows issue anymore.
2. Tearing is still visible in Steam app, but it is right now just a blink from
time to time, hard to notice.
3. Haven't noticed any other heavy tearing and flickering.
...
Rest points were solved previously. I remember I had a lot of tearing while
playing SeriousSam3 and STALKER (through wine) on DRI_PRIME=1, will have to
check it out again with gnome3 desktop.
If everything will be fine with above, might compiz cause the issues? Or is it
because I've up-to-date LLVM and Mesa drivers?
glxinfo:
Gallium 0.4 on AMD OLAND (DRM 2.43.0 / 4.4.0-81-generic, LLVM 4.0.1)
3.0 Mesa 17.2.0-devel
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1793 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
next prev parent reply other threads:[~2017-06-25 6:42 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-07 15:02 [Bug 98146] DRI_PRIME=1 and fullscreen issues bugzilla-daemon
2016-10-07 15:29 ` bugzilla-daemon
2016-10-07 16:33 ` bugzilla-daemon
2016-10-07 16:34 ` bugzilla-daemon
2016-10-07 16:55 ` bugzilla-daemon
2016-10-07 18:27 ` bugzilla-daemon
2016-10-07 18:46 ` bugzilla-daemon
2016-10-07 19:51 ` bugzilla-daemon
2016-10-07 19:53 ` bugzilla-daemon
2016-10-10 9:12 ` bugzilla-daemon
2016-10-11 7:21 ` bugzilla-daemon
2016-10-11 7:32 ` bugzilla-daemon
2016-10-11 7:41 ` bugzilla-daemon
2016-10-20 19:51 ` bugzilla-daemon
2016-10-20 20:27 ` bugzilla-daemon
2016-10-21 5:33 ` bugzilla-daemon
2016-10-22 16:24 ` bugzilla-daemon
2016-10-22 17:40 ` bugzilla-daemon
2016-10-22 20:52 ` bugzilla-daemon
2016-10-25 6:35 ` bugzilla-daemon
2017-06-25 6:42 ` bugzilla-daemon [this message]
2017-06-25 13:35 ` bugzilla-daemon
2017-07-25 12:33 ` 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-98146-502-Uvsudd6RpG@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).