Authentication-Results: mail-b.sr.ht; dkim=pass header.d=protonmail.ch header.i=@protonmail.ch
Received: from mail-40137.protonmail.ch (mail-40137.protonmail.ch [185.70.40.137])
	by mail-b.sr.ht (Postfix) with ESMTPS id BE2E011EFF3
	for <~eliasnaur/gio@lists.sr.ht>; Mon, 22 Feb 2021 14:17:11 +0000 (UTC)
Date: Mon, 22 Feb 2021 14:16:52 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.ch;
	s=protonmail; t=1614003430;
	bh=2w/ALOrRiZPJbDNmrumJdcO8XgOnKoCv8mtadMqjN14=;
	h=Date:To:From:Reply-To:Subject:In-Reply-To:References:From;
	b=EeiiVDTdB/bSPZCugQWwZrkwOdSWnTMxdvSmpedmk6lyiy3ggMwse+o1RRN7q4xET
	 SAdQy3llzMScd2bF8qAEZPcxNvxO6/EJjl4DnfZo1xs0v3ETUib5VTTwHeiaGvUKZd
	 64fwRmByL0jcHJncm+5EJs6++SjbVG1zXVx1Uh+A=
To: "~eliasnaur/gio@lists.sr.ht" <~eliasnaur/gio@lists.sr.ht>
From: Loki Verloren <stalker.loki@protonmail.ch>
Reply-To: Loki Verloren <stalker.loki@protonmail.ch>
Subject: Re: bogus destroy event caused by maximizing on linux ubuntu 20.10
Message-ID: <Cuwzf-AJ-RgMGPVDQmfjphZh-vPJJJxYZYY7FwUf_hB4YDWxzCSJpHUF_P5vnJ_GX8wJsZxofpEp8O1LYHPEf_46TxKIJeuXlf5AAxCRRNw=@protonmail.ch>
In-Reply-To: <VFXQR7IKLHCz14bpDEh0GoV1ADKa0VbDTVAJNzVUl9hXh3nlBU83d5oFuGg2zHkJXfqBqaQGGwKmWChhdj-mACojNHrsCA2QeeDBuoq-2i4=@protonmail.ch>
References: <Z7CG0iAUXdUQQfyjiT0Obo4ZGBub4fEgDxm2wkiAIKsmLoR1_lSwDtCFpxZqRU7ry4DmNN-eKSyLjZ7ftTCxBJslfWnv73w2Mkm8rkkE8yU=@protonmail.ch> <C99YB8QTL41E.2FOAG9HPZYD39@themachine> <VFXQR7IKLHCz14bpDEh0GoV1ADKa0VbDTVAJNzVUl9hXh3nlBU83d5oFuGg2zHkJXfqBqaQGGwKmWChhdj-mACojNHrsCA2QeeDBuoq-2i4=@protonmail.ch>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-Spam-Status: No, score=-1.2 required=10.0 tests=ALL_TRUSTED,DKIM_SIGNED,
	DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM shortcircuit=no
	autolearn=disabled version=3.4.4
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on
	mailout.protonmail.ch


 I have discovered that wayland in general is a pointless thing for most us=
ers
 currently due to nvidia lack of support, and so I iterated through some
 alternative nvidia driver versions to see if the bug had to do with the dr=
iver.
 Sure enough, "NVIDIA Server Driver metapackage from nvidia-driver-450-serv=
er"
 does not have this bug \o/ w00t!

 Since anyway most of the users will be running on windows which is fine (a=
nd
 great work eliminating the dependencies for it!), now just a note for nvid=
ia
 drivers on linux to suggest for 10 series use that driver as it has no iss=
ues
 and there is a known issue of 460 and 4k displays and windows taller than,
 not sure but I can guess it's 1080.