Bug#837786: mutter: Issues repainting the display on mouse movement

[John M.]

Since Wednesday, I've done as follows:
- Upgraded to mutter 3.21.91-2 and gnome-shell 3.21.91-1
(repaint/redraw issues).
- Tried to report the bug, but reportbug showed a version of mutter in
unstable.
- Upgraded to mutter 3.31.92-1 and gnome-shell 3.21.92-1
(repaint/redraw issues).
- Reported the bug.
- Downgraded to mutter 3.20.3-2 and gnome-shell 3.20.3-1 using dpkg and
/var/cache/archives.
- Upgraded to mutter 3.21.91-2 and gnome-shell 3.21.91-1 again
(repaint/redraw issues)
- Tried some DRI suggestions from ArchWiki, but none of them solve the
issue.
- Downgraded to mutter 3.20.3-2 and gnome-shell 3.20.3-1 using dpkg and
/var/cache/archives.
- Upgraded to mutter 3.21.91-2 and gnome-shell 3.21.91-1 again
(repaint/redraw issues)
- Tried disabling some files in modprobe, but it doesn't seem to solve
the issue.
- Downgraded to mutter 3.20.3-2 and gnome-shell 3.20.3-1 using dpkg and
/var/cache/archives.

So the problem is always reproducible.

--
John.




> Am 14.09.2016 um 17:16 schrieb JWM:
> 
> > > > After upgrading my system this morning and restarting a new gnome-
shell session
> > > > (by rebooting), everything being displayed fails to repaint
properly.
> > 
> > > > Everytime I launch an application and try to move the window it
leaves traces
> > > > (i.e., shadows of its previous positions). The same happens on
mouse hover.
> > 
> > > > Also, the clock (on the top desktop) flickers
constantly.  Something similar
> > happens with the title bar in certain applications (e.g., vivaldi).
> > 
> > > > Since the only packages upgraded were related to mutter and gnome-
shell, I
> > figure the one to blame is mutter.
> > 
> 
> 
> > Can you downgrade mutter to 3.21.91-2 (from testing), reboot and test
if
> the problem is reproducible?
> 
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-gnome-maintainers/attachments/20160917/bdd1cd14/attachment.html>