Anybody got any clues on where to go from here? In particular, why the filemanager desktop file can touch a file, but ours can't, when both are unconfined?
On Fri, 2016-04-29 at 10:39 +0100, Sam Bull wrote: > OK, my laptop got destroyed, but has been fixed and I am back trying > to > sort this out again. > > This is the status at the moment: > > When launching the app, there are a couple of apparmor denials > about > trying to read /usr/local/lib/python3.4/dist-packages. > This proves that it is atleast running the Python binary. > > We changed it to an unconfined app. This means there are no more > denials, but it still does not launch, and there are still no > logs, > crash reports or files written anywhere. > > We then wanted to check the unconfined nature of the app, and so > edited the desktop file and changed the Exec line to something > like > 'touch /home/phablet/testfile'. Still, this did not actually > succeed > in writing a file. > > We then tried editing the filemanager-app's desktop file with the > same command. This successfully wrote a file. > > So, now we are really confused as to how the filemanager-app is > able > to write this file, but our app is not able to. Despite running > the > same command, and according to Permy having the same apparmor > rules.
signature.asc
Description: This is a digitally signed message part
-- Mailing list: https://launchpad.net/~ubuntu-phone Post to : [email protected] Unsubscribe : https://launchpad.net/~ubuntu-phone More help : https://help.launchpad.net/ListHelp
