# Dunst crashes if run as service

**URL:** https://discourse.nixos.org/t/dunst-crashes-if-run-as-service/27671
**Category:** Help
**Created:** [April 27, 2023, 7:12pm UTC](https://discourse.nixos.org/t/dunst-crashes-if-run-as-service/27671 "2023-04-27T19:12:50Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![nairou](https://discourse.nixos.org/user_avatar/discourse.nixos.org/nairou/32/9192_2.png) [@nairou](https://discourse.nixos.org/u/nairou)
#### Post date: [April 28, 2023, 4:38pm UTC](https://discourse.nixos.org/t/dunst-crashes-if-run-as-service/27671/2 "2023-04-28T16:38:01Z")

</div>

I think I figured this one out. Apparently programs launched by dbus don’t by default see the wayland session. I was able to fix that by running:

```auto
dbus-update-activation-environment WAYLAND_DISPLAY

```

After that, `dunst` (and other notification daemons I tried, like `fnott` and `mako`) started working as expected.

---

_[View the full topic](https://discourse.nixos.org/t/dunst-crashes-if-run-as-service/27671)._
