On 2019-10-15 at 11:36:30, Nikos Tsipinakis wrote: > > /usr/bin/systemctl status --user dunst > > Huh, why `status` and not `start`? Is that a typo?
Yes, typo indeed! I've now fixed that. > Perhaps the import-environment fails, could you add `echo DISPLAY=$DISPLAY` > under that > and see if it appears in .xsession_errors? I added a line to that startup script to email me the value of $DISPLAY when it runs and I got the following: DISPLAY=:1 > Indeed that looks like it's running - however the error you showed is always > fatal and the logs do show dunst service failed a few times, so something > happens at that point in time daily that prevents access to X11 and dunst > can't > start? Bizarre. These are all of the dunst-related errors from today: Oct 20 07:04:58 hostname dunst[9811]: CRITICAL: Cannot open X11 display. Oct 20 07:04:58 hostname systemd[9794]: dunst.service: Main process exited, code=exited, status=1/FAILURE Oct 20 07:04:58 hostname systemd[9794]: dunst.service: Failed with result 'exit-code'. Oct 20 07:04:58 hostname systemd[9794]: Failed to start Dunst notification daemon. Oct 20 07:09:28 hostname dunst[24191]: CRITICAL: Cannot open X11 display. Oct 20 07:09:28 hostname systemd[24177]: dunst.service: Main process exited, code=exited, status=1/FAILURE Oct 20 07:09:28 hostname systemd[24177]: dunst.service: Failed with result 'exit-code'. Oct 20 07:09:28 hostname systemd[24177]: Failed to start Dunst notification daemon. Oct 20 07:42:24 hostname dunst[18236]: CRITICAL: Cannot open X11 display. Oct 20 07:42:24 hostname systemd[18223]: dunst.service: Main process exited, code=exited, status=1/FAILURE Oct 20 07:42:24 hostname systemd[18223]: dunst.service: Failed with result 'exit-code'. Oct 20 07:42:24 hostname systemd[18223]: Failed to start Dunst notification daemon. Oct 20 07:42:50 hostname dunst[18303]: CRITICAL: Cannot open X11 display. Oct 20 07:42:50 hostname systemd[18289]: dunst.service: Main process exited, code=exited, status=1/FAILURE Oct 20 07:42:50 hostname systemd[18289]: dunst.service: Failed with result 'exit-code'. Oct 20 07:42:50 hostname systemd[18289]: Failed to start Dunst notification daemon. > > Is there a cron-like job that runs every morning? > > No, there's nothing that's scheduled to run at a specific time. However, dbus > _will_ try to start dunst via systemd if a notification comes through and it > detects that it isn't running. Perhaps you have a cron scheduled at that time? I looked at the notification log (Ctrl+`) this morning after seeing these errors in the logs and there was nothing matching that timestamp. Not surprising since these are complaints about failing to start. The only cronjob I have that is set to run specifically at 7am is: /etc/cron.d/anacron but then maybe the /etc/cron.daily/ jobs also run at around that time. Francois -- https://fmarier.org/
