On 12/10, Francois Marier wrote: > On 2019-10-12 at 09:25:20, Nikos Tsipinakis wrote: > I've got this line in my ~/.config/i3/config: > > exec --no-startup-id /home/francois/devel/remote/user-scripts/startup > > and that corresponds to a script [1] with these lines: > > /usr/bin/systemctl --user import-environment DISPLAY > /usr/bin/systemctl status --user dunst
Huh, why `status` and not `start`? Is that a typo? Perhaps the import-environment fails, could you add `echo DISPLAY=$DISPLAY` under that and see if it appears in .xsession_errors? > > However it is weird that systemd reports that dunst is running even though > > it > > obviously fails to start. I'm not sure what is going on there. > > I don't think it fails to start because it works fine and it looks like > this: > > $ systemctl status --user dunst.service > ● dunst.service - Dunst notification daemon > Loaded: loaded (/usr/lib/systemd/user/dunst.service; enabled; vendor > preset: enabled) > Active: active (running) since Fri 2019-10-11 19:21:31 PDT; 15h ago > Docs: man:dunst(1) > Main PID: 5330 (dunst) > Memory: 4.0M > CGroup: /user.slice/user-1000.slice/user@1000.service/dunst.service > └─5330 /usr/bin/dunst > > $ pgrep -a dunst > 5330 /usr/bin/dunst 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. > The part that confuses me is that once a day (always almost exactly at the > same time) it tries to start or restart (and fails) even though it's already > running in my user session. > > 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?
