touch-packages team mailing list archive

[Zsombor Egri <1363112@xxxxxxxxxxxxxxxxxx>]

So, an iteration gives me the following log:
QStandardPaths: wrong permissions on runtime directory /run/user/32011
[StateSaver] No XDG_RUNTIME_DIR path set, cannot create appstate file.

The code prints this out is:
    QStringList runtimeDirs = QStandardPaths::standardLocations(QStandardPaths::RuntimeLocation);
    QString runtimeDir = runtimeDirs.size() > 0 ? runtimeDirs[0] : qgetenv("XDG_RUNTIME_DIR");
    if (runtimeDir.isEmpty()) {
        qWarning() << "[StateSaver] No XDG_RUNTIME_DIR path set, cannot create appstate file.";
        return;
    }

Which means that runtimeDirs string list is empty. If I do change the code to 
    QStringList runtimeDirs = QStandardPaths::standardLocations(QStandardPaths::RuntimeLocation);
    QString runtimeDir = (runtimeDirs.size() > 0 && !runtimeDirs[0].isEmpty()) ? runtimeDirs[0] : qgetenv("XDG_RUNTIME_DIR");
    if (runtimeDir.isEmpty()) {
        qWarning() << "[StateSaver] No XDG_RUNTIME_DIR path set, cannot create appstate file.";
        return;
    }


then I get the path correctly, because qgetenv() will be used to fetch the path. So, all in all seems QStandardPaths is just not good for this folder :/

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