Control: tag -1 - moreinfo
On Tue, 17 Nov 2020 20:36:50 +0100 Axel Beckert wrote: [...] > Francesco Poli wrote: [...] > > [notify-osd](https://packages.debian.org/sid/amd64/notify-osd/filelist) > > does not seem to. > > Indeed, thanks! > > > On the other hand, > > [xfce4-notifyd](https://packages.debian.org/sid/amd64/xfce4-notifyd/filelist) > > seems to ship one. > > That one clearly works. :-) > > > Should I give systray-mdstat/1.2.0-1 another try, after installing > > xfce4-notifyd? > > Yes, please, at least for the checking other issue which I assume that > it is solved with the upload. Let's try: $ apt policy xfce4-notifyd xfce4-notifyd: Installed: 0.6.1-1 Candidate: 0.6.1-1 Version table: *** 0.6.1-1 800 800 http://deb.debian.org/debian testing/main amd64 Packages 500 http://deb.debian.org/debian unstable/main amd64 Packages 100 /var/lib/dpkg/status $ apt policy systray-mdstat systray-mdstat: Installed: 1.2.0-1 Candidate: 1.2.0-1 Version table: *** 1.2.0-1 500 500 http://deb.debian.org/debian unstable/main amd64 Packages 100 /var/lib/dpkg/status 1.1.0-1 800 800 http://deb.debian.org/debian testing/main amd64 Packages $ systray-mdstat & [1] 16468 $ It does not complain and it produces a notification, as shown in the attached xfce4-notifyd_screenshot.png ! [...] > Hmmmmm, now that I think about. Could this issue be also the reason > for your initially reported issues in #886419, just that > Desktop::Notify is less tolerant about this? $ apt policy systray-mdstat systray-mdstat: Installed: 1.1.0-1 Candidate: 1.1.0-1 Version table: 1.2.0-1 500 500 http://deb.debian.org/debian unstable/main amd64 Packages *** 1.1.0-1 800 800 http://deb.debian.org/debian testing/main amd64 Packages 100 /var/lib/dpkg/status $ systray-mdstat & [1] 13746 no notify because setup failed: $ killall -TERM systray-mdstat [1] Terminated systray-mdstat $ /usr/lib/notification-daemon/notification-daemon & [2] 13767 $ systray-mdstat & [3] 13782 no notify because setup failed: $ killall -TERM systray-mdstat [3]+ Terminated systray-mdstat $ killall -TERM notification-daemon [2]+ Terminated /usr/lib/notification-daemon/notification-daemon It complains even when notification-daemon is running... [...] > A potential third variant, but much more ugly in implementation, would > be to rely on passing the messages to /usr/bin/notify-send on the > commandline or STDIN, i.e. forking for every notification. I agree that this would _not_ be an elegant solution! [...] > Which actually leads me to the suspicion that maybe the cause is that > notification-daemon is not running on your desktop system for whatever > reason (like using a classic X Window Manager which doesn't care about > autostart desktop files — which I consider to be a totally valid > reason btw. :-) I use Fluxbox as a standalone window manager: I don't use a full desktop environment. I start my X session with startx and a custom ~/.xsession file. > > And since you have none of the other notification daemons installed, > which could be activated over D-Bus automatically, the reported issue > sounds like a probable outcome of that scenario. > > <moreinfo> > > Could you check on your system if > /usr/lib/notification-daemon/notification-daemon is actually running? > > </moreinfo> It is not! I get not output from: $ ps aux | grep notification-daemo[n] $ > > If it is not running, we have found the cause (dependency still > missing, though :-) and I probably should catch that case in > systray-mdstat. Let's try the following: $ apt policy systray-mdstat systray-mdstat: Installed: 1.2.0-1 Candidate: 1.2.0-1 Version table: *** 1.2.0-1 500 500 http://deb.debian.org/debian unstable/main amd64 Packages 100 /var/lib/dpkg/status 1.1.0-1 800 800 http://deb.debian.org/debian testing/main amd64 Packages $ systray-mdstat & [1] 15080 org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Notifications was not provided by any .service files [1]+ Exit 11 systray-mdstat $ /usr/lib/notification-daemon/notification-daemon & [1] 15081 $ systray-mdstat & [2] 15085 $ It does not complain and it produces a notification, as shown in the attached notification-daemon_screenshot.png ! Should I add: /usr/lib/notification-daemon/notification-daemon & somewhere near the beginning of my ~/.xsession file? And: killall -TERM notification-daemon somewhere near the end of my ~/.xsession file? Or should I install xfce4-notifyd and have it autostarted via DBus? > > I nevertheless think that this then would be a bug in > notification-daemon as it only starts properly depending on the > desktop environment. If there's a way to automatically start notification-daemon, I would be happy to see it implemented... -- http://www.inventati.org/frx/ There's not a second to spare! To the laboratory! ..................................................... Francesco Poli . GnuPG key fpr == CA01 1147 9CD2 EFDF FB82 3925 3E1C 27E1 1F69 BFFE
pgpgJxt1mXY3o.pgp
Description: PGP signature
