[Touch-packages] [Bug 1352251] Re: Splash screen is shown as soon as QGuiApplication is instantiated
** 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 -- 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 1352251] Re: Splash screen is shown as soon as QGuiApplication is instantiated
Defer per discussion in the bug ** Changed in: canonical-devices-system-image Milestone: ww51-2014 = ww05-2015 -- 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: 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: 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
[Touch-packages] [Bug 1352251] Re: Splash screen is shown as soon as QGuiApplication is instantiated
confirmed status in system-image means product team approved it, it is not related to subtask status ** Changed in: canonical-devices-system-image Status: New = Confirmed -- 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: 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: 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
[Touch-packages] [Bug 1352251] Re: Splash screen is shown as soon as QGuiApplication is instantiated
This one's targeted to ww51 as well, which is what I tried to counter. -- 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: 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: 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
[Touch-packages] [Bug 1352251] Re: Splash screen is shown as soon as QGuiApplication is instantiated
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
[Touch-packages] [Bug 1352251] Re: Splash screen is shown as soon as QGuiApplication is instantiated
Alberto, can you please confirm if the above is good enough for you for now? And if not, please describe what other use case this lacks support for? -- 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: Confirmed Status in Qt integration with the Mir display server: Confirmed Status in unity8 package in Ubuntu: Confirmed Status in unity8 package in Ubuntu RTM: Confirmed 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
[Touch-packages] [Bug 1352251] Re: Splash screen is shown as soon as QGuiApplication is instantiated
I believe that as far as trust prompts go, we've resolved that they should ultimately never talk to the default Mir socket, which is the only case when they get a splash screen. The backends should open a trust session, even if it's not going to create any UI in the end (that is, if they require a Mir connection to function, as is the case for Oxide). Until we have the headless-client hints implemented on surfaces, you can open the trusted session with dash's PID or whatever else makes sense. Jury's still out on whether we want to disable splash screens for some apps, but that is more of a UX question than a technical one. Another approach we might consider is dropping the --desktop_file_hint hack (I believe OA is one of the last instances of it) and think of a different way to allow trusted helpers in. We could also say that only UAL-backed apps get splash screens. -- 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: Confirmed Status in Qt integration with the Mir display server: Confirmed Status in unity8 package in Ubuntu: Confirmed Status in unity8 package in Ubuntu RTM: Confirmed 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
[Touch-packages] [Bug 1352251] Re: Splash screen is shown as soon as QGuiApplication is instantiated
Yes, this is not really blocking me; until the headless-client hints are implemented I can just play safe and simply return an error on all UI requests. -- 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: Confirmed Status in Qt integration with the Mir display server: Confirmed Status in unity8 package in Ubuntu: Confirmed Status in unity8 package in Ubuntu RTM: Confirmed 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
[Touch-packages] [Bug 1352251] Re: Splash screen is shown as soon as QGuiApplication is instantiated
** Changed in: canonical-devices-system-image Importance: Undecided = High ** Changed in: canonical-devices-system-image Status: New = Confirmed ** Changed in: canonical-devices-system-image Milestone: None = r1 ** Changed in: canonical-devices-system-image Assignee: (unassigned) = Canonical Devices Products (canonical-devices-products-team) -- 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: Confirmed Status in Qt integration with the Mir display server: Confirmed Status in “unity8” package in Ubuntu: Confirmed Status in “unity8” package in Ubuntu RTM: Confirmed 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
[Touch-packages] [Bug 1352251] Re: Splash screen is shown as soon as QGuiApplication is instantiated
This bug is still valid: while all the UI interactions involving trust sessions are working fine (there is no splash screen -- as I believe is correct), there are still cases where the Online Accounts UI is not invoked within a trust session, and that's typically when the client process is not a GUI application. This is the case of scopes and some system services (sync-monitor, and maybe telepathy in the future). As I wrote in comment #1, many times even if the OAuth access token is expired, the cookies are still valid and we might be able to get a new access token without showing a web page. But we cannot know this in advance: we'll know it only after loading a webview (and Oxide requires a QGuiApplication) which we'll keep hidden until either we get redirected to the page where we get the access token (in which case the user will not see any UI at all) or until it's clear that we cannot proceed without the user interaction, in which case we can either show a snap decision or just return an error to the client. -- 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 Qt integration with the Mir display server: Confirmed Status in “unity8” package in Ubuntu: Confirmed Status in “unity8” package in Ubuntu RTM: Confirmed 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/qtmir/+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
[Touch-packages] [Bug 1352251] Re: Splash screen is shown as soon as QGuiApplication is instantiated
I'm not sure this bug is valid any more. The trusted prompt mechanism is different to how apps are created. Trusted prompts don't have splash screens (maybe they should?), but in any case a trusted session is short-lived, just for the duration of the prompt. The connection to Mir needs to happen on the trusted socket, so there's no connection that could trigger the splash screen (even if there was a splash screen) too early. -- 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 Qt integration with the Mir display server: Confirmed Status in “unity8” package in Ubuntu: Confirmed Status in “unity8” package in Ubuntu RTM: Confirmed 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/qtmir/+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
[Touch-packages] [Bug 1352251] Re: Splash screen is shown as soon as QGuiApplication is instantiated
** Also affects: unity8 (Ubuntu RTM) Importance: Undecided Status: New ** Changed in: unity8 (Ubuntu RTM) Status: New = Confirmed ** Changed in: unity8 (Ubuntu RTM) Importance: Undecided = High ** Changed in: unity8 (Ubuntu RTM) Assignee: (unassigned) = Josh Arenson (josharenson) -- 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 Qt integration with the Mir display server: Confirmed Status in “unity8” package in Ubuntu: Confirmed Status in “unity8” package in Ubuntu RTM: Confirmed 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/qtmir/+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
[Touch-packages] [Bug 1352251] Re: Splash screen is shown as soon as QGuiApplication is instantiated
** Tags added: ota-2 ** Changed in: qtmir Assignee: (unassigned) = Josh Arenson (josharenson) ** Changed in: unity8 (Ubuntu) Assignee: (unassigned) = Josh Arenson (josharenson) -- 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 Qt integration with the Mir display server: Confirmed Status in “unity8” package in Ubuntu: Confirmed 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/qtmir/+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
[Touch-packages] [Bug 1352251] Re: Splash screen is shown as soon as QGuiApplication is instantiated
** Changed in: qtmir Importance: Undecided = High ** Changed in: unity8 (Ubuntu) Importance: Undecided = High -- 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 Qt integration with the Mir display server: Confirmed Status in “unity8” package in Ubuntu: Confirmed 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/qtmir/+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
[Touch-packages] [Bug 1352251] Re: Splash screen is shown as soon as QGuiApplication is instantiated
** Tags added: rtm14 -- 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 Qt integration with the Mir display server: Confirmed Status in “unity8” package in Ubuntu: Confirmed 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/qtmir/+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
[Touch-packages] [Bug 1352251] Re: Splash screen is shown as soon as QGuiApplication is instantiated
Please rate this as High. -- 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 Qt integration with the Mir display server: Confirmed Status in “unity8” package in Ubuntu: Confirmed 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/qtmir/+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
[Touch-packages] [Bug 1352251] Re: Splash screen is shown as soon as QGuiApplication is instantiated
Unity8 tries to draw a splash screen for an app as soon as possible, so the UI is responsive to the user. It will paint a splash screen when either of these things happen: 1. user taps an app icon in launcher 2. when upstart notifies it an app is starting 3. when Mir notifies it an app connected For point 3, note I said connected - not created a surface and set it to show(). A QGuiApplication will create a Mir connection on instantiation. A QCoreApplication will not show a splash, as that does not create a Mir connection. Creation of a QWindow has no relation to the creation of a splash screen. This isn't something we want for desktop ofc, but for phablet I think it makes for a good user experience to paint a splash screen quickly. As a result, I don't believe there's a way a binary can tell shell not to paint a splash screen for it. Instead these are the only options I can think of: 1. shell having some heuristics to decide what apps should not get a splash screen 2. app supplies metadata via desktop file to specify if it wants a splash or not I dislike option 2, as I fear it could be abused by app developers, and make our platform appear slow to react to user input. Option 1 is also poor, as heuristics would be unreliable. So no path forward is clear to me on this matter. -- 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 Qt integration with the Mir display server: Confirmed Status in “unity8” package in Ubuntu: Confirmed 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/qtmir/+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
[Touch-packages] [Bug 1352251] Re: Splash screen is shown as soon as QGuiApplication is instantiated
** No longer affects: unity8 -- 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 Qt integration with the Mir display server: Confirmed Status in “unity8” package in Ubuntu: Confirmed 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/qtmir/+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
[Touch-packages] [Bug 1352251] Re: Splash screen is shown as soon as QGuiApplication is instantiated
** Changed in: unity8 (Ubuntu) Status: New = Confirmed -- 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 Qt integration with the Mir display server: Confirmed Status in The Unity 8 shell: Confirmed Status in “unity8” package in Ubuntu: Confirmed 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/qtmir/+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
