10:42:55     zsombi | [11:25:35] <zsombi> didrocks: if a simple ContentStore 
disables StateSaver, then perhabs that should be checked 
                    | fiorst...                                                 
                                                      
10:42:55     zsombi | [11:26:19] <zsombi> didrocks: all StateSaver does is to 
hook to SIGINT and SIGTERM signals to get notified when 
                    | the app is killed/stopped, not more                       
                                                      
10:42:55     zsombi | [11:26:53] <zsombi> didrocks: and then, if there're 
states saved, it will restore them one by one as they come  
                    | alive                                                     
                                                      
10:42:55     zsombi | [11:28:30] <zsombi> didrocks: there is a piece of code to 
which kenvandine might refer, which arises when an app
                    | is launched thru ContentHub, which delays state 
restoration till the URI is handled, but that piece of code is  
                    | not in the toolkit, so these two components have nothing 
in common really                                       

Ken, seems that Zomber thinks it's on your side, mind looking at it
then? Thanks!

-- 
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

Reply via email to