[Touch-packages] [Bug 2009699] Re: sytemd-udev package upgrade breaks if udev is masked

[Simon Fels]

Hey Mauricio,

> Could you please confirm if from the Anbox perspective, for a
> workaround, is it OK to temporatily unmask/start the unit
> (due to restart), then upgrade the package, and stop/mask again?

It's not that simple. We have prebuilt images we ship to users which run
through an automated bootstrap process (see https://anbox-
cloud.io/docs/exp/applications#bootstrap). As part of that process we
apply pending security patches to ensure the images are up to date. This
process fails with the latest udev update but it should have failed with
older udev versions as well. It only became a problem now due to bad
timing (us not having released a new image and the security patch being
rolled out). We will ship a new patch release next Wednesday (Mar 15)
which will then include the updated udev package and also a tweak to the
automatic process to prevent this from happening again.

For our users we have a simple knob in our management service to turn
off the process of applying pending updates to mitigate the situation
till the we roll out new images next week.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2009699

Title:
  sytemd-udev package upgrade breaks if udev is masked

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  The Anbox Cloud LXD images are based of the standard Ubuntu cloud
  images for LXD but have the systemd-udevd.service unit masked
  (`systemctl mask systemd-udevd.service`) as we do not need udev.

  With the latest security patch on Ubuntu 22.04 upgrading the udev
  package fails:

  ...
  Mar 07 21:33:48 ams-cg3qqttdjmctnqegcqag sh[753]: left to upgrade {'udev', 
'libudev1'}
  Mar 07 21:33:48 ams-cg3qqttdjmctnqegcqag sh[753]: applying set ['udev', 
'libudev1']
  Mar 07 21:33:48 ams-cg3qqttdjmctnqegcqag sh[753]: Log ended: 2023-03-07  
21:33:47
  Mar 07 21:33:48 ams-cg3qqttdjmctnqegcqag sh[753]: Log started: 2023-03-07  
21:33:48
  Mar 07 21:33:48 ams-cg3qqttdjmctnqegcqag sh[753]: [614B blob data]
  Mar 07 21:33:48 ams-cg3qqttdjmctnqegcqag sh[753]: Preparing to unpack 
.../udev_249.11-0ubuntu3.7_arm64.deb ...
  Mar 07 21:33:48 ams-cg3qqttdjmctnqegcqag sh[753]: Unpacking udev 
(249.11-0ubuntu3.7) over (249.11-0ubuntu3.6) ...
  Mar 07 21:33:49 ams-cg3qqttdjmctnqegcqag sh[753]: Preparing to unpack 
.../libudev1_249.11-0ubuntu3.7_arm64.deb ...
  Mar 07 21:33:49 ams-cg3qqttdjmctnqegcqag sh[753]: Unpacking libudev1:arm64 
(249.11-0ubuntu3.7) over (249.11-0ubuntu3.6) ...
  Mar 07 21:33:49 ams-cg3qqttdjmctnqegcqag sh[753]: Setting up libudev1:arm64 
(249.11-0ubuntu3.7) ...
  Mar 07 21:33:49 ams-cg3qqttdjmctnqegcqag sh[753]: Setting up udev 
(249.11-0ubuntu3.7) ...
  Mar 07 21:33:49 ams-cg3qqttdjmctnqegcqag systemd[1]: Reloading.
  Mar 07 21:33:49 ams-cg3qqttdjmctnqegcqag sh[753]: Failed to restart 
udev.service: Unit udev.service failed to load properly, please adjust/correct 
and reload service manager: File exists
  Mar 07 21:33:49 ams-cg3qqttdjmctnqegcqag sh[753]: See system logs and 
'systemctl status udev.service' for details.
  Mar 07 21:33:49 ams-cg3qqttdjmctnqegcqag sh[753]: invoke-rc.d: initscript 
udev, action "restart" failed.

  We can workaround this by doing a patch release to our users next week
  but it would be a lot better if the package scripts check if the
  service unit is masked and if it is avoid restarting udev.service

  The problem isn't introduced with the 249.11-0ubuntu3.7 but should
  exist for longer already. It just became a problem for us due to the
  security patch rolling in via unattended-upgrades

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2009699/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2009699] Re: sytemd-udev package upgrade breaks if udev is masked

[Simon Fels]

** Description changed:

  The Anbox Cloud LXD images are based of the standard Ubuntu cloud images
- for LXD but have the systemd-udev.service unit masked (`systemctl mask
- systemd-udev.service`) as we do not need udev.
+ for LXD but have the systemd-udevd.service unit masked (`systemctl mask
+ systemd-udevd.service`) as we do not need udev.
  
  With the latest security patch on Ubuntu 22.04 upgrading the udev
  package fails:
  
  ...
  Mar 07 21:33:48 ams-cg3qqttdjmctnqegcqag sh[753]: left to upgrade {'udev', 
'libudev1'}
  Mar 07 21:33:48 ams-cg3qqttdjmctnqegcqag sh[753]: applying set ['udev', 
'libudev1']
  Mar 07 21:33:48 ams-cg3qqttdjmctnqegcqag sh[753]: Log ended: 2023-03-07  
21:33:47
  Mar 07 21:33:48 ams-cg3qqttdjmctnqegcqag sh[753]: Log started: 2023-03-07  
21:33:48
  Mar 07 21:33:48 ams-cg3qqttdjmctnqegcqag sh[753]: [614B blob data]
  Mar 07 21:33:48 ams-cg3qqttdjmctnqegcqag sh[753]: Preparing to unpack 
.../udev_249.11-0ubuntu3.7_arm64.deb ...
  Mar 07 21:33:48 ams-cg3qqttdjmctnqegcqag sh[753]: Unpacking udev 
(249.11-0ubuntu3.7) over (249.11-0ubuntu3.6) ...
  Mar 07 21:33:49 ams-cg3qqttdjmctnqegcqag sh[753]: Preparing to unpack 
.../libudev1_249.11-0ubuntu3.7_arm64.deb ...
  Mar 07 21:33:49 ams-cg3qqttdjmctnqegcqag sh[753]: Unpacking libudev1:arm64 
(249.11-0ubuntu3.7) over (249.11-0ubuntu3.6) ...
  Mar 07 21:33:49 ams-cg3qqttdjmctnqegcqag sh[753]: Setting up libudev1:arm64 
(249.11-0ubuntu3.7) ...
  Mar 07 21:33:49 ams-cg3qqttdjmctnqegcqag sh[753]: Setting up udev 
(249.11-0ubuntu3.7) ...
  Mar 07 21:33:49 ams-cg3qqttdjmctnqegcqag systemd[1]: Reloading.
  Mar 07 21:33:49 ams-cg3qqttdjmctnqegcqag sh[753]: Failed to restart 
udev.service: Unit udev.service failed to load properly, please adjust/correct 
and reload service manager: File exists
  Mar 07 21:33:49 ams-cg3qqttdjmctnqegcqag sh[753]: See system logs and 
'systemctl status udev.service' for details.
  Mar 07 21:33:49 ams-cg3qqttdjmctnqegcqag sh[753]: invoke-rc.d: initscript 
udev, action "restart" failed.
  
  We can workaround this by doing a patch release to our users next week
  but it would be a lot better if the package scripts check if the service
  unit is masked and if it is avoid restarting udev.service
  
  The problem isn't introduced with the 249.11-0ubuntu3.7 but should exist
  for longer already. It just became a problem for us due to the security
  patch rolling in via unattended-upgrades

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2009699

Title:
  sytemd-udev package upgrade breaks if udev is masked

Status in systemd package in Ubuntu:
  New

Bug description:
  The Anbox Cloud LXD images are based of the standard Ubuntu cloud
  images for LXD but have the systemd-udevd.service unit masked
  (`systemctl mask systemd-udevd.service`) as we do not need udev.

  With the latest security patch on Ubuntu 22.04 upgrading the udev
  package fails:

  ...
  Mar 07 21:33:48 ams-cg3qqttdjmctnqegcqag sh[753]: left to upgrade {'udev', 
'libudev1'}
  Mar 07 21:33:48 ams-cg3qqttdjmctnqegcqag sh[753]: applying set ['udev', 
'libudev1']
  Mar 07 21:33:48 ams-cg3qqttdjmctnqegcqag sh[753]: Log ended: 2023-03-07  
21:33:47
  Mar 07 21:33:48 ams-cg3qqttdjmctnqegcqag sh[753]: Log started: 2023-03-07  
21:33:48
  Mar 07 21:33:48 ams-cg3qqttdjmctnqegcqag sh[753]: [614B blob data]
  Mar 07 21:33:48 ams-cg3qqttdjmctnqegcqag sh[753]: Preparing to unpack 
.../udev_249.11-0ubuntu3.7_arm64.deb ...
  Mar 07 21:33:48 ams-cg3qqttdjmctnqegcqag sh[753]: Unpacking udev 
(249.11-0ubuntu3.7) over (249.11-0ubuntu3.6) ...
  Mar 07 21:33:49 ams-cg3qqttdjmctnqegcqag sh[753]: Preparing to unpack 
.../libudev1_249.11-0ubuntu3.7_arm64.deb ...
  Mar 07 21:33:49 ams-cg3qqttdjmctnqegcqag sh[753]: Unpacking libudev1:arm64 
(249.11-0ubuntu3.7) over (249.11-0ubuntu3.6) ...
  Mar 07 21:33:49 ams-cg3qqttdjmctnqegcqag sh[753]: Setting up libudev1:arm64 
(249.11-0ubuntu3.7) ...
  Mar 07 21:33:49 ams-cg3qqttdjmctnqegcqag sh[753]: Setting up udev 
(249.11-0ubuntu3.7) ...
  Mar 07 21:33:49 ams-cg3qqttdjmctnqegcqag systemd[1]: Reloading.
  Mar 07 21:33:49 ams-cg3qqttdjmctnqegcqag sh[753]: Failed to restart 
udev.service: Unit udev.service failed to load properly, please adjust/correct 
and reload service manager: File exists
  Mar 07 21:33:49 ams-cg3qqttdjmctnqegcqag sh[753]: See system logs and 
'systemctl status udev.service' for details.
  Mar 07 21:33:49 ams-cg3qqttdjmctnqegcqag sh[753]: invoke-rc.d: initscript 
udev, action "restart" failed.

  We can workaround this by doing a patch release to our users next week
  but it would be a lot better if the package scripts check if the
  service unit is masked and if it is avoid restarting udev.service

  The problem isn't introduced with the 249.11-0ubuntu3.7 but should
  exist for longer already. It just became a problem for us due to the
  security patch rolling in via unattended-upgrades

To m

[Touch-packages] [Bug 2009699] [NEW] sytemd-udev package upgrade breaks if udev is masked

[Simon Fels]

Public bug reported:

The Anbox Cloud LXD images are based of the standard Ubuntu cloud images
for LXD but have the systemd-udev.service unit masked (`systemctl mask
systemd-udev.service`) as we do not need udev.

With the latest security patch on Ubuntu 22.04 upgrading the udev
package fails:

...
Mar 07 21:33:48 ams-cg3qqttdjmctnqegcqag sh[753]: left to upgrade {'udev', 
'libudev1'}
Mar 07 21:33:48 ams-cg3qqttdjmctnqegcqag sh[753]: applying set ['udev', 
'libudev1']
Mar 07 21:33:48 ams-cg3qqttdjmctnqegcqag sh[753]: Log ended: 2023-03-07  
21:33:47
Mar 07 21:33:48 ams-cg3qqttdjmctnqegcqag sh[753]: Log started: 2023-03-07  
21:33:48
Mar 07 21:33:48 ams-cg3qqttdjmctnqegcqag sh[753]: [614B blob data]
Mar 07 21:33:48 ams-cg3qqttdjmctnqegcqag sh[753]: Preparing to unpack 
.../udev_249.11-0ubuntu3.7_arm64.deb ...
Mar 07 21:33:48 ams-cg3qqttdjmctnqegcqag sh[753]: Unpacking udev 
(249.11-0ubuntu3.7) over (249.11-0ubuntu3.6) ...
Mar 07 21:33:49 ams-cg3qqttdjmctnqegcqag sh[753]: Preparing to unpack 
.../libudev1_249.11-0ubuntu3.7_arm64.deb ...
Mar 07 21:33:49 ams-cg3qqttdjmctnqegcqag sh[753]: Unpacking libudev1:arm64 
(249.11-0ubuntu3.7) over (249.11-0ubuntu3.6) ...
Mar 07 21:33:49 ams-cg3qqttdjmctnqegcqag sh[753]: Setting up libudev1:arm64 
(249.11-0ubuntu3.7) ...
Mar 07 21:33:49 ams-cg3qqttdjmctnqegcqag sh[753]: Setting up udev 
(249.11-0ubuntu3.7) ...
Mar 07 21:33:49 ams-cg3qqttdjmctnqegcqag systemd[1]: Reloading.
Mar 07 21:33:49 ams-cg3qqttdjmctnqegcqag sh[753]: Failed to restart 
udev.service: Unit udev.service failed to load properly, please adjust/correct 
and reload service manager: File exists
Mar 07 21:33:49 ams-cg3qqttdjmctnqegcqag sh[753]: See system logs and 
'systemctl status udev.service' for details.
Mar 07 21:33:49 ams-cg3qqttdjmctnqegcqag sh[753]: invoke-rc.d: initscript udev, 
action "restart" failed.

We can workaround this by doing a patch release to our users next week
but it would be a lot better if the package scripts check if the service
unit is masked and if it is avoid restarting udev.service

The problem isn't introduced with the 249.11-0ubuntu3.7 but should exist
for longer already. It just became a problem for us due to the security
patch rolling in via unattended-upgrades

** Affects: systemd (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2009699

Title:
  sytemd-udev package upgrade breaks if udev is masked

Status in systemd package in Ubuntu:
  New

Bug description:
  The Anbox Cloud LXD images are based of the standard Ubuntu cloud
  images for LXD but have the systemd-udev.service unit masked
  (`systemctl mask systemd-udev.service`) as we do not need udev.

  With the latest security patch on Ubuntu 22.04 upgrading the udev
  package fails:

  ...
  Mar 07 21:33:48 ams-cg3qqttdjmctnqegcqag sh[753]: left to upgrade {'udev', 
'libudev1'}
  Mar 07 21:33:48 ams-cg3qqttdjmctnqegcqag sh[753]: applying set ['udev', 
'libudev1']
  Mar 07 21:33:48 ams-cg3qqttdjmctnqegcqag sh[753]: Log ended: 2023-03-07  
21:33:47
  Mar 07 21:33:48 ams-cg3qqttdjmctnqegcqag sh[753]: Log started: 2023-03-07  
21:33:48
  Mar 07 21:33:48 ams-cg3qqttdjmctnqegcqag sh[753]: [614B blob data]
  Mar 07 21:33:48 ams-cg3qqttdjmctnqegcqag sh[753]: Preparing to unpack 
.../udev_249.11-0ubuntu3.7_arm64.deb ...
  Mar 07 21:33:48 ams-cg3qqttdjmctnqegcqag sh[753]: Unpacking udev 
(249.11-0ubuntu3.7) over (249.11-0ubuntu3.6) ...
  Mar 07 21:33:49 ams-cg3qqttdjmctnqegcqag sh[753]: Preparing to unpack 
.../libudev1_249.11-0ubuntu3.7_arm64.deb ...
  Mar 07 21:33:49 ams-cg3qqttdjmctnqegcqag sh[753]: Unpacking libudev1:arm64 
(249.11-0ubuntu3.7) over (249.11-0ubuntu3.6) ...
  Mar 07 21:33:49 ams-cg3qqttdjmctnqegcqag sh[753]: Setting up libudev1:arm64 
(249.11-0ubuntu3.7) ...
  Mar 07 21:33:49 ams-cg3qqttdjmctnqegcqag sh[753]: Setting up udev 
(249.11-0ubuntu3.7) ...
  Mar 07 21:33:49 ams-cg3qqttdjmctnqegcqag systemd[1]: Reloading.
  Mar 07 21:33:49 ams-cg3qqttdjmctnqegcqag sh[753]: Failed to restart 
udev.service: Unit udev.service failed to load properly, please adjust/correct 
and reload service manager: File exists
  Mar 07 21:33:49 ams-cg3qqttdjmctnqegcqag sh[753]: See system logs and 
'systemctl status udev.service' for details.
  Mar 07 21:33:49 ams-cg3qqttdjmctnqegcqag sh[753]: invoke-rc.d: initscript 
udev, action "restart" failed.

  We can workaround this by doing a patch release to our users next week
  but it would be a lot better if the package scripts check if the
  service unit is masked and if it is avoid restarting udev.service

  The problem isn't introduced with the 249.11-0ubuntu3.7 but should
  exist for longer already. It just became a problem for us due to the
  security patch rolling in via unattended-upgrades

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2009699/+subscri

[Touch-packages] [Bug 1528173] Re: org.freedesktop.DBus.Properties.GetAll fails always for fi.w1.wpa_supplicant1.Interface interface

[Simon Fels]

** Changed in: wpa (Ubuntu)
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wpa in Ubuntu.
https://bugs.launchpad.net/bugs/1528173

Title:
  org.freedesktop.DBus.Properties.GetAll fails always for
  fi.w1.wpa_supplicant1.Interface interface

Status in wpa package in Ubuntu:
  Fix Released

Bug description:
  With our package for wpa-supplicant a call

  $ sudo gdbus call -y -d fi.w1.wpa_supplicant1 -o
  /fi/w1/wpa_supplicant1/Interfaces/1 -m
  org.freedesktop.DBus.Properties.GetAll
  'fi.w1.wpa_supplicant1.Interface'

  fails always with

  Error: GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: No readable
  properties in this interface

  The reason for this is that the internal properties getter routine
  will never return any result when one internal getter fails.

  The responsible property here is the "Stations" one which was added by
  a patch in Ubuntu and is not available upstream. Take a look at
  https://bazaar.launchpad.net/~ubuntu-
  branches/ubuntu/wily/wpa/wily/view/head:/debian/patches/dbus-
  available-sta.patch

  The getter method wpas_dbus_getter_stas expects the ap_iface element
  to be see which isn't always the case and if that isn't true it will
  return false and causes the whole Properties.GetAll call to fail.

  The expected result is that the getter just returns an empty list if
  it can't determine the actual value.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1528173/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1662866] Re: libhybris blocks migration to libglvnd

[Simon Fels]

** Changed in: libhybris (Ubuntu)
 Assignee: (unassigned) => Simon Fels (morphis)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libhybris in Ubuntu.
https://bugs.launchpad.net/bugs/1662866

Title:
  libhybris blocks migration to libglvnd

Status in libhybris package in Ubuntu:
  New

Bug description:
  Mesa & nvidia would like to migrate to use libglvnd so that they can
  be installed and used in the same session. For more details about
  libglvnd see: https://github.com/NVIDIA/libglvnd

  libhybris installs it's own EGL libraries under $libdir/libhybris-egl
  and uses alternatives for the ld.so.conf. If mesa is migrated to not
  use alternatives, libhybris' EGL libs get priority. This results in
  unity7 session failing to load.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libhybris/+bug/1662866/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1574324] Re: pulseaudio crashes when connecting to bluetooth headphones (due to ubuntu changes?)

[Simon Fels]

Sorry, for seeing this one a bit late.

First of all the relevant problem is

(  15.152|   0.000) E: [pulseaudio] volume.c: Assertion
'pa_channels_valid(channels)' failed at pulse/volume.c:74, function
pa_cvolume_set(). Aborting.

Which basically means there is a volume level being set for an invalid
channel (simply a number which is out of range once passed to
pa_cvolume_set).

Looking into the code the function source_set_volume_cb in
src/modules/bluetooth/module-bluez5-device.c (line 961) calls
pa_cvolume_set and also sink_set_volume_cb (line 1187). Each gets called
for either when a source or sink is added to the device and the profile
being used is PA_BLUETOOTH_PROFILE_HEADSET_HEAD_UNIT. The sample_spec
struct being used to provide the channel is configured in
transport_config which is according to the log file attached in comment
#1 never called before the abort happens. The function transport_acquire
is called before and returns an error according to:

(  14.894|   0.000) D: [pulseaudio] module-bluez5-device.c: Acquiring transport 
/org/bluez/hci0/dev_44_5E_F3_B4_07_29/fd49
(  14.894|   0.000) I: [pulseaudio] backend-native.c: doing connect
(  15.151|   0.257) E: [pulseaudio] backend-native.c: connect(): Function not 
implemented

That the connect() syscall returns "Function no implemented" is
suspicious.

If we're going further in the log file we see

(  15.152|   0.000) D: [pulseaudio] backend-native.c: Transport
/org/bluez/hci0/dev_44_5E_F3_B4_07_29/fd49 available for profile
headset_head_unit

which happens inside src/modules/bluetooth/backend-native.c in function
profile_new_connection when we get called back from bluez if the HFP
profile you get connected with the remote side.

The next line is the interesting one:

(  15.152|   0.000) D: [pulseaudio] backend-native.c: RFCOMM << AT+VGS=8

This actually comes from set_speaker_gain in src/modules/bluetooth
/backend-native.c line 276 and is called by sink_set_volume_cb in
src/modules/bluetooth/module-bluez5-device.c (line 1187) which is called
subsequently from add_sink -> init_profile. As set_speaker_gain prints
out the string "RFCOMM << AT+VGS=8" AFTER it has the set volume in
sink_set_volume_cb the first call to pa_cvolume_set already happened and
went through without the assert in pa_cvolume_set failing for an
incorrect channel. The only left candidate then is source_set_volume_cb
but that one is using the same u->sample_spec.channels value as we used
before and it shouldn't have changed in between.

