[Desktop-packages] [Bug 1228765] Re: Need to implement DisplayConfig dbus interface within Unity

2014-03-04 Thread Tim
** Patch added: "gnome-desktop 3.10 update"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-desktop3/+bug/1228765/+attachment/4006361/+files/gd310.debdiff

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-desktop3 in Ubuntu.
https://bugs.launchpad.net/bugs/1228765

Title:
  Need to implement DisplayConfig dbus interface within Unity

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

Bug description:
  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).

  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 it seems the cleanest
  solution would be to copy the display config interface from Mutter
  into Unity. The code itself is fairly self contained, so apart from
  the resulting duplication of code, it shouldnt really be much of an
  issue.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1228765] Re: Need to implement DisplayConfig dbus interface within Unity

2014-02-28 Thread Jackson Doak
I have merges proposed for u-s-d and u-c-c.
Build logs are at 
https://launchpad.net/~noskcaj/+archive/build/+build/5648073/+files/buildlog_ubuntu-trusty-amd64.unity-settings-daemon_14.04.0%2B14.04.20140228-0ubuntu2_UPLOADING.txt.gz
 and 
https://launchpad.net/~noskcaj/+archive/build/+build/5648067/+files/buildlog_ubuntu-trusty-amd64.unity-control-center_14.04.3%2B14.04.20140226-0ubuntu2_UPLOADING.txt.gz
 repectively.

** Also affects: unity-control-center
   Importance: Undecided
   Status: New

** Changed in: unity-control-center
   Status: New => In Progress

** Changed in: unity-control-center
 Assignee: (unassigned) => Jackson Doak (noskcaj)

** Also affects: unity-settings-daemon
   Importance: Undecided
   Status: New

** Changed in: unity-settings-daemon
 Assignee: (unassigned) => Jackson Doak (noskcaj)

** Changed in: unity-settings-daemon
   Status: New => In Progress

** Branch unlinked: lp:~noskcaj/ubuntu/trusty/unity-control-center
/gnome-desktop-3.10

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

Title:
  Need to implement DisplayConfig dbus interface within Unity

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

Bug description:
  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).

  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 it seems the cleanest
  solution would be to copy the display config interface from Mutter
  into Unity. The code itself is fairly self contained, so apart from
  the resulting duplication of code, it shouldnt really be much of an
  issue.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1228765] Re: Need to implement DisplayConfig dbus interface within Unity

2014-02-28 Thread Launchpad Bug Tracker
** Branch linked: lp:~noskcaj/unity-control-center/gnome-desktop-3.10

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-desktop3 in Ubuntu.
https://bugs.launchpad.net/bugs/1228765

Title:
  Need to implement DisplayConfig dbus interface within Unity

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

Bug description:
  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).

  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 it seems the cleanest
  solution would be to copy the display config interface from Mutter
  into Unity. The code itself is fairly self contained, so apart from
  the resulting duplication of code, it shouldnt really be much of an
  issue.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1228765] Re: Need to implement DisplayConfig dbus interface within Unity

2014-02-28 Thread Jackson Doak
** Branch unlinked: lp:~noskcaj/ubuntu/trusty/unity-settings-daemon
/gnome-desktop-3.10

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-desktop3 in Ubuntu.
https://bugs.launchpad.net/bugs/1228765

Title:
  Need to implement DisplayConfig dbus interface within Unity

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

Bug description:
  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).

  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 it seems the cleanest
  solution would be to copy the display config interface from Mutter
  into Unity. The code itself is fairly self contained, so apart from
  the resulting duplication of code, it shouldnt really be much of an
  issue.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1228765] Re: Need to implement DisplayConfig dbus interface within Unity

2014-02-28 Thread Launchpad Bug Tracker
** Branch linked: lp:~noskcaj/unity-settings-daemon/gnome-desktop-3.10

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-desktop3 in Ubuntu.
https://bugs.launchpad.net/bugs/1228765

Title:
  Need to implement DisplayConfig dbus interface within Unity

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

Bug description:
  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).

  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 it seems the cleanest
  solution would be to copy the display config interface from Mutter
  into Unity. The code itself is fairly self contained, so apart from
  the resulting duplication of code, it shouldnt really be much of an
  issue.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1228765] Re: Need to implement DisplayConfig dbus interface within Unity

2014-02-28 Thread Launchpad Bug Tracker
** Branch linked: lp:~noskcaj/gnome-control-center/ubuntu

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-desktop3 in Ubuntu.
https://bugs.launchpad.net/bugs/1228765

Title:
  Need to implement DisplayConfig dbus interface within Unity

Status in Ubuntu GNOME:
  Triaged
Status in Unity:
  Triaged
Status in “gnome-desktop3” package in Ubuntu:
  Triaged
Status in “gnome-settings-daemon” package in Ubuntu:
  Triaged
Status in “unity” package in Ubuntu:
  Triaged

Bug description:
  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).

  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 it seems the cleanest
  solution would be to copy the display config interface from Mutter
  into Unity. The code itself is fairly self contained, so apart from
  the resulting duplication of code, it shouldnt really be much of an
  issue.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1228765] Re: Need to implement DisplayConfig dbus interface within Unity

