Bug#750844: apparmor-notify: aa-notify started but no notification
On 08/29/2014 05:44 AM, intrigeri wrote: Hi John, what do these command output: $ sudo grep apparmor /var/log/kern.log $ aa-notify -p -s 1 -w 60 ? Cheers, -- intrigeri Hello Intrigeri, sudo grep apparmor /var/log/kern.log Aug 31 22:06:06 redcat kernel: [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-3.14-2-amd64 root=UUID=cc5cf21d-ec9f-4bbc-87b0-e1fbd1bc5351 ro apparmor=1 security=apparmor quiet Aug 31 22:06:06 redcat kernel: [0.00] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.14-2-amd64 root=UUID=cc5cf21d-ec9f-4bbc-87b0-e1fbd1bc5351 ro apparmor=1 security=apparmor quiet aa-notify -p -s 1 -w 60 is already start at boot automatically, john@redcat:~$ ps aux |grep aa-notify john 3435 0.0 0.0 39876 5216 ?Ss 14:05 0:01 /usr/bin/perl /usr/bin/aa-notify -p -s 1 -w 60 john 27567 0.0 0.0 12624 936 pts/4S+ 17:39 0:00 grep --color=auto aa-notify If I kill it(3435), then run /usr/bin/aa-notify -p -s 1 -w 60 john@redcat:~$ /usr/bin/aa-notify -p -s 1 -w 60 Starting aa-notify It start and run without warning/error message. Thank you. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#750844: apparmor-notify: aa-notify started but no notification
Hi John, what do these command output: $ sudo grep apparmor /var/log/kern.log $ aa-notify -p -s 1 -w 60 ? Cheers, -- intrigeri -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#750844: apparmor-notify: aa-notify started but no notification
On 2014年06月08日 星期日 12:29 上午, intrigeri wrote: What do you have in /etc/apparmor/notify.conf ? How does please run aa-notify in the Perl debugger sound to your ear? Cheers, Hi, what is Perl debugger? # -- # #Copyright (C) 2010 Canonical Ltd. # #This program is free software; you can redistribute it and/or #modify it under the terms of version 2 of the GNU General Public #License published by the Free Software Foundation. # # -- # Set to 'no' to disable AppArmor notifications globally show_notifications=yes # Only people in use_group can use aa-notify use_group=adm Sorry to say that, I don't know why, but now, aa-notify will startup automatically on system bootup. Now, my only problem is, aa-notity do not send the notify messages, when some program denied by apparmor. Thanks. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#750844: apparmor-notify: aa-notify started but no notification
Package: apparmor-notify Version: 2.8.0-5.1 Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** 1. aa-notify not start up on boot (I added the user to adm group) 2. aa-notify do not notify/popup the warning messages, even some program denied by apparmor. (I can see those warning messages in /var/log/kern.log and aa-notify is running) my system is installed a two weeks, sid/64bit. aa-notify never work on this system. but my old computer(damaged) also running sid/64bit, and aa-notify well on this old computer, automatic running on system boot, and do notify the warning messages, when some program denied by apparmor. how do I find out the problem? thanks. * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.14-1-amd64 (SMP w/8 CPU cores) Locale: LANG=zh_HK.UTF-8, LC_CTYPE=zh_HK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages apparmor-notify depends on: ii libapparmor-perl 2.8.0-5.1 ii libnotify-bin 0.7.6-2 ii perl 5.18.2-4 apparmor-notify recommends no packages. apparmor-notify suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#750844: apparmor-notify: aa-notify started but no notification
Control: tag -1 + moreinfo Hi John, thank you for reporting this bug to Debian! John Wong wrote (07 Jun 2014 13:27:24 GMT) : 1. aa-notify not start up on boot I'm slightly confused: the bug title says that aa-notify is started, and now you're telling us that it is not. May you please clarify? FTR, aa-notify starts just fine on my own sid (running GNOME Shell), but I can't easily reproduce the no notification part, as I'm only using the systemd journal (that's not supported by aa-notify yet), and have disabled syslog, so my kern.log is empty. (I added the user to adm group) A simple check, just in case: did you logout and log in again after doing this change? 2. aa-notify do not notify/popup the warning messages, even some program denied by apparmor. (I can see those warning messages in /var/log/kern.log and aa-notify is running) If you started aa-notify by hand, what options did you pass it? The default (as set in /etc/X11/Xsession.d/90apparmor-notify) is to call: /usr/bin/aa-notify -p -s 1 -w 60 Another thing worth checking is whether you have a libnotify compatible daemon running: what desktop environment are you running? Cheers, -- intrigeri | GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc | OTR fingerprint @ https://gaffer.ptitcanardnoir.org/intrigeri/otr.asc -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#750844: apparmor-notify: aa-notify started but no notification
On 2014年06月07日 星期六 10:17 下午, intrigeri wrote:
Hi
I'm slightly confused: the bug title says that aa-notify is started,
and now you're telling us that it is not. May you please clarify?
Sorry, confused you and other, I mean aa-notify is started manually by hand,
not started by init script or systemd or any thing automatic on system
bootup
(on my old computer, aa-notify will started on system boot automatically)
FTR, aa-notify starts just fine on my own sid (running GNOME Shell),
but I can't easily reproduce the no notification part, as I'm only
using the systemd journal (that's not supported by aa-notify yet), and
have disabled syslog, so my kern.log is empty.
Umm. I will search what is systemd journal, Yes my system also installed
systemd
-
dpkg -l |grep systemd
ii libpam-systemd:amd64 204-10 amd64
system and service manager - PAM module
ii libsystemd-daemon0:amd64 204-10
amd64systemd utility library
ii libsystemd-id128-0:amd64 204-10
amd64systemd 128 bit ID utility library
ii libsystemd-journal0:amd64 204-10
amd64systemd journal utility library
ii libsystemd-login0:amd64 204-10
amd64systemd login utility library
ii systemd 204-10 amd64system and
service manager
ii systemd-sysv 204-10 amd64system
and service manager - SysV links
-
A simple check, just in case: did you logout and log in again after
doing this change?
Yes, I already did it. (login/shutdown/reboot)
If you started aa-notify by hand, what options did you pass it?
The default (as set in /etc/X11/Xsession.d/90apparmor-notify) is to
call:
/usr/bin/aa-notify -p -s 1 -w 60
Yes, I tried /usr/bin/aa-notify -p -s 1 -w 60
/usr/bin/aa-notify -p --display $DISPLAY -s 7 -w 60
/usr/bin/aa-notify -p --display $DISPLAY -s 7 -w 60 -f /var/log/kern.log
all started by manually/hand,
and if I type echo $DISPLAY, it will show :0.0
Another thing worth checking is whether you have a libnotify
compatible daemon running: what desktop environment are you running?
My system is running sid/64bit/xfce4/gdm3/systemd .
Yes, I already installed libnotify.
dpkg -l |grep notify
ii apparmor-notify 2.8.0-5.1 all
AppArmor notification system
ii gir1.2-notify-0.7 0.7.6-2amd64
sends desktop notifications to a notification daemon (Introspection files)
ii libnotify-bin 0.7.6-2amd64sends
desktop notifications to a notification daemon (Utilities)
ii libnotify4:amd64 0.7.6-2amd64
sends desktop notifications to a notification daemon
ii python-notify 0.1.1-3amd64Python
bindings for libnotify
ii vlc-plugin-notify 2.1.4-1+b2 amd64
LibNotify plugin for VLC
ii xfce4-notifyd 0.2.4-3amd64
simple, visually-appealing notification daemon for Xfce
I know aa-notify is written by perl, I tried force it send notify
messages for debug/testing.
--- /usr/bin/aa-notify2014-06-05 19:13:09.0 +0800
+++ /tmp/aa-notify2014-06-07 23:00:07.586682497 +0800
@@ -376,6 +376,7 @@
$SIG{INT} = $SIG{TERM} = $SIG{HUP} = \signal_handler;
$SIG{'PIPE'} = 'IGNORE';
+send_message(testing);
if ($opt_w) {
sleep($opt_w);
}
It can send the notify message.
How can I find out what problem?
why it can not send the apparmor's notify message.
Thank you.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#750844: apparmor-notify: aa-notify started but no notification
johnw wrote (07 Jun 2014 15:11:12 GMT) :
I know aa-notify is written by perl, I tried force it send notify
messages for debug/testing.
--- /usr/bin/aa-notify2014-06-05 19:13:09.0 +0800
+++ /tmp/aa-notify2014-06-07 23:00:07.586682497 +0800
@@ -376,6 +376,7 @@
$SIG{INT} = $SIG{TERM} = $SIG{HUP} = \signal_handler;
$SIG{'PIPE'} = 'IGNORE';
+send_message(testing);
if ($opt_w) {
sleep($opt_w);
}
It can send the notify message.
Ah, that's useful, thanks.
What do you have in /etc/apparmor/notify.conf ?
How does please run aa-notify in the Perl debugger sound to your ear?
Cheers,
--
intrigeri
| GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc
| OTR fingerprint @ https://gaffer.ptitcanardnoir.org/intrigeri/otr.asc
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