What somebody should now look into: Add pa_log_debug lines before and
after the actual pa_cvolume_set calls in src/modules/bluetooth/module-
bluez5-device.c so that we can verify which is actually causing the
abort. These should also print the value of u->sample_spec.channels.
With that we have at least the line which is causing the abort and can
then look into possible reasons why this is happening. I suspect the
order of a specific code flow has change slightly with the SCO-over-PCM
changes we did for Ubuntu Touch.

Also it would be great if someone who removed the patches can provide a
log file for pulseaudio in debug mode where the headset gets connected
and no abort occurs.

@Luke: Can you provide packages with the necessary changes so that
people expiring the abort can install these and provide new log files?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1574324

Title:
  pulseaudio crashes when connecting to bluetooth headphones (due to
  ubuntu changes?)

Status in pulseaudio package in Ubuntu:
  In Progress

Bug description:
  When I attempt to connect my Jaybird Bluebuds X to Ubuntu 16.04
  pulseaudio crashes, this does *NOT* happen with a Jambox which leads
  me to believe it's an intermittent problem with some hardware. This
  did not happen on Ubuntu 15.10 (which was an upgrade of 15.04).

  Ubuntu Release:

  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  Pulseaudio Version:

  pulseaudio:
    Installed: 1:8.0-0ubuntu3
    Candidate: 1:8.0-0ubuntu3
    Version table:
   *** 1:8.0-0ubuntu3 500
  500 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  Device info:

  [bluetooth]# info 44:5E:F3:B4:07:29
  Device 44:5E:F3:B4:07:29
   Name: BlueBuds X
   Alias: BlueBuds X
   Class: 0x240404
   Icon: audio-card
   Paired: yes
   Trusted: yes
   Blocked: no
   Connected: no
   LegacyPairing: no
   UUID: Headset   (1108--1000-8000-00805f9b34fb)
   UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
   UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
   UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
   UUID: Handsfree (111e--1000-8000-00805f9b34fb)
   UUID: Unknown   (80ff--1000-8000-00805f9b34fb)

  I have also att

[Touch-packages] [Bug 1623068] Re: Networkd fails to configure a ethernet network device on a 3.4 kernel

[Simon Fels]

That patch works but there are now more problems with the DHCP stack
inside networkd. See https://paste.ubuntu.com/23178198/ Needs more
investigation. To unblock our work we're now using a static ifupdown
configuration but need to fix this bug here for real networkd support.

** Changed in: systemd (Ubuntu)
   Importance: Undecided => High

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1623068

Title:
  Networkd fails to configure a ethernet network device on a 3.4 kernel

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Knowing that a 3.4 based kernel is unsupported we have to get it
  working for a specific customer.

  Systemd itself boots up nicely already but networkd fails to configure
  a network device with the following configuration file in
  /etc/systemd/network

  $ cat /etc/systemd/network/enp1s0.network 
  [Match]
  Name=enp1s0

  [Network]
  DNS=8.8.8.8
  Address=192.168.178.30
  Gateway=192.168.178.1

  This gives the following error messages

  $ sudo /lib/systemd/systemd-networkd
  Enumeration completed
  enp1s0: Could not bring up interface: Invalid argument
  enp1s0: Could not set route: Invalid argument

  ifupdown or NetworkManager is reliable able to get the same interface
  up and configured.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1623068/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1623068] Re: Networkd fails to configure a ethernet network device on a 3.4 kernel

[Simon Fels]

Yes, the kernel has IPv6 support enabled so socket_ipv6_is_supported()
returns true and with that it tries to setup the IPv6 part of the
interface.

The two problems which I've found so far are:

 - an empty IFLA_AF_SPEC seems to cause the kernel to return EINVAL
 - having IPv6 enabled and IFLA_AF_SPEC is filled with the ipv6ll mode we get 
EINVAL

So to fix this we have to do two things:

 1. disable IPv6 support in the 3.4 kernel; if that is not acceptable for the 
real product later than we have to find another solution.
 2. move the open/close_container() inside the if() statement to avoid an empty 
container.

For 2. we may can work around this on the kernel side too to allow empty
IFLA_AF_SPEC containers.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1623068

Title:
  Networkd fails to configure a ethernet network device on a 3.4 kernel

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Knowing that a 3.4 based kernel is unsupported we have to get it
  working for a specific customer.

  Systemd itself boots up nicely already but networkd fails to configure
  a network device with the following configuration file in
  /etc/systemd/network

  $ cat /etc/systemd/network/enp1s0.network 
  [Match]
  Name=enp1s0

  [Network]
  DNS=8.8.8.8
  Address=192.168.178.30
  Gateway=192.168.178.1

  This gives the following error messages

  $ sudo /lib/systemd/systemd-networkd
  Enumeration completed
  enp1s0: Could not bring up interface: Invalid argument
  enp1s0: Could not set route: Invalid argument

  ifupdown or NetworkManager is reliable able to get the same interface
  up and configured.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1623068/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1623068] Re: Networkd fails to configure a ethernet network device on a 3.4 kernel

[Simon Fels]

The actual error message comes from
https://github.com/systemd/systemd/blob/95adafc428b5b4be0ddd4d43a7b96658390388bc/src/network
/networkd-link.c#L1441 and due to the nature of this the problem only
occurs when the network interface isn't already up.

If lines 1391 to 1420 are commented on
https://github.com/systemd/systemd/blob/95adafc428b5b4be0ddd4d43a7b96658390388bc/src/network
/networkd-link.c#L1391 the kernel doesn't return EINVAL and the
interface is properly setup.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1623068

Title:
  Networkd fails to configure a ethernet network device on a 3.4 kernel

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Knowing that a 3.4 based kernel is unsupported we have to get it
  working for a specific customer.

  Systemd itself boots up nicely already but networkd fails to configure
  a network device with the following configuration file in
  /etc/systemd/network

  $ cat /etc/systemd/network/enp1s0.network 
  [Match]
  Name=enp1s0

  [Network]
  DNS=8.8.8.8
  Address=192.168.178.30
  Gateway=192.168.178.1

  This gives the following error messages

  $ sudo /lib/systemd/systemd-networkd
  Enumeration completed
  enp1s0: Could not bring up interface: Invalid argument
  enp1s0: Could not set route: Invalid argument

  ifupdown or NetworkManager is reliable able to get the same interface
  up and configured.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1623068/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1623068] Re: Networkd fails to configure a ethernet network device on a 3.4 kernel

[Simon Fels]

** Attachment added: "systemd-networkd-on-3.4.log"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1623068/+attachment/4740099/+files/systemd-networkd-on-3.4.log

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1623068

Title:
  Networkd fails to configure a ethernet network device on a 3.4 kernel

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Knowing that a 3.4 based kernel is unsupported we have to get it
  working for a specific customer.

  Systemd itself boots up nicely already but networkd fails to configure
  a network device with the following configuration file in
  /etc/systemd/network

  $ cat /etc/systemd/network/enp1s0.network 
  [Match]
  Name=enp1s0

  [Network]
  DNS=8.8.8.8
  Address=192.168.178.30
  Gateway=192.168.178.1

  This gives the following error messages

  $ sudo /lib/systemd/systemd-networkd
  Enumeration completed
  enp1s0: Could not bring up interface: Invalid argument
  enp1s0: Could not set route: Invalid argument

  ifupdown or NetworkManager is reliable able to get the same interface
  up and configured.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1623068/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1623068] [NEW] Networkd fails to configure a ethernet network device on a 3.4 kernel

[Simon Fels]

Public bug reported:

Knowing that a 3.4 based kernel is unsupported we have to get it working
for a specific customer.

Systemd itself boots up nicely already but networkd fails to configure a
network device with the following configuration file in
/etc/systemd/network

$ cat /etc/systemd/network/enp1s0.network 
[Match]
Name=enp1s0

[Network]
DNS=8.8.8.8
Address=192.168.178.30
Gateway=192.168.178.1

This gives the following error messages

$ sudo /lib/systemd/systemd-networkd
Enumeration completed
enp1s0: Could not bring up interface: Invalid argument
enp1s0: Could not set route: Invalid argument

ifupdown or NetworkManager is reliable able to get the same interface up
and configured.

** Affects: systemd (Ubuntu)
 Importance: Undecided
 Status: Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1623068

Title:
  Networkd fails to configure a ethernet network device on a 3.4 kernel

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Knowing that a 3.4 based kernel is unsupported we have to get it
  working for a specific customer.

  Systemd itself boots up nicely already but networkd fails to configure
  a network device with the following configuration file in
  /etc/systemd/network

  $ cat /etc/systemd/network/enp1s0.network 
  [Match]
  Name=enp1s0

  [Network]
  DNS=8.8.8.8
  Address=192.168.178.30
  Gateway=192.168.178.1

  This gives the following error messages

  $ sudo /lib/systemd/systemd-networkd
  Enumeration completed
  enp1s0: Could not bring up interface: Invalid argument
  enp1s0: Could not set route: Invalid argument

  ifupdown or NetworkManager is reliable able to get the same interface
  up and configured.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1623068/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1623068] Re: Networkd fails to configure a ethernet network device on a 3.4 kernel

[Simon Fels]

Output of

  sudo SYSTEMD_LOG_LEVEL=debug /lib/systemd/systemd-networkd

ubuntu@nirvana:~$   sudo SYSTEMD_LOG_LEVEL=debug /lib/systemd/systemd-networkd
sudo: unable to resolve host nirvana: Connection refused
Failed to connect to bus, trying again in 5s: No such file or directory
timestamp of '/etc/systemd/network' changed
p2p0: Flags change: +MULTICAST +BROADCAST
p2p0: Link 7 added
p2p0: udev initialized link
p2p0: Saved original MTU: 1500
sit0: MAC address not found for new device, continuing without
sit0: Flags change: +NOARP
sit0: Link 6 added
sit0: udev initialized link
sit0: Saved original MTU: 1480
wlan0: Flags change: +MULTICAST +BROADCAST
wlan0: Link 5 added
wlan0: udev initialized link
wlan0: Saved original MTU: 1500
enx00606e43a573: Flags change: +MULTICAST +BROADCAST
enx00606e43a573: Link 4 added
enx00606e43a573: udev initialized link
enx00606e43a573: Saved original MTU: 1500
enp1s0: Flags change: +MULTICAST +BROADCAST
enp1s0: Link 3 added
enp1s0: udev initialized link
enp1s0: Saved original MTU: 1500
dummy0: Flags change: +BROADCAST +NOARP
dummy0: Link 2 added
dummy0: udev initialized link
dummy0: Saved original MTU: 1500
lo: Flags change: +LOOPBACK +UP +LOWER_UP +RUNNING
lo: Link 1 added
lo: udev initialized link
lo: Saved original MTU: 16436
lo: Adding address: ::1/128 (valid forever)
lo: Adding address: 127.0.0.1/8 (valid forever)
Enumeration completed
p2p0: Link state is up-to-date
p2p0: Unmanaged
sit0: Link state is up-to-date
sit0: Unmanaged
wlan0: Link state is up-to-date
wlan0: Unmanaged
enx00606e43a573: Link state is up-to-date
enx00606e43a573: Unmanaged
enp1s0: Link state is up-to-date
enp1s0: found matching network '/etc/systemd/network/enp1s0.network'
enp1s0: Bringing link up
enp1s0: Setting addresses
dummy0: Link state is up-to-date
dummy0: Unmanaged
lo: Link state is up-to-date
lo: Unmanaged
enp1s0: Could not bring up interface: Invalid argument
enp1s0: Updating address: 192.168.178.30/24 (valid forever)
enp1s0: Addresses set
enp1s0: Setting routes
enp1s0: Could not set route: Invalid argument
enp1s0: Routes set

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1623068

Title:
  Networkd fails to configure a ethernet network device on a 3.4 kernel

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Knowing that a 3.4 based kernel is unsupported we have to get it
  working for a specific customer.

  Systemd itself boots up nicely already but networkd fails to configure
  a network device with the following configuration file in
  /etc/systemd/network

  $ cat /etc/systemd/network/enp1s0.network 
  [Match]
  Name=enp1s0

  [Network]
  DNS=8.8.8.8
  Address=192.168.178.30
  Gateway=192.168.178.1

  This gives the following error messages

  $ sudo /lib/systemd/systemd-networkd
  Enumeration completed
  enp1s0: Could not bring up interface: Invalid argument
  enp1s0: Could not set route: Invalid argument

  ifupdown or NetworkManager is reliable able to get the same interface
  up and configured.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1623068/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1318360] Re: Poor microphone quality (mako)

[Simon Fels]

** Changed in: libhybris (Ubuntu)
   Status: New => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libhybris in Ubuntu.
https://bugs.launchpad.net/bugs/1318360

Title:
  Poor microphone quality (mako)

Status in Canonical System Image:
  Fix Committed
Status in libhybris package in Ubuntu:
  Fix Committed
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  After months of complaints from people talking to me on the phone
  (mako ubuntu touch), I finally got around to use multiROM to dual boot
  Ubuntu Touch and Android. Several people can confirm that there is a
  noticable difference in terms of sound/microphone quality between
  Android and UT in phone calls. With UT, my voice gets distorted to an
  extent that person at the other end have real difficulties to hear
  what I am saying, while with Android call quality is much better with
  no distortion.

  I have had a suspicion for a long time that this might be a software
  and not a hardware issue. After trying Android and Ubuntu on the same
  hardware I believe this suspicion is proved correct. This issue has
  persisted in all the builds I have tried since at least the beginning
  of the year, but probably longer. I am now at r17 of Utopic.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1318360/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1318360] Re: Poor microphone quality (mako)

[Simon Fels]

** Changed in: libhybris (Ubuntu)
   Importance: Undecided => High

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libhybris in Ubuntu.
https://bugs.launchpad.net/bugs/1318360

Title:
  Poor microphone quality (mako)

Status in Canonical System Image:
  Fix Committed
Status in libhybris package in Ubuntu:
  Fix Committed
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  After months of complaints from people talking to me on the phone
  (mako ubuntu touch), I finally got around to use multiROM to dual boot
  Ubuntu Touch and Android. Several people can confirm that there is a
  noticable difference in terms of sound/microphone quality between
  Android and UT in phone calls. With UT, my voice gets distorted to an
  extent that person at the other end have real difficulties to hear
  what I am saying, while with Android call quality is much better with
  no distortion.

  I have had a suspicion for a long time that this might be a software
  and not a hardware issue. After trying Android and Ubuntu on the same
  hardware I believe this suspicion is proved correct. This issue has
  persisted in all the builds I have tried since at least the beginning
  of the year, but probably longer. I am now at r17 of Utopic.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1318360/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1318360] Re: Poor microphone quality (mako)

[Simon Fels]

** Changed in: libhybris (Ubuntu)
 Assignee: (unassigned) => Simon Fels (morphis)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libhybris in Ubuntu.
https://bugs.launchpad.net/bugs/1318360

Title:
  Poor microphone quality (mako)

Status in Canonical System Image:
  Fix Committed
Status in libhybris package in Ubuntu:
  Fix Committed
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  After months of complaints from people talking to me on the phone
  (mako ubuntu touch), I finally got around to use multiROM to dual boot
  Ubuntu Touch and Android. Several people can confirm that there is a
  noticable difference in terms of sound/microphone quality between
  Android and UT in phone calls. With UT, my voice gets distorted to an
  extent that person at the other end have real difficulties to hear
  what I am saying, while with Android call quality is much better with
  no distortion.

  I have had a suspicion for a long time that this might be a software
  and not a hardware issue. After trying Android and Ubuntu on the same
  hardware I believe this suspicion is proved correct. This issue has
  persisted in all the builds I have tried since at least the beginning
  of the year, but probably longer. I am now at r17 of Utopic.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1318360/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1318360] Re: Poor microphone quality (mako)

[Simon Fels]

** Changed in: pulseaudio (Ubuntu)
   Status: Fix Committed => Invalid

** Also affects: libhybris (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1318360

Title:
  Poor microphone quality (mako)

Status in Canonical System Image:
  Fix Committed
Status in libhybris package in Ubuntu:
  Fix Committed
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  After months of complaints from people talking to me on the phone
  (mako ubuntu touch), I finally got around to use multiROM to dual boot
  Ubuntu Touch and Android. Several people can confirm that there is a
  noticable difference in terms of sound/microphone quality between
  Android and UT in phone calls. With UT, my voice gets distorted to an
  extent that person at the other end have real difficulties to hear
  what I am saying, while with Android call quality is much better with
  no distortion.

  I have had a suspicion for a long time that this might be a software
  and not a hardware issue. After trying Android and Ubuntu on the same
  hardware I believe this suspicion is proved correct. This issue has
  persisted in all the builds I have tried since at least the beginning
  of the year, but probably longer. I am now at r17 of Utopic.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1318360/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1318360] Re: Poor microphone quality (mako)

[Simon Fels]

@K1773R: It does not have to be in the milestone list to land. The
package is already part of the overlay ppa and in rc-proposed so it will
be automatically land with OTA 13.

** Also affects: canonical-devices-system-image
   Importance: Undecided
   Status: New

** Changed in: pulseaudio (Ubuntu)
   Status: Confirmed => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1318360

Title:
  Poor microphone quality (mako)

Status in Canonical System Image:
  Fix Committed
Status in libhybris package in Ubuntu:
  Fix Committed
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  After months of complaints from people talking to me on the phone
  (mako ubuntu touch), I finally got around to use multiROM to dual boot
  Ubuntu Touch and Android. Several people can confirm that there is a
  noticable difference in terms of sound/microphone quality between
  Android and UT in phone calls. With UT, my voice gets distorted to an
  extent that person at the other end have real difficulties to hear
  what I am saying, while with Android call quality is much better with
  no distortion.

  I have had a suspicion for a long time that this might be a software
  and not a hardware issue. After trying Android and Ubuntu on the same
  hardware I believe this suspicion is proved correct. This issue has
  persisted in all the builds I have tried since at least the beginning
  of the year, but probably longer. I am now at r17 of Utopic.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1318360/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1318360] Re: Poor microphone quality (mako)

[Simon Fels]

This landed with 0.1.0+git20151016+6d424c9-0ubuntu18 in the overlay ppa.
Can't say if that went out with OTA 12 or will come with OTA 13.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1318360

Title:
  Poor microphone quality (mako)

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  After months of complaints from people talking to me on the phone
  (mako ubuntu touch), I finally got around to use multiROM to dual boot
  Ubuntu Touch and Android. Several people can confirm that there is a
  noticable difference in terms of sound/microphone quality between
  Android and UT in phone calls. With UT, my voice gets distorted to an
  extent that person at the other end have real difficulties to hear
  what I am saying, while with Android call quality is much better with
  no distortion.

  I have had a suspicion for a long time that this might be a software
  and not a hardware issue. After trying Android and Ubuntu on the same
  hardware I believe this suspicion is proved correct. This issue has
  persisted in all the builds I have tried since at least the beginning
  of the year, but probably longer. I am now at r17 of Utopic.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1318360/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1602950] Re: Unity8 crashes when switching back to lockscreen while using WiDi

[Simon Fels]

@Danial: You can easily do that with the attached crash file. So what
also would a ubuntu-bug provide?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1602950

