Bug 708841 – overview exit animation glitch

After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.

Bug 708841 - overview exit animation glitch


Summary:	overview exit animation glitch


Status:	RESOLVED INCOMPLETE

Product:	gnome-shell
Classification:	Core
Component:	general
Version:	unspecified
Hardware:	Other Linux

Importance:	Normal normal
Target Milestone:	---
Assigned To:	gnome-shell-maint
QA Contact:	gnome-shell-maint

URL:
Whiteboard:

Duplicates:	709599 (view as bug list)
Depends on:
Blocks:

Reported:	2013-09-26 14:41 UTC by Rui Matos
Modified:	2017-11-02 21:56 UTC

See Also:
GNOME target:	---
GNOME version:	---

Description Rui Matos 2013-09-26 14:41:00 UTC

1. move to an empty workspace
2. open a gnome-terminal window
3. open gnome-control-center
4. go to overview
5. click the gnome-terminal thumbnail

There's a visible glitch in the overview exit animation at this point. Seems to happen when exiting the overview and switching the focus from a non-CSD window to a CSD window or vice versa.

Comment 1 Rui Matos 2013-10-08 08:49:54 UTC

*** Bug 709599 has been marked as a duplicate of this bug. ***

Comment 2 Dan Doel 2013-10-08 14:08:33 UTC

In my experience this doesn't seem directly related to CSD. I can switch between nautilus (CSD) and gnome-terminal (non-CSD) without seeing the glitch. But, I also see the glitch when switching between nautilus and gnome-control-center. Somehow this seems to be control-center-specific for me (not sure how that's possible, but I haven't found another app that triggers it yet).

Hope that gives a little more to go on.

Comment 3 Florian Müllner 2015-02-28 01:29:10 UTC

I'm not seeing this, looks like it got fixed at one point?

Comment 4 Alexandre Franke 2017-11-02 21:56:11 UTC

Closing this bug report as no further information has been provided. Please feel free to reopen this bug report if you can provide the information that was asked for in a previous comment.
Thanks!