Changing Primary DIsplay Flips Which Display Has The Dock
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-control-center (Ubuntu) |
Confirmed
|
Low
|
Unassigned | ||
gnome-shell-extension-ubuntu-dock (Ubuntu) |
Confirmed
|
Low
|
Unassigned |
Bug Description
On a fresh install from at least Ubuntu 17.04 up to 18.10, when I change Settings-
For Example I have Monitor A and Monitor B
After a fresh install Monitor A is primary with title bar, clock, etc. and the dock. If I change the dock to Show on Monitor B it moves as desired. But when I change Primary Display to Monitor B also, the dock immediately goes to Monitor A again. When I check the Show on setting it still displays Monitor B but it's actually on Monitor A. Selecting Monitor A will move the dock to Monitor B.
Description: Ubuntu 18.04.1 LTS
Release: 18.04
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2018-10-31 (0 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
NonfreeKernelMo
Package: gnome-control-
PackageArchitec
ProcEnviron:
TERM=xterm-
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSign
Tags: bionic
Uname: Linux 4.15.0-38-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
_MarkForUpload: True
---
ProblemType: Bug
.proc.driver.
.proc.driver.
.proc.driver.
NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.77 Tue Jul 10 18:28:52 PDT 2018
GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-27ubuntu1
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
DistUpgraded: Fresh install
DistroCodename: bionic
DistroRelease: Ubuntu 18.04
DistroVariant: ubuntu
DkmsStatus:
nvidia, 390.77, 4.15.0-29-generic, x86_64: installed
nvidia, 390.77, 4.15.0-38-generic, x86_64: installed
ExtraDebuggingI
GraphicsCard:
Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1043:8534]
NVIDIA Corporation GK104 [GeForce GTX 760] [10de:1187] (rev a1) (prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. GK104 [GeForce GTX 760] [1043:8472]
InstallationDate: Installed on 2018-10-31 (1 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
MachineType: ASUS All Series
NonfreeKernelMo
Package: xorg-server (not installed)
ProcEnviron:
TERM=xterm-
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=
ProcVersionSign
Tags: bionic ubuntu
Uname: Linux 4.15.0-38-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
_MarkForUpload: True
dmi.bios.date: 08/18/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2103
dmi.board.
dmi.board.name: Z87-PRO
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.family: ASUS MB
dmi.product.name: All Series
dmi.product.
dmi.sys.vendor: ASUS
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.91-2
version.
version.
version.
version.
version.
version.
version.
version.
tags: | added: multimonitor |
Changed in gnome-control-center (Ubuntu): | |
importance: | Undecided → Low |
tags: | added: focal |
no longer affects: | nvidia-graphics-drivers-390 (Ubuntu) |
affects: | xorg-server (Ubuntu) → gnome-shell-extension-ubuntu-dock (Ubuntu) |
Changed in gnome-shell-extension-ubuntu-dock (Ubuntu): | |
importance: | Undecided → Low |
This bug is missing log files that will aid in diagnosing the problem. Please enter the following command in a terminal window:
apport-collect 1800963
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.