Ubuntu
gnome-control-center package

Dock settings can not be set to only one monitor

Bug #1875966 reported by Cornelius Huber on 2020-04-29

This bug report is a duplicate of: Bug #1866088: Problems with the Dock setting of "Show on" in the Appearance tab. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	gnome-control-center (Ubuntu)	New	Undecided	Unassigned

Bug Description

In the gnome-settings panel it is not possible to set the dock to being displayed on only one monitor after the option "all screens" has been selected once.
After selecting a specific monitor the setting immideately buggs back to "all screens".

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-control-center 1:3.36.1-1ubuntu5
ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
Uname: Linux 5.4.0-28-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr 29 22:48:55 2020
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2019-11-07 (173 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=de_DE.UTF-8
SHELL=/usr/bin/zsh
SourcePackage: gnome-control-center
UpgradeStatus: Upgraded to focal on 2020-04-24 (5 days ago)

Tags:

Revision history for this message

Cornelius Huber (booming) wrote on 2020-04-29:

Dependencies.txt Edit (21.0 KiB, text/plain; charset="utf-8")
ProcCpuinfoMinimal.txt Edit (1.2 KiB, text/plain; charset="utf-8")
ProcMaps.txt Edit (205.6 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (1.4 KiB, text/plain; charset="utf-8")

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2020-04-30:

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1866088, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.