Axel Regnat: > Not sure what you mean with "AppArmor audit daemon log" but I couldn't find > anything from apparmor in kern.log or sys.log when starting mumble. I also > updated to 1.3 like you suggested and the problem seems to be fixed. Thanks > for > your help. > > Axel
You're very welcome. :) I'm glad Mumble 1.3 fixes this. Re: AppArmor audit daemon: When using AppArmor it's beneficial to get reports of when certain actions are blocked, such as using apparmor-notify, and I believe another way is to use auditd to log these events. As long as you have some way of knowing when AppArmor blocks an action, that's all I was looking for, so that you could debug if that was the reason for the issue. And thanks for marking and closing the bug. :) -- Chris -- Chris Knadle chris.kna...@coredump.us
