This looks like the problem of using QStandardPaths::writableLocation().
The relevant code snipped from
QStandardPaths::writableLocation(RuntimeLocation):
// "and he MUST be the only one having read and write access to it. Its
Unix access mode MUST be 0700."
QFile file(xdgRuntimeDir);
const QFile::Permissions wantedPerms = QFile::ReadUser |
QFile::WriteUser | QFile::ExeUser;
if (file.permissions() != wantedPerms &&
!file.setPermissions(wantedPerms)) {
qWarning("QStandardPaths: wrong permissions on runtime directory
%s", qPrintable(xdgRuntimeDir));
return QString();
}
where QFile::permissions() drills down to ask for permissions using
QFileSystemMetaData::doStat(). This seems to cause the chmod issue we
have.
Not sure whether the failure described in this bug is caused by the
Toolkit's StateSaver services, but in case bug #1363112 fix solves this
issue, it can be marked as resolved. In StateSaver we have similar
issues as here, so at least I suspect the root cause is the same as we
have in the other bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1359831
Title:
Apps incorrectly perform a chmod on XDG_RUNTIME_DIR
To manage notifications about this bug go to:
https://bugs.launchpad.net/camera-app/+bug/1359831/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
