** Changed in: canonical-devices-system-image
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to content-hub in Ubuntu.
https://bugs.launchpad.net/bugs/1526836
Title:
Add
** Changed in: canonical-devices-system-image
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to content-hub in Ubuntu.
https://bugs.launchpad.net/bugs/1526836
Title:
Add
** Changed in: ubuntu-touch-meta (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to content-hub in Ubuntu.
https://bugs.launchpad.net/bugs/1526836
Title:
Add
** Also affects: content-hub (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to content-hub in Ubuntu.
https://bugs.launchpad.net/bugs/1526836
Title:
Add
** Changed in: canonical-devices-system-image
Milestone: ww02-2016 => ww08-2016
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to content-hub in Ubuntu.
https://bugs.launchpad.net/bugs/1526836
Title:
Add
It sounds like the content-hub portion can just be handled with changes
to content-hub and the app doesn't need anything new.
OBEX file sending/receiving sounds like it doesn't need app policy at
this time. That service can just run trusted (though it would be nice if
it ran confined with a
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: apparmor (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-touch-meta in
Ubuntu.
What does 'add apparmor policy' entail? What does qml-module-qtbluetooth
use on the backend? Will it support trust-store prompting (and therefore
be a 'common', safe policy group) or will it be an unsafe, 'reserved'
policy group (eg, like 'contacts' is today)?
--
You received this bug
** Changed in: ubuntu-touch-meta (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-touch-meta in
Ubuntu.
https://bugs.launchpad.net/bugs/1526836
Title:
Add
** Also affects: ubuntu-touch-meta (Ubuntu RTM)
Importance: Undecided
Status: New
** Changed in: ubuntu-touch-meta (Ubuntu RTM)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
** Changed in: ubuntu-touch-meta (Ubuntu RTM)
Importance: Undecided => High
** Changed in: ubuntu-touch-meta (Ubuntu RTM)
Assignee: (unassigned) => Łukasz Zemczak (sil2100)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** Changed in: ubuntu-touch-meta (Ubuntu RTM)
Status: Confirmed => Fix Released
** Changed in: ubuntu-touch-meta (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Some info:
The backend for the module is shipped with QtConnectivity, hence doesn't
have any trust prompts around. That backend will talk to BlueZ over
D-Bus on the system bus for the most part. Additionally, OBEX & RFCOMM
(the two most interesting profiles for a start) read from/write to unix
** Description changed:
Add to the seed
Make available in the ota9 framework
Add apparmor policy
+
+ API reference at http://doc.qt.io/qt-5/qtbluetooth-index.html
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
14 matches
Mail list logo
