-
Notifications
You must be signed in to change notification settings - Fork 293
Does not respect "Static Workspaces" setting #892
Description
(1) Issue/Bug Description:
When I open gnome tweaks and select 'static workspaces', it works for a while. Something, at some point, causes it to get ignored. When I change this setting in gnome-tweaks at first, it seems to work. Later, it stops working, but in gnome tweaks it will still show it as checked--it will just have a different number of selected static workspaces than I had selected (e.g., will show the '6' it has dynamically expanded to instead of the '4' I had selected, but still show 'static' as checked).
(2) Steps to reproduce (if you know):
Haven't figured it out exactly yet, but I will report back when I isolate 1 or more things that definitely cause this setting to stop being acknowledged
(3) Expected behavior:
As described above. Workspace number should respect gnome-tweaks setting.
(4) Distribution (run cat /etc/os-release):
20.10
(5) Gnome Shell version:
3.38.3
(6) Pop Shell version (run apt policy pop-shell or provide the latest commit if building locally):
$ apt policy pop-shell
pop-shell:
Installed: 1.1.0~1614198608~20.10~b8d6f19
Candidate: 1.1.0~1614198608~20.10~b8d6f19
Version table:
*** 1.1.0~1614198608~20.10~b8d6f19 1001
1001 http://ppa.launchpad.net/system76/pop/ubuntu groovy/main amd64 Packages
1001 http://ppa.launchpad.net/system76/pop/ubuntu groovy/main i386 Packages
100 /var/lib/dpkg/status
(7) Where was Pop Shell installed from:
Running fresh 20.10, have seen this behavior from basically since fresh install a week ago.
(8) Monitor Setup (2 x 1080p, 4K, Primary(Horizontal), Secondary(Vertical), etc):
3 x 1080p, two vertical, one horizontal.
(9) Other Installed/Enabled Extensions:
gnome-tweaks, not much else, try not to mess with gnome too much.
(10) Other Notes:
I assume that on something like waking up or rebooting, pop-shell is not checking whether static is indicated or not, and it's basically a 'race condition' without a check. unchecking/checking 'static' in gnome-tweaks fixes it until the next time I trigger the bug.