Package: apparmor-notify Version: 2.11.1-3 Followup-For: Bug #845232 I had the same issue.
= What did I do At first I found the .desktop file and run the command by hand. I learnt that I would nee dto read /var/log/kern.log, so I added my user to the adm group. After that I restarted my session and learn that I would need to be in the sudo group. = What I recommend Adding a README.Debian file explaining this details. That's the first thing I tried to find when I noticed aa-notify was not working. Thanks!! -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'unstable-debug'), (500, 'buildd-unstable'), (500, 'testing'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.14.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.UTF-8 (charmap=UTF-8), LANGUAGE=en_US (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) Versions of packages apparmor-notify depends on: ii libapparmor-perl 2.11.1-3 ii libnotify-bin 0.7.7-2 ii perl 5.26.1-3 apparmor-notify recommends no packages. apparmor-notify suggests no packages. -- no debconf information