I apologise for the delay in replying but I don't have many clues as to what's happening here or any easy ways to debug it.
On 20/10, Francois Marier wrote: > > 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 Curious why it's :1 and not :0, are you running a second X11 session? It could have something to do with that if that's the case. > 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. Well, when anacron runs it basically also calls all global crons in the system so that doesn't help much. >From the logs you provided it seems that for your own user session dunst seems to be running normally even when these failure logs appears, so my working hypotheses now is that there's an automated job trying to send a notification as a different user - systemd tries to start dunst which fails as there's no X11 running as that user. Does that sound something that might be happening - do you have any such customizations to your systems? I'm not aware of any packages that use libnotify notifications as part of cron/automated jobs so it's most likely something added later. -- Best Regards, Nikos Tsipinakis