2014-02-28 Thread Launchpad Bug Tracker
** Branch linked: lp:~noskcaj/gnome-settings-daemon/ubuntu

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-desktop3 in Ubuntu.
https://bugs.launchpad.net/bugs/1228765

Title:
  Need to implement DisplayConfig dbus interface within Unity

Status in Ubuntu GNOME:
  Triaged
Status in Unity:
  Triaged
Status in “gnome-desktop3” package in Ubuntu:
  Triaged
Status in “gnome-settings-daemon” package in Ubuntu:
  Triaged
Status in “unity” package in Ubuntu:
  Triaged

Bug description:
  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).

  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 it seems the cleanest
  solution would be to copy the display config interface from Mutter
  into Unity. The code itself is fairly self contained, so apart from
  the resulting duplication of code, it shouldnt really be much of an
  issue.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1228765] Re: Need to implement DisplayConfig dbus interface within Unity

2014-02-28 Thread Launchpad Bug Tracker
** Branch linked: lp:~noskcaj/ubuntu/trusty/unity-control-center/gnome-
desktop-3.10

** Branch linked: lp:~noskcaj/ubuntu/trusty/unity-settings-daemon/gnome-
desktop-3.10

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-desktop3 in Ubuntu.
https://bugs.launchpad.net/bugs/1228765

Title:
  Need to implement DisplayConfig dbus interface within Unity

Status in Ubuntu GNOME:
  Triaged
Status in Unity:
  Triaged
Status in “gnome-desktop3” package in Ubuntu:
  Triaged
Status in “gnome-settings-daemon” package in Ubuntu:
  Triaged
Status in “unity” package in Ubuntu:
  Triaged

Bug description:
  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).

  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 it seems the cleanest
  solution would be to copy the display config interface from Mutter
  into Unity. The code itself is fairly self contained, so apart from
  the resulting duplication of code, it shouldnt really be much of an
  issue.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1228765] Re: Need to implement DisplayConfig dbus interface within Unity

2013-12-10 Thread Tim
Tagging as high for Ubuntu GNOME, since this is blocking g-s-d/g-c-c
(once they have been forked for ubuntu)

** Also affects: ubuntu-gnome
   Importance: Undecided
   Status: New

** Changed in: ubuntu-gnome
   Importance: Undecided => High

** Changed in: ubuntu-gnome
   Status: New => Triaged

** Changed in: ubuntu-gnome
Milestone: None => trusty

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

Title:
  Need to implement DisplayConfig dbus interface within Unity

Status in Ubuntu GNOME:
  Triaged
Status in Unity:
  Triaged
Status in “gnome-desktop3” package in Ubuntu:
  Triaged
Status in “gnome-settings-daemon” package in Ubuntu:
  Triaged
Status in “unity” package in Ubuntu:
  Triaged

Bug description:
  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).

  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 it seems the cleanest
  solution would be to copy the display config interface from Mutter
  into Unity. The code itself is fairly self contained, so apart from
  the resulting duplication of code, it shouldnt really be much of an
  issue.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1228765] Re: Need to implement DisplayConfig dbus interface within Unity

2013-09-27 Thread Sebastien Bacher
** Changed in: gnome-settings-daemon (Ubuntu)
   Importance: Undecided => Wishlist

** Changed in: gnome-settings-daemon (Ubuntu)
   Status: New => Triaged

** Changed in: gnome-desktop3 (Ubuntu)
   Importance: Undecided => Wishlist

** Changed in: gnome-desktop3 (Ubuntu)
   Status: New => Triaged

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1228765

Title:
  Need to implement DisplayConfig dbus interface within Unity

Status in Unity:
  Triaged
Status in “gnome-desktop3” package in Ubuntu:
  Triaged
Status in “gnome-settings-daemon” package in Ubuntu:
  Triaged
Status in “unity” package in Ubuntu:
  Triaged

Bug description:
  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).

  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 it seems the cleanest
  solution would be to copy the display config interface from Mutter
  into Unity. The code itself is fairly self contained, so apart from
  the resulting duplication of code, it shouldnt really be much of an
  issue.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1228765] Re: Need to implement DisplayConfig dbus interface within Unity

2013-09-22 Thread Stephen M. Webb
** Changed in: unity (Ubuntu)
   Status: New => Triaged

** Changed in: unity (Ubuntu)
   Importance: Undecided => Medium

** Also affects: unity
   Importance: Undecided
   Status: New

** Changed in: unity
   Status: New => Triaged

** Changed in: unity
   Importance: Undecided => Medium

** Changed in: unity
Milestone: None => 7.2.0

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1228765

Title:
  Need to implement DisplayConfig dbus interface within Unity

Status in Unity:
  Triaged
Status in “gnome-desktop3” package in Ubuntu:
  New
Status in “gnome-settings-daemon” package in Ubuntu:
  New
Status in “unity” package in Ubuntu:
  Triaged

Bug description:
  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).

  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 it seems the cleanest
  solution would be to copy the display config interface from Mutter
  into Unity. The code itself is fairly self contained, so apart from
  the resulting duplication of code, it shouldnt really be much of an
  issue.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp