Differences between revisions 10 and 11
Revision 10 as of 2015-01-29 14:38:28
Size: 2422
Editor: UlrikeUhlig
Comment: dont use so many subtitles
Revision 11 as of 2015-01-29 16:09:32
Size: 2400
Editor: UlrikeUhlig
Comment: no more navigation on top level pages
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
<<Navigation(siblings)>>
----
Line 18: Line 16:
If you've found a bug in an !AppArmor profile provided either by [[DebianPts:apparmor-profiles-extra | apparmor-profiles-extra]] or a software in Debian which ships its own profile, you might want to report a bug against one of these packages. If you think you've found a bug in an !AppArmor profile provided either by [[DebianPts:apparmor-profiles-extra | apparmor-profiles-extra]] or a software in Debian which ships its own profile, you might want to report a bug against one of these packages.

Provide logs and inspect AppArmor's state on the system

When reporting bugs which might involve a malfunctioning AppArmor profile, one should always provide the logs, and in particular the lines containing "DENIED":

sudo tail -f /var/log/syslog | grep DENIED

or (if auditd is installed):  sudo tail -f /var/log/auditd/auditd.log | grep 'DENIED' 

Find out more on how to inspect and debug AppArmor profiles and processes.

Usertags

If you think you've found a bug in an AppArmor profile provided either by apparmor-profiles-extra or a software in Debian which ships its own profile, you might want to report a bug against one of these packages.

However as the Debian Bug Tracking System ist package-centric, only the package maintainers will be automatically made aware you reported this bug. That is why we kindly ask you to add a usertag to your bug report, so that the Debian AppArmor Packaging Team will also be notified if AppArmor is involved or if you need help diagnosing this very fact.

We have agreed to use certain usertags on the BTS. Please use these tags when you can, as follows:

  • use the tag help-needed, to request help for initial diagnosis.

  • use the tag buggy-profile if AppArmor has been identified as culprit

  • merge-to-upstream

  • modify-profile

  • merge-from-upstream

  • new-profile

  • patch

  • platform

Quick how to usertag a bug

By email

Basically, you would send an email to control@bugs.debian.org with the following content:

 user pkg-apparmor-team@lists.alioth.debian.org
 usertags 12345 merge-to-upstream 

where "12345" is your bug number and "merge-to-upstream" the tag you want to add to the bug.

Using the CLI

The btscommand is provided by the devscripts package.

bts  user pkg-apparmor-team@lists.alioth.debian.org . usertags 12345 merge-to-upstream 

where "12345" is your bug number and "merge-to-upstream" the tag you want to add to the bug.