- name: bluejay
- description: Bluetooth device manager
- snapcraft: Snap-Bluejay/snapcraft.yaml at main · Kyuyrii/Snap-Bluejay · GitHub
- upstream: GitHub - EbonJaeger/bluejay: Bluetooth manager written in Qt
- upstream-relation: I contacted the developer and I’m making the Snap version for him since he doesn’t know how to handle Snaps.
- interfaces:
- <interface-name>: bluez
- request-type: auto-connection
- reasoning: This is an interface that is about Bluetooth and Bluejay is a bluetooth device manager.
- <interface-name>: bluetooth-control
- request-type: auto-connection
- reasoning: As the name says, it’s another plug involving bluetooth, so I suppose it’s also necessary.
- <interface-name>: bluez
This request has been added to the queue for review by the @reviewers team.
Hi @Kyuyrii!
Given the snap’s functionality, both requested interfaces make sense to me. +1(#voteFor) from me for auto-connecting bluez and bluetooth-control interfaces to bluejay.
Hi @Kyuyrii
According to bluejay description I’m not sure bluetooth-control is required. Could you please share the denials you observe without the bluetooth-control interface? (#askForInfo)
Thanks!
In this case, I don’t have Bluetooth on my device, so someone else is testing it for me.
The text below was sent before the bluetooth-control and bluez plugs were connected, but at that time the network-control plug wasn’t even added.
Warning: Schema “org.gnome.system.locale” has path “/system/locale/”. Paths starting with “/apps/”, “/desktop/” or “/system/” are deprecated.
Warning: Schema “org.gnome.system.proxy” has path “/system/proxy/”. Paths starting with “/apps/”, “/desktop/” or “/system/” are deprecated.
Warning: Schema “org.gnome.system.proxy.http” has path “/system/proxy/http/”. Paths starting with “/apps/”, “/desktop/” or “/system/” are deprecated.
Warning: Schema “org.gnome.system.proxy.https” has path “/system/proxy/https/”. Paths starting with “/apps/”, “/desktop/” or “/system/” are deprecated.
Warning: Schema “org.gnome.system.proxy.ftp” has path “/system/proxy/ftp/”. Paths starting with “/apps/”, “/desktop/” or “/system/” are deprecated.
Warning: Schema “org.gnome.system.proxy.socks” has path “/system/proxy/socks/”. Paths starting with “/apps/”, “/desktop/” or “/system/” are deprecated.
Gtk-Message: 18:41:05.020: Failed to load module "xapp-gtk3-module"
Gtk-Message: 18:41:05.020: Failed to load module "appmenu-gtk-module"
Qt: Session management error: Could not open network socket
/usr/share/libdrm/amdgpu.ids: No such file or directory
kf.bluezqt: Cannot open /dev/rfkill for reading!
kf.bluezqt: Cannot open /dev/rfkill for reading!
kf.bluezqt: GetManagerJob Error: "An AppArmor policy prevents this sender from sending this message to this recipient; type=\"method_call\", sender=\":1.263\" (uid=1000 pid=26799 comm=\"/snap/bluejay/1/usr/bin/bluejay\" label=\"snap.bluejay.bluejay (enforce)\") interface=\"org.freedesktop.DBus\" member=\"NameHasOwner\" error name=\"(unset)\" requested_reply=\"0\" destination=\"org.freedesktop.DBus\" (bus)"
Error initializing the BluezQt Manager: "An AppArmor policy prevents this sender from sending this message to this recipient; type=\"method_call\", sender=\":1.263\" (uid=1000 pid=26799 comm=\"/snap/bluejay/1/usr/bin/bluejay\" label=\"snap.bluejay.bluejay (enforce)\") interface=\"org.freedesktop.DBus\" member=\"NameHasOwner\" error name=\"(unset)\" requested_reply=\"0\" destination=\"org.freedesktop.DBus\" (bus)"
kf.bluezqt: GetManagerJob Error: "An AppArmor policy prevents this sender from sending this message to this recipient; type=\"method_call\", sender=\":1.263\" (uid=1000 pid=26799 comm=\"/snap/bluejay/1/usr/bin/bluejay\" label=\"snap.bluejay.bluejay (enforce)\") interface=\"org.freedesktop.DBus\" member=\"NameHasOwner\" error name=\"(unset)\" requested_reply=\"0\" destination=\"org.freedesktop.DBus\" (bus)"
Yo! Any updates on the request?
It’s been several months, so it seems like it’s simply been forgotten…