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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1363112 Title: StateSaver is not working on devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1363112/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
