I disabled the two Firefox-related AppArmor profiles, verified that Firefox launched, then re-enabled them in enforce mode.
The sequence was approximately: ```bash sudo aa-disable /etc/apparmor.d/firefox sudo aa-disable /etc/apparmor.d/usr.bin.firefox firefox sudo aa-enforce /etc/apparmor.d/firefox firefox sudo aa-enforce /etc/apparmor.d/usr.bin.firefox firefox ``` After that, Firefox kept launching normally, and I no longer saw new `file_lock` denials on `.parentlock` in `journalctl`. On 7/8/26 14:38, John Johansen wrote: > can you explain the method you used to reload/recompile the apparmor > profile for firefox? -- -- Sylvain Hallé, Ph.D. Professeur titulaire / Full professor Titulaire de la Chaire de recherche du Canada en spécification, test et vérification de systèmes informatiques Canada Research Chair on Software Specification, Testing and Verification Université du Québec à Chicoutimi, Canada E-mail: [email protected] Web: https://leduotang.ca/sylvain -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2160083 Title: Firefox AppArmor profile denied file lock on .parentlock after snap- to-PPA transition; reload fixed, reboot did not To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2160083/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
