In overview, windows from all workspaces are shown for the second display (when using "Workspaces span displays")

Bug #1743736 reported by Mitar on 2018-01-17
20
This bug affects 2 people
Affects Status Importance Assigned to Milestone
GNOME Shell
Unknown
Unknown
gnome-shell (Ubuntu)
Medium
Unassigned

Bug Description

I have disabled workspaces on primary display only, and I have enabled workspaces to span displays, in tweak tool.

Now things mostly work how I expect. Windows are isolated to the workspace they are and I can move them between displays (monitors). The issue is if I go into an overview mode. Then, for the primary display, I see only windows from my current workspace. But for the secondary display, I see windows from all workspaces being shown in the overview mode.

I would expect that only the windows from the current workspace are shown also on the secondary display in the overview mode.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.26.2-0ubuntu0.1
ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
Uname: Linux 4.13.0-25-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Jan 17 02:19:13 2018
DisplayManager: gdm3
InstallationDate: Installed on 2017-11-20 (57 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

This bug also affects the new LTS release:

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-shell 3.28.1-0ubuntu2
ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
Uname: Linux 4.15.0-22-generic x86_64
NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice talpa_vcdevice talpa_core talpa_linux talpa_syscallhook nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed May 23 15:25:07 2018
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
InstallationDate: Installed on 2018-05-18 (5 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

Mitar (mitar) wrote :
Daniel van Vugt (vanvugt) wrote :

Thanks for the bug report. I've not seen this problem reported before so please look at the upstream bug list to see if you can find it there:

  https://bugzilla.gnome.org/

If not then please also report the bug there and let us know the link to that new bug.

tags: added: multimonitor
Changed in gnome-shell (Ubuntu):
status: New → Incomplete
Mitar (mitar) wrote :

It seems this one is reporting the issue: https://bugzilla.gnome.org/show_bug.cgi?id=652580

There are few patches, but it does not like fixed.

So I do not care so much about switcher than the behavior described:

Observed behavior: Actvities overview (got by pressing the logo key), however, handles the two monitors differently: for the primary monitor, it exposes only windows on the current workspace, but for the external monitor, it always shows all windows on all workspaces.

Expected behavior: when /desktop/gnome/shell/windows/workspaces_only_on_primary is false, both monitors should behave the same, and both should show only windows on the current workspace.

Changed in gnome-shell (Ubuntu):
importance: Undecided → Medium
status: Incomplete → Fix Committed
status: Fix Committed → Confirmed
summary: In overview, windows from all workspaces are shown for the second
- display
+ display (when using "Workspaces span displays")
david23 (david-3791) wrote :

I can confirm the bug. However, the bug reported on gnome's bugzilla is very old. I've been using ubuntu gnome 16.04 for the last two years and everything worked fine. I've seen this bug for the first time trying out ubuntu 17.10, so I would conclude it's either related to ubuntu's customization of gnome, or to gnome versions >3.18

tags: added: bionic
david23 (david-3791) on 2018-05-24
description: updated
tags: removed: wayland-session
Alexander (eetfuk1988) wrote :

I can confirm it as well. Occurred after upgrade to 18.04 (X and Wayland), worked fine with 16.04 (on Gnome). Unfortunately this is a core feature to my workflow, is there a workaround?

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.