Bug#837786: mutter: Issues repainting the display on mouse movement
I confirm, same problem for me; - Even with Gnome 3.22.0 - Nvidia Graphic
Bug#837786: mutter: Issues repainting the display on mouse movement
I confirm, same problem for me; - Even with Gnome 3.22.0 - Nvidia Graphic GTX660 with proprietary drivers
Bug#837786: mutter: Issues repainting the display on mouse movement
Version 3.22.0 (currently from unstable) still affected. Today`s update to Mesa 12.0.3-1 didn`t help. --- I am not familiar with Linux graphic stack. Frames that should not be displayed (because they are few seconds old) are still flickering into current proper frame, seems like framebuffer is not correctly flushed or something like that.
Bug#837786: mutter: Issues repainting the display on mouse movement
On Sun, 18 Sep 2016 15:24:42 +0200 Mourad De Clerck wrote: > Hello, > > another datapoint: I'm experiencing the same issue on an AMD Pitcairn > (7870) using radeonsi. > > -- M > > Hi ! Same here and but I use nvidia-driver (367.44-1). It worked with previous 3.20 version so I downgraded to a snapshot version from 12th of September before the buggy version was migrated to testing. Here is how its done: https://hackedbellini.org/linux/downgrade-and-force-some-packages-on-debian-to-a-previous-version/ Greets
Bug#837786: mutter: Issues repainting the display on mouse movement
Hello, another datapoint: I'm experiencing the same issue on an AMD Pitcairn (7870) using radeonsi. -- M
Bug#837786: mutter: Issues repainting the display on mouse movement
Hi I have run into the same problem. I can't add anything, only video of how it looks like on my system: https://youtu.be/4Fxuzm-FvbE Marek
Bug#837786: mutter: Issues repainting the display on mouse movement
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? > >
Bug#837786: mutter: Issues repainting the display on mouse movement
On Sat, 17 Sep 2016 09:18:45 +0200 Michael Biebl wrote: 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? -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? Versions 3.21.92-1 and 3.21.91-2 are both affected Versions without redraw issues are only 3.20 Downgrade to 3.20 from Debian snapshots helped: gir1.2-mutter-3.0_3.20.3-2_amd64.deb gnome-shell-common_3.20.3-1_all.deb gnome-shell_3.20.3-1_amd64.deb libmutter0h_3.20.3-2_amd64.deb mutter-common_3.20.3-2_all.deb mutter_3.20.3-2_amd64.deb
Bug#837786: mutter: Issues repainting the display on mouse movement
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? -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#837786: mutter: Issues repainting the display on mouse movement
I tried setting the "DRI" option to "false" (and to "2", as suggested by ArchWiki), but the result is the same ---maybe due to the fact that I also have a discrete display (Nvidia Optimus): $ sudo lshw -c video *-display UNCLAIMED description: VGA compatible controller product: GK208M [GeForce GT 730M] vendor: NVIDIA Corporation physical id: 0 bus info: pci@:02:00.0 version: a1 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress vga_controller cap_list configuration: latency=0 resources: memory:f000-f0ff memory:c000-cfff memory:d000-d1ff ioport:3000(size=128) *-display description: VGA compatible controller product: 4th Gen Core Processor Integrated Graphics Controller vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 06 width: 64 bits clock: 33MHz capabilities: msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:32 memory:f100-f13f memory:e000- efff ioport:4000(size=64) memory:c-d Or maybe it's something in my modprobe.d directory: $ for file in `ls`; do echo -e "\n\n#$(pwd)/$file:" >> /tmp/combined.txt; cat $file >> /tmp/combined.txt; done && cat /tmp/combined.txt #/etc/modprobe.d/amd64-microcode-blacklist.conf: # The microcode module attempts to apply a microcode update when # it autoloads. This is not always safe, so we block it by default. blacklist microcode #/etc/modprobe.d/bumblebee.conf: # This file is installed by bumblebee, do NOT edit! # to be used by kmod / module-init-tools, and installed in /etc/modprobe.d/ # or equivalent # do not automatically load nouveau as it may prevent nvidia from loading blacklist nouveau # do not automatically load nvidia as it's unloaded anyway when bumblebeed # starts and may fail bumblebeed to disable the card in a race condition. # Debian blacklist nvidia blacklist nvidia-current blacklist nvidia-legacy-304xx blacklist nvidia-legacy-340xx # Ubuntu blacklist nvidia blacklist nvidia-current blacklist nvidia-current-updates # 304 blacklist nvidia-304 blacklist nvidia-304-updates blacklist nvidia-experimental-304 # 310 blacklist nvidia-310 blacklist nvidia-310-updates blacklist nvidia-experimental-310 # 313 blacklist nvidia-313 blacklist nvidia-313-updates blacklist nvidia-experimental-313 # 319 blacklist nvidia-319 blacklist nvidia-319-updates blacklist nvidia-experimental-319 # 325 blacklist nvidia-325 blacklist nvidia-325-updates blacklist nvidia-experimental-325 # 331 blacklist nvidia-331 blacklist nvidia-331-updates blacklist nvidia-experimental-331 # 334 blacklist nvidia-334 blacklist nvidia-334-updates blacklist nvidia-experimental-334 # 337 blacklist nvidia-337 blacklist nvidia-337-updates blacklist nvidia-experimental-337 # 340 blacklist nvidia-340 blacklist nvidia-340-updates blacklist nvidia-experimental-340 # 343 blacklist nvidia-343 blacklist nvidia-343-updates blacklist nvidia-experimental-343 # 346 blacklist nvidia-346 blacklist nvidia-346-updates blacklist nvidia-experimental-346 # 349 blacklist nvidia-349 blacklist nvidia-349-updates blacklist nvidia-experimental-349 # 352 blacklist nvidia-352 blacklist nvidia-352-updates blacklist nvidia-experimental-352 # 355 blacklist nvidia-355 blacklist nvidia-355-updates blacklist nvidia-experimental-355 # 358 blacklist nvidia-358 blacklist nvidia-358-updates blacklist nvidia-experimental-358 # 361 blacklist nvidia-361 blacklist nvidia-361-updates blacklist nvidia-experimental-361 # 364 blacklist nvidia-364 blacklist nvidia-364-updates blacklist nvidia-experimental-364 #/etc/modprobe.d/dkms.conf: # modprobe information used for DKMS modules # # This is a stub file, should be edited when needed, # used by default by DKMS. #/etc/modprobe.d/i915.conf: options i915 i915_enable_rc6=7 i915_enable_fbc=1 lvds_downclock=1 #/etc/modprobe.d/intel-microcode-blacklist.conf: # The microcode module attempts to apply a microcode update when # it autoloads. This is not always safe, so we block it by default. blacklist microcode #/etc/modprobe.d/nvidia-blacklists-nouveau.conf: # You need to run "update-initramfs -u" after editing this file. # see #580894 blacklist nouveau #/etc/modprobe.d/nvidia.conf: install nvidia modprobe -i nvidia-current $CMDLINE_OPTS install nvidia-modeset modprobe nvidia ; modprobe -i nvidia-current- modeset $CMDLINE_OPTS install nvidia-uvm modprobe nvidia ; modprobe -i nvidia-current-uvm $CMDLINE_OPTS remove nvidia modprobe -r -i nvidia-modeset nvidia-uvm nvidia # These aliases are defined in *all* nvidia modules. # Duplicating them here sets higher precedence and ensures the selected # module gets loaded instead of a random first match if more than one # version is installed. See #798207. alias pci:v10DEd0E00sv*sd*bc04sc80i00*nvidia alias pci:v10DEd0AA3sv*
Bug#837786: mutter: Issues repainting the display on mouse movement
I can confirm this issues. As usable workaround, I disabled DRI for Intel driver via Xorg configuration. Section "Device" Identifier "Intel Graphics" Driver "Intel" Option "DRI" "false" EndSection $ lshw -c video *-display description: VGA compatible controller product: 2nd Generation Core Processor Family Integrated Graphics Controller vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 09 width: 64 bits clock: 33MHz capabilities: msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:35 memory:f640-f67f memory:c000-cfff ioport:f000(size=64) memory:c-d -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.6.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=cs_CZ.utf8, LC_CTYPE=cs_CZ.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages mutter depends on: ii gsettings-desktop-schemas 3.21.4-2 ii libc6 2.23-5 ii libglib2.0-0 2.49.6-1 ii libmutter0i3.21.92-1 ii libx11-6 2:1.6.3-1 ii libxcomposite1 1:0.4.4-1 ii mutter-common 3.21.92-1 ii zenity 3.20.0-1 Versions of packages mutter recommends: ii gnome-session [x-session-manager]3.20.2-1 ii gnome-session-flashback [x-session-manager] 3.20.2-1 Versions of packages mutter suggests: ii gnome-control-center 1:3.21.90-1 ii xdg-user-dirs 0.15-2 -- no debconf information
Bug#837786: mutter: Issues repainting the display on mouse movement
Package: mutter Version: 3.21.92-1 Severity: grave Justification: causes non-serious data loss Dear Maintainer, 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. I tried upgrading mutter to the version in unstable, but the result is the same. There is also no difference by using the classic gnome session or the wayland session ---although, with wayland, the flickering and repainting is slightly less frequent. I tried recording the desktop session (with GNOME's screencast functionality), but funnily the flickering stops while recording. -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing'), (200, 'unstable'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.7.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages mutter depends on: ii gsettings-desktop-schemas 3.21.4-2 ii libc6 2.23-5 ii libglib2.0-0 2.49.6-1 ii libmutter0i3.21.92-1 ii libx11-6 2:1.6.3-1 ii libxcomposite1 1:0.4.4-1 ii mutter-common 3.21.92-1 ii zenity 3.20.0-1 Versions of packages mutter recommends: ii gnome-session [x-session-manager] 3.20.2-1 Versions of packages mutter suggests: ii gnome-control-center 1:3.21.90-1 ii xdg-user-dirs 0.15-2 -- no debconf information