From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 98964] Chromium complains about glXGetSyncValuesOML in 13.0.2
Date: Tue, 06 Dec 2016 13:20:14 +0000 [thread overview]
Message-ID: <bug-98964-502-rUM39AjjI0@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-98964-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 991 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=98964
--- Comment #13 from Zoltán Böszörményi <zboszor@pr.hu> ---
More details from testing several scenarios:
1. When there is only a single X screen then this line does not appear in the
logs. It does not matter if we have the default mirrored screen configuration
and there is an external VGA monitor attached or not, or if the X Intel driver
is configured in a way to light up only one CRTC.
2. When we use a configuration to create :0.0 and :0.1 with the latter
appearing on the external VGA and Chromium is started on both :0.0 and :0.1,
this glXGetSyncValuesOML complaint is coming from only the one on :0.1
This particular Pineview machine has pipe1 wired to the internal panel and
pipe0 is on the external VGA.
xf86-video-intel is from GIT commit bde946054efbc1c7ae1483b84c3b4fa3c2c7e2ec
SNA is used.
Xorg server version 1.18.4
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1787 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:[~2016-12-06 13:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-02 9:31 [Bug 98964] Chromium complains about glXGetSyncValuesOML in 13.0.2 bugzilla-daemon
2016-12-02 9:32 ` bugzilla-daemon
2016-12-02 19:40 ` bugzilla-daemon
2016-12-03 5:47 ` bugzilla-daemon
2016-12-05 21:58 ` bugzilla-daemon
2016-12-05 22:00 ` bugzilla-daemon
2016-12-06 5:18 ` bugzilla-daemon
2016-12-06 5:39 ` bugzilla-daemon
2016-12-06 12:02 ` bugzilla-daemon
2016-12-06 12:38 ` bugzilla-daemon
2016-12-06 13:20 ` bugzilla-daemon [this message]
2016-12-06 14:45 ` bugzilla-daemon
2019-09-18 19:40 ` 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-98964-502-rUM39AjjI0@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).