Title:
  Unity8 crashes when switching back to lockscreen while using WiDi

Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  Testing new aethercast changes (https://requests.ci-
  train.ubuntu.com/#/ticket/1620) and found unity8 is crashing when it
  switches after a timeout automatically to the lock screen.

  This is on

  current build number: 142
  device name: frieza
  channel: ubuntu-touch/rc-proposed/bq-aquaris-pd.en
  last update: 2016-07-13 05:57:58
  version version: 142
  version ubuntu: 20160713
  version device: 20160622.0
  version custom: 20160712--42-19-vivid

  SEGV backtrace:

   #0  0xe656f40e in MirBufferSGTexture::bind() () from 
/usr/lib/arm-linux-gnueabihf/qt5/qml/Unity/Application/libunityapplicationplugin.so
   No symbol table info available.
   #1  0xf6f605e2 in 
QSGOpaqueTextureMaterialShader::updateState(QSGMaterialShader::RenderState 
const&, QSGMaterial*, QSGMaterial*) () from 
/usr/lib/arm-linux-gnueabihf/libQt5Quick.so.5
   No symbol table info available.
   #2  0xf6f5194a in 
QSGBatchRenderer::Renderer::renderMergedBatch(QSGBatchRenderer::Batch const*) 
() from /usr/lib/arm-linux-gnueabihf/libQt5Quick.so.5
   No symbol table info available.
   #3  0xf6f527c8 in QSGBatchRenderer::Renderer::renderBatches() () from 
/usr/lib/arm-linux-gnueabihf/libQt5Quick.so.5
   No symbol table info available.
   #4  0xf70d2f48 in ?? () from /usr/lib/arm-linux-gnueabihf/libQt5Quick.so.5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1602950/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1602950] [NEW] Unity8 crashes when switching back to lockscreen while using WiDi

[Simon Fels]

Public bug reported:

Testing new aethercast changes (https://requests.ci-
train.ubuntu.com/#/ticket/1620) and found unity8 is crashing when it
switches after a timeout automatically to the lock screen.

This is on

current build number: 142
device name: frieza
channel: ubuntu-touch/rc-proposed/bq-aquaris-pd.en
last update: 2016-07-13 05:57:58
version version: 142
version ubuntu: 20160713
version device: 20160622.0
version custom: 20160712--42-19-vivid

SEGV backtrace:

 #0  0xe656f40e in MirBufferSGTexture::bind() () from 
/usr/lib/arm-linux-gnueabihf/qt5/qml/Unity/Application/libunityapplicationplugin.so
 No symbol table info available.
 #1  0xf6f605e2 in 
QSGOpaqueTextureMaterialShader::updateState(QSGMaterialShader::RenderState 
const&, QSGMaterial*, QSGMaterial*) () from 
/usr/lib/arm-linux-gnueabihf/libQt5Quick.so.5
 No symbol table info available.
 #2  0xf6f5194a in 
QSGBatchRenderer::Renderer::renderMergedBatch(QSGBatchRenderer::Batch const*) 
() from /usr/lib/arm-linux-gnueabihf/libQt5Quick.so.5
 No symbol table info available.
 #3  0xf6f527c8 in QSGBatchRenderer::Renderer::renderBatches() () from 
/usr/lib/arm-linux-gnueabihf/libQt5Quick.so.5
 No symbol table info available.
 #4  0xf70d2f48 in ?? () from /usr/lib/arm-linux-gnueabihf/libQt5Quick.so.5

** Affects: unity8 (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: "_usr_bin_unity8.32011.crash"
   
https://bugs.launchpad.net/bugs/1602950/+attachment/4700604/+files/_usr_bin_unity8.32011.crash

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1602950

Title:
  Unity8 crashes when switching back to lockscreen while using WiDi

Status in unity8 package in Ubuntu:
  New

Bug description:
  Testing new aethercast changes (https://requests.ci-
  train.ubuntu.com/#/ticket/1620) and found unity8 is crashing when it
  switches after a timeout automatically to the lock screen.

  This is on

  current build number: 142
  device name: frieza
  channel: ubuntu-touch/rc-proposed/bq-aquaris-pd.en
  last update: 2016-07-13 05:57:58
  version version: 142
  version ubuntu: 20160713
  version device: 20160622.0
  version custom: 20160712--42-19-vivid

  SEGV backtrace:

   #0  0xe656f40e in MirBufferSGTexture::bind() () from 
/usr/lib/arm-linux-gnueabihf/qt5/qml/Unity/Application/libunityapplicationplugin.so
   No symbol table info available.
   #1  0xf6f605e2 in 
QSGOpaqueTextureMaterialShader::updateState(QSGMaterialShader::RenderState 
const&, QSGMaterial*, QSGMaterial*) () from 
/usr/lib/arm-linux-gnueabihf/libQt5Quick.so.5
   No symbol table info available.
   #2  0xf6f5194a in 
QSGBatchRenderer::Renderer::renderMergedBatch(QSGBatchRenderer::Batch const*) 
() from /usr/lib/arm-linux-gnueabihf/libQt5Quick.so.5
   No symbol table info available.
   #3  0xf6f527c8 in QSGBatchRenderer::Renderer::renderBatches() () from 
/usr/lib/arm-linux-gnueabihf/libQt5Quick.so.5
   No symbol table info available.
   #4  0xf70d2f48 in ?? () from /usr/lib/arm-linux-gnueabihf/libQt5Quick.so.5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1602950/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1596464] Re: unity greeter stays in desktop mode if a bluetooth HID is connected

[Simon Fels]

This is nothing related to aethercast. Must be something wrong in
unity8.

** Changed in: aethercast
   Status: New => Invalid

** Also affects: canonical-devices-system-image
   Importance: Undecided
   Status: New

** Also affects: unity8 (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1596464

Title:
  unity greeter stays in desktop mode if a bluetooth HID is connected

Status in aethercast:
  Invalid
Status in Canonical System Image:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  Reproduce steps
  1. Connect with Microsoft Wireless Display Adapter V2.0.8350
  2. Force disconnected by removing Microsoft Wireless Display Adapter.
  3. Ubuntu Phone returns back to Unity greeter but does not restore to phone 
mode, user is not able to use on screen keyboard to login.

  Expected behavior:
  The unity greeter should return back to Staged usage mode.

  VERSION
  current build number: 10
  device name: turbo
  channel: ubuntu-touch/rc-proposed/meizu-pd.zh-proposed
  last update: 2016-06-27 16:25:25
  version version: 10
  version ubuntu: 20160624
  version device: 20160617-82a5c0d
  version custom: 20160626-981-7-3

  aethercast0.1+15.04.20160607-0ubuntu1
  aethercast-tools  0.1+15.04.20160607-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/aethercast/+bug/1596464/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1583057] Re: Deny audio recording for all snap applications

[Simon Fels]

Updated the patch. We now add snappy-policy always to default.pa. I
couldn't figure out what I have to change to make the ifelse statement
work properly to add the snappy policy module only conditionally to
default.pa

Also fixed the compiler warnings and other small things.

** Patch added: "pa-snappy-policy.patch"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1583057/+attachment/4696316/+files/pa-snappy-policy.patch

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1583057

Title:
  Deny audio recording for all snap applications

Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Xenial:
  In Progress
Status in pulseaudio source package in Yakkety:
  Fix Released

Bug description:
  [Impact]
  Currently snaps on Ubuntu Classic may declare in their snap.yaml that they 
want access to pulseaudio. When installed, snapd will auto-connect the 
pulseaudio interface giving the snap access to the pulseaudio server for 
playback and recording. Because recording is allowed, snaps are allowed to 
eavesdrop on users without the user knowing. Phase 1 of the pulseaudio 
interface should block recording for snaps while the details of phase 2 (which 
combines pulseaudio/snappy interfaces and trust-store) are worked out.

  [Test Case]
  First, install pulseaudio then reboot (alternatively can 'killall pulseaudio' 
from within your session or logout then killall pulseaudio from a vt and then 
log back in). pulseaudio needs to be restarted for the changes to be in effect 
and a reboot is the easiest way to achieve that.

  1. unconfined can play audio
  2. unconfined can record audio
  3. non-snap confined can play audio
  4. non-snap confined can record audio
  5. snap confined can play audio
  6. snap confined cannot record audio
  7. snap confined devmode can record audio
  8. indicator-sound and 'Sound Settings... works'
  9. click can record audio if trust-store allows (eg, 'SnapRecorder' from the 
store)
  10. click can play audio (eg, playback of recording from 'SnapRecorder' from 
the store)

  Currently '6' is not implemented and all snaps may record audio. When
  this bug is fixed, no snaps should be able to record audio (until
  phase 2 is implemented which will be in a different bug).

  The attached script tests 1-7. 9 and 10 require testing on a device
  and using

  [Regression Potential]
  The patch is quite small and easy to understand and is implemented to only 
affect processes that want to record and are running with a security label that 
starts with 'snap.' Unconfined processes and process running under other 
security labels should not be affected.

  Original description:
  Until we have a proper trust-store implementation with snappy and on the 
desktop/ubuntu core we want pulseaudio to simply deny any audio recording 
request coming from an app shipped as part of a snap.

  The implementation adds a module-snappy-policy module to pulseaudio
  which adds a hook for audio recording requests and checks on
  connection if the apparmor security label of the connecting peer
  starts with "snap." which will identify it as a snap application.

  Pulseaudio with the patch is available as part of the landing request
  at https://requests.ci-train.ubuntu.com/#/ticket/1428

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1583057/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1583057] Re: Deny audio recording for all snap applications

[Simon Fels]

@Jamie: Works fine here for me. Using a simple snap

name: pulseaudio-clients
version: 8.0-1
summary: Clients for PulseAudio
description: |
 Contains PulseAudio client utilities

apps:
  pactl:
command: usr/bin/pactl
plugs: [pulseaudio]
  paplay:
command: usr/bin/paplay
plugs: [pulseaudio]
  parec:
command: usr/bin/parec
plugs: [pulseaudio]

parts:
  packages:
plugin: nil
stage-packages:
  - pulseaudio


to test.

Make sure that  the module is loaded:

simon@nirvana ~/Work/ubuntu/snappy/paplay-snap $ pactl list modules | grep 
snappy
Name: module-snappy-policy

If not you can load it with

$ pactl load-module module-snappy-policy

If you now install the snap from above and run

$ pulseaudio-clients.parec

you will see the client hangs. If you unload the module

$ pactl unload-module module-snappy-policy

you will see the client can record now and doesn't hang any longer.

The only thing which might have went wrong with the package debdiff is
that the module for the snappy policy wasn't added to
/etc/pulse/daemon.pa. Will check that now.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1583057

Title:
  Deny audio recording for all snap applications

Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Xenial:
  In Progress
Status in pulseaudio source package in Yakkety:
  Fix Released

Bug description:
  [Impact]
  Currently snaps on Ubuntu Classic may declare in their snap.yaml that they 
want access to pulseaudio. When installed, snapd will auto-connect the 
pulseaudio interface giving the snap access to the pulseaudio server for 
playback and recording. Because recording is allowed, snaps are allowed to 
eavesdrop on users without the user knowing. Phase 1 of the pulseaudio 
interface should block recording for snaps while the details of phase 2 (which 
combines pulseaudio/snappy interfaces and trust-store) are worked out.

  [Test Case]
  First, install pulseaudio then reboot (alternatively can 'killall pulseaudio' 
from within your session or logout then killall pulseaudio from a vt and then 
log back in). pulseaudio needs to be restarted for the changes to be in effect 
and a reboot is the easiest way to achieve that.

  1. unconfined can play audio
  2. unconfined can record audio
  3. non-snap confined can play audio
  4. non-snap confined can record audio
  5. snap confined can play audio
  6. snap confined cannot record audio
  7. snap confined devmode can record audio
  8. indicator-sound and 'Sound Settings... works'
  9. click can record audio if trust-store allows (eg, 'SnapRecorder' from the 
store)
  10. click can play audio (eg, playback of recording from 'SnapRecorder' from 
the store)

  Currently '6' is not implemented and all snaps may record audio. When
  this bug is fixed, no snaps should be able to record audio (until
  phase 2 is implemented which will be in a different bug).

  The attached script tests 1-7. 9 and 10 require testing on a device
  and using

  [Regression Potential]
  The patch is quite small and easy to understand and is implemented to only 
affect processes that want to record and are running with a security label that 
starts with 'snap.' Unconfined processes and process running under other 
security labels should not be affected.

  Original description:
  Until we have a proper trust-store implementation with snappy and on the 
desktop/ubuntu core we want pulseaudio to simply deny any audio recording 
request coming from an app shipped as part of a snap.

  The implementation adds a module-snappy-policy module to pulseaudio
  which adds a hook for audio recording requests and checks on
  connection if the apparmor security label of the connecting peer
  starts with "snap." which will identify it as a snap application.

  Pulseaudio with the patch is available as part of the landing request
  at https://requests.ci-train.ubuntu.com/#/ticket/1428

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1583057/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1583057] Re: Deny audio recording for all snap applications

[Simon Fels]

@Jamie: Attached is a debdiff to update the pulse pacakge with snappy
support.

** Patch added: "pulseaudio-snappy-deny-recording.diff"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1583057/+attachment/4695115/+files/pulseaudio-snappy-deny-recording.diff

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1583057

Title:
  Deny audio recording for all snap applications

Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Xenial:
  Triaged
Status in pulseaudio source package in Yakkety:
  Fix Released

Bug description:
  Until we have a proper trust-store implementation with snappy and on
  the desktop/ubuntu core we want pulseaudio to simply deny any audio
  recording request coming from an app shipped as part of a snap.

  The implementation adds a module-snappy-policy module to pulseaudio
  which adds a hook for audio recording requests and checks on
  connection if the apparmor security label of the connecting peer
  starts with "snap." which will identify it as a snap application.

  Pulseaudio with the patch is available as part of the landing request
  at https://requests.ci-train.ubuntu.com/#/ticket/1428

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1583057/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1583057] Re: Deny audio recording for all snap applications

[Simon Fels]

@Luke: How did you test the change before landing it?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1583057

Title:
  Deny audio recording for all snap applications

Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  Until we have a proper trust-store implementation with snappy and on
  the desktop/ubuntu core we want pulseaudio to simply deny any audio
  recording request coming from an app shipped as part of a snap.

  The implementation adds a module-snappy-policy module to pulseaudio
  which adds a hook for audio recording requests and checks on
  connection if the apparmor security label of the connecting peer
  starts with "snap." which will identify it as a snap application.

  Pulseaudio with the patch is available as part of the landing request
  at https://requests.ci-train.ubuntu.com/#/ticket/1428

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1583057/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1583057] [NEW] Deny audio recording for all snap applications

[Simon Fels]

Public bug reported:

Until we have a proper trust-store implementation with snappy and on the
desktop/ubuntu core we want pulseaudio to simply deny any audio
recording request coming from an app shipped as part of a snap.

The implementation adds a module-snappy-policy module to pulseaudio
which adds a hook for audio recording requests and checks on connection
if the apparmor security label of the connecting peer starts with
"snap." which will identify it as a snap application.

Pulseaudio with the patch is available as part of the landing request at
https://requests.ci-train.ubuntu.com/#/ticket/1428

** Affects: pulseaudio (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1583057

Title:
  Deny audio recording for all snap applications

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Until we have a proper trust-store implementation with snappy and on
  the desktop/ubuntu core we want pulseaudio to simply deny any audio
  recording request coming from an app shipped as part of a snap.

  The implementation adds a module-snappy-policy module to pulseaudio
  which adds a hook for audio recording requests and checks on
  connection if the apparmor security label of the connecting peer
  starts with "snap." which will identify it as a snap application.

  Pulseaudio with the patch is available as part of the landing request
  at https://requests.ci-train.ubuntu.com/#/ticket/1428

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1583057/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1576711] Re: [xenial] Enable arm64 build

[Simon Fels]

** Package changed: aethercast (Ubuntu) => aethercast

** Changed in: aethercast
 Assignee: (unassigned) => Simon Fels (morphis)

** Changed in: aethercast
   Importance: Undecided => High

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libhybris in Ubuntu.
https://bugs.launchpad.net/bugs/1576711

Title:
  [xenial] Enable arm64 build

Status in aethercast:
  New
Status in Canonical System Image:
  Confirmed
Status in initramfs-tools-ubuntu-touch package in Ubuntu:
  New
Status in libhybris package in Ubuntu:
  Fix Released
Status in qtmir-gles package in Ubuntu:
  New
Status in qtubuntu-camera package in Ubuntu:
  New
Status in qtubuntu-gles package in Ubuntu:
  New
Status in qtubuntu-media package in Ubuntu:
  Fix Committed
Status in qtubuntu-sensors package in Ubuntu:
  New
Status in ubuntu-touch-meta package in Ubuntu:
  New
Status in unity-scope-click package in Ubuntu:
  New

Bug description:
  Tracking bug for touch packages without arm64 enabled on xenial

To manage notifications about this bug go to:
https://bugs.launchpad.net/aethercast/+bug/1576711/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1579915] Re: network-manager 1.2 uses more power

[Simon Fels]

** Changed in: network-manager (Ubuntu)
   Status: Confirmed => In Progress

** Changed in: canonical-devices-system-image
   Status: Confirmed => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1579915

Title:
  network-manager 1.2 uses more power

Status in Canonical System Image:
  In Progress
Status in network-manager package in Ubuntu:
  In Progress

Bug description:
  On krillin and arale, power use went up significantly in new builds starting 
on May 4.  So far, I have results for:
  * krillin rc-proposed 324 and 325
  * arale rc-proposed 316 and 317

  When the radios are off, results are unchanged.  However, power went up in 
two common cases -- standby with all radios enabled, and screen-on with radios 
enabled.
  * krillin standby: ~8mA -> ~80mA
  * arale standby: ~35mA -> ~79mA
  * krillin screen-on: ~177mA -> ~215mA
  * arale screen-on: ~305mA -> ~353mA

  Quite a few things landed in that build, but some of the top suspects are:
  * network-manager got updated to 1.2
  * indicator-network got a cell data switch
  * USS got "fixes to sleep/idle settings"
  * ubuntu-push got a fix related to network-manager
  * libhybris got partial support for wireless display
  * account-polld got a new calendar plugin

  Full list:
  
http://people.canonical.com/~lzemczak/landing-team/ubuntu-touch/rc-proposed/bq-aquaris.en/krillin/324.commitlog
  
http://people.canonical.com/~lzemczak/landing-team/ubuntu-touch/rc-proposed/meizu.en/arale/316.commitlog

  This change cuts typical standby time anywhere from 50% to 90%, so it
  probably should be fixed before release.  However, tests suggest that
  simply turning off wifi returns the phone to a nice low standby power
  -- about 6mA for both devices.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1579915/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1579915] Re: network-manager 1.2 uses more power

[Simon Fels]

Checked this on krillin with

current build number: 329
device name: krillin
channel: ubuntu-touch/rc-proposed/bq-aquaris.en
last update: 2016-05-10 03:25:03
version version: 329
version ubuntu: 20160510
version device: 20160329-a9bacdb
version custom: 20160505-975-38-9

Device doesn't go to sleep and attempts are visible in dmesg which also
shows

[ 1231.568056] active wakeup source: WLAN AHB ISR

as the reason for the failed attempt to sleep.

Looks like something in NetworkManager causes the kernel to still held a
wakelock even if the device should go into suspend.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1579915

Title:
  network-manager 1.2 uses more power

Status in Canonical System Image:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  On krillin and arale, power use went up significantly in new builds starting 
on May 4.  So far, I have results for:
  * krillin rc-proposed 324 and 325
  * arale rc-proposed 316 and 317

  When the radios are off, results are unchanged.  However, power went up in 
two common cases -- standby with all radios enabled, and screen-on with radios 
enabled.
  * krillin standby: ~8mA -> ~80mA
  * arale standby: ~35mA -> ~79mA
  * krillin screen-on: ~177mA -> ~215mA
  * arale screen-on: ~305mA -> ~353mA

  Quite a few things landed in that build, but some of the top suspects are:
  * network-manager got updated to 1.2
  * indicator-network got a cell data switch
  * USS got "fixes to sleep/idle settings"
  * ubuntu-push got a fix related to network-manager
  * libhybris got partial support for wireless display
  * account-polld got a new calendar plugin

  Full list:
  
http://people.canonical.com/~lzemczak/landing-team/ubuntu-touch/rc-proposed/bq-aquaris.en/krillin/324.commitlog
  
http://people.canonical.com/~lzemczak/landing-team/ubuntu-touch/rc-proposed/meizu.en/arale/316.commitlog

  This change cuts typical standby time anywhere from 50% to 90%, so it
  probably should be fixed before release.  However, tests suggest that
  simply turning off wifi returns the phone to a nice low standby power
  -- about 6mA for both devices.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1579915/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1579915] Re: big power increase in May 4th and later builds

[Simon Fels]

** Also affects: network-manager (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1579915

Title:
  network-manager 1.2 uses more power

Status in Canonical System Image:
  New
Status in network-manager package in Ubuntu:
  New

Bug description:
  On krillin and arale, power use went up significantly in new builds starting 
on May 4.  So far, I have results for:
  * krillin rc-proposed 324 and 325
  * arale rc-proposed 316 and 317

  When the radios are off, results are unchanged.  However, power went up in 
two common cases -- standby with all radios enabled, and screen-on with radios 
enabled.
  * krillin standby: ~8mA -> ~80mA
  * arale standby: ~35mA -> ~79mA
  * krillin screen-on: ~177mA -> ~215mA
  * arale screen-on: ~305mA -> ~353mA

  Quite a few things landed in that build, but some of the top suspects are:
  * network-manager got updated to 1.2
  * indicator-network got a cell data switch
  * USS got "fixes to sleep/idle settings"
  * ubuntu-push got a fix related to network-manager
  * libhybris got partial support for wireless display
  * account-polld got a new calendar plugin

  Full list:
  
http://people.canonical.com/~lzemczak/landing-team/ubuntu-touch/rc-proposed/bq-aquaris.en/krillin/324.commitlog
  
http://people.canonical.com/~lzemczak/landing-team/ubuntu-touch/rc-proposed/meizu.en/arale/316.commitlog

  This change cuts typical standby time anywhere from 50% to 90%, so it
  probably should be fixed before release.  However, tests suggest that
  simply turning off wifi returns the phone to a nice low standby power
  -- about 6mA for both devices.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1579915/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1579915] Re: network-manager 1.2 uses more power

[Simon Fels]

** Changed in: network-manager (Ubuntu)
   Importance: Undecided => Critical

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1579915

Title:
  network-manager 1.2 uses more power

Status in Canonical System Image:
  New
Status in network-manager package in Ubuntu:
  New

Bug description:
  On krillin and arale, power use went up significantly in new builds starting 
on May 4.  So far, I have results for:
  * krillin rc-proposed 324 and 325
  * arale rc-proposed 316 and 317

  When the radios are off, results are unchanged.  However, power went up in 
two common cases -- standby with all radios enabled, and screen-on with radios 
enabled.
  * krillin standby: ~8mA -> ~80mA
  * arale standby: ~35mA -> ~79mA
  * krillin screen-on: ~177mA -> ~215mA
  * arale screen-on: ~305mA -> ~353mA

  Quite a few things landed in that build, but some of the top suspects are:
  * network-manager got updated to 1.2
  * indicator-network got a cell data switch
  * USS got "fixes to sleep/idle settings"
  * ubuntu-push got a fix related to network-manager
  * libhybris got partial support for wireless display
  * account-polld got a new calendar plugin

  Full list:
  
http://people.canonical.com/~lzemczak/landing-team/ubuntu-touch/rc-proposed/bq-aquaris.en/krillin/324.commitlog
  
http://people.canonical.com/~lzemczak/landing-team/ubuntu-touch/rc-proposed/meizu.en/arale/316.commitlog

  This change cuts typical standby time anywhere from 50% to 90%, so it
  probably should be fixed before release.  However, tests suggest that
  simply turning off wifi returns the phone to a nice low standby power
  -- about 6mA for both devices.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1579915/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1513020] Re: [Wishlist] DLNA/Miracast/other WiFi support

[Simon Fels]

The feature itself is there now. What will follow is support for new
devices, performance improvements and additional features like audio
support.

That FlymeOS 5 will be available for the MX 4 doesn't mean anything for
the version running Ubuntu which will be still based on an BSP with
Android 4.x and that will not changed.

Also its not necessary to change to Android 5.x as pointed out with
https://lists.launchpad.net/ubuntu-phone/msg20284.html

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1513020

Title:
  [Wishlist] DLNA/Miracast/other WiFi support

Status in Canonical System Image:
  Fix Committed
Status in Mir:
  Fix Released
