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
amd64 systemd utility library
ii libsystemd-id128-0:amd64 204-10
amd64 systemd 128 bit ID utility library
ii libsystemd-journal0:amd64 204-10
amd64 systemd journal utility library
ii libsystemd-login0:amd64 204-10
amd64 systemd login utility library
ii systemd 204-10 amd64 system and
service manager
ii systemd-sysv 204-10 amd64 system
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-2 amd64
sends desktop notifications to a notification daemon (Introspection files)
ii libnotify-bin 0.7.6-2 amd64 sends
desktop notifications to a notification daemon (Utilities)
ii libnotify4:amd64 0.7.6-2 amd64
sends desktop notifications to a notification daemon
ii python-notify 0.1.1-3 amd64 Python
bindings for libnotify
ii vlc-plugin-notify 2.1.4-1+b2 amd64
LibNotify plugin for VLC
ii xfce4-notifyd 0.2.4-3 amd64
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-notify 2014-06-05 19:13:09.000000000 +0800
+++ /tmp/aa-notify 2014-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
