[Pkg-privacy-maintainers] Bug#812981: Bug#812981: torbrowser-launcher: torbrowser cannot start possibly due to apparmor issue

[Γιώργος Πάλλας]

On 28/01/16 12:47, Holger Levsen wrote:
> forcemerge 793142 812981
> user pkg-apparmor-team at lists.alioth.debian.org
> usertags 793142 + buggy-profile
> tags 793142 + help
> thanks
>
> Hi Giorgos,
>
> On Donnerstag, 28. Januar 2016, Giorgos Pallas wrote:
>> Package: torbrowser-launcher
>> Version: 0.1.9-1+deb8u2
> that's not the latest version but rather the latest version in stable…
> (refering to our previous private discussion…)

Yes, because I meant the latest and fully updated version from whatever 
Debian suite I am using, which is Debian GNU/Linux 8.3 (jessie).

>
> and indeed a known bug, see:
>
> #793142 torbrowser-launcher: Broken AppArmor profile on Jessie

So, indeed, I disabled apparmor (aa-disable 
/etc/apparmor.d/*torbrowser*) and it worked. But I see that #793142 has 
not been updated since July when it was filed. How could I help for 
solving this?
In our private discussion you suggested that I build the package from 
sid, but I don't understand what has this to do with fixing the apparmor 
rules.

G.

>
> Help to fix this would be much welcome.
>
>
> cheers,
> 	Holger


-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4446 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-privacy-maintainers/attachments/20160128/d341fab0/attachment-0001.bin>