It's possible this is a feature request and not bug (felt borderline), so feel free to update :)

Rofi version (rofi -v)

1.7.5

Configuration

https://gist.github.com/russelltg/302aa2af722d3c43192f53ee553da731

Theme

https://gist.github.com/russelltg/eb33d77bbb4645483bf2911fe2f507cb

Timing report

No response

Launch command

rofi -show drun

Step to reproduce

1. Find a .desktop file with a different commandline for dbus activation and non-dbus activation. I use the easyeffects flatpak.
2. Spawn it with rofi -show drun
3. Check the commandline used. I use ps aux | grep easyeffects

Expected behavior

It uses d-bus activation. In the case of easyeffects, this means that the commndline is easyeffects --gapplication-service

Actual behavior

dbus activation is not use. In the case of easyeffects, the commandline is just easyeffects

Additional information

The author of easyeffects told me (wwmm/easyeffects#1215 (comment)) that rofi should use dbus activation. It seems gnome, kde, and gtk-launch all launch properly with dbus activation.

Using wayland display server protocol

• No, I don't use the wayland display server protocol

I've checked if the issue exists in the latest stable release

• Yes, I have checked the problem exists in the latest stable version