Status in aethercast package in Ubuntu:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  Hello,

  I think that there should be possibility to connect our phones to TV
  or other displays by some wireless technology.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1513020/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1570765] Re: Land initial support for WiFi Display with OTA 11

[Simon Fels]

Everything landed in the overlay ppa on last Friday.

** Changed in: aethercast
   Status: In Progress => Fix Released

** Changed in: network-manager (Ubuntu)
   Status: In Progress => Fix Released

** Changed in: ubuntu-system-settings (Ubuntu)
   Status: In Progress => Fix Released

** Changed in: wpa (Ubuntu)
   Status: In Progress => Fix Released

** Changed in: canonical-devices-system-image
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1570765

Title:
  Land initial support for WiFi Display with OTA 11

Status in aethercast:
  Fix Released
Status in Canonical System Image:
  Fix Committed
Status in network-manager package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings package in Ubuntu:
  Fix Released
Status in wpa package in Ubuntu:
  Fix Released

Bug description:
  This is about landing initial WiFi Display support for OTA 11 for the
  following target devices

  - turbo
  - frieza / cooler

  Things to land:
  - libhybris stable-20160413.1 [In progress, 
https://requests.ci-train.ubuntu.com/#/ticket/1256]
  - NetworkManager 1.2 / wpa 2.4 / ics-dhcp fix [In progress, 
https://requests.ci-train.ubuntu.com/#/ticket/1214]
  - aethercast / wds /ubuntu-system-settings [In progress, 
https://requests.ci-train.ubuntu.com/#/ticket/708]
  - device tarball for each target device with libhybris stable-20160413.1 
[turbo only]

  Actual silos will be noted here once available.

To manage notifications about this bug go to:
https://bugs.launchpad.net/aethercast/+bug/1570765/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1513020] Re: [Wishlist] DLNA/Miracast/other WiFi support

[Simon Fels]

Wireless Display supported landed in the overlay ppa last Friday.

** Changed in: aethercast (Ubuntu)
   Status: In Progress => Fix Released

** 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 mir in Ubuntu.
https://bugs.launchpad.net/bugs/1513020

Title:
  [Wishlist] DLNA/Miracast/other WiFi support

Status in Canonical System Image:
  Fix Committed
Status in Mir:
  Fix Released
Status in aethercast package in Ubuntu:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  Hello,

  I think that there should be possibility to connect our phones to TV
  or other displays by some wireless technology.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1513020/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1577132] Re: network manager update causes dbus spam with NameOwnerChanged

[Simon Fels]

*** This bug is a duplicate of bug 1575184 ***
https://bugs.launchpad.net/bugs/1575184

** This bug has been marked a duplicate of bug 1575184
   ubuntu-push is flooding dbus with NameOwnerChanged signals

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bugs/1577132

Title:
  network manager update causes dbus spam with NameOwnerChanged

Status in Canonical System Image:
  Triaged
Status in dbus package in Ubuntu:
  New
Status in network-manager package in Ubuntu:
  New

Bug description:
  After upgrading network-manager to 1.1.93-0ubuntu1~vivid1, dbus-
  monitor shows spam with NameOwnerChanged signals - there's no crash
  files or anything, but the top of top looks like so:

    PID USER  PR  NIVIRTRESSHR S  %CPU %MEM TIME+ COMMAND
   2921 phablet   20   0 1164048 277924   7444 S  34,9 28,3   4:18.54 
ubuntu-push-cli
    847 message+  20   06412   2444832 R  32,9  0,2   3:43.92 
dbus-daemon
   2255 phablet   20   07080   2172   1156 R  22,2  0,2   2:40.95 upstart
   2592 phablet   20   0   33704   4848   4140 R  17,6  0,5   1:52.28 
mission-control

  dbus-monitor shows hundreds of events like so:

  signal time=1462098650.817539 sender=:1.0 -> destination=(null destination) 
serial=11224 path=/com/ubuntu/Upstart; interface=com.ubuntu.Upstart0_6; 
member=EventEmitted
     string "dbus"
     array [
    string "SIGNAL=NameOwnerChanged"
    string "BUS=session"
    string "INTERFACE=org.freedesktop.DBus"
    string "OBJPATH=/org/freedesktop/DBus"
    string "SENDER=org.freedesktop.DBus"
    string "ARG0=:1.167"
    string "ARG1="
    string "ARG2=:1.167"
     ]

  3s of dbus-monitor:

  $ time dbus-monitor > dbus.log
  ^C
  real0m2.719s

  Shows 226 signals - so it's just under 100 signals a second:

  $ grep -c NameOwnerChanged dbus.log
  226

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: dbus 1.8.12-1ubuntu5
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.17.2-0ubuntu1.3touch1
  Architecture: armhf
  Date: Sun May  1 12:22:38 2016
  InstallationDate: Installed on 2016-04-29 (2 days ago)
  InstallationMedia: Ubuntu 15.04 - armhf (20160429-020305)
  SourcePackage: dbus
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.17.2-0ubuntu1.3touch1
  Architecture: armhf
  DistroRelease: Ubuntu 15.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   # Include files from /etc/network/interfaces.d:
   source-directory /etc/network/interfaces.d
  InstallationDate: Installed on 2016-04-29 (2 days ago)
  InstallationMedia: Ubuntu 15.04 - armhf (20160429-020305)
  IpRoute:
   default via 10.2.0.254 dev wlan0  proto static  metric 600 
   10.0.0.0/13 via 10.2.0.1 dev wlan0  proto dhcp  metric 600 
   10.2.0.0/24 dev wlan0  proto kernel  scope link  src 10.2.0.65  metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  Package: network-manager 1.1.93-0ubuntu1~vivid1 [origin: 
LP-PPA-ci-train-ppa-service-stable-phone-overlay]
  PackageArchitecture: armhf
  PciNetwork:
   
  Tags: third-party-packages vivid
  Uname: Linux 3.4.67 armv7l
  UnreportableReason: To nie jest oficjalny pakiet Ubuntu. Proszę usunąć 
wszystkie pakiety pochodzące z innych źródeł niż oficjalne i spróbować ponownie.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip plugdev sudo tty video
  _MarkForUpload: True
  
modified.conffile..etc.polkit.1.localauthority.50.local.d.org.freedesktop.NetworkManager.pkla:
 [deleted]
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1577132/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1513020] Re: [Wishlist] DLNA/Miracast/other WiFi support

[Simon Fels]

** Changed in: aethercast (Ubuntu)
   Status: New => In Progress

** Changed in: aethercast (Ubuntu)
   Importance: Undecided => High

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1513020

Title:
  [Wishlist] DLNA/Miracast/other WiFi support

Status in Canonical System Image:
  Confirmed
Status in Mir:
  Fix Released
Status in aethercast package in Ubuntu:
  In Progress
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  Hello,

  I think that there should be possibility to connect our phones to TV
  or other displays by some wireless technology.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1513020/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1472789] Re: libmtp error copying big files

[Simon Fels]

** Changed in: mtp (Ubuntu)
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mtp in Ubuntu.
https://bugs.launchpad.net/bugs/1472789

Title:
  libmtp error copying big files

Status in Canonical System Image:
  Fix Committed
Status in mtp package in Ubuntu:
  Fix Released

Bug description:
  An error message is shown when trying to copy a file of 3GB from my
  ubuntu desktop to my krillin phone using Nautilus.

  Steps to reproduce:
  1. Plug a krillin device 
  2. Create a file with > dd if=/dev/urandom of=/tmp/bigfile.txt bs=1024 
count=300
  3. Using Nautilus, copy the file to the Documents directory in the device

  In my machine it is happening that after that 2.1 GB are copied the
  process does not copy more content and an error screen appears (see
  atached). The error displayed is: "libmtp error: Could not send
  object"

  
  The free space in my device is about 3.7 GB
  My desktop os: Ubuntu 15.04
  My krilling version is: 58 (rc-proposed)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1472789/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1570765] Re: Land initial support for WiFi Display with OTA 11

[Simon Fels]

** Description changed:

  This is about landing initial WiFi Display support for OTA 11 for the
  following target devices
  
  - turbo
  - frieza / cooler
  
  Things to land:
  - libhybris stable-20160413.1 [In progress, 
https://requests.ci-train.ubuntu.com/#/ticket/1256]
  - NetworkManager 1.2 / wpa 2.4 / ics-dhcp fix [In progress, 
https://requests.ci-train.ubuntu.com/#/ticket/1214]
- - aethercast / wds /ubuntu-system-settings
- - device tarball for each target device with libhybris stable-20160413.1
+ - aethercast / wds /ubuntu-system-settings [In progress, 
https://requests.ci-train.ubuntu.com/#/ticket/708]
+ - device tarball for each target device with libhybris stable-20160413.1 
[turbo only]
  
  Actual silos will be noted here once available.

** Also affects: network-manager (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: wpa (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: network-manager (Ubuntu)
   Status: New => In Progress

** Changed in: network-manager (Ubuntu)
 Assignee: (unassigned) => Tony Espy (awe)

** Changed in: wpa (Ubuntu)
   Status: New => In Progress

** Changed in: wpa (Ubuntu)
 Assignee: (unassigned) => Simon Fels (morphis)

** Changed in: wpa (Ubuntu)
   Importance: Undecided => High

** Changed in: network-manager (Ubuntu)
   Importance: Undecided => High

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1570765

Title:
  Land initial support for WiFi Display with OTA 11

Status in aethercast:
  In Progress
Status in Canonical System Image:
  In Progress
Status in network-manager package in Ubuntu:
  In Progress
Status in ubuntu-system-settings package in Ubuntu:
  In Progress
Status in wpa package in Ubuntu:
  In Progress

Bug description:
  This is about landing initial WiFi Display support for OTA 11 for the
  following target devices

  - turbo
  - frieza / cooler

  Things to land:
  - libhybris stable-20160413.1 [In progress, 
https://requests.ci-train.ubuntu.com/#/ticket/1256]
  - NetworkManager 1.2 / wpa 2.4 / ics-dhcp fix [In progress, 
https://requests.ci-train.ubuntu.com/#/ticket/1214]
  - aethercast / wds /ubuntu-system-settings [In progress, 
https://requests.ci-train.ubuntu.com/#/ticket/708]
  - device tarball for each target device with libhybris stable-20160413.1 
[turbo only]

  Actual silos will be noted here once available.

To manage notifications about this bug go to:
https://bugs.launchpad.net/aethercast/+bug/1570765/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1571522] Re: Detect captive WiFi hotspots

[Simon Fels]

connman does a really good job here in implementing WiSPr
(https://en.wikipedia.org/wiki/WISPr) support to deal with captive
portals.

If you want to check if you're really not on an captive portral you want
to implement something like this to perform a check if you're "online"
or not:

1. Setup a well known server, lets say online.ubuntu.com which returns 
respecific HTTP headers like X-Ubuntu-Online: true once a HTTP GET request is 
received
2. When NetworkManager performs a check if its online or not (when connected to 
a new WiFi network or when the IP configuration has changed) it can send a HTTP 
GET request to online.ubuntu.com and if it gets the X-Ubuntu-Online header back 
its really online and otherwise not.

There is not right way to rely on result codes as those are not
reliable. The one way is to set up an endpoint which will return a set
expectation if you're really online.

This feature would be really something to add to NetworkManager rather
than indicator-network.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1571522

Title:
  Detect captive WiFi hotspots

Status in Canonical System Image:
  Confirmed
Status in indicator-network package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  New

Bug description:
  Right now it is very annoying that when you connect to a captive wifi
  portal, the device does not detect that. All other devices open the
  log in page automatically, except ubuntu devices. One needs to
  manually open the browser, type a url and get redirected before being
  able to log in and start e.g. telegram messaging over the wifi
  connection.

  My proposed solution to solve this:
  When a WiFi connection is established, indicator-network should do a http GET 
call to ubuntu.com. If the reply turns out to be a redirect, it should open the 
browser with the redirect url.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1571522/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1519718] Re: Screen doesn't change after connecting a BT mouse and no cursor displayed.

[Simon Fels]

@Jonas: Seems to be a problem with BlueZ (either kernel or userland).

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1519718

Title:
  Screen doesn't change after connecting a BT mouse and no cursor
  displayed.

Status in bluez package in Ubuntu:
  New
Status in ubuntu-system-settings package in Ubuntu:
  Incomplete

Bug description:
  ~$ system-image-cli -i
  current build number: 177
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.en
  last update: 2015-11-25 11:02:09
  version version: 177
  version ubuntu: 20151124
  version device: 20151019-6d4a3ab
  version custom: 2015-918-8-52

  Reproduce steps:
  Setup:Bluetooth mouse set to discovery mode.
  Step 1.Unlock the phone.
  Step 2.Swipe down the Bluetooth indicator.
  Step 3.Tap on Bluetooth settings.
  Step 4.Wait a moment for the device to appear in the list.
  Step 5.App switches to the device page, tap on connect.

  Actual result:Screen doesn't change after connecting a BT mouse and no
  cursor displayed.

  Expected result:App switches to Windowed mode and turns back to the
  Main Setting page for Bluetooth.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1519718/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1567201] Re: Wifi stops scan after enabled and disabled under flight mode, then disable flight mode

[Simon Fels]

@Evan: I suspect the problem is similar. However Tony is currently
working on a big overhaul of the NetworkManager stack to bring us back
in par with the upcoming 1.2 upstream release which will have some
fundamental changes of how the whole scan management is implemented.
There is a good chance that that will improve this bug too. Lets wait
until that big change lands and then verify again that this bug still
exists or not. We don't want to put much more time into the 0.9 release
we have currently on Touch with 1.2 being very close.

However can you please attach /var/log/syslog and all other log files
below /var/log so that we can rule out other things?

** Also affects: network-manager (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1567201

Title:
  Wifi stops scan after enabled and disabled under flight mode, then
  disable flight mode

Status in Canonical System Image:
  New
Status in network-manager package in Ubuntu:
  New

Bug description:
  $ system-image-cli -i
  current build number: 307
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2016-04-06 21:36:35
  version version: 307
  version ubuntu: 20160406
  version device: 20160329-a9bacdb
  version custom: 20160324--36-54-vivid

  Steps to reproduce:
  1. Connected to an available AP
  2. Enable Flight Mode from network indicator, both Cellular data and wifi are 
disabled
  3. Enable wifi, wifi reconnected and listing the available AP
  4. Disabled wifi again, wifi disabled and the available AP list disappears
  5. Disable Flight Mode

  Actual results:
  The wifi toggle is switched to 'On', but no available AP listed, network 
indicator showing the state of Cellular data connection.
  If manual disable wifi then enable it again, it works normally.
  Not sure if it's the same root cause of bug #1560793, though the reproduce 
steps are a bit different.

  network-manager 0.9.10.0-4ubuntu15.1.11

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1567201/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1560094] Re: Starting bluez service is denied

[Simon Fels]

** Changed in: bluez (Ubuntu)
   Status: New => In Progress

** Changed in: bluez (Ubuntu)
 Assignee: (unassigned) => Scott Sweeny (ssweeny)

** Changed in: bluez (Ubuntu)
   Importance: Undecided => High

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1560094

Title:
  Starting bluez service is denied

Status in bluez package in Ubuntu:
  In Progress

Bug description:
  If snappy core is updated in the background (on Raspberry Pi 2), and
  then bluez installed, starting the service is failing.

  
  Denials:

  [   45.955490] audit: type=1400 audit(1458574955.667:11): apparmor="DENIED" 
operation="mknod" profile="bluez5_bluez_5.37-2-armhf" 
name="/etc/dbus-1/system.d/bluez5_bluez_5.37-2-armhf.conf" pid=834 comm="c0
  [   46.197608] audit: type=1326 audit(1458574955.907:12): auid=4294967295 
uid=0 gid=0 ses=4294967295 pid=831 comm="obexd" 
exe="/snaps/bluez5/5.37-2-armhf/usr/lib/bluetooth/obexd" sig=31 arch=4028 
sysc0
  [   46.275680] audit: type=1400 audit(1458574955.987:13): apparmor="DENIED" 
operation="create" profile="bluez5_bluez_5.37-2-armhf" pid=829 
comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1
  [   46.276483] audit: type=1326 audit(1458574955.987:14): auid=4294967295 
uid=0 gid=0 ses=4294967295 pid=829 comm="bluetoothd" 
exe="/snaps/bluez5/5.37-2-armhf/usr/lib/bluetooth/bluetoothd" sig=31 arch=4000
  [   46.412021] audit: type=1326 audit(1458574956.123:15): auid=4294967295 
uid=0 gid=0 ses=4294967295 pid=839 comm="obexd" 
exe="/snaps/bluez5/5.37-2-armhf/usr/lib/bluetooth/obexd" sig=31 arch=4028 
sysc0
  [   46.504308] audit: type=1400 audit(1458574956.215:16): apparmor="DENIED" 
operation="mknod" profile="bluez5_bluez_5.37-2-armhf" 
name="/etc/dbus-1/system.d/bluez5_bluez_5.37-2-armhf.conf" pid=842 comm="c0
  [   46.520137] audit: type=1400 audit(1458574956.231:17): apparmor="DENIED" 
operation="create" profile="bluez5_bluez_5.37-2-armhf" pid=841 
comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1
  [   46.520800] audit: type=1326 audit(1458574956.231:18): auid=4294967295 
uid=0 gid=0 ses=4294967295 pid=841 comm="bluetoothd" 
exe="/snaps/bluez5/5.37-2-armhf/usr/lib/bluetooth/bluetoothd" sig=31 arch=4000
  [   46.625293] audit: type=1326 audit(1458574956.335:19): auid=4294967295 
uid=0 gid=0 ses=4294967295 pid=844 comm="obexd" 
exe="/snaps/bluez5/5.37-2-armhf/usr/lib/bluetooth/obexd" sig=31 arch=4028 
sysc0
  [   46.721080] audit: type=1400 audit(1458574956.431:20): apparmor="DENIED" 
operation="mknod" profile="bluez5_bluez_5.37-2-armhf" 
name="/etc/dbus-1/system.d/bluez5_bluez_5.37-2-armhf.conf" pid=847 comm="c2

  If trying to start bluetootctl:

  [  582.205066] audit: type=1400 audit(1458575491.915:31): apparmor="DENIED" 
operation="connect" profile="bluez5_bluetoothctl_5.37-2-armhf" 
name="/run/dbus/system_bus_socket" pid=993 comm="bluetoothctl" re0
  [bluetooth]# 

  
  ubuntu@localhost:~$ snappy list
  NameDate   Version  Developer 
  bluez5  2016-02-04 5.37-2-armhf canonical 
  canonical-pi2   2016-02-02 3.0  canonical 
  canonical-pi2-linux 2016-02-03 4.3.0-1006-3 canonical 
  ubuntu-core 2016-03-08 16.04.0-15.armhf canonical 
  ubuntu@localhost:~$ 

  ubuntu@localhost:~$ snappy info
  release: core/rolling
  architecture: armhf
  frameworks: bluez5.canonical
  apps:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1560094/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1481136] Re: Bluetooth mouse fails to reconnect after suspend + resume

[Simon Fels]

@kgunn: it looks like you're enabling the pairing mode on your BT
keyboard again (long press of the connect button) in your video. If that
is the case the keyboard will erase its part of the pairing where the
phone will still keep its part. If the phone now tries to reconnect the
connection simply fails. We don't have a user-side support story yet for
this case to show some tips or to help him removing the device and
repair.  However reinitiate the pairing from the accessory side will
always render the the remembered device information on the phone
unusable and you have to remove it.

Can you check if a long press on your BT keyboard triggers the pairing
process or does a simple connect?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1481136

Title:
  Bluetooth mouse fails to reconnect after suspend + resume

Status in Canonical System Image:
  Confirmed
Status in Canonical Pocket Desktop:
  In Progress
Status in bluez package in Ubuntu:
  In Progress

Bug description:
  I can connect the bluetooth mouse (Logitech M557) using the GUI and
  the device works properly.

  However, after suspend and resume the mouse fails to reconnect. It
  does "attempt" to reconnect, in that I see the padlock flashes
  momentarily onto the bluetooth icon on the toolbar applet. Similarly,
  if the Bluetooth Settings dialog is open the devices flashes
  momentarily bold as if connected. Both effects happen whenever the
  mouse is used (movement or mouse click) but the device does not
  connect.

  I have a workaround, which is to remove the device and pair it using
  the command line as follows:

  sudo bluez-test-device remove 00:1F:20:EF:B1:00
  sudo bluez-simple-agent hci0 00:1F:20:EF:B1:00 remove
  sudo bluez-simple-agent hci0 00:1F:20:EF:B1:00
  sudo bluez-test-device trusted 00:1F:20:EF:B1:00 yes
  sudo bluez-test-input connect 00:1F:20:EF:B1:00

  Once paired manually in this manner the devices appears in the
  Bluetooth Settings as normal an successfully reconnects when resuming.

  I'm submitted a new bug as this is similar but not the same as other
  bugs reported. In particular the workarounds presented in other bugs
  do not work for me and the workaround I'm using was not suggested in
  other cases.

  Thanks.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: bluez 4.101-0ubuntu25
  ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2
  Uname: Linux 3.19.0-25-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Aug  4 09:53:18 2015
  InstallationDate: Installed on 2014-01-23 (557 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: TOSHIBA KIRA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-25-generic.efi.signed 
root=UUID=a0fdb0ee-bbeb-4872-8e79-1a785c304e91 ro libata.force=noncq 
vesafb.invalid=1 splash quiet nopat vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/15/2013
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: Version 1.30
  dmi.board.asset.tag: 00
  dmi.board.name: KIRA
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Version A0
  dmi.chassis.asset.tag: 00
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: Version 1.0
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrVersion1.30:bd02/15/2013:svnTOSHIBA:pnKIRA:pvrPSU7FA-00T00K:rvnTOSHIBA:rnKIRA:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
  dmi.product.name: KIRA
  dmi.product.version: PSU7FA-00T00K
  dmi.sys.vendor: TOSHIBA
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
    BD Address: B4:B6:76:C4:A2:88  ACL MTU: 310:10  SCO MTU: 64:8
    UP RUNNING PSCAN
    RX bytes:587136 acl:36542 sco:0 events:271 errors:0
    TX bytes:2913 acl:109 sco:0 commands:81 errors:0
  mtime.conffile..etc.bluetooth.main.conf: 2015-08-01T14:24:23.630880

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1481136/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1553657] Re: Clicking on camera & microphone settings crashes app on mako & flo

[Simon Fels]

** Changed in: android (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 libhybris in Ubuntu.
https://bugs.launchpad.net/bugs/1553657

Title:
  Clicking on camera & microphone settings crashes app on mako & flo

Status in Canonical System Image:
  Fix Committed
Status in android package in Ubuntu:
  Fix Committed
Status in libhybris package in Ubuntu:
  Invalid
Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  On latest RC-proposed (255?) on my mako.

  I go to Settings, Privacy & Permissions, then click on Camera &
  Microphone. Get a crash or freeze each time I've tried it. (but no
  crash file?)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1553657/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1553657] Re: Clicking on camera & microphone settings crashes app on mako & flo

[Simon Fels]

Landing request for a fix is at https://requests.ci-
train.ubuntu.com/#/ticket/1145

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libhybris in Ubuntu.
https://bugs.launchpad.net/bugs/1553657

Title:
  Clicking on camera & microphone settings crashes app on mako & flo

Status in Canonical System Image:
  Confirmed
Status in android package in Ubuntu:
  In Progress
Status in libhybris package in Ubuntu:
  Invalid
Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  On latest RC-proposed (255?) on my mako.

  I go to Settings, Privacy & Permissions, then click on Camera &
  Microphone. Get a crash or freeze each time I've tried it. (but no
  crash file?)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1553657/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1553657] Re: Clicking on camera & microphone settings crashes app on mako & flo

[Simon Fels]

@Olivier: No, the android package doesn't have any effect on frieza. But
we've just merged an upgrade for platform-api/libhybris for frieza,
which should fix the same problem. Alfonso will release a new image on
rc-proposed with this change included later today.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libhybris in Ubuntu.
https://bugs.launchpad.net/bugs/1553657

Title:
  Clicking on camera & microphone settings crashes app on mako & flo

Status in Canonical System Image:
  Confirmed
Status in android package in Ubuntu:
  In Progress
Status in libhybris package in Ubuntu:
  Invalid
Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  On latest RC-proposed (255?) on my mako.

  I go to Settings, Privacy & Permissions, then click on Camera &
  Microphone. Get a crash or freeze each time I've tried it. (but no
  crash file?)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1553657/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1560068] Re: Settings report incorrect Microphone device names

[Simon Fels]

@David: Not sure, but you can take a look at

$ pactl list sources

That lists all properties pulse reports for the source devices. However
from the Android side (that is where we're reading the list of available
devices from) we only get 'primary' as the name of the source and not
further information.

With that we could fix the description of the pulse source to remove
'Droid' from the name and just have something like 'primary source'.
What you also have to respect is that the primary source has different
ports

Source #1
State: SUSPENDED
Name: source.primary
Description: Droid source primary
Driver: module-droid-card.c
Sample Specification: s16le 2ch 44100Hz
Channel Map: front-left,front-right
Owner Module: 5
Mute: no
Volume: front-left: 65536 / 100% / 0.00 dB,   front-right: 65536 / 100% 
/ 0.00 dB
balance 0.00
Base Volume: 65536 / 100% / 0.00 dB
Monitor of Sink: n/a
Latency: 0 usec, configured 0 usec
Flags: HARDWARE HW_MUTE_CTRL DECIBEL_VOLUME 
Properties:
device.description = "Droid source primary"
droid.hw_module = "primary"
device.icon_name = "audio-card"
droid.audio_source = "default"
Ports:
input-builtin_mic: Input from builtin mic (priority: 300)
input-bluetooth_sco_headset: Input from bluetooth sco headset 
(priority: 200)
input-wired_headset: Input from wired headset (priority: 500, 
not available)
input-voice_call: Input from voice call (priority: 200)
input-back_mic: Input from back mic (priority: 200)
input-default: Input from default (priority: 200)
input-parking: Parking port (priority: 50)
Active Port: input-builtin_mic
Formats:
pcm

So the primary source can be the builtin-mic, a connect HFP headset,
audio coming from a call, ... Which port is active depends on different
factors in the system. We should also look into gnome-control-center and
see how the audio configuration is handled there.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1560068

Title:
  Settings report incorrect Microphone device names

Status in Oxide:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  When opening the "Camera & microphone" settings in the webbrowser-app
  I get the following list of  Microphone devices I can select one from:

  - Default
  - Droid source primary
  - Null input

  The last two ones are incorrect and should never reach the user. The
  user doesn't know what to do with those names.

  Either we're missing a proper alias in pulseaudio or webbrowser-app
  needs to add them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1560068/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1560094] Re: Starting bluez service is denied

