Nautilus windows not respecting workspace isolation
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-shell-extension-ubuntu-dock (Ubuntu) |
Fix Released
|
Low
|
Marco Trevisan (Treviño) | ||
Jammy |
In Progress
|
Undecided
|
Marco Trevisan (Treviño) |
Bug Description
[ Impact ]
Workspace isolation is not respected by nautilus in dock
[ Test case ]
1. From settings -> Multitasking:
- Enable "Include applications from the current workspace only"
2. Open a Files window in a workspace
3. Switch to another workspace
4. File manager icon should be visible with no count
5. Open a new file-manager instance (clicking on the dock icon)
6. A icon dot should be visible
7. Switching back to the initial workspace should show the icon dots
respecting the number of icons
[ Regression potential ]
Wrong number of windows are shown on file-manager icons
---
In settings, under multitasking > application switching, setting "include applications from the current workspace only" is supposed to provide workspace isolation, making only apps in the current workspace show in the dock. For example, if I have 2 firefox windows in workspace 1, and a terminal window in workspace 2, terminal should not show as open in the dock in workspace 1, and firefox should not show as open in the dock in workspace 2.
Additionally, quitting all windows from right click in the dock should close only all windows of that app in the current workspace.
This mostly works correctly, but for some reason some apps, including nautilus and software and updates, do not respect it. If you switch workspaces with them open, the new workspace shows them as having the same number of open windows as the previous workspace, even though no windows are open in that workspace. If you quit with right click from the dock, it sometimes quits all instances across all workspaces. If you open a separate window in the new workspace with right click on the dock, it then updates to the correct number, but the problem then returns on switching back to the previous workspace. If you open and close a window in the new workspace, then switch back to the old one, it is possible to get to a point where despite several windows of the app being open in that workspace, it shows as not open in the dock.
The problem persists across different installs and machines
To reproduce:
Open ubuntu (a live version is fine). Turn on workspace isolation in settings. Pin nautilus to favorites so it shows in the dock. Open a window of nautilus, and a window of some other app (firefox works). Switch workspaces. Observe that an orange dot is still present under nautilus, and it still acts like it is open in the new workspace
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckR
CurrentDesktop: ubuntu:GNOME
DisplayManager: gdm3DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2020-04-25 (735 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
NonfreeKernelMo
Package: gnome-shell 42.0-2ubuntu1
PackageArchitec
ProcEnviron:
TERM=xterm-
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSign
RelatedPackageV
Tags: jammy
Uname: Linux 5.15.0-27-generic x86_64
UpgradeStatus: Upgraded to jammy on 2022-04-30 (1 days ago)
UserGroups: adm cdrom dip lpadmin lxd nordvpn plugdev sambashare sudo wireshark
_MarkForUpload: True
Changed in gnome-shell-extension-ubuntu-dock (Ubuntu): | |
importance: | Undecided → Low |
description: | updated |
Changed in gnome-shell-extension-ubuntu-dock (Ubuntu): | |
status: | New → In Progress |
assignee: | nobody → Marco Trevisan (Treviño) (3v1n0) |
Changed in gnome-shell-extension-ubuntu-dock (Ubuntu Jammy): | |
assignee: | nobody → Marco Trevisan (Treviño) (3v1n0) |
Changed in gnome-shell-extension-ubuntu-dock (Ubuntu Jammy): | |
status: | New → Triaged |
Changed in gnome-shell-extension-ubuntu-dock (Ubuntu Jammy): | |
status: | Triaged → In Progress |
description: | updated |
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https:/ /wiki.ubuntu. com/Bugs/ FindRightPackag e. You might also ask for help in the #ubuntu-bugs irc channel on Libera.chat.
To change the source package that this bug is filed about visit https:/ /bugs.launchpad .net/ubuntu/ +bug/1971012/ +editstatus and add the package name in the text box next to the word Package.
[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]