automatically inject dbus slot & use it
Metadata
Current evaluation
Feature request to have snapcraft auto-inject a dbus session slot when an app's desktop file declares X-DBUS-ServiceName, so KDE-style apps work out of the box. Open since ~2017 with no labels, no comments, no maintainer activity, and no evidence of implementation.
Suggested action: needs triage
Reason: The issue has zero comments, no labels, and no maintainer interaction in ~7.4 years (2705 days), so it has never been triaged. It is a well-motivated feature request (dbus registration failures breaking KDE apps in snaps) rather than a bug, but no evidence exists that it was implemented or superseded, so it should be assessed by a maintainer before any close decision.
Impact:
40
Quick Win:
18.0
Staleness:
95
Complexity:
55
Confidence:
65
Support Request:
10
Issue body
example:
https://github.com/apachelogger/snap-appstreamtest
In KDE software we often use dbus on applications and 90% of the time do it in fashion that also discretely exposes this information via the desktop file.
When a snapcraft `app` has a desktop file (in snap/, or via desktop-file:, or via common-id:) it could check this desktop file for a 'X-DBUS-ServiceName' entry and automatically inject the relevant dbus boilerplate to register the service with the snap app.
From the snap-appstreamtest example
- snapcraft.yaml has app kbruch and that has common-id org.kde.kbruch.desktop
- the appstream data for that common-id define a launchable org.kde.kbruch.desktop
- https://github.com/apachelogger/snap-appstreamtest/blob/master/src/usr/share/applications/org.kde.kbruch.desktop
- desktop file has `X-DBUS-ServiceName=org.kde.kbruch`
- snapcraft could automatically inject a boilerplate slot to enable dbus.
slots:
dbus-session-org-kde-kbruch:
interface: dbus
name: org.kde.kbruch # as per the desktop file entry
bus: session
Currently the dev experience sucks a bit because they'd snap an application (and forget about dbus, because why wouldn't they), upload to store, wait for snap tests to pass, publish, install, and find that the application usually will not work because it attempts to register on dbus and fails to (and usually that is handled as a fatal problem).
If snapcraft automatically detected dbus names this would just work out of the box.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.8-27b |
Impact:
40
Quick Win:
18.0
Staleness:
95
Complexity:
55
Confidence:
65
Support Request:
10
|
needs triage | Feature request to have snapcraft auto-inject a dbus session slot when an app's desktop file declares X-DBUS-ServiceName, so KDE-style apps work out of the box. Open since ~2017 with no labels, no comments, no maintainer activity, and no evidence of implementation. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
70
Confidence:
90
Support Request:
10
|
close stale | Feature request to auto-inject dbus slots from desktop file X-DBUS-ServiceName entries. Untriaged, 7+ years old, no maintainer interaction, and likely obsolete given snapcraft's evolution and standard manual slot practices. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
65
Confidence:
92
Support Request:
10
|
close stale | Feature request to auto-inject D-Bus slots from desktop file entries. Open for over seven years with zero maintainer interaction or implementation. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
95
Complexity:
45
Confidence:
70
Support Request:
5
|
needs triage | Feature request to automatically inject D-Bus slots into snapcraft.yaml based on X-DBUS-ServiceName in desktop files. Untriaged, inactive for over 7 years. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
98
Complexity:
45
Confidence:
85
Support Request:
10
|
needs triage | Feature request for snapcraft to auto-detect X-DBUS-ServiceName in desktop files and inject corresponding dbus slots, improving developer experience. Unresponded to for over 7 years. |
Update history
No update history recorded yet.
Related issues
No related issues found above the similarity threshold.