I can confirm that QStandardPaths::writableLocation() is the main cause this and bug #1359831 is happening. The method checks whether the path specified is writable, and returns an empty string if cannot chmod +w on the path. The log we captured yesterday was not visible so far, therefore we diid not suspected that. Previous tests with the branch were working on device with any arbitrary sample app.
Adding some logs to StateSaver resulted in the following: QStandardPaths: wrong permissions on runtime directory /run/user/32011 [StateSaver] PATH "/com.ubuntu.camera/statesaver.appstate" Which means that the state file was about to be created in the root folder due to QStandardPaths::writableLocation() returned empty string. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor-easyprof-ubuntu in Ubuntu. https://bugs.launchpad.net/bugs/1363112 Title: StateSaver is not working on devices Status in Ubuntu UI Toolkit: Confirmed Status in “apparmor-easyprof-ubuntu” package in Ubuntu: Fix Released Status in “camera-app” package in Ubuntu: Fix Released Bug description: build 212 The StateSaver is not working anymore on devices, so apps saved state is no longer restored when they are relaunched after being killed by oom killer (or manually via kill -2) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1363112/+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