← Back to team overview

desktop-packages team mailing list archive

[Bug 1292398] Re: Second screen position isn't saved from one session to another


I have the same issue on Ubuntu 14.04 LTS.
Restarting the settings daemon works, but adding 2 seconds waiting time to the upstart script 
caused my background to behave strangely (I'm using conky and the windows I move leave a copy of themselves on the desktop).
Also it doesn't solve the  issue with the login screen. It is displayed on my tv, in another room.

You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.

  Second screen position isn't saved from one session to another

Status in elementary OS:
Status in Gnome Settings Daemon:
Status in GNOME Shell:
Status in Ubuntu GNOME:
Status in “gnome-settings-daemon” package in Ubuntu:
Status in “gnome-shell” package in Ubuntu:

Bug description:
  (Noticed on Ubuntu 14.04 beta 1 GNOME)
  At work I have a second screen, which I prefer to virtually put on the left side of my laptop screen.
  Using gnome-control-center I can change the position of the second without problem.
  But when I disconnect the second screen (to work on another place) and then connect it again
  OR if I just power off the laptop and turn it on again,
  the second screen position is set back to the default right position.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gnome-control-center 1:3.6.3-0ubuntu53
  ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6
  Uname: Linux 3.13.0-17-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Mar 14 08:50:00 2014
  InstallationDate: Installed on 2014-03-01 (12 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140226)
   PATH=(custom, no user)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_gnome-control-center: deja-dup 29.5-0ubuntu2

To manage notifications about this bug go to: