← Back to issue list

No OpenHAB-ondra Bluetooth (BlueZ) access

View original Launchpad issue

Metadata

Project
snapcraft (launchpad)
Number
#1826741
Type
issue
State
open
Author
~martin-hagborg
Labels
—
Created
Updated
Closed
—

Current evaluation

openHAB snap on Ubuntu Core 18/RPi3B cannot init BlueZ (HANDLER_INITIALIZING_ERROR); reporter asks how to grant Bluetooth group/plug access. Support question about a third-party snap manifest, untriaged.

Suggested action: close not a bug

Reason: This is a usage/support question, not a snapcraft defect: the reporter asks "how does one add 'the OS user' to the 'bluetooth group' on ubuntu snappy core?" and whether the openHAB snap should declare a plug. Both are answered by the third-party openHAB snap's own snapcraft.yaml plus snapd interface policy, not by anything in this repo — snapcraft already fully supports the needed manifest keys ("system-usernames" and app "plugs" are defined in schema/snapcraft.json at lines 1002 and 1016, with examples such as "{snap-daemon: shared}"), so no code change is possible here. Additionally the report targets Ubuntu Core 18 / core20-era bases where the bluetooth-control interface (snapd 2.44+) did not exist and the bluetooth group did not exist, making the scenario obsolete for current bases. Zero maintainer comments and no triage in 2714 days confirm nothing actionable remains in this repository.

Evaluated by: mr-cal-bot

Impact: 12 Quick Win: 2 Complexity: 20 Confidence: 72 Actionability: 18

Issue body

BlueZ OpenHAB addon/binding thing Status: "UNINITIALIZED - HANDLER_INITIALIZING_ERROR" i found this remark in the openhab documentation of blueZ: “Also note that the OS user needs to be a member of the “bluetooth” group of Linux in order to have the rights to access the BlueZ stack” how does one add “the OS user” to the “bluetooth group” on ubuntu snappy core? or does the openhap snap (snapcraft.yaml) have to associate/consumes/implement/use the bluetooth/bluez plug (as sugested by the cannonical snapcraft.yaml documentation: “When a plug is connected to one of these slots, the application will be granted the permissions specified for that interface”)? Ubuntu Core 18 on Raspberry PI 3B

Evaluation history

Date Model Scores Action Summary
stealth/space-bunny-alpha
Impact: 12
Quick Win: 2
Complexity: 20
Confidence: 72
Actionability: 18
close not a bug openHAB snap on Ubuntu Core 18/RPi3B cannot init BlueZ (HANDLER_INITIALIZING_ERROR); reporter asks how to grant Bluetooth group/plug access. Support question about a third-party snap manifest, untriaged.
stealth/space-bunny-alpha
Impact: 42
Quick Win: 12
Complexity: 38
Confidence: 87
Actionability: 45
needs triage Untriaged report that openHAB on Ubuntu Core 18/Raspberry Pi 3B cannot initialize BlueZ access, asking whether to add the snap user to a Bluetooth group or declare a Bluetooth plug.
qwen/qwen3.8-27b
Impact: 5
Quick Win: 4
Staleness: 95
Complexity: 10
Confidence: 75
Support Request: 90
close not a bug OpenHAB snap on Ubuntu Core 18 fails BlueZ binding init (HANDLER_INITIALIZING_ERROR); reporter asks how to grant the snap Bluetooth access (user in bluetooth group or a bluetooth plug in snapcraft.yaml). No maintainer response; ~7.3 years old.
qwen/qwen3.6-35b-a3b
Staleness: 98
Complexity: 15
Confidence: 90
Support Request: 90
close not a bug Support request regarding BlueZ Bluetooth permissions for the OpenHAB snap on Ubuntu Core 18. No maintainer response, inactive for over 7 years, and references an obsolete OS version.
qwen/qwen3.6-35b-a3b
Staleness: 95
Complexity: 15
Confidence: 90
Support Request: 95
close not a bug User asks how to grant Bluetooth permissions to the OpenHAB snap on Ubuntu Core 18. Issue is a support request with no maintainer response and has been inactive for over 7 years. Ubuntu Core 18 is EOL.
qwen3.6-35b-a3b-mtp-q6
Staleness: 98
Complexity: 10
Confidence: 90
Support Request: 95
close stale User asks how to grant Bluetooth permissions to the OpenHAB snap on Ubuntu Core 18. No maintainer response in over 7 years. Ubuntu Core 18 is EOL and OpenHAB has significantly evolved since then.

Update history

Date Change
created

Related issues

No related issues found above the similarity threshold.