Absolpega

i had the same issue, deleting the lines `DUNST_INSTALLED=false && [[ -e "$(command -v dunstctl)" ]] && DUNST_INSTALLED=true` and `DUNST_IS_PAUSED=false && [[ "$DUNST_INSTALLED" == "true" ]] && DUNST_IS_PAUSED=$(dunstctl is-paused)` fixed...

I have just reinstalled arch and ran into this issue again. I am running awesomewm which uses its own notifications daemon. I tried installing dunst for a different WM when...

elkowar/eww uses this to detect wayland ```rust fn detect_wayland() -> bool { let session_type = std::env::var("XDG_SESSION_TYPE").unwrap_or_default(); let wayland_display = std::env::var("WAYLAND_DISPLAY").unwrap_or_default(); session_type.contains("wayland") || (!wayland_display.is_empty() && !session_type.contains("x11")) } ```

don't know how to work with github did not mean to do that

Now to try and tackle this problem. I think the approach in the current xprop implementation is based on this stack overflow question https://stackoverflow.com/a/1115292 No idea how xlib and xcb...