[Simon Fels]

** Tags removed: bluez snap
** Tags added: bluez-snappy

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1560094

Title:
  Starting bluez service is denied

Status in bluez package in Ubuntu:
  New

Bug description:
  If snappy core is updated in the background (on Raspberry Pi 2), and
  then bluez installed, starting the service is failing.

  
  Denials:

  [   45.955490] audit: type=1400 audit(1458574955.667:11): apparmor="DENIED" 
operation="mknod" profile="bluez5_bluez_5.37-2-armhf" 
name="/etc/dbus-1/system.d/bluez5_bluez_5.37-2-armhf.conf" pid=834 comm="c0
  [   46.197608] audit: type=1326 audit(1458574955.907:12): auid=4294967295 
uid=0 gid=0 ses=4294967295 pid=831 comm="obexd" 
exe="/snaps/bluez5/5.37-2-armhf/usr/lib/bluetooth/obexd" sig=31 arch=4028 
sysc0
  [   46.275680] audit: type=1400 audit(1458574955.987:13): apparmor="DENIED" 
operation="create" profile="bluez5_bluez_5.37-2-armhf" pid=829 
comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1
  [   46.276483] audit: type=1326 audit(1458574955.987:14): auid=4294967295 
uid=0 gid=0 ses=4294967295 pid=829 comm="bluetoothd" 
exe="/snaps/bluez5/5.37-2-armhf/usr/lib/bluetooth/bluetoothd" sig=31 arch=4000
  [   46.412021] audit: type=1326 audit(1458574956.123:15): auid=4294967295 
uid=0 gid=0 ses=4294967295 pid=839 comm="obexd" 
exe="/snaps/bluez5/5.37-2-armhf/usr/lib/bluetooth/obexd" sig=31 arch=4028 
sysc0
  [   46.504308] audit: type=1400 audit(1458574956.215:16): apparmor="DENIED" 
operation="mknod" profile="bluez5_bluez_5.37-2-armhf" 
name="/etc/dbus-1/system.d/bluez5_bluez_5.37-2-armhf.conf" pid=842 comm="c0
  [   46.520137] audit: type=1400 audit(1458574956.231:17): apparmor="DENIED" 
operation="create" profile="bluez5_bluez_5.37-2-armhf" pid=841 
comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1
  [   46.520800] audit: type=1326 audit(1458574956.231:18): auid=4294967295 
uid=0 gid=0 ses=4294967295 pid=841 comm="bluetoothd" 
exe="/snaps/bluez5/5.37-2-armhf/usr/lib/bluetooth/bluetoothd" sig=31 arch=4000
  [   46.625293] audit: type=1326 audit(1458574956.335:19): auid=4294967295 
uid=0 gid=0 ses=4294967295 pid=844 comm="obexd" 
exe="/snaps/bluez5/5.37-2-armhf/usr/lib/bluetooth/obexd" sig=31 arch=4028 
sysc0
  [   46.721080] audit: type=1400 audit(1458574956.431:20): apparmor="DENIED" 
operation="mknod" profile="bluez5_bluez_5.37-2-armhf" 
name="/etc/dbus-1/system.d/bluez5_bluez_5.37-2-armhf.conf" pid=847 comm="c2

  If trying to start bluetootctl:

  [  582.205066] audit: type=1400 audit(1458575491.915:31): apparmor="DENIED" 
operation="connect" profile="bluez5_bluetoothctl_5.37-2-armhf" 
name="/run/dbus/system_bus_socket" pid=993 comm="bluetoothctl" re0
  [bluetooth]# 

  
  ubuntu@localhost:~$ snappy list
  NameDate   Version  Developer 
  bluez5  2016-02-04 5.37-2-armhf canonical 
  canonical-pi2   2016-02-02 3.0  canonical 
  canonical-pi2-linux 2016-02-03 4.3.0-1006-3 canonical 
  ubuntu-core 2016-03-08 16.04.0-15.armhf canonical 
  ubuntu@localhost:~$ 

  ubuntu@localhost:~$ snappy info
  release: core/rolling
  architecture: armhf
  frameworks: bluez5.canonical
  apps:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1560094/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1560068] Re: Settings report incorrect Microphone device names

[Simon Fels]

There are two things:

1. The incorrect named "Droid source primary" element which is something
we could easily fix from pulseaudio by just adding a better description
for the source.

2. The null input should be never listed as its useless for the user and
just used internally to allow proper routing for Bluetooth audio
devices. Whoever (I suspect webbrowser-app) lists the devices here needs
to filter that device out.  There are a number of different hings for
the source element we can use for that

Source #3
State: SUSPENDED
Name: source.fake.sco
Description: Null Input
Driver: module-null-source.c
Sample Specification: s16le 1ch 8000Hz
Channel Map: mono
Owner Module: 8
Mute: no
Volume: mono: 65536 / 100% / 0.00 dB
balance 0.00
Base Volume: 65536 / 100% / 0.00 dB
Monitor of Sink: n/a
Latency: 0 usec, configured 0 usec
Flags: DECIBEL_VOLUME LATENCY 
Properties:
device.description = "Null Input"
device.class = "abstract"
device.icon_name = "audio-input-microphone"
Formats:
pcm


** Also affects: pulseaudio (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1560068

Title:
  Settings report incorrect Microphone device names

Status in pulseaudio package in Ubuntu:
  New
Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  When opening the "Camera & microphone" settings in the webbrowser-app
  I get the following list of  Microphone devices I can select one from:

  - Default
  - Droid source primary
  - Null input

  The last two ones are incorrect and should never reach the user. The
  user doesn't know what to do with those names.

  Either we're missing a proper alias in pulseaudio or webbrowser-app
  needs to add them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1560068/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1560067] [NEW] Settings report incorrect Microphone device names

[Simon Fels]

Public bug reported:

When opening the "Camera & microphone" settings in the webbrowser-app I
get the following list of  Microphone devices I can select one from:

- Default
- Droid source primary
- Null input

The last two ones are incorrect and should never reach the user. The
user doesn't know what to do with those names.

Either we're missing a proper alias in pulseaudio or webbrowser-app
needs to add them.

** Affects: webbrowser-app (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1560067

Title:
  Settings report incorrect Microphone device names

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  When opening the "Camera & microphone" settings in the webbrowser-app
  I get the following list of  Microphone devices I can select one from:

  - Default
  - Droid source primary
  - Null input

  The last two ones are incorrect and should never reach the user. The
  user doesn't know what to do with those names.

  Either we're missing a proper alias in pulseaudio or webbrowser-app
  needs to add them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1560067/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1560068] [NEW] Settings report incorrect Microphone device names

[Simon Fels]

Public bug reported:

When opening the "Camera & microphone" settings in the webbrowser-app I
get the following list of  Microphone devices I can select one from:

- Default
- Droid source primary
- Null input

The last two ones are incorrect and should never reach the user. The
user doesn't know what to do with those names.

Either we're missing a proper alias in pulseaudio or webbrowser-app
needs to add them.

** Affects: webbrowser-app (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1560068

Title:
  Settings report incorrect Microphone device names

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  When opening the "Camera & microphone" settings in the webbrowser-app
  I get the following list of  Microphone devices I can select one from:

  - Default
  - Droid source primary
  - Null input

  The last two ones are incorrect and should never reach the user. The
  user doesn't know what to do with those names.

  Either we're missing a proper alias in pulseaudio or webbrowser-app
  needs to add them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1560068/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1551811] Re: Opening the camera for the first time leads to reboot

[Simon Fels]

Just reproduce the crash again. Still caused by the same kernel panic as
mentioned in comment 7.

** Description changed:

  Test case.
  - Flash the phone.
  - Open Telegram app.
  - Fill the account details.
  - Add a contact (if needed).
  - Select a contact to send a message.
  - Tap on the clip to attach a photo.
  - Select the camera.
  
  Expected result.
  - After accepting the permission dialog, camera app allows to take a picture.
  
  Actual result.
  - After accepting the permission dialog, phone reboots.
  
  I'm not sure whether this is a problem with Telegram or with the camera.
  However, I couldn't reproduce the problem using the messaging-app. And
  once the permission dialog is accepted, the reboot is gone.
  
  com.ubuntu.telegram_2.0.8.0_armhf.click
  current build number: 259
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.en
+ 
+ --
+ 
+ Same happens with the following steps:
+ 
+ 1. Flash device (arale) with
+ 
+ $ ubuntu-device-flash touch --device arale --channel ubuntu/rc-
+ proposed/meizu.en --recovery-image 
+ --bootstrap
+ 
+ 2. Wait until flash process is done
+ 3. Go through first-start wizard
+ 4. Pass tutorial
+ 5. Directly launch camera-app, approve trust-prompt
+ 
+ Repeat 1-5 multiple times and you will see a frozen device after step 5.
+ You can verify it happened due to a kernel panic mentioned in comment
+ #7. To verify it was really the kernel panic run
+ 
+ $ sudo cat /proc/last_kmsg
+ 
+ once the device has rebooted.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1551811

Title:
  Opening the camera for the first time leads to reboot

Status in camera-app:
  New
Status in Canonical System Image:
  Confirmed
Status in Telegram app:
  Invalid
Status in mir package in Ubuntu:
  Incomplete

Bug description:
  Test case.
  - Flash the phone.
  - Open Telegram app.
  - Fill the account details.
  - Add a contact (if needed).
  - Select a contact to send a message.
  - Tap on the clip to attach a photo.
  - Select the camera.

  Expected result.
  - After accepting the permission dialog, camera app allows to take a picture.

  Actual result.
  - After accepting the permission dialog, phone reboots.

  I'm not sure whether this is a problem with Telegram or with the
  camera. However, I couldn't reproduce the problem using the messaging-
  app. And once the permission dialog is accepted, the reboot is gone.

  com.ubuntu.telegram_2.0.8.0_armhf.click
  current build number: 259
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.en

  --

  Same happens with the following steps:

  1. Flash device (arale) with

  $ ubuntu-device-flash touch --device arale --channel ubuntu/rc-
  proposed/meizu.en --recovery-image 
  --bootstrap

  2. Wait until flash process is done
  3. Go through first-start wizard
  4. Pass tutorial
  5. Directly launch camera-app, approve trust-prompt

  Repeat 1-5 multiple times and you will see a frozen device after step
  5. You can verify it happened due to a kernel panic mentioned in
  comment #7. To verify it was really the kernel panic run

  $ sudo cat /proc/last_kmsg

  once the device has rebooted.

To manage notifications about this bug go to:
https://bugs.launchpad.net/camera-app/+bug/1551811/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1551811] Re: Opening the camera for the first time leads to reboot

[Simon Fels]

Updated the descriptions with the steps I used to reproduce this.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1551811

Title:
  Opening the camera for the first time leads to reboot

Status in camera-app:
  New
Status in Canonical System Image:
  Confirmed
Status in Telegram app:
  Invalid
Status in mir package in Ubuntu:
  Incomplete

Bug description:
  Test case.
  - Flash the phone.
  - Open Telegram app.
  - Fill the account details.
  - Add a contact (if needed).
  - Select a contact to send a message.
  - Tap on the clip to attach a photo.
  - Select the camera.

  Expected result.
  - After accepting the permission dialog, camera app allows to take a picture.

  Actual result.
  - After accepting the permission dialog, phone reboots.

  I'm not sure whether this is a problem with Telegram or with the
  camera. However, I couldn't reproduce the problem using the messaging-
  app. And once the permission dialog is accepted, the reboot is gone.

  com.ubuntu.telegram_2.0.8.0_armhf.click
  current build number: 259
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.en

  --

  Same happens with the following steps:

  1. Flash device (arale) with

  $ ubuntu-device-flash touch --device arale --channel ubuntu/rc-
  proposed/meizu.en --recovery-image 
  --bootstrap

  2. Wait until flash process is done
  3. Go through first-start wizard
  4. Pass tutorial
  5. Directly launch camera-app, approve trust-prompt

  Repeat 1-5 multiple times and you will see a frozen device after step
  5. You can verify it happened due to a kernel panic mentioned in
  comment #7. To verify it was really the kernel panic run

  $ sudo cat /proc/last_kmsg

  once the device has rebooted.

To manage notifications about this bug go to:
https://bugs.launchpad.net/camera-app/+bug/1551811/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1551811] Re: Opening the camera for the first time leads to reboot

[Simon Fels]

@Kevin: I've seen it only on arale so far and also Dave says that is the
only device he saw this so far on. So suspecting an issue on the device
side is valid.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1551811

Title:
  Opening the camera for the first time leads to reboot

Status in camera-app:
  New
Status in Canonical System Image:
  Confirmed
Status in Telegram app:
  Invalid
Status in mir package in Ubuntu:
  Incomplete

Bug description:
  Test case.
  - Flash the phone.
  - Open Telegram app.
  - Fill the account details.
  - Add a contact (if needed).
  - Select a contact to send a message.
  - Tap on the clip to attach a photo.
  - Select the camera.

  Expected result.
  - After accepting the permission dialog, camera app allows to take a picture.

  Actual result.
  - After accepting the permission dialog, phone reboots.

  I'm not sure whether this is a problem with Telegram or with the
  camera. However, I couldn't reproduce the problem using the messaging-
  app. And once the permission dialog is accepted, the reboot is gone.

  com.ubuntu.telegram_2.0.8.0_armhf.click
  current build number: 259
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.en

To manage notifications about this bug go to:
https://bugs.launchpad.net/camera-app/+bug/1551811/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1551811] Re: Opening the camera for the first time leads to reboot

[Simon Fels]

@Cemil: Also that the syslog's don't show the actual crash I've seen is
likely because this is a kernel panic and syslog might not get the
kernel output before the device is rebooted. Use something like

$ cat /proc/last_kmsg

on the next boot to get the kernel side output only which is stored in
memory and remembered from last boot (not if you turn the device off).

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1551811

Title:
  Opening the camera for the first time leads to reboot

Status in camera-app:
  New
Status in Canonical System Image:
  Confirmed
Status in Telegram app:
  Invalid
Status in mir package in Ubuntu:
  Incomplete

Bug description:
  Test case.
  - Flash the phone.
  - Open Telegram app.
  - Fill the account details.
  - Add a contact (if needed).
  - Select a contact to send a message.
  - Tap on the clip to attach a photo.
  - Select the camera.

  Expected result.
  - After accepting the permission dialog, camera app allows to take a picture.

  Actual result.
  - After accepting the permission dialog, phone reboots.

  I'm not sure whether this is a problem with Telegram or with the
  camera. However, I couldn't reproduce the problem using the messaging-
  app. And once the permission dialog is accepted, the reboot is gone.

  com.ubuntu.telegram_2.0.8.0_armhf.click
  current build number: 259
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.en

To manage notifications about this bug go to:
https://bugs.launchpad.net/camera-app/+bug/1551811/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1553657] Re: Clicking on camera & microphone settings crashes app on mako & flo

[Simon Fels]

** Also affects: android (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: android (Ubuntu)
   Status: New => In Progress

** Changed in: android (Ubuntu)
   Importance: Undecided => Critical

** Changed in: android (Ubuntu)
 Assignee: (unassigned) => Simon Fels (morphis)

** Changed in: libhybris (Ubuntu)
   Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libhybris in Ubuntu.
https://bugs.launchpad.net/bugs/1553657

Title:
  Clicking on camera & microphone settings crashes app on mako & flo

Status in Canonical System Image:
  Confirmed
Status in android package in Ubuntu:
  In Progress
Status in libhybris package in Ubuntu:
  Invalid
Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  On latest RC-proposed (255?) on my mako.

  I go to Settings, Privacy & Permissions, then click on Camera &
  Microphone. Get a crash or freeze each time I've tried it. (but no
  crash file?)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1553657/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1549163] Re: Bluetooth headset HSP/HFP mode not working in Xenial

[Simon Fels]

@David: Remember that for HFP you need a mobile telephony connection
which is currently only supported through ofono which we don't ship on
the desktop. What you more want here is HSP.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1549163

Title:
  Bluetooth headset HSP/HFP mode not working in Xenial

Status in HWE Next:
  New
Status in pulseaudio package in Ubuntu:
  Triaged

Bug description:
  Using the 2/14 Xenial daily build, paired bluetooth headsets' do not
  work in HSP/HFP mode.

  [Steps to reproduce]
  1. Pair a bluetooth headset with laptop installed with Xenial 2/14 daily build
  2. In the laptop, go to sound settings > output tab > try switching mode to 
