← Back to issue list

automatically inject dbus slot & use it

View original Launchpad issue

Metadata

Project
snapcraft (launchpad)
Number
#1823308
Type
issue
State
open
Author
~apachelogger
Labels
—
Created
Updated
Closed
—

Current evaluation

Requests automatic D-Bus slot injection from desktop metadata, including X-DBUS-ServiceName; it remains open and untriaged, with current common-id and explicit bus-name support not covering the requested inference.

Suggested action: needs triage

Reason: The body supplies a concrete common-id/desktop-file example and exact slot shape, but the issue has no labels or comments and shows no maintainer triage. Repository history contains later common-id support (#1960) and D-Bus schema support (#3425), while the requested X-DBUS-ServiceName inference is not shown; the issue's age alone does not justify closing it.

Evaluated by: mr-cal-bot

Impact: 55 Quick Win: 17 Complexity: 54 Confidence: 64 Actionability: 68

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
stealth/space-bunny-alpha
Impact: 55
Quick Win: 17
Complexity: 54
Confidence: 64
Actionability: 68
needs triage Requests automatic D-Bus slot injection from desktop metadata, including X-DBUS-ServiceName; it remains open and untriaged, with current common-id and explicit bus-name support not covering the requested inference.
stealth/space-bunny-alpha
Impact: 48
Quick Win: 12
Complexity: 67
Confidence: 89
Actionability: 74
needs triage Untriaged proposal to auto-create a D-Bus service slot from X-DBUS-ServiceName in desktop metadata; its KDE reproducer is concrete, but no implementation or maintainer assessment is evident.
qwen/qwen3.8-27b
Impact: 40
Quick Win: 18
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.

Update history

Date Change
created

Related work

  • Related To: snapcraft#1960 (confidence 92%)

    Later extractor work added common-id support, relevant to locating desktop files but not implementing D-Bus-name inference.

  • Related To: snapcraft#3425 (confidence 86%)

    Later schema work added D-Bus activation and bus-name fields, providing explicit configuration but not automatic desktop-file detection.

Related issues

No related issues found above the similarity threshold.