
rule) Have you seen such an entries in your log files etc.? Did you have had a similar issues with firefox, just before adding rules (see bug report)? (Especially these mentioned in bug report).īy the way: Simon, what about two rules: mentioned above "unix" and "dbus" rule (see bug report and 7. Once again: thank You Simon for an informations! I hope also that someone else will confirm the correctness of all these rules. ✗ monitor the log files, journalctl(1) command etc. ✗ use only "/tmp/.X11-unix/* rw," rule (until more information will be gathered)

✗ add an "owner" prefix for all rules (thanks Simon!) # profile= "/usr/lib/ firefox/ firefox _mask=r' (see bug report)Īnd everything seems to work okay: just as before update to 60.0 version. Here are the AppArmor rules, that helped and now Firefox works okay. Firefox main windows has been resized etc.Īnyway, there was also a lot of "DENIED" entries in a log files. No website was working, I can not click on anything, there was no menu bar and so on. After first start there was so many problems: with new tab (errors), Sandbox option (one new option with 'false' value).
