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
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
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
On 2019-10-12 at 09:25:20, Nikos Tsipinakis wrote:
> This is usually caused by not having exported the DISPLAY variable into the
> systemd environment, there has been extensive discussion about this in #347[1]
> upstream.
>
> How are you starting X11, are you using a custom xinitrc?
I've got this
Hi,
This is usually caused by not having exported the DISPLAY variable into the
systemd environment, there has been extensive discussion about this in #347[1]
upstream.
How are you starting X11, are you using a custom xinitrc?
However it is weird that systemd reports that dunst is running even
Package: dunst
Version: 1.4.1-1
Severity: normal
Once a day, at exactly the same time (+/- a couple of minutes), I get the
following errors in my logs:
Oct 6 07:39:49 akranes dunst[28243]: CRITICAL: Cannot open X11 display.
Oct 6 07:39:49 akranes systemd[28227]: dunst.service: Main process
6 matches
Mail list logo
