No, not a duplicate - bug 1671424 is about *not* signalling the processes, but just closing the windows.
This bug is about quitting the whole app at once (not all its windows in sequence) or force-quitting it for whatever reason (say, misbehaving app). With Unity8, an app is more than just the Mir client - it's the whole group of processes managed through UAL/systemd. ** This bug is no longer a duplicate of bug 1671424 qtmir destroys windows after requesting them to close -- 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/1628589 Title: Need better session management for apps Status in Canonical System Image: Triaged Status in Libertine: Triaged Status in Libertine devel series: Triaged Status in Libertine trunk series: Triaged Status in libertine package in Ubuntu: Triaged Status in ubuntu-app-launch package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Triaged Bug description: This is the master bug for better session management for apps. All other bugs affected by this will be dup'ed to this bug. Currently, if a user closes an app using the 'X' button on the window, many bad things can happen including data loss. If a user is editing a document and accidentally hits the X while the data is not saved, the user will not be prompted to save and the data will be lost. Another example is Libertine helper apps can crash when Xmir is killed. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1628589/+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
