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 721133 - Launching and closing an app on the 2nd workspace
Launching and closing an app on the 2nd workspace
Status: RESOLVED DUPLICATE of bug 709064
Product: gnome-shell
Classification: Core
Component: general
3.10.x
Other Linux
: Normal normal
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2013-12-27 15:42 UTC by betdomagoj
Modified: 2013-12-27 22:01 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description betdomagoj 2013-12-27 15:42:29 UTC
My current configuration is a system with OpenSuse 13.1, Gnome 3.10 running on
an Intel Core™ i5 CPU M 430 @ 2.27GHz × 4, 4 GB of RAM and AMD RADEONHD 5470M
with catalyst drivers installed.

It is important to note that the bug is present on open source amd drivers as
well and it is across distors - it occurs on Arch, Fedora and OpenSuse.

After launching, though even more frequently, when closing ann app on the second workspace for a second or so there appears and disapperas (flashes) the focused app on the first workspace.

This is further demonstrated in my screencast - I change the focus on the 1st workspace from Firefox to Nautilus and then nautilus starts flashing on the 2nd workspace when I close an app there.

This is not app dependent - it happens with all apps and combinations in my experience.

I've provided a screencast of what I'm talking about since it's kinda hard to explain and make a screenshot of.

https://drive.google.com/file/d/0BwMYKCbS9MgtUE1SdndnOTJEX0U/edit?usp=sharing
Comment 1 Florian Müllner 2013-12-27 22:01:24 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 709064 ***