I'd like to point out that this bug has a similar effect on nvidia graphics as well, as pointed out in the bug report
And their solution was also to generate an xorg.conf file, so I'd guess it's the same bug.
- Cem
On Tue, 25 Jun 2019 09:33:34 +0200 Yves-Alexis Perez <
corsac@debian.org> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> control: affects -1 xserver-xorg-core
>
> On Sat, 2019-06-22 at 17:34 -0400, John Franklin wrote:
> > I've been suffering from this bug in a clean Buster system, too. A
> > solution noted in another bug tracker is to explicitly tell X.org to
> > use the intel driver. Apparently, it uses the fbdev driver by default.
> > (Sorry, I don't have a reference to other bug handy.)
>
> Hi John,
>
> it uses the modesetting DDX driver by default, not fbdev, but it's good to
> know that changing to the intel DDX workarounds the issue.
>
> Regards
> - --
> Yves-Alexis
> -----BEGIN PGP SIGNATURE-----
>
> iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAl0Rzk4ACgkQ3rYcyPpX
> RFsKGggAgv9hw7Cen7bEiCpPU87DniXPvJ+5NsszICoQXal7YBet/RMBpyYSoujo
> 7G32lLpazDO1s+f8TGReCx/JopjLsZgLVxtL6tOCBLFFBzfRTG8HnoQpwJrITwWU
> pPbp3e+shd5I6yKPqdv+ZoBG8Eq58poPgrzJbJXLRN3vMAafChl0C+b/N4NYUBuJ
> HIaz1qkKuoU3ZDtnMdNrIbsfHr/baO9B1Dht5/0TO3WHgd5UIRIuOqNgi4LnJxVF
> QOQJEYtJSWSZdJGVBGhP9/qxAPI69j/NgEYL1L4ITYb5YrDbPNJUbxBBw3G3nG2Z
> 4cbF9eOmWAqn4iD8EfoWA4p/i3fuCQ==
> =XzOA
> -----END PGP SIGNATURE-----
>
>