New comment by TeusLollo on void-packages repository

https://github.com/void-linux/void-packages/issues/37555#issuecomment-1913678185

Comment:
> @TeusLollo, here's the missing part:
> 
> `dbus-update-activation-environment DISPLAY WAYLAND_DISPLAY XDG_CURRENT_DESKTOP`
> 
> It should be executed after those variables initialized, e.g. inside `~/.config/river/init` in my case.

Indeed. 
I came across the whole `DISPLAY` mojo later when I also came across this other issue: https://bbs.archlinux.org/viewtopic.php?id=191251

I actually run: 

`exec dbus-run-session sway`
`exec dbus-update-activation-environment DISPLAY XAUTHORITY WAYLAND_DISPLAY XDG_CURRENT_DESKTOP`

In a custom script to start the `sway` WM. 

I specifically did that to solve the `[Gtk-WARNING **: cannot open display]` , but I had not connected the dots that this would also solve the whole `wofi` issue. This still does not explain why using `gendesk` worked as a workaround, but I digress. 

So, to anyone looking to utilize custom WMs, remember to run somewhere: 

`exec dbus-update-activation-environment DISPLAY XAUTHORITY WAYLAND_DISPLAY XDG_CURRENT_DESKTOP`

After your WM wayland session has begun.