El 7 dic. 2017 5:40 a.m., "intrigeri" <intrig...@debian.org> escribió:
Hi, Lisandro Damián Nicanor Pérez Meyer: > On 6 December 2017 at 18:59, Lisandro Damián Nicanor Pérez Meyer > <lisan...@debian.org> wrote: >> 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. I believe this problem has nothing to do with the one reported by Jean-Michel, Uups, sorry for the hijack then! but whatever: it's a really good point & thanks for your suggestion. The next upload (most likely today) will fix that by: - documenting in /u/s/doc/apparmor-notify/README.Debian that one must be in the "adm" group to use aa-notify Please note that after adding myself to the adm group I still had to add myself to the sudo group... - disabling use_group in notify.conf, so this (mostly useless AFAICT) check does not harm UX ... But maybe this explains it? So let's not bother tracking this on a new, dedicated bug. ACK, thanks for your work!
