[Touch-packages] [Bug 1363112] Re: StateSaver is not working on devices
** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: New = Fix Released -- 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: Fix Released Status in apparmor-easyprof-ubuntu package in Ubuntu: Fix Released Status in camera-app package in Ubuntu: Fix Released Status in ubuntu-ui-toolkit package in Ubuntu: Fix Released Status in ubuntu-ui-toolkit source package in Vivid: New 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
[Touch-packages] [Bug 1363112] Re: StateSaver is not working on devices
** Changed in: ubuntu-ui-toolkit (Ubuntu Vivid) Status: New = Fix Released -- 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: Fix Released Status in apparmor-easyprof-ubuntu package in Ubuntu: Fix Released Status in camera-app package in Ubuntu: Fix Released Status in ubuntu-ui-toolkit package in Ubuntu: Fix Released Status in ubuntu-ui-toolkit source package in Vivid: 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
[Touch-packages] [Bug 1363112] Re: StateSaver is not working on devices
** Changed in: ubuntu-ui-toolkit Status: Fix Committed = Fix Released -- 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: Fix Released 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
[Touch-packages] [Bug 1363112] Re: StateSaver is not working on devices
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
[Touch-packages] [Bug 1363112] Re: StateSaver is not working on devices
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
--
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
[Touch-packages] [Bug 1363112] Re: StateSaver is not working on devices
** Branch linked: lp:~zsombi/ubuntu-ui-toolkit/statesaver_path -- 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
[Touch-packages] [Bug 1363112] Re: StateSaver is not working on devices
Bill, I have ARM packages for the attached toolkit branch, could you also test with it? Camera app works for me, I can see the states restored (again) and also the state file created. https://launchpad.net/~ubuntu-sdk- team/+archive/ubuntu/testing/+build/6427230 -- 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
[Touch-packages] [Bug 1363112] Re: StateSaver is not working on devices
Jamie, I tried to add the following code to log the file permissions:
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;
}
QString path =
QString(%1/%2/statesaver.appstate).arg(runtimeDir).arg(applicationName);
qDebug() [StateSaver] PATH path;
// log permissions
QFile::Permissions wanted = QFile::ReadUser | QFile::WriteUser |
QFile::ExeUser;
QFile xdg(runtimeDir);
qDebug() QString([StateSaver] PERMISSIONS %1 WANTED
%2).arg(xdg.permissions(), 0, 16).arg(wanted, 0, 16);
And I'm getting the following result:
QStandardPaths: wrong permissions on runtime directory /run/user/32011
[StateSaver] PATH /run/user/32011/com.ubuntu.camera/statesaver.appstate
[StateSaver] PERMISSIONS 7700 WANTED 700
So, QFile::permissions() return 0x7700 for XDG_RUNTIME_DIR, which is
weird!
--
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
[Touch-packages] [Bug 1363112] Re: StateSaver is not working on devices
I'm guessing with the logging you are not doing the same comparison. xdg.permissions() and wanted don't have the same number of digits. I suggest looking at http://qt-project.org/doc/qt-4.8/qfile.html and reading the code for QFile.permissions() to make sure your logging is doing exactly the same thing. -- 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
[Touch-packages] [Bug 1363112] Re: StateSaver is not working on devices
Exactly, QFile.permissions() returns Qt-format permissions flags, which should not be mixed with UNIX permissions. What I printed out is the same QStandardPaths is having, and both are in Qt format. It's a coincidence that User RWX is the same as UNIX flags :) I filed a bug for QStandardPaths, meanwhile we can have the workaround in the last MR. -- 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
[Touch-packages] [Bug 1363112] Re: StateSaver is not working on devices
I tested the debs from comment 19 and all working as expected! -- 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
[Touch-packages] [Bug 1363112] Re: StateSaver is not working on devices
Fix committed into lp:ubuntu-ui-toolkit/staging at revision None, scheduled for release in ubuntu-ui-toolkit, milestone Unknown ** Changed in: ubuntu-ui-toolkit Status: Confirmed = Fix Committed -- 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: Fix Committed 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
[Touch-packages] [Bug 1363112] Re: StateSaver is not working on devices
** Changed in: ubuntu-ui-toolkit Milestone: None = 10.09 -- 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: Fix Committed 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
[Touch-packages] [Bug 1363112] Re: StateSaver is not working on devices
using rtm proposed build 75 (latest on krillin) I am still having the same problems as before as reported in comment #2 -- 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: Fix Committed 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
[Touch-packages] [Bug 1363112] Re: StateSaver is not working on devices
** Changed in: ubuntu-ui-toolkit Status: Fix Committed = Confirmed -- 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
[Touch-packages] [Bug 1363112] Re: StateSaver is not working on devices
Seems QStandardPath has some problems with XDG_RUNTIME_DIR, investigation continues... -- 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
[Touch-packages] [Bug 1363112] Re: StateSaver is not working on devices
** Branch linked: lp:ubuntu/utopic-proposed/ubuntu-ui-toolkit -- 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: Fix Committed 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
[Touch-packages] [Bug 1363112] Re: StateSaver is not working on devices
Fix committed into lp:ubuntu-ui-toolkit/staging at revision None, scheduled for release in ubuntu-ui-toolkit, milestone Unknown ** Changed in: ubuntu-ui-toolkit Status: In Progress = Fix Committed -- 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: Fix Committed 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
[Touch-packages] [Bug 1363112] Re: StateSaver is not working on devices
** Tags removed: touch-2014-09-11 ** Tags added: touch-2014-09-25 -- 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: In Progress 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
[Touch-packages] [Bug 1363112] Re: StateSaver is not working on devices
This bug was fixed in the package apparmor-easyprof-ubuntu - 1.2.22
---
apparmor-easyprof-ubuntu (1.2.22) utopic; urgency=medium
* Updates for abstract and anonymous socket mediation (LP: #1362199):
- ubuntu/*/ubuntu-*:
+ use dbus-strict and dbus-session-strict abstractions and remove
duplicated policy
+ allow ubuntu-sdk and ubuntu-webapp connect, receive and send on the
maliit abstract socket
+ allow write access to owner /{,var/}run/user/*/@{APP_PKGNAME}/{,**}
- ubuntu/*/unconfined: allow unix
- ubuntu/webview:
+ allow oxide to talk to sandbox via unix sockets
+ allow sandbox to talk to @{APP_PKGNAME}_@{APP_APPNAME}_@{APP_VERSION}
peer
+ allow various unix perms from base abstract for the sandbox to use
unix sockets
- debian/control: Depends on apparmor = 2.8.96~2541-0ubuntu4
* ubuntu/webview: use @{APP_PKGNAME}_@{APP_APPNAME}_@{APP_VERSION} for
signal now that we have @{APP_APPNAME} available (LP: #1363112)
* ubuntu/debug: 'audit deny @{HOME}/.local/share/ r' which is used by the
SDK to see if confined
* debian/control: Depends on apparmor = 2.8.96~2541-0ubuntu4~
-- Jamie Strandboge ja...@ubuntu.com Fri, 05 Sep 2014 15:17:07 -0500
** Changed in: apparmor-easyprof-ubuntu (Ubuntu)
Status: In Progress = Fix Released
--
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:
In Progress
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
[Touch-packages] [Bug 1363112] Re: StateSaver is not working on devices
Update: seems XDG_RUNTIME_DIR/APP_PKGNAME folder wasn't added to the policy, so the reason why we couldn't save the state. The policy is being added as we speak, so hopefully we will get it soon. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to camera-app in Ubuntu. https://bugs.launchpad.net/bugs/1363112 Title: StateSaver is not working on devices Status in Ubuntu UI Toolkit: In Progress Status in “camera-app” package in Ubuntu: New 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
[Touch-packages] [Bug 1363112] Re: StateSaver is not working on devices
Note, I have never seen a denial against XDG_RUNTIME_DIR/APP_PKGNAME which is why this hasn't come up prior to now. This path will be allowed in the next version of apparmor-easyprof-ubuntu. ** Also affects: apparmor-easyprof-ubuntu (Ubuntu) Importance: Undecided Status: New ** Changed in: camera-app (Ubuntu) Status: New = In Progress ** Changed in: camera-app (Ubuntu) Assignee: (unassigned) = Jamie Strandboge (jdstrand) -- 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: In Progress Status in “apparmor-easyprof-ubuntu” package in Ubuntu: New Status in “camera-app” package in Ubuntu: In Progress 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
[Touch-packages] [Bug 1363112] Re: StateSaver is not working on devices
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: apparmor-easyprof-ubuntu (Ubuntu) Status: New = Confirmed -- 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: In Progress Status in “apparmor-easyprof-ubuntu” package in Ubuntu: Confirmed Status in “camera-app” package in Ubuntu: In Progress 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
[Touch-packages] [Bug 1363112] Re: StateSaver is not working on devices
This bug was fixed in the package camera-app - 3.0.0+14.10.20140903-0ubuntu1 --- camera-app (3.0.0+14.10.20140903-0ubuntu1) utopic; urgency=low [ Michał Sawicz ] * Add :any to python dependency and install the camera app module in app-private libdir. [ Ugo Riboni ] * Add translations inside the .desktop file (LP: #1318008) [ Florian Boucault ] * Disable mode switching while recording videos. * Disable camera switching while recording videos. (LP: #1358302) * Photo roll: more fine grained media folder monitoring as to properly forward deletions to the view. Workarounded a couple of Qt bugs related to snapMode SnapOneItem. (LP: #1355407) * Do not allow switching to the camera roll while recording a video. * Rename application from 'camera' to 'com.ubuntu.camera' to make state saving work again. Seamlessly transition ~/Pictures/camera and ~/Videos/camera to new locations. (LP: #1363112) * Remove the X-Ubuntu-Gettext-Domain from the .desktop file, which causes the click scope not to load the inline translations. (LP: #1325626) * Align snapshot with viewfinder as to assure visual continuity in the transition from one to the other. (LP: #1362822) * Added cancel button in content export mode. (LP: #1362823) -- Ubuntu daily release ps-jenk...@lists.canonical.com Wed, 03 Sep 2014 18:52:44 + ** Branch linked: lp:ubuntu/utopic-proposed/camera-app ** Changed in: camera-app (Ubuntu) Status: In Progress = Fix Released -- 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: In Progress Status in “apparmor-easyprof-ubuntu” package in Ubuntu: Confirmed 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
[Touch-packages] [Bug 1363112] Re: StateSaver is not working on devices
We tested on camera-app and gallery-app (both are click) and neither working anymore -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1363112 Title: StateSaver is not working on devices Status in Ubuntu UI Toolkit: New Status in “ubuntu-ui-toolkit” package in Ubuntu: New 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
