From debbugs-submit-bounces@debbugs.gnu.org Mon Sep 16 10:57:37 2019 Received: (at 36924) by debbugs.gnu.org; 16 Sep 2019 14:57:37 +0000 Received: from localhost ([127.0.0.1]:50789 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1i9sRa-000878-IA for submit@debbugs.gnu.org; Mon, 16 Sep 2019 10:57:34 -0400 Received: from mout02.posteo.de ([185.67.36.142]:54557) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1i9sRX-00086s-Mi for 36924@debbugs.gnu.org; Mon, 16 Sep 2019 10:57:32 -0400 Received: from submission (posteo.de [89.146.220.130]) by mout02.posteo.de (Postfix) with ESMTPS id BAE162400FF for <36924@debbugs.gnu.org>; Mon, 16 Sep 2019 16:57:25 +0200 (CEST) Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 46X8VD1YV3z9rxK; Mon, 16 Sep 2019 16:57:23 +0200 (CEST) From: L p R n d n To: Andreas Enge Subject: Re: bug#36924: Mesa/GDM/XFCE References: <87tvawzlvq.fsf@elephly.net> <20190912095430.GA1559@jurong> <874l1hpwti.fsf@gnu.org> <20190916094454.GA1265@jurong> Date: Mon, 16 Sep 2019 16:57:21 +0200 In-Reply-To: <20190916094454.GA1265@jurong> (Andreas Enge's message of "Mon, 16 Sep 2019 11:44:54 +0200") Message-ID: <878sqoe1bi.fsf@lprndn.info> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Spam-Score: -1.6 (-) X-Debbugs-Envelope-To: 36924 Cc: 36924@debbugs.gnu.org, Ludovic =?utf-8?Q?Court=C3=A8s?= X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -2.6 (--) Hello, Andreas Enge writes: > Hello, > > On Thu, Sep 12, 2019 at 01:40:09PM +0200, Ludovic Court=C3=A8s wrote: >> Thanks for the report, Andreas! > > and thanks for the time spent putting me on the good track! > >> Andreas Enge skribis: >> > xfwm4: ../mesa-19.1.4/src/mesa/drivers/dri/i965/intel_mipmap_tree.c:12= 93: >> intel_miptree_match_image: Zusicherung =C2=BBimage->TexObject->Target = =3D=3D >> mt->target=C2=AB nicht erf=C3=BCllt. >> That=E2=80=99s the likely root cause to me (in which case it may be unre= lated to >> this , after all.) >> I found these bug reports: >> https://bugs.freedesktop.org/show_bug.cgi?id=3D107117 >> https://bugzilla.redhat.com/show_bug.cgi?id=3D1678334 >>=20 >> In both cases, Xfce and Mesa=E2=80=99s i965 drivers are involved, as is = the case >> on your machine. The 2nd bug report includes an xfwm4 patch, even. > > The first one also contains a patch, but it has been integrated into later > mesa releases, in particular the one we are using. > >> I wonder if Xfce before the recent updates (so before >> 8549e0ca6fd68a57253471436de49b88b2d47e64) works better. >> Andreas, if you feel like it, could you try: >> guix pull --commit=3D97ce5964fb5d52cf2151fea685e28fa23a98b264 >> sudo guix system reconfigure =E2=80=A6 > > Indeed, the problem disappears with this commit; I can log in and out > and in again with xfce working. So I am cc-ing the author of the commits > updating xfce, maybe they have an answer! It seems some bugs have been introduced in xfwm4 between 4.12 and 4.14. (All issues previously linked are for >=3D4.13 wich was the dev version of 4.14). I found https://forum.xfce.org/viewtopic.php?id=3D13233 which seems interesting. Please let us know if it changes anything. I don't know what would be the correct way to deal with the problem in guix though. > And I will try to look at the patch in the second report you reference > above. > > Thanks! > > Andreas Have a nice day, L p r n d n