nect

> Not sure what you mean by "wait for an XScreen to be set up" when there are already many. In may case it's not because I'm running Wayland, in...

> I'm guessing from this Dunst will simply not work for me going forward then since it will by design bail rather than just run on the XScreen it's being...

> It doesn't work now which is why I have my above report. Well it works but ONLY on one XScreen. If anything calls it from another XScreen it just...

> Gotcha, I'm just glad it doesn't crash when called from a different XScreen any longer. Back when I chimed in on this bug report if I launched dunst on...

> Heh well I know myself a few others would probably dig that but seems nuts like me are a dying breed. Maybe XCB would make that easier? (if the...

> Same here: > > -❯ echo $WAYLAND_DISPLAY wayland-1 > > Linux nixos 6.6.26 1-NixOS SMP PREEMPT_DYNAMIC Wed Apr 10 14:36:08 UTC 2024 x86_64 GNU/Linux > > -❯ dunst --version...

> @bynect Yea I was getting the same errors as mentioned above. It's working fine now. I'm fairly new to > nixos so I'm not sure how dunst is starting...

> UPDATE: So the fix is to add `Environment=DISPLAY=:0` in the Service section. This was also mentioned here [NixOS/nixpkgs#154318](https://github.com/NixOS/nixpkgs/issues/154318). I am not sure if it's an issue related to dunst....

> @bynect I'm getting `wayland-1` is there anything you can suggest to fix this? I am not sure what you mean(?) Anyhow, dunst checks the WAYLAND_DISPLAY env var and if...

> >I am not sure what you mean(?) > > I meant the output of `echo $WAYLAND_DISPLAY` is `wayland-1`. > > I think it's probably not a big deal since...