From mboxrd@z Thu Jan 1 00:00:00 1970
From: bugzilla-daemon@freedesktop.org
Subject: [Bug 73444] wayland/weston EGL/GLESv2 - top portion of screen in
fullscreen: vertices being clipped/flicker
Date: Fri, 10 Jan 2014 02:12:57 +0000
Message-ID:
References:
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="===============1654139091=="
Return-path:
Received: from culpepper.freedesktop.org (unknown [131.252.210.165])
by gabe.freedesktop.org (Postfix) with ESMTP id 9624E106A05
for ;
Thu, 9 Jan 2014 18:12:57 -0800 (PST)
In-Reply-To:
List-Unsubscribe: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
Sender: dri-devel-bounces@lists.freedesktop.org
Errors-To: dri-devel-bounces@lists.freedesktop.org
To: dri-devel@lists.freedesktop.org
List-Id: dri-devel@lists.freedesktop.org
--===============1654139091==
Content-Type: multipart/alternative; boundary="1389319977.bD2f70.29211"; charset="us-ascii"
--1389319977.bD2f70.29211
Date: Fri, 10 Jan 2014 02:12:57 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
https://bugs.freedesktop.org/show_bug.cgi?id=3D73444
--- Comment #1 from Michel D=C3=A4nzer ---
(In reply to comment #1)
> 12:30 < pq> so if super+s, or zoom, or having it in a window makes the
> problem go away, then the fundamental difference is likely that when west=
on
> composites, everything goes well, but when weston tries to scan out the
> client image directly, something breaks.
Yes, it sounds like when weston tries to scan out the client surfaces direc=
tly,
you're intermittently seeing the wrong surface being scanned out, or the ri=
ght
surface at the wrong time.
--=20
You are receiving this mail because:
You are the assignee for the bug.
--1389319977.bD2f70.29211
Date: Fri, 10 Jan 2014 02:12:57 +0000
MIME-Version: 1.0
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Comment=
# 1
on bug 73444<=
/a>
from Michel D=C3=A4nzer
(In reply to comment #1=
)
> 12:30 < pq> so if super+s, or zoom, or hav=
ing it in a window makes the
> problem go away, then the fundamental difference is likely that when w=
eston
> composites, everything goes well, but when weston tries to scan out the
> client image directly, something breaks.
Yes, it sounds like when weston tries to scan out the client surfaces direc=
tly,
you're intermittently seeing the wrong surface being scanned out, or the ri=
ght
surface at the wrong time.
You are receiving this mail because:
=20=20=20=20=20=20
- You are the assignee for the bug.
--1389319977.bD2f70.29211--
--===============1654139091==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
--===============1654139091==--