HSP/HFP mode
  3. Press the "test sound" button and try playing sound
  4. Go to the input tab and check if bluetooth headset mic is listed

  [Expected result]
  After step 3, a window for mono audio test should pop up
  After step 4, the input tab should list a bluetooth headset mic device

  [Actual result]
  After step 3, the window that pops up is for stereo (A2DP) audio test
  After step 4, the input tab does not list any bluetooth headset mic

  [Details]
  BT wireless module:
   * Intel 3160
  BT headset:
   * Jabra CLI
  Xenial: 2/14 daily build:
   * Kernel: 4.4.0-6
   * bluez: 5.36-0ubuntu1
   * gstreamer1.0-pulseaudio:amd64: 1.7.2-1ubuntu1
   * pulseaudio: 1:8.0-0ubuntu2
   * pulseaudio-module-bluetooth: 1:8.0-0ubuntu2

  [Note]
  Also double checked with same set of hardware, but with 15.10 installed.
  Bluetooth headset HSP/HFP mode worked correctly in 15.10.

  15.10 details:
   * kernel: 4.2.0-19
   * bluez: 5.35-0ubuntu2
   * gstreamer1.0-pulseaudio:amd64: 1.6.0-1ubuntu1
   * pulseaudio: 1:6.0-0ubuntu13
   * pulseaudio-module-bluetooth: 1:6.0-0ubuntu13

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1549163/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1553657] Re: Clicking on camera & microphone settings crashes app on mako & flo

[Simon Fels]

We're clearly missing symbols in libcamera_compat_layer.so in the device
tarball on the Android side but I don't have a clue yet why. A local
build of the package we have in the overlay ppa show me that the symbols
ends up in the .so. Doing a no-change rebuild in silo 38
(https://launchpad.net/~ci-train-ppa-
service/+archive/ubuntu/landing-038/) now.

** Also affects: canonical-devices-system-image
   Importance: Undecided
   Status: New

** Changed in: canonical-devices-system-image
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libhybris in Ubuntu.
https://bugs.launchpad.net/bugs/1553657

Title:
  Clicking on camera & microphone settings crashes app on mako & flo

Status in Canonical System Image:
  Confirmed
Status in libhybris package in Ubuntu:
  Confirmed
Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  On latest RC-proposed (255?) on my mako.

  I go to Settings, Privacy & Permissions, then click on Camera &
  Microphone. Get a crash or freeze each time I've tried it. (but no
  crash file?)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1553657/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1539158] Re: Unable to pair with in-car hands-free system after OTA-9 update

[Simon Fels]

** Changed in: ubuntu-system-settings (Ubuntu)
 Assignee: Simon Fels (morphis) => Ken VanDine (ken-vandine)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1539158

Title:
  Unable to pair with in-car hands-free system after OTA-9 update

Status in Canonical System Image:
  In Progress
Status in bluez package in Ubuntu:
  Invalid
Status in ubuntu-system-settings package in Ubuntu:
  In Progress

Bug description:
  After OTA-9 I started having trouble with my bluetooth connection to the car 
hands-free system (no sound, and incoming calls no longer displayed the 
number), so I have reset both the car and the phone connections (eg. forgot the 
devices).
  Now I can't even pair the phone with the car's system. 
  The car finds the phone, and then asks me to enter the code "" to pair 
the device, but after a few moments, it just says the connection failed and 
asks me to try again. Which fails again.

  It was working fine just before the update.

  Any logs I should post to help debug?

  PS - The car is a 2015 Honda Civic Tourer, if that matters.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1539158/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1553657] Re: Clicking on camera & microphone settings crashes app on mako & flo

[Simon Fels]

libhybris/android related problem. Nothing with camera-app

** Changed in: webbrowser-app (Ubuntu)
   Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libhybris in Ubuntu.
https://bugs.launchpad.net/bugs/1553657

Title:
  Clicking on camera & microphone settings crashes app on mako & flo

Status in libhybris package in Ubuntu:
  Confirmed
Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  On latest RC-proposed (255?) on my mako.

  I go to Settings, Privacy & Permissions, then click on Camera &
  Microphone. Get a crash or freeze each time I've tried it. (but no
  crash file?)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libhybris/+bug/1553657/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1513020] Re: [Wishlist] DLNA/Miracast/other WiFi support

[Simon Fels]

** Also affects: aethercast (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: aethercast (Ubuntu)
 Assignee: (unassigned) => Simon Fels (morphis)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1513020

Title:
  [Wishlist] DLNA/Miracast/other WiFi support

Status in Canonical System Image:
  Confirmed
Status in Mir:
  New
Status in aethercast package in Ubuntu:
  New
Status in mir package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  I think that there should be possibility to connect our phones to TV
  or other displays by some wireless technology.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1513020/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1539158] Re: Unable to pair with in-car hands-free system after OTA-9 update

[Simon Fels]

@Stunts: Do the following on your HOST system:

$ sudo add-apt-repository ppa:phablet-team/ubuntu/tools
$ sudo apt-get install phablet-tools-citrain

Now connect the phone over adb (make sure developer mode is enabled):

Still from the HOST system:

$ citrain device-upgrade  

PLEASE KEEP IN MIND: This will change the content of the device rootfs
system. If you don't want to reflash via ubuntu-device-flash or don't
know how to do that it might be better to wait until this fix lands with
the next OTA.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1539158

Title:
  Unable to pair with in-car hands-free system after OTA-9 update

Status in Canonical System Image:
  In Progress
Status in bluez package in Ubuntu:
  Invalid
Status in ubuntu-system-settings package in Ubuntu:
  In Progress

Bug description:
  After OTA-9 I started having trouble with my bluetooth connection to the car 
hands-free system (no sound, and incoming calls no longer displayed the 
number), so I have reset both the car and the phone connections (eg. forgot the 
devices).
  Now I can't even pair the phone with the car's system. 
  The car finds the phone, and then asks me to enter the code "" to pair 
the device, but after a few moments, it just says the connection failed and 
asks me to try again. Which fails again.

  It was working fine just before the update.

  Any logs I should post to help debug?

  PS - The car is a 2015 Honda Civic Tourer, if that matters.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1539158/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1530807] Re: [FHD] Bluetooth cannot be activated on several devices

[Simon Fels]

** Branch linked: lp:~morphis/indicator-bluetooth/fix-lp1530807

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-bluetooth in
Ubuntu.
https://bugs.launchpad.net/bugs/1530807

Title:
  [FHD] Bluetooth cannot be activated on several devices

Status in The Avila project:
  In Progress
Status in Canonical System Image:
  Fix Committed
Status in Canonical Pocket Desktop:
  Confirmed
Status in indicator-bluetooth package in Ubuntu:
  In Progress
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed

Bug description:
  Using RC proposed 04/01/2016 bluetooth cannot be enabled.

  Tested on a nexus 7.

  Expected behavior:
  Bluetooth slider is moved to on
  Bluetooth activates
  Available devices appear in the list

  Experienced behavior: 
  Bluetooth slider is moved to on
  Activity spinners appear 
  Bluetooth slider moves to off.

To manage notifications about this bug go to:
https://bugs.launchpad.net/avila/+bug/1530807/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1529049] Re: Switch bluetooth keyboard from qwerty to azerty

[Simon Fels]

*** This bug is a duplicate of bug 1491340 ***
https://bugs.launchpad.net/bugs/1491340

This isn't a problem with bluez or the bluetooth stack. There is work in
progress to select the right keyboard layout as this isn't working no
matter through which technology the keyboard is connected with.

** Changed in: bluez (Ubuntu)
   Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1529049

Title:
  Switch bluetooth keyboard from qwerty to azerty

Status in ubuntu-keyboard:
  New
Status in bluez package in Ubuntu:
  Invalid

Bug description:
  Trying convergence, I've noticed that :

  When a bluetooth keyboard is paired, the keyboard is by default in
  Qwerty (even if it's an Azerty keyboard and the settings of UT are on
  French Azerty keyboard layout)

  We should have an option to set the Azerty / Qwerty option in bluetooth 
settings.
  Or a better solution could be that the bluetooth keyboard layout is set to 
the default keyboard layout we have put in Language settings.

  Does someone know a way to set correctly the layout of the bluetooth
  keyboard ? (I've tried : 'loadkeys fr' in terminal but this didn't
  work, I suspect that the default layout was already on fr but the
  bluetooth keyboard doesn't detect it)

  Device : mako rc-proposed last revision of 24 dec 2015

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-keyboard/+bug/1529049/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1488170] Re: Bluetooth initiated after quitting airplane mode

[Simon Fels]

** Changed in: urfkill (Ubuntu)
   Status: Confirmed => Invalid

** 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 bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1488170

Title:
  Bluetooth initiated after quitting airplane mode

Status in Canonical System Image:
  Fix Committed
Status in bluez package in Ubuntu:
  Fix Committed
Status in urfkill package in Ubuntu:
  Invalid

Bug description:
  This happens despite bluetooth not being enabled when entering
  airplane mode.

  On Aquaris E5 OTA-5.

  Boot with bluetooth disabled
  Turn on flight mode
  turn off flight mode
  Bluetooth gets enabled

  See bug #1421249 for related symptoms

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1488170/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1539158] Re: Unable to pair with in-car hands-free system after OTA-9 update

[Simon Fels]

MP with a possible fix is linked now.

@Stunts: I've put the MP into silo 67 (https://requests.ci-
train.ubuntu.com/#/ticket/1102). Can you install that one on your device
and try if that fixes the problem for you?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1539158

Title:
  Unable to pair with in-car hands-free system after OTA-9 update

Status in Canonical System Image:
  In Progress
Status in bluez package in Ubuntu:
  Invalid
Status in ubuntu-system-settings package in Ubuntu:
  In Progress

Bug description:
  After OTA-9 I started having trouble with my bluetooth connection to the car 
hands-free system (no sound, and incoming calls no longer displayed the 
number), so I have reset both the car and the phone connections (eg. forgot the 
devices).
  Now I can't even pair the phone with the car's system. 
  The car finds the phone, and then asks me to enter the code "" to pair 
the device, but after a few moments, it just says the connection failed and 
asks me to try again. Which fails again.

  It was working fine just before the update.

  Any logs I should post to help debug?

  PS - The car is a 2015 Honda Civic Tourer, if that matters.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1539158/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1539158] Re: Unable to pair with in-car hands-free system after OTA-9 update

[Simon Fels]

** Changed in: ubuntu-system-settings (Ubuntu)
   Status: Confirmed => In Progress

** Changed in: ubuntu-system-settings (Ubuntu)
   Importance: Undecided => High

** Changed in: ubuntu-system-settings (Ubuntu)
   Importance: High => Critical

** Changed in: ubuntu-system-settings (Ubuntu)
 Assignee: (unassigned) => Simon Fels (morphis)

** Branch linked: lp:~morphis/ubuntu-system-settings/fix-lp1539158

** Changed in: canonical-devices-system-image
   Status: Confirmed => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1539158

Title:
  Unable to pair with in-car hands-free system after OTA-9 update

Status in Canonical System Image:
  In Progress
Status in bluez package in Ubuntu:
  Invalid
Status in ubuntu-system-settings package in Ubuntu:
  In Progress

Bug description:
  After OTA-9 I started having trouble with my bluetooth connection to the car 
hands-free system (no sound, and incoming calls no longer displayed the 
number), so I have reset both the car and the phone connections (eg. forgot the 
devices).
  Now I can't even pair the phone with the car's system. 
  The car finds the phone, and then asks me to enter the code "" to pair 
the device, but after a few moments, it just says the connection failed and 
asks me to try again. Which fails again.

  It was working fine just before the update.

  Any logs I should post to help debug?

  PS - The car is a 2015 Honda Civic Tourer, if that matters.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1539158/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1539158] Re: Unable to pair with in-car hands-free system after OTA-9 update

[Simon Fels]

Analyzed the latest log files and came to following conclusion about
that is going on here:

The key point here is that the car initiates the pairing with the phone
which then leads to a timing problem in ubuntu-system-settings. But step
by step:

Feb 23 09:43:45 ubuntu-phablet bluetoothd[880]: 
src/adapter.c:device_found_callback() hci0 addr 84:38:35:62:28:DF, rssi -91 
flags 0x eir_len 72
Feb 23 09:43:45 ubuntu-phablet bluetoothd[880]: src/device.c:device_create() 
dst 84:38:35:62:28:DF
Feb 23 09:43:45 ubuntu-phablet bluetoothd[880]: src/device.c:device_new() 
address 84:38:35:62:28:DF
Feb 23 09:43:45 ubuntu-phablet bluetoothd[880]: src/device.c:device_new() 
Creating device /org/bluez/hci0/dev_84_38_35_62_28_DF
Feb 23 09:43:45 ubuntu-phablet bluetoothd[880]: 
src/device.c:device_set_legacy() legacy 0
Feb 23 09:43:45 ubuntu-phablet bluetoothd[880]: 
src/device.c:device_set_rssi_with_delta() rssi -91
Feb 23 09:43:45 ubuntu-phablet bluetoothd[880]: 
src/device.c:btd_device_device_set_name() /org/bluez/hci0/dev_84_38_35_62_28_DF 
MacBook Air de Cristina
Feb 23 09:43:45 ubuntu-phablet bluetoothd[880]: src/device.c:device_set_class() 
/org/bluez/hci0/dev_84_38_35_62_28_DF 0x38010C

Here we see that bluez correctly finds the device and directly continues
with an pairing attempt which it gets from the remote device

Feb 23 09:43:46 ubuntu-phablet bluetoothd[880]: 
src/adapter.c:pin_code_request_callback() hci0 00:0A:30:B3:52:4B
Feb 23 09:43:46 ubuntu-phablet bluetoothd[880]: src/device.c:device_create() 
dst 00:0A:30:B3:52:4B
Feb 23 09:43:46 ubuntu-phablet bluetoothd[880]: src/device.c:device_new() 
address 00:0A:30:B3:52:4B
Feb 23 09:43:46 ubuntu-phablet bluetoothd[880]: src/device.c:device_new() 
Creating device /org/bluez/hci0/dev_00_0A_30_B3_52_4B
Feb 23 09:43:46 ubuntu-phablet bluetoothd[880]: src/device.c:new_auth() 
Requesting agent authentication for 00:0A:30:B3:52:4B
Feb 23 09:43:46 ubuntu-phablet bluetoothd[880]: src/agent.c:agent_ref() 
0xb7113930: ref=2
Feb 23 09:43:46 ubuntu-phablet bluetoothd[880]: src/agent.c:agent_ref() 
0xb7113930: ref=3

So there is basically no time span between the phone detecting the
device and getting the pairing request. BlueZ then sends out the pairing
request to its registered agents:

Feb 23 09:43:46 ubuntu-phablet bluetoothd[880]: Agent 
/com/canonical/SettingsBluetoothAgent/adapteragent replied with an error: 
org.bluez.Error.Rejected, The request was rejected: RequestPinCode
Feb 23 09:43:46 ubuntu-phablet bluetoothd[880]: 
src/adapter.c:btd_adapter_pincode_reply() hci0 addr 00:0A:30:B3:52:4B pinlen 0

.. which gets denied from settings app as it doesn't have the device in
its internal list yet. See https://bazaar.launchpad.net/~system-
settings-touch/ubuntu-system-
settings/trunk/view/head:/plugins/bluetooth/agent.cpp#L115 for details.

We need to rework ubuntu-system-settings here to add the new device
based on the object path it gets from bluez with the pairing request.

** Also affects: ubuntu-system-settings (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: bluez (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: ubuntu-system-settings (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1539158

Title:
  Unable to pair with in-car hands-free system after OTA-9 update

Status in Canonical System Image:
  Confirmed
Status in bluez package in Ubuntu:
  Invalid
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed

Bug description:
  After OTA-9 I started having trouble with my bluetooth connection to the car 
hands-free system (no sound, and incoming calls no longer displayed the 
number), so I have reset both the car and the phone connections (eg. forgot the 
devices).
  Now I can't even pair the phone with the car's system. 
  The car finds the phone, and then asks me to enter the code "" to pair 
the device, but after a few moments, it just says the connection failed and 
asks me to try again. Which fails again.

  It was working fine just before the update.

  Any logs I should post to help debug?

  PS - The car is a 2015 Honda Civic Tourer, if that matters.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1539158/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1494225] Re: Call audio is not routed to headset with HFP

[Simon Fels]

Looked through Pat's log file and it actually shows that the HFP profile
is never correctly connected due to

Mar  1 13:26:27 ubuntu-phablet bluetoothd[739]: src/profile.c:ext_connect() 
hfp_ag connected to 00:18:16:20:00:FE
Mar  1 13:26:27 ubuntu-phablet bluetoothd[739]: src/service.c:change_state() 
0xb775f8b8: device 00:18:16:20:00:FE profile hfp_ag state changed: connecting 
-> disconnected (-5)
Mar  1 13:26:27 ubuntu-phablet bluetoothd[739]: 
src/device.c:device_profile_connected() hfp_ag Input/output error (5)

That is the reason why audio is never routed throught he headset. Needs
more investigation to find out what the reason for this is.

** Also affects: ofono (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1494225

Title:
  Call audio is not routed to headset with HFP

Status in Canonical System Image:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed
Status in media-hub package in Ubuntu:
  Invalid
Status in ofono package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  With bluez 5.33 on Nexus 4 and silo 43 installed:

  * pair and connect a headset over HFP
  * Establish an outgoing call or accept an incoming one
  * Once the call is established the call audio isn't routed through the 
handsfree device

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1494225/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1536493] Re: Call/SMS Alert are not routed to bluetooth headset

[Simon Fels]

*** This bug is a duplicate of bug 1552128 ***
https://bugs.launchpad.net/bugs/1552128

** Description changed:

  Expected Result:
  All audio from the phone should play in the bluetooth headset when it is 
connected.
  
  Actual Result:
  The music and other audio plays on the bluetooth headset however the SMS/Call 
alerts are not. They are still played in the phone's speaker. This causes the 
user to miss the notification because you can't hear it especially when 
listening to music/podcast.
  
  Device:
  bq Aquarius E5 HD
  Version:
  OTA 8.5
  
  Same on MX4 rc-proposed/ota 9
- 
- In addition when answering the call, the call audio is not on the
- headset

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1536493

Title:
  Call/SMS Alert are not routed to bluetooth headset

Status in Canonical System Image:
  Confirmed
Status in bluez package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  New
Status in telepathy-ofono package in Ubuntu:
  New

Bug description:
  Expected Result:
  All audio from the phone should play in the bluetooth headset when it is 
connected.

  Actual Result:
  The music and other audio plays on the bluetooth headset however the SMS/Call 
alerts are not. They are still played in the phone's speaker. This causes the 
user to miss the notification because you can't hear it especially when 
listening to music/podcast.

  Device:
  bq Aquarius E5 HD
  Version:
  OTA 8.5

  Same on MX4 rc-proposed/ota 9

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1536493/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1500242] Re: Bluetooth devices (Jabra BT250, Audi A3 car kit) can not be connected with BQ Aquaris 4.5

[Simon Fels]

** Tags added: bluetooth-ota10

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1500242

Title:
  Bluetooth devices (Jabra BT250, Audi A3 car kit) can not be connected
  with BQ Aquaris 4.5

Status in Canonical System Image:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed
Status in ofono package in Ubuntu:
  Incomplete

Bug description:
  STEPS:
  Requirements: Aquaris E4.5, Jabra BT250 blue tooth handset device (rather old 
one supports blue tooth 1.1 and therefore I thought should be no issue) or Audi 
car kit (A3 2012 model)

  1. Put Jabra BT250 into receiving mode
  2. Phone searches automatically every 15 - 30 seconds for a new blue tooth 
device
  3. Phone finds Jabra BT250 and asks for pairing code
  4. Enter code into phone
  5. Jabra BT250 automatically exits the pairing mode (which is a sign that 
pairing should have worked)
  6. Phone looses connection to Jabra BT250
  7. Manual reconnection via phone works (shows Jabra BT250 as being connected) 
but ignores the device

  Same behaviour with Audi car kit (Audi A3, 2012 model)

  EXPECTED:
  I expect that the blue tooth kits work similar to my Seat Alhambra (also 2012 
model) where the blue tooth pairing etc. works great (except some bugs which 
are already filed).

  ACTUAL:
  No connection to the blue tooth device

  VERSIONS:
  OS-Build-Number: 25
  Ubuntu-Image: 20150825.1

  POSSIBLE ROOT CAUSE:
  Is this issue also solved as soon as bluez5 is implemented? When will this be?

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1500242/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1494225] Re: Call audio is not routed to headset with HFP

[Simon Fels]

** Tags added: bluetooth-ota10

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1494225

Title:
  Call audio is not routed to headset with HFP

Status in Canonical System Image:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed
Status in media-hub package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  With bluez 5.33 on Nexus 4 and silo 43 installed:

  * pair and connect a headset over HFP
  * Establish an outgoing call or accept an incoming one
  * Once the call is established the call audio isn't routed through the 
handsfree device

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1494225/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1536493] Re: Call/SMS Alert are not routed to bluetooth headset

[Simon Fels]

Possible duplicate of https://bugs.launchpad.net/canonical-devices-
system-image/+bug/1552128

** Tags added: bluetooth-ota10

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1536493

Title:
  Call/SMS Alert are not routed to bluetooth headset

Status in Canonical System Image:
  Confirmed
Status in bluez package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  New
Status in telepathy-ofono package in Ubuntu:
  New

Bug description:
  Expected Result:
  All audio from the phone should play in the bluetooth headset when it is 
connected.

  Actual Result:
  The music and other audio plays on the bluetooth headset however the SMS/Call 
alerts are not. They are still played in the phone's speaker. This causes the 
user to miss the notification because you can't hear it especially when 
listening to music/podcast.

  Device:
  bq Aquarius E5 HD
  Version:
  OTA 8.5

  Same on MX4 rc-proposed/ota 9

  In addition when answering the call, the call audio is not on the
  headset

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1536493/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1479438] Re: IN CAR: Battery levels not shared via bluetooth for in car experience

[Simon Fels]

** Tags added: bluetooth-ota10

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1479438

Title:
  IN CAR: Battery levels not shared via bluetooth for in car experience

Status in Canonical System Image:
  In Progress
Status in bluez package in Ubuntu:
  In Progress
