Bearing the above in mind we have time to properly consider all the use
cases and implement the long-term solution without hackfixes.
** Changed in: canonical-devices-system-image
Status: Confirmed => New
** Changed in: unity8 (Ubuntu RTM)
Assignee: Josh Arenson (josharenson) => (unassigned)
** Changed in: unity8 (Ubuntu)
Assignee: Josh Arenson (josharenson) => (unassigned)
** Changed in: qtmir
Assignee: Josh Arenson (josharenson) => (unassigned)
** Changed in: qtmir
Status: Confirmed => Opinion
** Changed in: unity8 (Ubuntu RTM)
Status: Confirmed => Opinion
** Changed in: unity8 (Ubuntu)
Status: Confirmed => Opinion
--
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:
Splash screen is shown as soon as QGuiApplication is instantiated
Status in the base for Ubuntu mobile products:
New
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:
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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1352251/+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
