- 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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1228765 Title: [FFe] Implement DisplayConfig dbus interface and transition to gnome- desktop 3.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1228765/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
