StateSaver doesn't work when app is closed via SIGINT or SIGTERM

The right way to do it in Qt5:
http://qt-project.org/doc/qt-5.0/qtdoc/unix-signals.html

It is important to respond to these signals because at the moment they are the main way to terminate an application when writing an autopilot test that requires the app to be restarted.
On the desktop this can be worked around by sending the app CTRL+F4 but on the device at the moment there's no standard way to terminate the app except sending it a signal.

Actually this is important for the case when upstart stops an app from the application scope. Importance risen to Critical.

It has been decided that SIGTERM clears the states saved, therefore only SIGINT will do state saving.

This bug was fixed in the package ubuntu-ui-toolkit - 0.1.46+14.04.20140331-0ubuntu1

---------------
ubuntu-ui-toolkit (0.1.46+14.04.20140331-0ubuntu1) trusty; urgency=low

  [ Zoltán Balogh ]
  * Separate the online and offline documentation and install the QtC
    help file

  [ Zsombor Egri ]
  * Move state data file to temp folder (LP: #1276760)
  * StateSaver does cleanup if the app is closed due to SIGTERM. This is
    needed as upstart sends this signal when the application is closed
    from app scope. SIGINT saves the state. (LP: #1259498)
  * MainView binding loop fix when backgroundColor is changed runtime.
    (LP: #1204453)

  [ Loïc Molinari ]
  * [Perf metrics] Considered number of CPU cores for CPU usage.

  [ tpeeters ]
  * Add useDeprecatedToolbar property to MainView which can be used to
    disable the current toolbar. Unsetting that property will in future
    also enable new features in the header. (LP: #1273184)
  * Close panel on contents press instead of click, so that composed
    events are not eaten by the InverseMouseArea of the Panel. (LP:
    #1295720)

  [ Christian Dywan ]
  * Treat QML warnings as fatal except for explicitly listed tests
 -- Ubuntu daily release <email address hidden> Mon, 31 Mar 2014 18:26:59 +0000