I'm wondering why this has not been fixed earlier for a package like firefox. Bugs were reported a long time ago whereas each of the fixes was easy, and sometimes even suggested by the reporters.
Not only that: Every time a new major release of FF is released it seems to be necessary to also test and adapt the apparmor profile. In the future, that can and should be done _before_ releasing a firefox package.
@chrisccoulson
Thanks. Please note that my patch is supposed to fix issues
- 1659922 apparmor blocking /dev/shm/ org.chromium. [...] vfs.MountTracke r
- 1659988 apparmor blocking python 3.5
- 1495248 apparmor blocking blocks /dev/shm
- 1553712 apparmor blocking org.gtk.
- 1628956 apparmor blocking /proc/[...]/net/arp
- 1643200 firefox showing black/white tabs (side effect of the fixes above)
I'm wondering why this has not been fixed earlier for a package like firefox. Bugs were reported a long time ago whereas each of the fixes was easy, and sometimes even suggested by the reporters.
Not only that: Every time a new major release of FF is released it seems to be necessary to also test and adapt the apparmor profile. In the future, that can and should be done _before_ releasing a firefox package.