touch-packages team mailing list archive

[kevin gunn <kevin.gunn@xxxxxxxxxxxxx>]

** Description changed:

+ In order to keep continuity, keeping this original bug rather than
+ spawning a new one.
+ 
+ new description:
+ currently non ui process are asking for trust prompts from related focused ui's, example scopes ask for dash to host a prompt. however, it needs to be the other way around, with the ui process having a list of pid's that it can host for.
+ 
+ original description:
+ 
  On the phone, a splash screen is shown as soon as QGuiApplication is instantiated; however, a QWindow might be created much later, or not be created at all.
  We have for example a D-Bus service (ubuntu-system-settings-online-accounts) which is a QGuiApplication, but creates QWindows only as client requests arrive. In the common case, this works fine because the service is generally started when a window needs to be displayed, but we are now preparing for implementing trust session support, and that would require either this bug to be fixed, or a deeper refactoring of our code.
+ 
+ see below, that the original description was simply incorrectly using
+ the default socket, instead of the trust socket. the default socket
+ causes the splash screen, whereas the trust socket won't

** Summary changed:

- Splash screen is shown as soon as QGuiApplication is instantiated
+ Reverse trust prompt hosting

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

Title:
  Reverse trust prompt hosting

Status in the base for Ubuntu mobile products:
  Confirmed
Status in Qt integration with the Mir display server:
  Opinion
Status in unity8 package in Ubuntu:
  Opinion
Status in unity8 package in Ubuntu RTM:
  Opinion

Bug description:
  In order to keep continuity, keeping this original bug rather than
  spawning a new one.

  new description:
  currently non ui process are asking for trust prompts from related focused ui's, example scopes ask for dash to host a prompt. however, it needs to be the other way around, with the ui process having a list of pid's that it can host for.

  original description:

  On the phone, a splash screen is shown as soon as QGuiApplication is instantiated; however, a QWindow might be created much later, or not be created at all.
  We have for example a D-Bus service (ubuntu-system-settings-online-accounts) which is a QGuiApplication, but creates QWindows only as client requests arrive. In the common case, this works fine because the service is generally started when a window needs to be displayed, but we are now preparing for implementing trust session support, and that would require either this bug to be fixed, or a deeper refactoring of our code.

  see below, that the original description was simply incorrectly using
  the default socket, instead of the trust socket. the default socket
  causes the splash screen, whereas the trust socket won't

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1352251/+subscriptions