Status in ofono package in Ubuntu:
  Confirmed
Status in ofono package in Ubuntu RTM:
  Confirmed

Bug description:
  STEPS:
  Requirements: DUT a car with bluetooth and phone connection kit (Skoda Superb 
2013 in my instance)

  1. Connect the DUT to the car
  2. On the display panel the battery always shows full

  EXPECTED:
  I expect to see the actual level of the battery on the device

  ACTUAL:
  The display always shows the battery at 100% I assume the default if no info 
is available.

  VERSIONS:
  current build number: 71
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.en
  last update: 2015-07-28 18:01:08
  version version: 71
  version ubuntu: 20150728
  version device: 20150709-8965e37
  version custom: 20150716-819-8-42

  MODIFICATIONS:
  Installation of silo19 for in car bt fix

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1479438/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1494230] Re: Audio is not routed to A2DP sink when connected

[Simon Fels]

** Tags added: bluetooth-ota10

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1494230

Title:
  Audio is not routed to A2DP sink when connected

Status in Canonical System Image:
  In Progress
Status in bluez package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Fix Committed

Bug description:
  With bluez 5.33 on Nexus 4 and silo 43 installed.

  * Pair/connect A2DP sink device
  * Play any audio

  -> Audio is not played on A2DP sink and also not on speakers

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1494230/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1488170] Re: Bluetooth initiated after quitting airplane mode

[Simon Fels]

** Tags added: bluetooth-ota10

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1488170

Title:
  Bluetooth initiated after quitting airplane mode

Status in Canonical System Image:
  Confirmed
Status in bluez package in Ubuntu:
  Fix Committed
Status in urfkill package in Ubuntu:
  Confirmed

Bug description:
  This happens despite bluetooth not being enabled when entering
  airplane mode.

  On Aquaris E5 OTA-5.

  Boot with bluetooth disabled
  Turn on flight mode
  turn off flight mode
  Bluetooth gets enabled

  See bug #1421249 for related symptoms

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1488170/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1519681] Re: Some media keys on keyboards do not work as expected

[Simon Fels]

** Tags added: bluetooth-ota10

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1519681

Title:
  Some media keys on keyboards do not work as expected

Status in The Avila project:
  Confirmed
Status in Canonical System Image:
  Confirmed
Status in Canonical Pocket Desktop:
  New
Status in bluez package in Ubuntu:
  Confirmed
Status in qtubuntu-media package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  $ system-image-cli -i
  current build number: 75
  device name: mako
  channel: ubuntu-touch/rc-proposed/ubuntu-pd
  last update: 2015-11-24 05:39:02
  version version: 75
  version ubuntu: 20151124
  version device: 20150911
  version custom: 20150929-2-vivid

  Steps to reproduce:
  1. Windowed mode is enabled with BT mouse/keyboard connected
  2. Launch music app to play all of a playlist
  3. Press Pause/Play, Fast forward/Rewind keys on BT keyboard

  Actual results:
  Press media keys(Pause/Play, Fast forward/Rewind) on BT keyboard has no 
control for playback 
  currently only Volume Up/ Down and Mute/Unmute media keys work

  BT keyboard type: Logitech K480 and Rapoo E6350

To manage notifications about this bug go to:
https://bugs.launchpad.net/avila/+bug/1519681/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1539158] Re: Unable to pair with in-car hands-free system after OTA-9 update

[Simon Fels]

** Tags removed: bluetooth
** Tags added: bluetooth-ota10bluetooth

** Tags removed: bluetooth-ota10bluetooth
** Tags added: bluetooth bluetooth-ota10

** Tags added: bluez-touch

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1539158

Title:
  Unable to pair with in-car hands-free system after OTA-9 update

Status in Canonical System Image:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  After OTA-9 I started having trouble with my bluetooth connection to the car 
hands-free system (no sound, and incoming calls no longer displayed the 
number), so I have reset both the car and the phone connections (eg. forgot the 
devices).
  Now I can't even pair the phone with the car's system. 
  The car finds the phone, and then asks me to enter the code "" to pair 
the device, but after a few moments, it just says the connection failed and 
asks me to try again. Which fails again.

  It was working fine just before the update.

  Any logs I should post to help debug?

  PS - The car is a 2015 Honda Civic Tourer, if that matters.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1539158/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1552128] Re: Music audio is not transferred to headset after it is connected

[Simon Fels]

** Tags added: bluetooth-ota10

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1552128

Title:
  Music audio is not transferred to headset after it is connected

Status in Canonical System Image:
  Confirmed
Status in bluez package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Device and Ubuntu version
  =

  Tested on Krillin [Aquaris E4.5], with BlueZ 5.37

  phablet@ubuntu-phablet:~$ lsb_release -rd
  Description:Ubuntu 15.04
  Release:15.04
  phablet@ubuntu-phablet:~$

  Tested with:
  1. Sony SBH52 headset
  2. Philips SHB5500 headphones

  Description:
  =

  In disconnect state play the music on the phone and do the connection
  (bluetoothctl connect ).

  Audio is not transferred to the BT headset but it still plays on the
  phone instead. On the other hand the bluetoothctl and UI shows that
  the device is connected. The headset blinkenlights indicate that it is
  connected too.

  The audio is properly routed again after the incoming call is made and
  rejected/accepted+terminated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1552128/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1543179] Re: Audio does not get routed to BT headset/speaker

[Simon Fels]

** Tags added: bluetooth-ota10

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1543179

Title:
  Audio does not get routed to BT headset/speaker

Status in Canonical System Image:
  Confirmed
Status in bluez package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  STEPS:
  1. Flash the latest daily rc-proposed image to a phone
  2. Connect a bluetooth headset to the phone
  3. Connect a speaker to the phone.

  EXPECTED:
  I expect the devices to connect and play audio

  ACTUAL:
  Speakers just connect and instantly disconnect

  Headsets don't get trusted and disconnect instantly, Once you trust it
  and then turn the headset off and back on again it connect can accept
  calls but the audio from both the mic and earpiece don't function.

  Image: 242

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1543179/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1546310] Re: In CAR bluetooth not working

[Simon Fels]

** Tags added: bluetooth-ota10

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1546310

Title:
  In CAR bluetooth not working

Status in Canonical System Image:
  Fix Committed
Status in bluez package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Fix Committed

Bug description:
  I have paired my phone with my car as always (connection did work in
  the past). Connection runs as expected and everything like display,
  phone book, ... but this evening I wanted to place a call from my car
  and it did not work. I was then also not able to take a call (I could
  not hear the conterpart and the counterpart could not hear me).

  Since yesterday I am on:

  current build number: 259
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2016-02-16 12:09:18
  version version: 259
  version ubuntu: 20160216
  version device: 20160108-efc96d8
  version custom: 20160111-926-36--vivid

  With OTA9 I did not have the issue. I have attached my logs. I have
  enabled the following bug-settings for bluetooth:

  sudo sed -i 's/exec \/usr\/sbin\/bluetoothd/exec
  \/usr\/sbin\/bluetoothd -d/g' /etc/init/bluetooth.conf

  sudo sed -i 's/--start/--start --log-level=debug/g'
  /usr/share/upstart/sessions/pulseaudio.conf

  I have modified the line in ofono.override to:

  exec ofonod -P -d provision,udev*,dun*,smart*,hfp_bluez5,stktest,sap

  I hope my reporting helps to trace down this issue.

  Uranicus

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1546310/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1555608] Re: Bluetooth "Connection timed out" during a longer call

[Simon Fels]

** Also affects: bluez (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: bluez (Ubuntu)
   Importance: Undecided => High

** Tags added: bluez-touch

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1555608

Title:
  Bluetooth "Connection timed out" during a longer call

Status in Canonical System Image:
  New
Status in bluez package in Ubuntu:
  New

Bug description:
  Issue:
  Phone disconnected bluetooth connection during a longer call.

  I am on:
  current build number: 275
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2016-03-08 06:14:58
  version version: 275
  version ubuntu: 20160308
  version device: 20160108-efc96d8
  version custom: 20160111-926-36--vivid

  I was in a longer telephone call. All of a sudden the bluetooth
  connection got interrupted. At the time when the bluetooth connection
  got disconnected the following statement from bluetooth was logged:

  Mar 9 08:26:31 ubuntu-phablet bluetoothd[899]: Start: Connection timed out 
(110)
  + following logs (see attached)

  The call itself still was active just the phone disconnected from my
  car.

  Logs are attached.

  Matthias

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1555608/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1546310] Re: In CAR bluetooth not working

[Simon Fels]

@Matthias: Yes lets take the disconnection as separate bug so that we
can close this one. The bug you've tested now landed in rc-proposed and
will be part of OTA10.

That the connection times out smells really like a different problem so
another bug is the right way. Can you attach the log files there too?

** Changed in: pulseaudio (Ubuntu)
   Status: In Progress => Fix Committed

** 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 bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1546310

Title:
  In CAR bluetooth not working

Status in Canonical System Image:
  Fix Committed
Status in bluez package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Fix Committed

Bug description:
  I have paired my phone with my car as always (connection did work in
  the past). Connection runs as expected and everything like display,
  phone book, ... but this evening I wanted to place a call from my car
  and it did not work. I was then also not able to take a call (I could
  not hear the conterpart and the counterpart could not hear me).

  Since yesterday I am on:

  current build number: 259
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2016-02-16 12:09:18
  version version: 259
  version ubuntu: 20160216
  version device: 20160108-efc96d8
  version custom: 20160111-926-36--vivid

  With OTA9 I did not have the issue. I have attached my logs. I have
  enabled the following bug-settings for bluetooth:

  sudo sed -i 's/exec \/usr\/sbin\/bluetoothd/exec
  \/usr\/sbin\/bluetoothd -d/g' /etc/init/bluetooth.conf

  sudo sed -i 's/--start/--start --log-level=debug/g'
  /usr/share/upstart/sessions/pulseaudio.conf

  I have modified the line in ofono.override to:

  exec ofonod -P -d provision,udev*,dun*,smart*,hfp_bluez5,stktest,sap

  I hope my reporting helps to trace down this issue.

  Uranicus

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1546310/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1550050] Re: repeating phantom key when bt disconnects

[Simon Fels]

Marked as invalid for bluez until we prove there is still a problem.

** Changed in: bluez (Ubuntu)
   Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1550050

Title:
  repeating phantom key when bt disconnects

Status in Canonical System Image:
  In Progress
Status in Canonical Pocket Desktop:
  New
Status in Mir:
  In Progress
Status in Mir 0.20 series:
  In Progress
Status in bluez package in Ubuntu:
  Invalid
Status in mir package in Ubuntu:
  In Progress

Bug description:
  Every now and then when having bt mouse/keyboard connected - you will
  see when selecting a text box there is a repeating character (there is
  no specific character, but always repeats)

  It seems to be related somehow to bt devices disconnecting
  the only cure is a reboot

  This was reproduced by turning off the keyboard while holding down a
  key. We suspect the key up event is never delivered. This mimics the
  case where the BT connection drops off momentarily or perhaps an event
  is missed over the BT connection.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1550050/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1552128] Re: Music audio is not transferred to headset after it is connected

[Simon Fels]

** Changed in: bluez (Ubuntu)
 Assignee: (unassigned) => Konrad Zapałowicz (kzapalowicz)

** Changed in: pulseaudio (Ubuntu)
 Assignee: (unassigned) => Konrad Zapałowicz (kzapalowicz)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1552128

Title:
  Music audio is not transferred to headset after it is connected

Status in Canonical System Image:
  Confirmed
Status in bluez package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Device and Ubuntu version
  =

  Tested on Krillin [Aquaris E4.5], with BlueZ 5.37

  phablet@ubuntu-phablet:~$ lsb_release -rd
  Description:Ubuntu 15.04
  Release:15.04
  phablet@ubuntu-phablet:~$

  Tested with:
  1. Sony SBH52 headset
  2. Philips SHB5500 headphones

  Description:
  =

  In disconnect state play the music on the phone and do the connection
  (bluetoothctl connect ).

  Audio is not transferred to the BT headset but it still plays on the
  phone instead. On the other hand the bluetoothctl and UI shows that
  the device is connected. The headset blinkenlights indicate that it is
  connected too.

  The audio is properly routed again after the incoming call is made and
  rejected/accepted+terminated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1552128/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1527354] Re: [Jawbone ERA] HFP features not working with Bluez5 when phone initiates connection

[Simon Fels]

@Tony: With your last comment: BlueZ 5.37 doesn't fix that problem too?
Or do you still see this with bluez 5.37?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1527354

Title:
  [Jawbone ERA] HFP features not working with Bluez5 when phone
  initiates connection

Status in Canonical System Image:
  New
Status in bluez package in Ubuntu:
  In Progress

Bug description:
  While debugging some re-factoring work on the ofono upower plugin, I
  noticed that I wasn't able to answer or terminate calls using my
  Jawbone ERA headset.  I bought this headset last year, and although
  it's an older model, it's spec sheet states that it supports HSP 1.1,
  and HFP 1.5.

  I can pair the device with my krillin, and it properly auto connects (
  note, this seems to work better than my iPhone ).   In-call audio
  works for both incoming and outgoing calls, however I get no ringtone
  in the headset and as mentioned above, I can't answer or terminate the
  call.   I've verified on my iPhone6, that the headset works.  In
  addition to a ringtone in the earpiece, the headset also announces the
  incoming phone number.

  From looking at the ofono debug output, I'm never seeing a new HFP
  connection occur.  I noticed as the upower plugin uses a foreach_atom
  (HFP) style call to update the battery indicators on all attached HFP
  devices.

  I've tested this extensively on krillin, running rc-proposed:

  phablet@ubuntu-phablet:~$ system-image-cli -i
  current build number: 205
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2015-12-16 17:53:19
  version version: 205
  version ubuntu: 20151216
  version device: 20151204-2254a36
  version custom: 2015--36-46-vivid

  I've also tested on mako, rc-proposed ( #317 ).

  For reference here's the versions of bluez, ofono, and PulseAudio on
  the device:

  bluez 5.36-0ubuntu2~overlay1
  ofono  1.17.bzr6908+15.04.20151203-0ubuntu1~awe3
  pulseaudio1:6.0-0ubuntu9.11

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1527354/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1551858] Re: [bluetooth] Connecting to Apple BT keyboard fails due to PIN prompt

[Simon Fels]

@Tony: Can you reproduce this once again and record the HCI packets by
running

 $ sudo btmon -w test.cap

Then attach test.cap here.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1551858

Title:
  [bluetooth] Connecting to Apple BT keyboard fails due to PIN prompt

Status in Canonical System Image:
  New
Status in bluez package in Ubuntu:
  New
Status in ubuntu-system-settings package in Ubuntu:
  New

Bug description:
  Connecting to the latest generation Apple BT keyboard ( the one with
  the USB port & no batteries ) fails on an Ubuntu Touch device, as when
  you press the "Connect" button on the device page, a dialog titled
  "Bluetooth Pairing Request" is displayed, with the following text:

  Please confirm that the PIN displayed on 'Magic Keyboard' matches this
  one: XX

  The dialog has "Cancel" and "Confirm PIN" buttons.

  The keyboard has no display on which a PIN could be displayed.

  When using other devices ( Ubuntu Desktop 15.10, 16.04, Android, OS X,
  ... ) to connect this keyboard all that's necessary is to click/press
  the 'Connect' button in the appropriate place, and the keyboard
  automatically connects, and is usable with no other actions required
  from the user.

  Reproduced on krillin ( rc-proposed/bq-aquris.en/270 ) which has bluez
  5.36-0ubuntu2~overlay1 installed.

  Reproduced on arale ( rc-proposed/meizu.en/258 ) which has bluez 5.37
  installed from silo 39.

  Note, after dismissing the dialog, subsequent attempts to connect may
  not re-display the PIN dialog, instead nothing happens.  I've found
  that this requires power cycling the keyboard to clear and cause the
  PIN dialog to be displayed again.

  [bluetooth]# show
  Controller B8:64:91:48:2B:1E
Name: Aquaris E4.5 Ubuntu Edition
Alias: Aquaris E4.5 Ubuntu Edition
Class: 0x1c020c
Powered: yes
Discoverable: no
Pairable: yes
UUID: Headset AG(1112--1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb)
UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb)
UUID: PnP Information   (1200--1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
UUID: Audio Source  (110a--1000-8000-00805f9b34fb)
UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
UUID: Message Notification Se.. (1133--1000-8000-00805f9b34fb)
UUID: Phonebook Access Server   (112f--1000-8000-00805f9b34fb)
Modalias: usb:v1D6Bp0246d0525
Discovering: no

  [bluetooth]# devices
  Device 18:EE:69:21:6C:D3 18-EE-69-21-6C-D3
  Device DE:76:E2:04:9D:6F BB-9D6F
  Device 7C:D1:C3:1C:B4:03 7C-D1-C3-1C-B4-03
  Device 7C:D1:C3:19:2B:D8 7C-D1-C3-19-2B-D8
  Device 84:38:35:67:0C:3D ubuntu-0
  Device 04:69:F8:C2:A0:09 tony espy’s Keyboard
  Device 00:21:3C:A0:14:A6 Jawbone ERA
  Device 1C:1A:C0:B2:9A:D7 1C-1A-C0-B2-9A-D7

  Device info *before* pairing attempt:

  Device 04:69:F8:C2:A0:09
Name: tony espy’s Keyboard
Alias: tony espy’s Keyboard
Class: 0x002540
Icon: input-keyboard
Paired: no
Trusted: no
Blocked: no
Connected: no
LegacyPairing: no
Modalias: bluetooth:v004Cp0267d0066

  No changes in any of the attributes after *after* the pairing attempt
  ( output of info command is the same ).

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551858/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1551858] Re: [bluetooth] Connecting to Apple BT keyboard fails due to PIN prompt

[Simon Fels]

Just as a additional note: The actual pairing method is selected in the
kernel. See
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/net/bluetooth/smp.c#n859

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1551858

Title:
  [bluetooth] Connecting to Apple BT keyboard fails due to PIN prompt

Status in Canonical System Image:
  New
Status in bluez package in Ubuntu:
  New
Status in ubuntu-system-settings package in Ubuntu:
  New

Bug description:
  Connecting to the latest generation Apple BT keyboard ( the one with
  the USB port & no batteries ) fails on an Ubuntu Touch device, as when
  you press the "Connect" button on the device page, a dialog titled
  "Bluetooth Pairing Request" is displayed, with the following text:

  Please confirm that the PIN displayed on 'Magic Keyboard' matches this
  one: XX

  The dialog has "Cancel" and "Confirm PIN" buttons.

  The keyboard has no display on which a PIN could be displayed.

  When using other devices ( Ubuntu Desktop 15.10, 16.04, Android, OS X,
  ... ) to connect this keyboard all that's necessary is to click/press
  the 'Connect' button in the appropriate place, and the keyboard
  automatically connects, and is usable with no other actions required
  from the user.

  Reproduced on krillin ( rc-proposed/bq-aquris.en/270 ) which has bluez
  5.36-0ubuntu2~overlay1 installed.

  Reproduced on arale ( rc-proposed/meizu.en/258 ) which has bluez 5.37
  installed from silo 39.

  Note, after dismissing the dialog, subsequent attempts to connect may
  not re-display the PIN dialog, instead nothing happens.  I've found
  that this requires power cycling the keyboard to clear and cause the
  PIN dialog to be displayed again.

  [bluetooth]# show
  Controller B8:64:91:48:2B:1E
Name: Aquaris E4.5 Ubuntu Edition
Alias: Aquaris E4.5 Ubuntu Edition
Class: 0x1c020c
Powered: yes
Discoverable: no
Pairable: yes
UUID: Headset AG(1112--1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb)
UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb)
UUID: PnP Information   (1200--1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
UUID: Audio Source  (110a--1000-8000-00805f9b34fb)
UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
UUID: Message Notification Se.. (1133--1000-8000-00805f9b34fb)
UUID: Phonebook Access Server   (112f--1000-8000-00805f9b34fb)
Modalias: usb:v1D6Bp0246d0525
Discovering: no

  [bluetooth]# devices
  Device 18:EE:69:21:6C:D3 18-EE-69-21-6C-D3
  Device DE:76:E2:04:9D:6F BB-9D6F
  Device 7C:D1:C3:1C:B4:03 7C-D1-C3-1C-B4-03
  Device 7C:D1:C3:19:2B:D8 7C-D1-C3-19-2B-D8
  Device 84:38:35:67:0C:3D ubuntu-0
  Device 04:69:F8:C2:A0:09 tony espy’s Keyboard
  Device 00:21:3C:A0:14:A6 Jawbone ERA
  Device 1C:1A:C0:B2:9A:D7 1C-1A-C0-B2-9A-D7

  Device info *before* pairing attempt:

  Device 04:69:F8:C2:A0:09
Name: tony espy’s Keyboard
Alias: tony espy’s Keyboard
Class: 0x002540
Icon: input-keyboard
Paired: no
Trusted: no
Blocked: no
Connected: no
LegacyPairing: no
Modalias: bluetooth:v004Cp0267d0066

  No changes in any of the attributes after *after* the pairing attempt
  ( output of info command is the same ).

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551858/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1551858] Re: [bluetooth] Connecting to Apple BT keyboard fails due to PIN prompt

[Simon Fels]

And there we go:

Mar  7 15:08:44 ubuntu-phablet bluetoothd[890]: src/device.c:new_auth() 
Requesting agent authentication for 04:69:F8:C2:A0:09
Mar  7 15:08:44 ubuntu-phablet bluetoothd[890]: src/agent.c:agent_ref() 
0xb8c78950: ref=3
Mar  7 15:08:44 ubuntu-phablet bluetoothd[890]: 
src/agent.c:agent_request_confirmation() Calling Agent.RequestConfirmation: 
name=:1.119, path=/com/canonical/SettingsBluetoothAgent/adapteragent, 
passkey=800772

