[Touch-packages] [Bug 1324183] Re: [enhancement] FD passing for unity-system-compositor

2021-06-30 Thread Dan Streetman
** Changed in: systemd (Ubuntu)
   Status: Triaged => Invalid

** Changed in: systemd
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1324183

Title:
  [enhancement] FD passing for unity-system-compositor

Status in Light Display Manager:
  New
Status in systemd:
  Invalid
Status in Unity System Compositor:
  Triaged
Status in lightdm package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Invalid
Status in unity-system-compositor package in Ubuntu:
  Triaged
Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  Here's the global bug for FD passing from unity-system-compositor to
  unity8 rather than having a socket file.

  The general flow would be:
  *) LightDM gets a client socket from USC
  *) LightDM sends that fd to logind as a part of the session description 
(instead of X server number)
  *) unity8 pulls the fd from logind on startup

  This then needs an apparmour profile so that dbus denies access to the
  system-compositor fd from everything that's not unity.

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

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


[Touch-packages] [Bug 1324183] Re: [enhancement] FD passing for unity-system-compositor

2017-04-04 Thread Stephen M. Webb
** Changed in: unity-system-compositor
   Status: New => Triaged

** Changed in: unity-system-compositor
   Importance: Undecided => Wishlist

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-system-compositor in
Ubuntu.
https://bugs.launchpad.net/bugs/1324183

Title:
  [enhancement] FD passing for unity-system-compositor

Status in Light Display Manager:
  New
Status in systemd:
  New
Status in Unity System Compositor:
  Triaged
Status in lightdm package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Triaged
Status in unity-system-compositor package in Ubuntu:
  Triaged
Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  Here's the global bug for FD passing from unity-system-compositor to
  unity8 rather than having a socket file.

  The general flow would be:
  *) LightDM gets a client socket from USC
  *) LightDM sends that fd to logind as a part of the session description 
(instead of X server number)
  *) unity8 pulls the fd from logind on startup

  This then needs an apparmour profile so that dbus denies access to the
  system-compositor fd from everything that's not unity.

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

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


[Touch-packages] [Bug 1324183] Re: [enhancement] FD passing for unity-system-compositor

2014-09-09 Thread Michał Sawicz
** No longer affects: unity8

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-system-compositor in
Ubuntu.
https://bugs.launchpad.net/bugs/1324183

Title:
  [enhancement] FD passing for unity-system-compositor

Status in Light Display Manager:
  New
Status in systemd:
  New
Status in Unity System Compositor:
  New
Status in “lightdm” package in Ubuntu:
  Triaged
Status in “systemd” package in Ubuntu:
  Triaged
Status in “unity-system-compositor” package in Ubuntu:
  Triaged
Status in “unity8” package in Ubuntu:
  Triaged

Bug description:
  Here's the global bug for FD passing from unity-system-compositor to
  unity8 rather than having a socket file.

  The general flow would be:
  *) LightDM gets a client socket from USC
  *) LightDM sends that fd to logind as a part of the session description 
(instead of X server number)
  *) unity8 pulls the fd from logind on startup

  This then needs an apparmour profile so that dbus denies access to the
  system-compositor fd from everything that's not unity.

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

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