right, so looking a bit more into the issue the state saver code is
http://bazaar.launchpad.net/~ubuntu-sdk-team/ubuntu-ui- toolkit/trunk/view/head:/src/Ubuntu/Components/plugin/statesaverbackend_p.cpp#L44 only sig2/15 are handled by unix handlers, the state saver triggers on sigkill (which Didier is using for testing) through the " QObject::connect(&QuickUtils::instance(), &QuickUtils::deactivated," signal summary of the issues - is sigkill supposed to be handled directly like e.g sigint? - ContentStore somehow makes the "deactivated" signal stop being triggered - the documentation doesn't list the handled signals -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1485222 Title: Using ContentStore disables silently any StateSaver capability To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/content-hub/+bug/1485222/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
