dx-packages team mailing list archive

[Tim <tim@xxxxxxxxxxxxxx>]

- I fixed the issue with configurations not being read from the gnome-settings-daemon monitors.xml config file, I',m not entirely sure what wrote this file, but Laney suggested it was maybe copied across by one of the indicators?
- I couldn't reproduce the pointer barrier issue here on my dual monitor setup. I actually don't believe there is any code dealing with pointer barriers involved here either.
- Right, Unity no longer requires changes with this solution. marked invalid.
- Our build of g-c-c 3.10 has the bluetooth changes reverted, so no need for BlueZ 5 this cycle (will definitely need that for next cycle however).
- I will add a list of the changed API tomorrow, however I don't believe gnome-screensaver is affected by this and certainly built fine when I tested it. Most of the API changes are pretty internal (i.e. limited to g-s-d and g-c-c). The api's that most apps are using (background, thumbnailer, etc) are unaffected.

As a side note, I have spoken with upstream about splitting out all app
dependencies from gnome-desktop, at which point it would become feasible
to fork gnome-desktop, however this won't happen until atleast 3.14
anyway.

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1228765

Title:
  [FFe] Implement DisplayConfig dbus interface and transition to gnome-
  desktop 3.10

Status in Ubuntu GNOME:
  Triaged
Status in Unity:
  Invalid
Status in Unity Control Center:
  In Progress
Status in Unity Settings Daemon:
  In Progress
Status in “gnome-desktop3” package in Ubuntu:
  New
Status in “gnome-settings-daemon” package in Ubuntu:
  Triaged
Status in “unity” package in Ubuntu:
  Triaged

Bug description:
  Ubuntu GNOME would like to transition for gnome-settings-daemon/gnome-
  control-center 3.10. This however requires a transition to gnome-
  desktop 3-10. I have been working on this for quite some time however
  this work was essentially blocked waiting on the unity- forks for
  settings daemon and control center. These were only finalised the day
  before feature freeze.

  Right now there are quite a few features that are not available for
  configuration in g-c-c given it is so old. We are also hitting some
  odd bugs with mutter using its own display config separate to what
  gnome-settings-daemon is doing with xrandr.

  For GNOME 3.10, all the display configuration/xrandr code has been
  moved into Mutter as dbus interface. The Main reason for this move was
  to abstract away the display server (x11/wayland). Apart from these
  changes there were no significant changes in the API.

  This affects gnome-desktop3 and gnome-settings-daemon. In particular
  the changes in gnome-desktop would create a gigantic mess if we tried
  to revert these changes for Unity only. As such have forked the
  display config code from mutter and ported *-settings-daemon and
  *-control-center to the new api. The code itself is fairly self
  contained, so apart from the resulting duplication of code, it
  shouldnt really be much of an issue.

  We have tested this via a ppa, however it was hard to get extensive
  testing, due to the amount of archive churn in the affected packages.
  I am pretty confident there are no much regressions and I will commit
  to fixing any issues to do appear.

  Essentially this transition will involve:
  new displayconfig package: This is the relevant code forked from mutter 3.10.4 (with a couple of fixes from 3.11 backported), wrapped up in a daemon. This gets autostarted when required by g/u-s-d (although dbus activation may be broken in flashback session)
  my upstream branch is at https://github.com/darkxst/displayconfig (I had trouble working out how to import a git branch into bzr, but I imagine it should live in bzr once approved)

  gnome/unity-settings-daemon, have backported patches to adapt to the new API.
  Likewise for gnome/unity-control-center.
  All other rdepends just require a no-change rebuild to adapt to the new soname.

  Assuming this gets a approved, subsequent FFe's for gnome-settings-
  daemon and gnome-control-center 3.10 will follow.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-gnome/+bug/1228765/+subscriptions