Skip to content

Conversation

@City-busz
Copy link
Contributor

And mark the application as D-Bus activatable. This allows application launchers to activate it via D-Bus.

Reference:
https://specifications.freedesktop.org/desktop-entry-spec/1.3/dbus.html

City-busz and others added 2 commits April 13, 2025 10:33
And mark the application as D-Bus activatable. This allows application
launchers to activate it via D-Bus.
@mufeedali
Copy link
Member

Hey @City-busz , could you let me know what use case in particular does this solve for you?

@City-busz
Copy link
Contributor Author

This is needed for better integration with GNOME. See: https://developer.gnome.org/documentation/guidelines/maintainer/integrating.html#d-bus-activation

When DBusActivatable=true is set in the desktop file, the application launcher of GNOME Shell and KDE Plasma launches the application via D-Bus instead of fork()/exec() the executable, so the D-Bus daemon will control the process by setting up its environment, adding it to the correct cgroup, just like how usual D-Bus services work. And when the application is already running, the primary instance will receive the activation or the desired action directly.
If the service file is installed, the app can be launched via D-Bus with the following command:

gapplication launch app.drey.Dialect

@mufeedali mufeedali merged commit 24a3e3e into dialect-app:main Nov 25, 2025
2 checks passed
@mufeedali
Copy link
Member

Sorry it has taken so long. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants