From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 97796] Parts of screen do not update Date: Thu, 15 Sep 2016 16:19:30 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1896724086==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [IPv6:2610:10:20:722:a800:ff:fe98:4b55]) by gabe.freedesktop.org (Postfix) with ESMTP id 9EC926E8E1 for ; Thu, 15 Sep 2016 16:19:30 +0000 (UTC) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============1896724086== Content-Type: multipart/alternative; boundary="14739563701.DDde80E.1681"; charset="UTF-8" --14739563701.DDde80E.1681 Date: Thu, 15 Sep 2016 16:19:30 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated https://bugs.freedesktop.org/show_bug.cgi?id=3D97796 --- Comment #6 from Uli Schlachter --- By default awesome uses a visual with depth=3D32 for all of its windows. AF= AIK (someone who can reproduce this, please test), starting awesome with the --no-argb argument (=3D use the root window's visual) makes these problems = go away. Also, AFAIK all kinds of screenshots show the correct data. Oh and once upon a time (but couldn't reproduce) I saw Xephyr having this problem, but moving the mouse pointer across the affected area of the taskl= ist made the expected/real content visible (at least for the part that the mouse pointer touched). I have no clue about the server, but this sounds like software cursor "fixing" things? Also, I could be mixing several different bugs which just have similar resu= lts. At least the depth=3D32 might be a useful hint. Paul, do you know if --no-argb works around these problems for you? --=20 You are receiving this mail because: You are the assignee for the bug.= --14739563701.DDde80E.1681 Date: Thu, 15 Sep 2016 16:19:30 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated

Comment= # 6 on bug 97796<= /a> from Uli Schlachter 
By default awesome uses a visual with depth=3D32 for all of it=
s windows. AFAIK
(someone who can reproduce this, please test), starting awesome with the
--no-argb argument (=3D use the root window's visual) makes these problems =
go
away. Also, AFAIK all kinds of screenshots show the correct data.

Oh and once upon a time (but couldn't reproduce) I saw Xephyr having this
problem, but moving the mouse pointer across the affected area of the taskl=
ist
made the expected/real content visible (at least for the part that the mouse
pointer touched). I have no clue about the server, but this sounds like
software cursor "fixing" things?

Also, I could be mixing several different bugs which just have similar resu=
lts.
At least the depth=3D32 might be a useful hint.
Paul, do you know if --no-argb works around these problems for you?

You are receiving this mail because:
  • You are the assignee for the bug.
= --14739563701.DDde80E.1681-- --===============1896724086== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg== --===============1896724086==--