Hi, Holger Levsen wrote (12 Aug 2014 11:43:35 GMT) : > so the launcher (version 0.1.2 still) today tried to upgrade to tbb > 4.0-alpha, > which IMO it shouldnt do, but anyway, it also failed:
0.1.2-1 worked for me 2 days ago on sid. Not tried 0.1.3-1 yet. > [...] > exceptions.OSError: [Errno 13] Permission denied > I assume this is due to me using apparmor, Quite possibly, as the AppArmor profiles shipped in 0.1.2-1 are only partly updated wrt. the XDG-compliant dirs, were clearly never fully tested on current sid, and are totally broken: https://github.com/micahflee/torbrowser-launcher/issues/124 https://github.com/micahflee/torbrowser-launcher/pull/125 (They are even more broken once combined with the fact that torbrowser-launcher downloads 4.0-alpha, that changes the location of many directories. Addressed too in my pull request.) > Aug 12 13:32:31 matrix kernel: audit: type=1400 audit(1407843151.609:1377): > apparmor="DENIED" operation="open" profile="/usr/bin/torbrowser-launcher" > name="/usr/bin/python2.7" pid=20218 comm="file" requested_mask="r" > denied_mask="r" fsuid=1002 ouid=0 This specific one is innocuous, and I've proposed to hide it with commit bfabd82 that's on the #125 pull request. Did you see any other AppArmor denial message that could help confirm that the AppArmor profiles were at fault on that one? Cheers, -- intrigeri -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