I expected bluez to call DisplayPasskey here rather than
RequestConfirmation. So what settings displays is correct (in terms of
what it was asked for).

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1551858

Title:
  [bluetooth] Connecting to Apple BT keyboard fails due to PIN prompt

Status in Canonical System Image:
  New
Status in bluez package in Ubuntu:
  New
Status in ubuntu-system-settings package in Ubuntu:
  New

Bug description:
  Connecting to the latest generation Apple BT keyboard ( the one with
  the USB port & no batteries ) fails on an Ubuntu Touch device, as when
  you press the "Connect" button on the device page, a dialog titled
  "Bluetooth Pairing Request" is displayed, with the following text:

  Please confirm that the PIN displayed on 'Magic Keyboard' matches this
  one: XX

  The dialog has "Cancel" and "Confirm PIN" buttons.

  The keyboard has no display on which a PIN could be displayed.

  When using other devices ( Ubuntu Desktop 15.10, 16.04, Android, OS X,
  ... ) to connect this keyboard all that's necessary is to click/press
  the 'Connect' button in the appropriate place, and the keyboard
  automatically connects, and is usable with no other actions required
  from the user.

  Reproduced on krillin ( rc-proposed/bq-aquris.en/270 ) which has bluez
  5.36-0ubuntu2~overlay1 installed.

  Reproduced on arale ( rc-proposed/meizu.en/258 ) which has bluez 5.37
  installed from silo 39.

  Note, after dismissing the dialog, subsequent attempts to connect may
  not re-display the PIN dialog, instead nothing happens.  I've found
  that this requires power cycling the keyboard to clear and cause the
  PIN dialog to be displayed again.

  [bluetooth]# show
  Controller B8:64:91:48:2B:1E
Name: Aquaris E4.5 Ubuntu Edition
Alias: Aquaris E4.5 Ubuntu Edition
Class: 0x1c020c
Powered: yes
Discoverable: no
Pairable: yes
UUID: Headset AG(1112--1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb)
UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb)
UUID: PnP Information   (1200--1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
UUID: Audio Source  (110a--1000-8000-00805f9b34fb)
UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
UUID: Message Notification Se.. (1133--1000-8000-00805f9b34fb)
UUID: Phonebook Access Server   (112f--1000-8000-00805f9b34fb)
Modalias: usb:v1D6Bp0246d0525
Discovering: no

  [bluetooth]# devices
  Device 18:EE:69:21:6C:D3 18-EE-69-21-6C-D3
  Device DE:76:E2:04:9D:6F BB-9D6F
  Device 7C:D1:C3:1C:B4:03 7C-D1-C3-1C-B4-03
  Device 7C:D1:C3:19:2B:D8 7C-D1-C3-19-2B-D8
  Device 84:38:35:67:0C:3D ubuntu-0
  Device 04:69:F8:C2:A0:09 tony espy’s Keyboard
  Device 00:21:3C:A0:14:A6 Jawbone ERA
  Device 1C:1A:C0:B2:9A:D7 1C-1A-C0-B2-9A-D7

  Device info *before* pairing attempt:

  Device 04:69:F8:C2:A0:09
Name: tony espy’s Keyboard
Alias: tony espy’s Keyboard
Class: 0x002540
Icon: input-keyboard
Paired: no
Trusted: no
Blocked: no
Connected: no
LegacyPairing: no
Modalias: bluetooth:v004Cp0267d0066

  No changes in any of the attributes after *after* the pairing attempt
  ( output of info command is the same ).

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551858/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1551858] Re: [bluetooth] Connecting to Apple BT keyboard fails due to PIN prompt

[Simon Fels]

Because what pairing method is selected is chosen further down the stack
so settings only reacts on what bluez tells it should do. I suspect the
keyboard uses pairing capability KeyboardOnly which then should lead to
passkey entry where the initiator displays and the responder inputs the
PIN (we use KeyboardDisplay) [see Core spec 4.0 page 1968].

However the described dialog on your side is incorrect as it just asks
the user to confirm or cancel which could still be an settings app issue
just displaying the dialog but also an issue down the stack.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1551858

Title:
  [bluetooth] Connecting to Apple BT keyboard fails due to PIN prompt

Status in Canonical System Image:
  New
Status in bluez package in Ubuntu:
  New
Status in ubuntu-system-settings package in Ubuntu:
  New

Bug description:
  Connecting to the latest generation Apple BT keyboard ( the one with
  the USB port & no batteries ) fails on an Ubuntu Touch device, as when
  you press the "Connect" button on the device page, a dialog titled
  "Bluetooth Pairing Request" is displayed, with the following text:

  Please confirm that the PIN displayed on 'Magic Keyboard' matches this
  one: XX

  The dialog has "Cancel" and "Confirm PIN" buttons.

  The keyboard has no display on which a PIN could be displayed.

  When using other devices ( Ubuntu Desktop 15.10, 16.04, Android, OS X,
  ... ) to connect this keyboard all that's necessary is to click/press
  the 'Connect' button in the appropriate place, and the keyboard
  automatically connects, and is usable with no other actions required
  from the user.

  Reproduced on krillin ( rc-proposed/bq-aquris.en/270 ) which has bluez
  5.36-0ubuntu2~overlay1 installed.

  Reproduced on arale ( rc-proposed/meizu.en/258 ) which has bluez 5.37
  installed from silo 39.

  Note, after dismissing the dialog, subsequent attempts to connect may
  not re-display the PIN dialog, instead nothing happens.  I've found
  that this requires power cycling the keyboard to clear and cause the
  PIN dialog to be displayed again.

  [bluetooth]# show
  Controller B8:64:91:48:2B:1E
Name: Aquaris E4.5 Ubuntu Edition
Alias: Aquaris E4.5 Ubuntu Edition
Class: 0x1c020c
Powered: yes
Discoverable: no
Pairable: yes
UUID: Headset AG(1112--1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb)
UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb)
UUID: PnP Information   (1200--1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
UUID: Audio Source  (110a--1000-8000-00805f9b34fb)
UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
UUID: Message Notification Se.. (1133--1000-8000-00805f9b34fb)
UUID: Phonebook Access Server   (112f--1000-8000-00805f9b34fb)
Modalias: usb:v1D6Bp0246d0525
Discovering: no

  [bluetooth]# devices
  Device 18:EE:69:21:6C:D3 18-EE-69-21-6C-D3
  Device DE:76:E2:04:9D:6F BB-9D6F
  Device 7C:D1:C3:1C:B4:03 7C-D1-C3-1C-B4-03
  Device 7C:D1:C3:19:2B:D8 7C-D1-C3-19-2B-D8
  Device 84:38:35:67:0C:3D ubuntu-0
  Device 04:69:F8:C2:A0:09 tony espy’s Keyboard
  Device 00:21:3C:A0:14:A6 Jawbone ERA
  Device 1C:1A:C0:B2:9A:D7 1C-1A-C0-B2-9A-D7

  Device info *before* pairing attempt:

  Device 04:69:F8:C2:A0:09
Name: tony espy’s Keyboard
Alias: tony espy’s Keyboard
Class: 0x002540
Icon: input-keyboard
Paired: no
Trusted: no
Blocked: no
Connected: no
LegacyPairing: no
Modalias: bluetooth:v004Cp0267d0066

  No changes in any of the attributes after *after* the pairing attempt
  ( output of info command is the same ).

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551858/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1552128] Re: Music audio is not transferred to headset after it is connected

[Simon Fels]

** Also affects: pulseaudio (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: bluez (Ubuntu)
   Status: New => Invalid

** Changed in: pulseaudio (Ubuntu)
   Importance: Undecided => Critical

** Changed in: pulseaudio (Ubuntu)
   Status: New => Confirmed

** Also affects: canonical-devices-system-image
   Importance: Undecided
   Status: New

** Changed in: canonical-devices-system-image
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1552128

Title:
  Music audio is not transferred to headset after it is connected

Status in Canonical System Image:
  Confirmed
Status in bluez package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Device and Ubuntu version
  =

  Tested on Krillin [Aquaris E4.5], with BlueZ 5.37

  phablet@ubuntu-phablet:~$ lsb_release -rd
  Description:Ubuntu 15.04
  Release:15.04
  phablet@ubuntu-phablet:~$

  Tested with:
  1. Sony SBH52 headset
  2. Philips SHB5500 headphones

  Description:
  =

  In disconnect state play the music on the phone and do the connection
  (bluetoothctl connect ).

  Audio is not transferred to the BT headset but it still plays on the
  phone instead. On the other hand the bluetoothctl and UI shows that
  the device is connected. The headset blinkenlights indicate that it is
  connected too.

  The audio is properly routed again after the incoming call is made and
  rejected/accepted+terminated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1552128/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1543179] Re: Audio does not get routed to BT headset/speaker

[Simon Fels]

** Also affects: pulseaudio (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: pulseaudio (Ubuntu)
   Status: New => Confirmed

** Changed in: bluez (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: pulseaudio (Ubuntu)
   Importance: Undecided => Critical

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1543179

Title:
  Audio does not get routed to BT headset/speaker

Status in Canonical System Image:
  Confirmed
Status in bluez package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  STEPS:
  1. Flash the latest daily rc-proposed image to a phone
  2. Connect a bluetooth headset to the phone
  3. Connect a speaker to the phone.

  EXPECTED:
  I expect the devices to connect and play audio

  ACTUAL:
  Speakers just connect and instantly disconnect

  Headsets don't get trusted and disconnect instantly, Once you trust it
  and then turn the headset off and back on again it connect can accept
  calls but the audio from both the mic and earpiece don't function.

  Image: 242

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1543179/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1517597] Re: [regression] mouse pointer support on emulator is broken

[Simon Fels]

New release for the android package is in progress now at
https://requests.ci-train.ubuntu.com/#/ticket/1081

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1517597

Title:
  [regression] mouse pointer support on emulator is broken

Status in Client Developer Experience:
  New
Status in Canonical System Image:
  Fix Committed
Status in Mir:
  Fix Committed
Status in Mir 0.18 series:
  Won't Fix
Status in Mir 0.19 series:
  Triaged
Status in Mir 0.20 series:
  Fix Released
Status in android package in Ubuntu:
  In Progress
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  STEPS:
  1. Flash with sudo ubuntu-emulator create --channel ubuntu-touch/rc/ubuntu 
rc-test
  2. Wait for it to build
  3. Run with ubuntu-emulator run rc-test
  4. Starts up but the mouse never moves meaning you can't leave the first page 
of the welcome wizard

  EXPECTED:
  I expect the emulator cursor to follow the mouse cursor and be able to click 
on things

  ACTUAL:
  Emulator cursors stay in the top left preventing movement.

  As noted below F6 toggles the input mode.
  The pointer movement is quite slow and jerky.
  You also can no longer initiate an edge swipe even in trackball mode.

  This is a major regression from how the emulator used to perform.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-developer-experience/+bug/1517597/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1543179] Re: image 242 no audio bt devices connect

[Simon Fels]

@Christopher: You say you connected two BT devices at the same time and
expect audio being played on both?

Can you also please follow https://wiki.ubuntu.com/DebuggingBluetooth
and provide some log files here?

** Description changed:

  STEPS:
  1. Flash the latest daily rc-proposed image to a phone
  2. Connect a bluetooth headset to the phone
  3. Connect a speaker to the phone.
  
  EXPECTED:
  I expect the devices to connect and play audio
  
  ACTUAL:
  Speakers just connect and instantly disconnect
  
  Headsets don't get trusted and disconnect instantly, Once you trust it
  and then turn the headset off and back on again it connect can accept
  calls but the audio from both the mic and earpiece don't function.
+ 
+ Image: 242

** Summary changed:

- image 242 no audio bt devices connect
+ Audio does not get routed to BT headset/speaker

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1543179

Title:
  Audio does not get routed to BT headset/speaker

Status in Canonical System Image:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  STEPS:
  1. Flash the latest daily rc-proposed image to a phone
  2. Connect a bluetooth headset to the phone
  3. Connect a speaker to the phone.

  EXPECTED:
  I expect the devices to connect and play audio

  ACTUAL:
  Speakers just connect and instantly disconnect

  Headsets don't get trusted and disconnect instantly, Once you trust it
  and then turn the headset off and back on again it connect can accept
  calls but the audio from both the mic and earpiece don't function.

  Image: 242

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1543179/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1517597] Re: [regression] mouse pointer support on emulator is broken

[Simon Fels]

** Changed in: android (Ubuntu)
   Status: Confirmed => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1517597

Title:
  [regression] mouse pointer support on emulator is broken

Status in Client Developer Experience:
  New
Status in Canonical System Image:
  Fix Committed
Status in Mir:
  Fix Committed
Status in Mir 0.18 series:
  Won't Fix
Status in Mir 0.19 series:
  Triaged
Status in Mir 0.20 series:
  Fix Released
Status in android package in Ubuntu:
  In Progress
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  STEPS:
  1. Flash with sudo ubuntu-emulator create --channel ubuntu-touch/rc/ubuntu 
rc-test
  2. Wait for it to build
  3. Run with ubuntu-emulator run rc-test
  4. Starts up but the mouse never moves meaning you can't leave the first page 
of the welcome wizard

  EXPECTED:
  I expect the emulator cursor to follow the mouse cursor and be able to click 
on things

  ACTUAL:
  Emulator cursors stay in the top left preventing movement.

  As noted below F6 toggles the input mode.
  The pointer movement is quite slow and jerky.
  You also can no longer initiate an edge swipe even in trackball mode.

  This is a major regression from how the emulator used to perform.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-developer-experience/+bug/1517597/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1531925] Re: Can't connect Logitech Living Room Keyboard [LE]

[Simon Fels]

@Pat: One important thing: Don't use hciconfig up  anymore. Even if
its still there and works to some degree that will only initialize the
controller partly as its using an old kernel API. Use bluetoothctl only
to power on/off bluetooth:

$ bluetoothctl
[bluetooth]# power on
Changing power on succeeded

As in this case you don't see an LE device this comes from the fact that
we power on bluetooth via hciconfig.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1531925

Title:
  Can't connect Logitech Living Room Keyboard [LE]

Status in Canonical System Image:
  New
Status in bluez package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed

Bug description:
  Cannot connect a Logitech Illuminated Living Room keyboard to a device
  running bluez5.  There are two versions of the keyboard, a unifying
  receiver version, and a Bluetooth version.  The latter has a BT symbol
  on the 'del' key.  To put the BT version in pairing mode, power on the
  keyboard, then briefly hold the FN and 'del' key together and release.
  A green LED at the top right of the keyboard should start flashing
  quickly.

  Once in pairing mode, the device will become visible on desktop using
  the BT settings UI, however it's *never* shown in the UI on a device
  running the latest Touch ( OTA9.1+ ).  Note, this includes devices
  running a silo version of bluez 5.37, including both arale and
  krillin.  On both devices, the keyboard *is* viewable using
  bluetoothctl.

  It should be noted that LE keyboard support on touch should be a
  considered a missing feature.

  Here's the reported attributes of the device from my macair running
  15.10 + bluez 5.37:

  Device DF:08:A9:A0:13:93
    Name: K830
    Alias: K830
    Appearance: 0x03c1
    Icon: input-keyboard
    Paired: yes
    Trusted: no
    Blocked: no
    Connected: yes
    LegacyPairing: no
    UUID: Generic Access Profile (1800--1000-8000-00805f9b34fb)
    UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb)
    UUID: Device Information  (180a--1000-8000-00805f9b34fb)
    UUID: Battery Service (180f--1000-8000-00805f9b34fb)
    UUID: Human Interface Device (1812--1000-8000-00805f9b34fb)
    UUID: Vendor specific   (0001--1000-8000-011f246d)
    Modalias: usb:v046DpB335d0010

  From bluetoothctl on both my laptop and my desktop, I'm able to pair,
  trust and connect the device, and info reflects these changes, however
  the device never actually connects, it's LED remains blinking fast,
  and the keyboard cannot be used.

  Note, before pairing, I issued the command 'agent KeyboardOnly' and
  'default-agent'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1531925/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1398193] Re: The bluetooth headset can not control the media playback

[Simon Fels]

Possible related to https://bugs.launchpad.net/ubuntu/+source/indicator-
sound/+bug/1538703

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1398193

Title:
  The bluetooth headset can not control the media playback

Status in Canonical System Image:
  Confirmed
Status in bluez package in Ubuntu:
  In Progress
Status in media-hub package in Ubuntu:
  Invalid
Status in media-hub package in Ubuntu RTM:
  Invalid

Bug description:
  [Preconditions]
  1.The DUT pair with bluetooth headset

  [Procedures]
  1.Play a video using the mediaplayer-app
  2.Play/pause video by bluetooth headset

  [Expect results]
  The bluetooth headset can play/pause video
  [Actual results]
  The bluetooth headset can not control the video playback.

  [Reproduce]
  Always

  Same for audio playback

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1398193/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1545174] Re: can no longer use hands free calling after upgrade to OTA9

[Simon Fels]

@Jamie: Can you follow https://wiki.ubuntu.com/DebuggingBluetooth to
give us some more details about what is happening on your end?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1545174

Title:
  can no longer use hands free calling after upgrade to OTA9

Status in Canonical System Image:
  Confirmed
Status in bluez package in Ubuntu:
  New

Bug description:
  I'm on arale. With OTA8.5 I could pair, listen to music and make calls
  with no problem. After upgrading to OTA9 (and without unpairing/re-
  pairing after upgrading), I can connect to the car, and I can listen
  to music but if I try to make a call while connected to bluetooth, the
  car will after a few moments say "the call has been transferred to the
  phone", but when I pick up the phone to continue the call, the call is
  made (ie, the dialer indicates the call is ongoing and the person I
  called sees an incoming call from me) but there is no sound and the
  other end cannot hear me.

  I have not tried unpairing and re-pairing. In other words, I can no
  longer use hands free calling after upgrading to OTA9. OTA9.1 also
  suffers from this issue.

  I'm not sure if this is related, but after OTA9 I can connect to the
  car and both the phone and the car say they're connected, but then
  after a second or two it disconnects and then after a while 10-30
  seconds, the reconnect and they stay connected. Before, once connected
  they would stay connected.

  I'm not sure this is related to bug #1539158 or not, but I was afraid
  to unpair due to other MX4 users in that bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1545174/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1552371] Re: Bluetooth connection turns on the device

[Simon Fels]

For a mouse and a keyboard this for sure intended. Both act as input
device like the power key and therefore can activate the device. For
example when I have the tablet or the phone working as a converged
device I as a user want the device to go to sleep when I wake up but be
back when I active either one of those input devices (power-button,
mouse or keyboard).

That the device wakes up from a deep-sleep is something we can't prevent
and really shouldn't. If I turn on my paired headset I expect it to be
usable no matter what state the other device is in. So connection
establishment is fine here.

What we should fix is the use of the proximity sensor or other sensors
to find out if the device is in a state where a turned on display is
intended (like it being in your pocket or somewhere else).

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1552371

Title:
  Bluetooth connection turns on the device

Status in Canonical System Image:
  Confirmed
Status in bluez package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  I have been noticing my phone and tablet occasionally turning on without 
interaction. Several times with my phone in my pocket I found it in the 
emergency call UI
  I also see the tablet display turn on while lying idle on the desk.

  I have reproduced one case such that turning on a BT device (headset)
  causes the phone to light up and display the volume slider. Similarly
  turning on the BT keyboard while the tablet screen is off caused the
  display to turn on.These may be as intended.

  I suspect other BT events can similarly resume the device and/or turn on the 
display if it happens to be awake due to the 5 min polling timer.
  The proximity sensor is also not honored when this happens, if its covered 
the screen still comes on.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1552371/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1531925] Re: Can't connect Logitech Living Room Keyboard [LE]

[Simon Fels]

@Pat: Did you saved any logs from that attempt?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1531925

Title:
  Can't connect Logitech Living Room Keyboard [LE]

Status in Canonical System Image:
  New
Status in bluez package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  New

Bug description:
  Cannot connect a Logitech Illuminated Living Room keyboard to a device
  running bluez5.  There are two versions of the keyboard, a unifying
  receiver version, and a Bluetooth version.  The latter has a BT symbol
  on the 'del' key.  To put the BT version in pairing mode, power on the
  keyboard, then briefly hold the FN and 'del' key together and release.
  A green LED at the top right of the keyboard should start flashing
  quickly.

  Once in pairing mode, the device will become visible on desktop using
  the BT settings UI, however it's *never* shown in the UI on a device
  running the latest Touch ( OTA9.1+ ).  Note, this includes devices
  running a silo version of bluez 5.37, including both arale and
  krillin.  On both devices, the keyboard *is* viewable using
  bluetoothctl.

  It should be noted that LE keyboard support on touch should be a
  considered a missing feature.

  Here's the reported attributes of the device from my macair running
  15.10 + bluez 5.37:

  Device DF:08:A9:A0:13:93
    Name: K830
    Alias: K830
    Appearance: 0x03c1
    Icon: input-keyboard
    Paired: yes
    Trusted: no
    Blocked: no
    Connected: yes
    LegacyPairing: no
    UUID: Generic Access Profile (1800--1000-8000-00805f9b34fb)
    UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb)
    UUID: Device Information  (180a--1000-8000-00805f9b34fb)
    UUID: Battery Service (180f--1000-8000-00805f9b34fb)
    UUID: Human Interface Device (1812--1000-8000-00805f9b34fb)
    UUID: Vendor specific   (0001--1000-8000-011f246d)
    Modalias: usb:v046DpB335d0010

  From bluetoothctl on both my laptop and my desktop, I'm able to pair,
  trust and connect the device, and info reflects these changes, however
  the device never actually connects, it's LED remains blinking fast,
  and the keyboard cannot be used.

  Note, before pairing, I issued the command 'agent KeyboardOnly' and
  'default-agent'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1531925/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp