# \[SOLVED\] Apparmor service not starting after Trixie upgrade

**URL:** https://discuss.freedombox.org/t/solved-apparmor-service-not-starting-after-trixie-upgrade/3865
**Category:** Support
**Created:** [August 24, 2025, 6:22pm UTC](https://discuss.freedombox.org/t/solved-apparmor-service-not-starting-after-trixie-upgrade/3865 "2025-08-24T18:22:44Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![joseph](https://discuss.freedombox.org/letter_avatar_proxy/v4/letter/j/dc4da7/32.png) [@joseph](https://discuss.freedombox.org/u/joseph)
#### Post date: [November 16, 2025, 9:14pm UTC](https://discuss.freedombox.org/t/solved-apparmor-service-not-starting-after-trixie-upgrade/3865/2 "2025-11-16T21:14:39Z")

</div>

There was an ejabberd apparmor profile which was preventing this service from starting. ejabberd was inactive on my FreedomBox and unused for a long time. GUI removal of ejabberd removed the apparmor profile which was causing the service to fail.

You can diagnose a problem such as this by using the logs applet in Cockpit.

Starting with this log entry…

 ![Screenshot From 2025-11-16 13-51-00](https://discuss.freedombox.org/uploads/default/original/2X/a/a366043457c702b4a472153377479ff384ec6c67.png)

I knew I needed something related to ‘su’. This command helped me find the suspect apparmor profile (does not need root):  
`/sbin/apparmor_parser -N /etc/apparmor.d | grep su`

The output from this included `/usr/sbin/ejabberdctl//su` which lead me to uninstalling ejabberd.

---

_[View the full topic](https://discuss.freedombox.org/t/solved-apparmor-service-not-starting-after-trixie-upgrade/3865)._