The dialog is created with the context of the Page. When closing the dialog, it starts to fade out, and then the page is popped (and destroyed) before the dialog fade-out is finished. This makes the context of the dialog invalid, and the ScriptAction that makes the dialog invisible (and destroys it) is not executed. Because of this, the dialog stays active (but with opacity 0) and blocks events from getting to the active page.
-- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1568016 Title: Freezes in uitk Status in ubuntu-ui-toolkit package in Ubuntu: In Progress Bug description: Ever since moving to uitk 1.3, I see occational freezes, mostly related to page push/pop operations. This happens very randomly but causes the app to freeze and requires a restart. I've triggered such freezes in many situations in all sorts of different apps but never could really reproduce it. There is definitely a race condition involved. Such freezes seem to happen most likely directly after app startup when pressing a button in the toolbar while stuff is still loading, but not only. I've also seen it happening in the middle of using an app. Now a friend of mine wrote an app and managed to get into a situation where it reliably triggers a freeze. I am not sure if this is the same as I'm observing or if its a different one. However, it is a freeze and might lead us to the real reason. Attached you'll find an archive that allows reproducing at least that one variant of the freeze. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1568016/+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
