[Desktop-packages] [Bug 1597681] Re: [CTA] Enable WAPI support

[John McAleely]

** Changed in: canonical-devices-system-image
 Assignee: John McAleely (john.mcaleely) => (unassigned)

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

Title:
  [CTA] Enable WAPI support

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

Bug description:
  The phone does not currently support WAPI [1]

  It should do so. As part of this, support for the SMS4 [2] cipher is
  also required.

  
  [1] 
https://en.wikipedia.org/wiki/WLAN_Authentication_and_Privacy_Infrastructure
  [2]: https://en.wikipedia.org/wiki/SMS4

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

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

[Desktop-packages] [Bug 1505213] Re: Multiple bluetooth audio devices break audio routing

[John McAleely]

** Changed in: canonical-devices-system-image
 Assignee: John McAleely (john.mcaleely) => (unassigned)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1505213

Title:
  Multiple bluetooth audio devices break audio routing

Status in Canonical System Image:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed
Status in telepathy-ofono package in Ubuntu:
  Confirmed

Bug description:
  When connecting multiple bluetooth audio devices the audio routing
  doesn't behave as it should.

  When multiple devices are connected which support A2DP for example we
  have to

  * Pick one which becomes the active one
  * When the active one disappears (disconnected, out-of-range) we need to pick 
the next one and set it as the active

  Right now the result is not constant when connecting multiple devices:

  * bluez and PA (mainly PA) try to setup all devices not respecting if one is 
already active
  * when disconnecting the active one the previously not-active one doesn't 
become active and stays unused

  Also we need to check if telepathy-ofono takes always the right audio
  card from PA to setup the audio routing for voicecalls.

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

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

[Desktop-packages] [Bug 1430769] Re: Does not detect hidden WiFi on first attempt

[John McAleely]

** Changed in: canonical-devices-system-image
 Assignee: John McAleely (john.mcaleely) => (unassigned)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to wpasupplicant in Ubuntu.
https://bugs.launchpad.net/bugs/1430769

Title:
  Does not detect hidden WiFi on first attempt

Status in Canonical System Image:
  Confirmed
Status in indicator-network package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Invalid
Status in wpasupplicant package in Ubuntu:
  Confirmed

Bug description:
  The WiFi network I use at home is a hidden one. While it works with my
  Ubuntu Phone, I always have to toggle WiFi on and off about 3 times
  until it is detected.

  phablet@ubuntu-phablet:~$ system-image-cli --info
  current build number: 129
  device name: mako
  channel: ubuntu-touch/devel-proposed
  alias: ubuntu-touch/vivid-proposed
  last update: 2015-03-11 13:19:54
  version version: 129
  version ubuntu: 20150310.3
  version device: 20150210
  version custom: 20150310.3

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

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

[Desktop-packages] [Bug 1506340] Re: Multimedia audio is routed for half of a second through HFP SCO after call has ended

[John McAleely]

** Changed in: canonical-devices-system-image
 Assignee: John McAleely (john.mcaleely) => (unassigned)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1506340

Title:
  Multimedia audio is routed for half of a second through HFP SCO after
  call has ended

Status in Canonical System Image:
  Confirmed
Status in bluez package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New
Status in telepathy-ofono package in Ubuntu:
  New

Bug description:
  When playing audio through A2DP and a call comes in, gets accepted and
  finishes after some time the multimedia audio will start again after
  the call but is played for half of a second either through the phone
  speaker or HFP SCO channel rather than only being played again through
  A2DP as it was before the call.

  This happens with BlueZ 4.x and 5.x and is related to how we handle
  the audio routing setup currently.

  The telepathy-ofono service currently switches the different ports,
  sinks, sources and profiles of our PulseAudio elements to enable
  everything needed to do a voicecall and to switch things back
  correctly once the voicecall is done. The issue described above is the
  result of either a incorrect sequence of enabling/disbling things or
  bound to timing issues when the switching is done.

  We need to do some more analysis on the routing in PulseAudio and how
  telepathy-ofono does things.

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

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

[Desktop-packages] [Bug 1580146] Re: [touch] Internet connection stops working while WiFi is still connected

[John McAleely]

** Changed in: canonical-devices-system-image
 Assignee: John McAleely (john.mcaleely) => (unassigned)

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

Title:
  [touch] Internet connection stops working while WiFi is still
  connected

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

Bug description:
  krillin, rc-proposed, r329

  Description:
  It often happens that the internet connection stops working while the device 
is still connected to a (working) WiFi AP.
  The indicator shows that the phone is connected to the AP, here's the ouput 
of "nmcli d" and "nmcli c" http://pastebin.ubuntu.com/16344985/

  Tapping on the AP in the network indicator resets the connection and
  fixes the issue, which however reappears after a while.

  Here's also a "grep NetworkManager" from syslog
  http://pastebin.ubuntu.com/16344990/

  How to reproduce:
  I don't have a recipe, but here's what usually happens on my phone
  1) I connect to the office WiFi (Canonical's HQ, BlueFin office)
  2) Use browser, perform random google searches to check internet is working
  3) After a while (sometimes I put the phone to sleep, sometimes I checked the 
Updates from system settings a few times), I go back to the browser, and it 
starts returning "Network Error". NM, as you can see from the logs, says WiFi 
is "connected"
  4) At this point I use Terminal app and discover that "ping 8.8.8.8" is 
working correctly, "ping google.com" immediately returns "unkown host", i.e. it 
doesn't seem to be waiting for a timeout, it returns pretty fast.

  There are no related crash files in /var/crash

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

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

[Desktop-packages] [Bug 1579389] Re: wireless keeps freezing

[John McAleely]

** Changed in: canonical-devices-system-image
 Assignee: John McAleely (john.mcaleely) => (unassigned)

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

Title:
  wireless keeps freezing

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

Bug description:
  Hi there,

  After i did update my ubuntu to OTA 10.1 on my bq 4.5, my wireless
  began to freeze everytime the phone idles, it doesn't matter if i am
  home or at work or in a cafe, everytime the phone is doing nothing the
  wireless stop working, So i have to turn it off and then on and
  everything works fine till the phone idles again.

  I have asked on IRC and i was informed to come here report a bug. If
  you guys want me to send you files or anything just give me the
  commands i need to type in my terminal or what files i need to send to
  here.

  Regards,

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

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

[Desktop-packages] [Bug 1579549] Re: Music stops playing from main speaker when a call comes in

[John McAleely]

** Changed in: canonical-devices-system-image
 Assignee: John McAleely (john.mcaleely) => (unassigned)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1579549

Title:
  Music stops playing from main speaker when a call comes in

Status in Canonical System Image:
  Confirmed
Status in Ubuntu Music App:
  New
Status in media-hub package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Confirmed
Status in media-hub package in Ubuntu RTM:
  Invalid
Status in pulseaudio package in Ubuntu RTM:
  Confirmed

Bug description:
  1. Start some music playback from the music-app
  2. It is ok with SMS notification and sound but whenever a call comes music 
stops playing during call but after the call is disconnected music resumes 
playing in low volume and i turned the volume to full and still the sound is 
low and then i noticed that music stopped playing from the phone's loud speaker 
instead it is playing from top talking speaker (my nexus 4).
  3. To resolve this issue i've to close and re open music app which is very 
frustrating.

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

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

[Desktop-packages] [Bug 1230391] Re: please provide visual cue during background recording

[John McAleely]

** Changed in: canonical-devices-system-image
 Assignee: John McAleely (john.mcaleely) => (unassigned)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1230391

Title:
  please provide visual cue during background recording

Status in Canonical System Image:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Confirmed
Status in qtubuntu-camera package in Ubuntu:
  Confirmed

Bug description:
  After bug #1224756 is fixed, we should provide a visual cue for when
  an app moves to the background and is recording audio. This will allow
  an app like Skype to work normally in the foreground, but if the user
  launches another app into the foreground, the user is able to see that
  he/she is still on the Skype call. In addition to the usability
  benefit, this provides a security benefit because it stops
  eavesdropping because the user will have a visual cue that the
  malicious/misbehaving app is recording audio.

  This needs design.

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

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

[Desktop-packages] [Bug 1407928] Re: [phone] Does not auto-switch to available, known WiFi

[John McAleely]

** Changed in: canonical-devices-system-image
 Assignee: John McAleely (john.mcaleely) => (unassigned)

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

Title:
  [phone] Does not auto-switch to available, known WiFi

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

Bug description:
  This might not be the place for this bug, please reassign as
  appropriate.

  I was only able to reproduce this on mako/rtm, krillin/vivid seems to
  behave better (but I do remember the same issue there).

  Steps:
  * connect to a password-protected WiFi network
  * go out of range
  * make sure a GSM connection is established
  * go back in the WiFi range

  Expected:
  * phone connects to the known WiFi automatically

  Current:
  * phone does not connect to WiFi

  Please find attached network-test-session logs from when I toggled
  WiFi and Plane mode to get some data on the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu RTM 14.09
  Package: indicator-network 0.5.1+15.04.20141215~rtm-0ubuntu1
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: armhf
  Date: Tue Jan  6 12:01:55 2015
  InstallationDate: Installed on 2014-12-18 (18 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20141218-163635)
  SourcePackage: indicator-network
  UpgradeStatus: No upgrade log present (probably fresh install)
  indicator-network.log:
   Attempted to unregister path (path[0] = org path[1] = freedesktop) which 
isn't registered
   Attempted to unregister path (path[0] = org path[1] = freedesktop) which 
isn't registered
  upstart.indicator-network.log:
   Attempted to unregister path (path[0] = org path[1] = freedesktop) which 
isn't registered
   Attempted to unregister path (path[0] = org path[1] = freedesktop) which 
isn't registered

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

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

[Desktop-packages] [Bug 1543179] Re: Audio does not get routed to BT headset/speaker

[John McAleely]

** Changed in: canonical-devices-system-image
 Assignee: John McAleely (john.mcaleely) => (unassigned)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1543179

Title:
  Audio does not get routed to BT headset/speaker

Status in Canonical System Image:
  In Progress
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

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

[John McAleely]

** Changed in: canonical-devices-system-image
 Assignee: John McAleely (john.mcaleely) => (unassigned)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio 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:
  Confirmed
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1590844] Re: Call with Bluetooth headset not working [Meizu Pro 5 Ubuntu Edition]

[John McAleely]

** Changed in: canonical-devices-system-image
 Assignee: John McAleely (john.mcaleely) => (unassigned)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1590844

Title:
  Call with Bluetooth headset not working [Meizu Pro 5 Ubuntu Edition]

Status in Canonical System Image:
  Confirmed
Status in turbo:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed
Status in telephony-service package in Ubuntu:
  Confirmed

Bug description:
  My bluetooth headset perfectly connects to my Meizu Pro 5. However,
  the sound quality is so poor (a lot of noise) such that you don't
  understand your communication partner. Note that the headset works
  perfectly together with Ubuntu on my Nexus 4.

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

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

[Desktop-packages] [Bug 1434832] Re: Add sound enhancements such as equaliser or normalisation

[John McAleely]

** Changed in: canonical-devices-system-image
 Assignee: John McAleely (john.mcaleely) => (unassigned)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1434832

Title:
  Add sound enhancements such as equaliser or normalisation

Status in Canonical System Image:
  Confirmed
Status in Ubuntu Music App:
  Triaged
Status in pulseaudio package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu RTM:
  New

Bug description:
  Hi there! o/

  After using this app since two days, i really like it. Some other bugs
  i had have already been mentioned.

  At the moment, i am having problems listening to music through my
  headphones:

  The volume is not loud enough for older tracks. I am talking about
  albums from the 70s/60s/80s, which were not effected by the "loudness
  war". Nowadays, the albums are mixed pretty loud, screw dynamic! :D

  However, it would be nice to have a menu option to activate/deactivate
  the volume limits. Maybe it can be included into the equalizer, which
  might be inplented some day in the app?

  Thank you in advance!

  Cheers,
  Kurisu

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

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

[Desktop-packages] [Bug 1493722] Re: [Media services] Volume up/down long press should skip to next/previous track

[John McAleely]

** Changed in: canonical-devices-system-image
 Assignee: John McAleely (john.mcaleely) => (unassigned)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1493722

Title:
  [Media services] Volume up/down long press should skip to
  next/previous track

Status in Canonical System Image:
  Confirmed
Status in Media Hub:
  Invalid
Status in Ubuntu Music App:
  New
Status in Ubuntu UX:
  Triaged
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  A handy feature of music players is the ability to quickly skip tracks
  by long-pressing the volume buttons. This allows users to control
  their music without having to take the device out of their pocket,
  turn its screen on, unlock it, go to the music app and press "Next".

  As of now, when I long press the volume button, it rapidly increases
  the volume, which is not very nice to my ears ;-)

  Is it possible to control the music app this way on Ubuntu phone?

  Music app version tested: 2.2.910 (2015-09-03)
  Device: Meizu MX 4
  System info: Ubuntu 15.04 (r4)

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

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

[Desktop-packages] [Bug 1443244] Re: [touch] small cracking sound when changing volume

[John McAleely]

** Changed in: canonical-devices-system-image
 Assignee: John McAleely (john.mcaleely) => (unassigned)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1443244

Title:
  [touch] small cracking sound when changing volume

Status in Canonical System Image:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  phablet@ubuntu-phablet:~$ system-image-cli -i
  current build number: 169
  device name: mako
  channel: ubuntu-touch/devel-proposed
  alias: ubuntu-touch/vivid-proposed
  last update: 2015-04-12 20:38:14
  version version: 169
  version ubuntu: 20150412
  version device: 20150210
  version custom: 20150412

  Just change the volume quickly when playing a sound, and you can hear
  really small cracking sounds as the volume increases/decreases. This
  is even more noticeable with Pathwind's (touch game) soundtrack.

  Not critical for the user experience but can be a bit annoying.

  Remember that here pulse is only changing the volume for the
  multimedia role itself (or any other active role used when reproducing
  the bug). Not really touching the hardware.

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

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

[Desktop-packages] [Bug 1521288] Re: Having a TV connected via SlimPort/HDMI does not route sound to it

[John McAleely]

** Changed in: canonical-devices-system-image
 Assignee: John McAleely (john.mcaleely) => (unassigned)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1521288

Title:
  Having a TV connected via SlimPort/HDMI does not route sound to it

Status in Canonical System Image:
  Confirmed
Status in Canonical Pocket Desktop:
  New
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  While a TV is connected to the phone via SlimPort/HDMI, audio should
  be routed to the TV.

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

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

[Desktop-packages] [Bug 1587305] Re: Add support for USB-LAN adapter

[John McAleely]

** Changed in: canonical-devices-system-image
 Assignee: John McAleely (john.mcaleely) => (unassigned)

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

Title:
  Add support for USB-LAN adapter

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

Bug description:
  Some users contacted BQ because the USB-LAN adapters they own are not
  recognized by Frieza. They expect the device to automatically
  config/connect to their LAN network. They want the tablet to behave
  the same way as a Ubuntu PC does when LAN/Wi-Fi network is
  connected/disconnected. (I think they should be able to set the
  network through nmcli)

  Product: bq Aquaris E4.5, E5 & M10
  FW version: OTA-10.1
  HW version: MP

  STEPS TO REPRO:
  1. Connect DUT>USB-OTG>USB-LAN adapter>Rj45(picture attached)

  Actual Result:
  USB-LAN adapter is not recognized or it does not auto-connect to home LAN

  Expected Result:
  Whether Wifi is on or off, once LAN adapter is connected, it should 
auto-connect to home LAN

  Additional info: here is the link provided by one of the users
  http://de.anker.com/product/A7522012

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

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

[Desktop-packages] [Bug 1502330] Re: bluetooth - GPS navigator - pairing trouble

[John McAleely]

** Also affects: location-service (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: canonical-devices-system-image
 Assignee: John McAleely (john.mcaleely) => (unassigned)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to location-service in Ubuntu.
https://bugs.launchpad.net/bugs/1502330

Title:
  bluetooth - GPS navigator - pairing trouble

Status in Canonical System Image:
  Confirmed
Status in location-service package in Ubuntu:
  New
Status in ubuntu-system-settings package in Ubuntu:
  New

Bug description:
  morning,

  i have trouble with an aquaris BQ 4.5 (krilin01a-
  s15a_bq_l100en_2025_150825) paring a GPS NAVIGATOR IV.

  the 1rst pairing is ok (the request use a key i have to enter into bq
  phone : the timing is very short but i can pairing GPS end BQ phone),
  all is ok, icant consult contact from the GPS, the GPS permit me to
  handle incoming call, ...)

  the trouble come in when on of those device is poweroff (most of the
  time the GPS), when the GPS come back online the automatique pairing
  does not work, and if i try on both device to force a manual pairing
  it does not work !!

  i have to remove device on the 2 devices then re run a manual pairing
  with key exchange 

  this is a very cripping behaviour.

  here are logs files.

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

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

[Desktop-packages] [Bug 1578673] Re: [Touch] Volume level is not maintained per output device

[John McAleely]

** Also affects: ubuntu-ux
   Importance: Undecided
   Status: New

** Changed in: canonical-devices-system-image
   Importance: High => Wishlist

** Changed in: canonical-devices-system-image
 Assignee: John McAleely (john.mcaleely) => (unassigned)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1578673

Title:
  [Touch] Volume level is not maintained per output device

Status in Canonical System Image:
  Confirmed
Status in Ubuntu UX:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  If I'm not mistaken this issue was not present before OTA-10. I
  usually like to keep the volume at around 80% on speaker and around
  50% on earphones. Previously the device used to remember these choices
  and adjust them accordingly. But now it only remembers the previously
  set volume level and hence I have to adjust manually all the time
  while switching output devices.

  Device: bq E5, OTA-10.1

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

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

[Desktop-packages] [Bug 1591935] Re: [CTA] audio record works for call audio

[John McAleely]

** Changed in: canonical-devices-system-image
 Assignee: John McAleely (john.mcaleely) => (unassigned)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1591935

Title:
  [CTA] audio record works for call audio

Status in Canonical System Image:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed
Status in trust-store package in Ubuntu:
  Confirmed

Bug description:
  krillin:ubuntu-touch/rc-proposed/bq-aquaris.en,#350

  Install the app 'Recorder' from the Ubuntu Store.

  Confirm it works by opening and making a recording. Note that the app
  requests permission to access the microphone, and you grant this with
  the usual trust store prompt.

  Now move to the phone app, and place a regular phone call. With the
  call active, open Recorder again, and start recording.

  Stop recording after some time, and hang up the call.

  return to the recorder app, and play the recording made during the
  phone call. Audio from both the local microphone and the remote
  handset (Which the user heard during the call) will be present on the
  track.

  It was expected that no audio from the call could be captured by
  applications.

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

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

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

[John McAleely]

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

** Changed in: canonical-devices-system-image
Milestone: None => 13

-- 
You received this bug notification because you are a member of Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

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

[John McAleely]

** Changed in: canonical-devices-system-image
   Importance: Undecided => High

-- 
You received this bug notification because you are a member of Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

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

[John McAleely]

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => John McAleely (john.mcaleely)

-- 
You received this bug notification because you are a member of Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1574729] Re: Audio/Video not in sync on M10/frieza

[John McAleely]

** Changed in: avila
 Assignee: (unassigned) => Alfonso Sanchez-Beato (alfonsosanchezbeato)

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

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

** Changed in: avila
Milestone: None => 13

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1574729

Title:
  Audio/Video not in sync on M10/frieza

Status in The Avila project:
  Confirmed
Status in Canonical System Image:
  Confirmed
Status in frieza:
  Confirmed
Status in media-hub package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Watching a video (either with the media player or the browser) shows a
  lag between audio and video. It's out of sync for some hundred
  milliseconds, just enough to be very annoying while watching the
  video.

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

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

Re: [Desktop-packages] [Bug 1607684] Re: wifi networks not remembered correctly (ubuntu touch, bq M10)

[John McAleely]

I am not certain, but I believe it is labelled 'nvram'. Describing the
problem in terms of using format & download should be sufficient. BQ
support are aware of the problems the tool has.

On 2 August 2016 at 11:38, Samuel Walladge 
wrote:

> Ok.
>
> "You will have lost your S/N, MAC addresses, and some key
> material the HDMI software expects to find (but does not use)."
>
> What partition(s) keep that data?
> (Asking because I'm trying to gather data for discussing with BQ.)
>
> --
> You received this bug notification because you are a bug assignee.
> https://bugs.launchpad.net/bugs/1607684
>
> Title:
>   wifi networks not remembered correctly (ubuntu touch, bq M10)
>
> Status in Canonical System Image:
>   Incomplete
> Status in network-manager package in Ubuntu:
>   New
>
> Bug description:
>   I have a M10, on ubuntu touch OTA-12 (and same issue previously on
>   OTA-11).
>
>   The issue is that it doesn't remember wifi networks properly. To
>   explain:
>
>   1. turn on tablet
>   2. select my wifi network from the list
>   3. enter password and click connect
>   4. reboot device
>   5. select my wifi network from the list
>   6. enter password and click connect
>   .
>   .
>   .
>   30. go to wifi settings -> previous networks
>   31. view long list that looks like:
>
>   MyWifinetwork1
>   MyWifinetwork2
>   MyWifinetwork3
>   MyWifinetwork4
>   ...
>
>   What it should do (and did some time ago), is see that MyWifinetwork
>   was saved in previous networks and automatically connect using the
>   saved password/settings.
>
>   So, I'm wondering is this a bug, something badly configured in my wifi
>   network (although other devices remember it fine), or something else?
>
>   Thanks.
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/canonical-devices-system-image/+bug/1607684/+subscriptions
>

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

Title:
  wifi networks not remembered correctly (ubuntu touch, bq M10)

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

Bug description:
  I have a M10, on ubuntu touch OTA-12 (and same issue previously on
  OTA-11).

  The issue is that it doesn't remember wifi networks properly. To
  explain:

  1. turn on tablet
  2. select my wifi network from the list
  3. enter password and click connect
  4. reboot device
  5. select my wifi network from the list
  6. enter password and click connect
  .
  .
  .
  30. go to wifi settings -> previous networks
  31. view long list that looks like:

  MyWifinetwork1
  MyWifinetwork2
  MyWifinetwork3
  MyWifinetwork4
  ...

  What it should do (and did some time ago), is see that MyWifinetwork
  was saved in previous networks and automatically connect using the
  saved password/settings.

  So, I'm wondering is this a bug, something badly configured in my wifi
  network (although other devices remember it fine), or something else?

  Thanks.

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

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

Re: [Desktop-packages] [Bug 1607684] Re: wifi networks not remembered correctly (ubuntu touch, bq M10)

[John McAleely]

I think so, yes. There are a number of ways that tool can be used to brick
devices.

That is why we try to only document ubuntu-device-flash, which knows to
keep clear of these pitfalls.

Note that your tablet never had an IMEI - that's a phone thing.

On 2 August 2016 at 02:16, Samuel Walladge 
wrote:

> Ouch. What a way to learn about imei...
>
> Is this then a fault with the flash tool I used? (I mean an official
> tool from the manufacturer isn't supposed to destroy the device...)
>
> --
> You received this bug notification because you are a bug assignee.
> https://bugs.launchpad.net/bugs/1607684
>
> Title:
>   wifi networks not remembered correctly (ubuntu touch, bq M10)
>
> Status in Canonical System Image:
>   Incomplete
> Status in network-manager package in Ubuntu:
>   New
>
> Bug description:
>   I have a M10, on ubuntu touch OTA-12 (and same issue previously on
>   OTA-11).
>
>   The issue is that it doesn't remember wifi networks properly. To
>   explain:
>
>   1. turn on tablet
>   2. select my wifi network from the list
>   3. enter password and click connect
>   4. reboot device
>   5. select my wifi network from the list
>   6. enter password and click connect
>   .
>   .
>   .
>   30. go to wifi settings -> previous networks
>   31. view long list that looks like:
>
>   MyWifinetwork1
>   MyWifinetwork2
>   MyWifinetwork3
>   MyWifinetwork4
>   ...
>
>   What it should do (and did some time ago), is see that MyWifinetwork
>   was saved in previous networks and automatically connect using the
>   saved password/settings.
>
>   So, I'm wondering is this a bug, something badly configured in my wifi
>   network (although other devices remember it fine), or something else?
>
>   Thanks.
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/canonical-devices-system-image/+bug/1607684/+subscriptions
>

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

Title:
  wifi networks not remembered correctly (ubuntu touch, bq M10)

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

Bug description:
  I have a M10, on ubuntu touch OTA-12 (and same issue previously on
  OTA-11).

  The issue is that it doesn't remember wifi networks properly. To
  explain:

  1. turn on tablet
  2. select my wifi network from the list
  3. enter password and click connect
  4. reboot device
  5. select my wifi network from the list
  6. enter password and click connect
  .
  .
  .
  30. go to wifi settings -> previous networks
  31. view long list that looks like:

  MyWifinetwork1
  MyWifinetwork2
  MyWifinetwork3
  MyWifinetwork4
  ...

  What it should do (and did some time ago), is see that MyWifinetwork
  was saved in previous networks and automatically connect using the
  saved password/settings.

  So, I'm wondering is this a bug, something badly configured in my wifi
  network (although other devices remember it fine), or something else?

  Thanks.

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

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

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

[John McAleely]

Is this the bug I saw last week? bug #1607466

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio 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:
  Confirmed
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Re: [Desktop-packages] [Bug 1607684] Re: wifi networks not remembered correctly (ubuntu touch, bq M10)

[John McAleely]

So, your symptoms are unfortunately perfectly explained by wiping with
format & download. You will have lost your S/N, MAC addresses, and some key
material the HDMI software expects to find (but does not use).

When your MAC addresses are wiped, the system will generate fresh ones
every boot, which explains why the wifi association is forgotten &
recreated. There are other ways the system can forget wifi (which are
bugs), but losing the hard coded MAC addresses does explain this one.

You are correct to observe that there are other bugs (both for wifi and
HDMI interoperability).

On 30 July 2016 at 00:48, Samuel Walladge 
wrote:

> Also, probably related, I just discovered through an irc conversation on
> #ubuntu-touch (thanks Mister_Q) that using the bq flash tool (which I did
> to fix an unbootable
> system) and selecting 'format and download' (which I also did), would have
> deleted the imei partition.
>
> Quite possible, seeing as the serial number displayed in the 'about'
> section
> shows "0123456789ABCDEF".
>
> Apparently it could also cause my other problem of the tablet not
> recognizing
> or outputting to HDMI monitors via a micro-hdmi to hdmi cable.
>
> Although... that doesn't explain why the wifi problem has been seen
> before, or
> why there's plenty of other reports of the M10 not outputting to displays
> (at
> least not reliably). - see
>
> http://askubuntu.com/questions/762148/bq-m10-ubuntu-touch-micro-hdmi-not-outputting-to-tv
> for example.
>
> --
> You received this bug notification because you are a bug assignee.
> https://bugs.launchpad.net/bugs/1607684
>
> Title:
>   wifi networks not remembered correctly (ubuntu touch, bq M10)
>
> Status in Canonical System Image:
>   Incomplete
> Status in network-manager package in Ubuntu:
>   New
>
> Bug description:
>   I have a M10, on ubuntu touch OTA-12 (and same issue previously on
>   OTA-11).
>
>   The issue is that it doesn't remember wifi networks properly. To
>   explain:
>
>   1. turn on tablet
>   2. select my wifi network from the list
>   3. enter password and click connect
>   4. reboot device
>   5. select my wifi network from the list
>   6. enter password and click connect
>   .
>   .
>   .
>   30. go to wifi settings -> previous networks
>   31. view long list that looks like:
>
>   MyWifinetwork1
>   MyWifinetwork2
>   MyWifinetwork3
>   MyWifinetwork4
>   ...
>
>   What it should do (and did some time ago), is see that MyWifinetwork
>   was saved in previous networks and automatically connect using the
>   saved password/settings.
>
>   So, I'm wondering is this a bug, something badly configured in my wifi
>   network (although other devices remember it fine), or something else?
>
>   Thanks.
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/canonical-devices-system-image/+bug/1607684/+subscriptions
>

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

Title:
  wifi networks not remembered correctly (ubuntu touch, bq M10)

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

Bug description:
  I have a M10, on ubuntu touch OTA-12 (and same issue previously on
  OTA-11).

  The issue is that it doesn't remember wifi networks properly. To
  explain:

  1. turn on tablet
  2. select my wifi network from the list
  3. enter password and click connect
  4. reboot device
  5. select my wifi network from the list
  6. enter password and click connect
  .
  .
  .
  30. go to wifi settings -> previous networks
  31. view long list that looks like:

  MyWifinetwork1
  MyWifinetwork2
  MyWifinetwork3
  MyWifinetwork4
  ...

  What it should do (and did some time ago), is see that MyWifinetwork
  was saved in previous networks and automatically connect using the
  saved password/settings.

  So, I'm wondering is this a bug, something badly configured in my wifi
  network (although other devices remember it fine), or something else?

  Thanks.

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

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

[Desktop-packages] [Bug 1607466] Re: Mono BT headset has no in-call audio on recent rc-proposed

[John McAleely]

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1607466

Title:
  Mono BT headset has no in-call audio on recent rc-proposed

Status in Canonical System Image:
  Incomplete
Status in bluez package in Ubuntu:
  New
Status in phone-app package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  MX4/arale
  ubuntu-touch/rc-proposed/meizu.en #387

  Flash phone with --bootstrap, and walk through the welcome wizard.
  Once you have a phone to use, visit the BT settings, and pair a mono
  'HSP' headset. In my case an old Jabra OTE-1.

  Once the device is paired, make an incoming call to the handset. Use
  the headset button to answer the call.

  The handset transitions to showing you an in-call UI, and appears to
  claim the audio is routed to the headset.

  I heard no audio.

  Expected: Audio was heard on the headset during the call.

  Note that this does not occur on rc-proposed/meizu.en #381, so it
  seems to be a recent regression.

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

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

[Desktop-packages] [Bug 1607466] Re: Mono BT headset has no in-call audio on recent rc-proposed

[John McAleely]

I have tried to reproduce on both 387 & 389. I have been unable to,
using the same equipment as last night.

I did not enable logging, so it does not seem to be the presence of
extra logging that stops reproduction.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1607466

Title:
  Mono BT headset has no in-call audio on recent rc-proposed

Status in Canonical System Image:
  New
Status in bluez package in Ubuntu:
  New
Status in phone-app package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  MX4/arale
  ubuntu-touch/rc-proposed/meizu.en #387

  Flash phone with --bootstrap, and walk through the welcome wizard.
  Once you have a phone to use, visit the BT settings, and pair a mono
  'HSP' headset. In my case an old Jabra OTE-1.

  Once the device is paired, make an incoming call to the handset. Use
  the headset button to answer the call.

  The handset transitions to showing you an in-call UI, and appears to
  claim the audio is routed to the headset.

  I heard no audio.

  Expected: Audio was heard on the headset during the call.

  Note that this does not occur on rc-proposed/meizu.en #381, so it
  seems to be a recent regression.

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

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

[Desktop-packages] [Bug 1607466] Re: Mono BT headset has no in-call audio on recent rc-proposed

[John McAleely]

Here's a set of logs from #381, where the bug does not reproduce.

** Attachment added: "working.tgz"
   
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1607466/+attachment/4709413/+files/working.tgz

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1607466

Title:
  Mono BT headset has no in-call audio on recent rc-proposed

Status in Canonical System Image:
  New
Status in bluez package in Ubuntu:
  New
Status in phone-app package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  MX4/arale
  ubuntu-touch/rc-proposed/meizu.en #387

  Flash phone with --bootstrap, and walk through the welcome wizard.
  Once you have a phone to use, visit the BT settings, and pair a mono
  'HSP' headset. In my case an old Jabra OTE-1.

  Once the device is paired, make an incoming call to the handset. Use
  the headset button to answer the call.

  The handset transitions to showing you an in-call UI, and appears to
  claim the audio is routed to the headset.

  I heard no audio.

  Expected: Audio was heard on the headset during the call.

  Note that this does not occur on rc-proposed/meizu.en #381, so it
  seems to be a recent regression.

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

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

[Desktop-packages] [Bug 1607466] Re: Mono BT headset has no in-call audio on recent rc-proposed

[John McAleely]

** Description changed:

  MX4/arale
  ubuntu-touch/rc-proposed/meizu.en #387
  
  Flash phone with --bootstrap, and walk through the welcome wizard. Once
  you have a phone to use, visit the BT settings, and pair a mono 'HSP'
  headset. In my case an old Jabra OTE-1.
  
  Once the device is paired, make an incoming call to the handset. Use the
- button to answer the call.
+ headset button to answer the call.
  
  The handset transitions to showing you an in-call UI, and appears to
  claim the audio is routed to the headset.
  
  I heard no audio.
  
  Expected: Audio was heard on the headset during the call.
  
  Note that this does not occur on rc-proposed/meizu.en #381, so it seems
  to be a recent regression.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1607466

Title:
  Mono BT headset has no in-call audio on recent rc-proposed

Status in Canonical System Image:
  New
Status in bluez package in Ubuntu:
  New
Status in phone-app package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  MX4/arale
  ubuntu-touch/rc-proposed/meizu.en #387

  Flash phone with --bootstrap, and walk through the welcome wizard.
  Once you have a phone to use, visit the BT settings, and pair a mono
  'HSP' headset. In my case an old Jabra OTE-1.

  Once the device is paired, make an incoming call to the handset. Use
  the headset button to answer the call.

  The handset transitions to showing you an in-call UI, and appears to
  claim the audio is routed to the headset.

  I heard no audio.

  Expected: Audio was heard on the headset during the call.

  Note that this does not occur on rc-proposed/meizu.en #381, so it
  seems to be a recent regression.

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

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

[Desktop-packages] [Bug 1607466] Re: Mono BT headset has no in-call audio on recent rc-proposed

[John McAleely]

I plan to capture logs, following the instructions here:

https://wiki.ubuntu.com/DebuggingBluetooth

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1607466

Title:
  Mono BT headset has no in-call audio on recent rc-proposed

Status in Canonical System Image:
  New
Status in bluez package in Ubuntu:
  New
Status in phone-app package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  MX4/arale
  ubuntu-touch/rc-proposed/meizu.en #387

  Flash phone with --bootstrap, and walk through the welcome wizard.
  Once you have a phone to use, visit the BT settings, and pair a mono
  'HSP' headset. In my case an old Jabra OTE-1.

  Once the device is paired, make an incoming call to the handset. Use
  the button to answer the call.

  The handset transitions to showing you an in-call UI, and appears to
  claim the audio is routed to the headset.

  I heard no audio.

  Expected: Audio was heard on the headset during the call.

  Note that this does not occur on rc-proposed/meizu.en #381, so it
  seems to be a recent regression.

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

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

[Desktop-packages] [Bug 1607466] Re: Mono BT headset has no in-call audio on recent rc-proposed

[John McAleely]

I discovered this apparent regression while testing the silo 60+37 combo
@koza is using to land bluez 5.41, but note that the bug appears (and
then disappears) on vanilla 387 vs 381.


** Changed in: canonical-devices-system-image
Milestone: None => 13

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1607466

Title:
  Mono BT headset has no in-call audio on recent rc-proposed

Status in Canonical System Image:
  New
Status in bluez package in Ubuntu:
  New
Status in phone-app package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  MX4/arale
  ubuntu-touch/rc-proposed/meizu.en #387

  Flash phone with --bootstrap, and walk through the welcome wizard.
  Once you have a phone to use, visit the BT settings, and pair a mono
  'HSP' headset. In my case an old Jabra OTE-1.

  Once the device is paired, make an incoming call to the handset. Use
  the button to answer the call.

  The handset transitions to showing you an in-call UI, and appears to
  claim the audio is routed to the headset.

  I heard no audio.

  Expected: Audio was heard on the headset during the call.

  Note that this does not occur on rc-proposed/meizu.en #381, so it
  seems to be a recent regression.

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

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

[Desktop-packages] [Bug 1607466] [NEW] Mono BT headset has no in-call audio on recent rc-proposed

[John McAleely]

Public bug reported:

MX4/arale
ubuntu-touch/rc-proposed/meizu.en #387

Flash phone with --bootstrap, and walk through the welcome wizard. Once
you have a phone to use, visit the BT settings, and pair a mono 'HSP'
headset. In my case an old Jabra OTE-1.

Once the device is paired, make an incoming call to the handset. Use the
button to answer the call.

The handset transitions to showing you an in-call UI, and appears to
claim the audio is routed to the headset.

I heard no audio.

Expected: Audio was heard on the headset during the call.

Note that this does not occur on rc-proposed/meizu.en #381, so it seems
to be a recent regression.

** Affects: canonical-devices-system-image
 Importance: Undecided
 Status: New

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

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

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

** Also affects: phone-app (Ubuntu)
   Importance: Undecided
   Status: New

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

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1607466

Title:
  Mono BT headset has no in-call audio on recent rc-proposed

Status in Canonical System Image:
  New
Status in bluez package in Ubuntu:
  New
Status in phone-app package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  MX4/arale
  ubuntu-touch/rc-proposed/meizu.en #387

  Flash phone with --bootstrap, and walk through the welcome wizard.
  Once you have a phone to use, visit the BT settings, and pair a mono
  'HSP' headset. In my case an old Jabra OTE-1.

  Once the device is paired, make an incoming call to the handset. Use
  the button to answer the call.

  The handset transitions to showing you an in-call UI, and appears to
  claim the audio is routed to the headset.

  I heard no audio.

  Expected: Audio was heard on the headset during the call.

  Note that this does not occur on rc-proposed/meizu.en #381, so it
  seems to be a recent regression.

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

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

[Desktop-packages] [Bug 1591935] Re: [CTA] audio record works for call audio

[John McAleely]

re-opening, and moving this bug to clarify status. The general solution
proposed here is the one we wish to use in the future, but we assume
that we can simply disable this feature at lower levels in devices
launched before this bug is fixed.

OEM bug #1597028 covers this.

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

** Changed in: canonical-devices-system-image
Milestone: fi => backlog

** Changed in: canonical-devices-system-image
   Importance: Critical => High

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1591935

Title:
  [CTA] audio record works for call audio

Status in Canonical System Image:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed
Status in trust-store package in Ubuntu:
  Confirmed

Bug description:
  krillin:ubuntu-touch/rc-proposed/bq-aquaris.en,#350

  Install the app 'Recorder' from the Ubuntu Store.

  Confirm it works by opening and making a recording. Note that the app
  requests permission to access the microphone, and you grant this with
  the usual trust store prompt.

  Now move to the phone app, and place a regular phone call. With the
  call active, open Recorder again, and start recording.

  Stop recording after some time, and hang up the call.

  return to the recorder app, and play the recording made during the
  phone call. Audio from both the local microphone and the remote
  handset (Which the user heard during the call) will be present on the
  track.

  It was expected that no audio from the call could be captured by
  applications.

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

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

[Desktop-packages] [Bug 1368868] Re: libmtp error when attempting to write to root of internal storage

[John McAleely]

** Information type changed from Embargoed to Proprietary

** Project changed: barajas => avila

** Information type changed from Proprietary to Public

** Project changed: avila => canonical-devices-system-image

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libmtp in Ubuntu.
https://bugs.launchpad.net/bugs/1368868

Title:
  libmtp error when attempting to write to root of internal storage

Status in Canonical System Image:
  Triaged
Status in libmtp package in Ubuntu:
  New

Bug description:
  Version: ubuntu-rtm r32

  Steps to reproduce:
   * connect the device to an Ubuntu desktop via USB
   * open the device in the file manager
   * enter the internal storage (krillin folder)
   * attempt to copy a file to the device

  Expected result:
   - file is written

  Actual result:
   - ugly dialog presented to user

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

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

[Desktop-packages] [Bug 1597681] Re: [CTA] Enable WAPI support

[John McAleely]

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

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

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

** Changed in: canonical-devices-system-image
 Assignee: Tony Espy (awe) => John McAleely (john.mcaleely)

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

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

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

Title:
  [CTA] Enable WAPI support

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

Bug description:
  The phone does not currently support WAPI [1]

  It should do so. As part of this, support for the SMS4 [2] cipher is
  also required.

  
  [1] 
https://en.wikipedia.org/wiki/WLAN_Authentication_and_Privacy_Infrastructure
  [2]: https://en.wikipedia.org/wiki/SMS4

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

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

[Desktop-packages] [Bug 1580146] Re: [touch] Internet connection stops working while WiFi is still connected

[John McAleely]

I have captured the logs requested in #25.

Note that during the session, the problem with 'network error' occured
after a few mins. Unlike in #28, a sleep (power button) cycle did not
recover the issue, but I noted that I was connected via ADB, perhaps
changing the power behaviour.

Therefore toward the end of the log, I used the network indicator pull
down to disable and then re-enable wifi. On rejoining the wifi (which it
did automatically), the browser could successfully refresh a page.

I therefore currently speculate that power cycling the wifi chipset
clears this issue.

I terminated the log gathering shortly after this event.

** Attachment added: "nm-nl.out"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1580146/+attachment/4692927/+files/nm-nl.out

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

Title:
  [touch] Internet connection stops working while WiFi is still
  connected

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

Bug description:
  krillin, rc-proposed, r329

  Description:
  It often happens that the internet connection stops working while the device 
is still connected to a (working) WiFi AP.
  The indicator shows that the phone is connected to the AP, here's the ouput 
of "nmcli d" and "nmcli c" http://pastebin.ubuntu.com/16344985/

  Tapping on the AP in the network indicator resets the connection and
  fixes the issue, which however reappears after a while.

  Here's also a "grep NetworkManager" from syslog
  http://pastebin.ubuntu.com/16344990/

  How to reproduce:
  I don't have a recipe, but here's what usually happens on my phone
  1) I connect to the office WiFi (Canonical's HQ, BlueFin office)
  2) Use browser, perform random google searches to check internet is working
  3) After a while (sometimes I put the phone to sleep, sometimes I checked the 
Updates from system settings a few times), I go back to the browser, and it 
starts returning "Network Error". NM, as you can see from the logs, says WiFi 
is "connected"
  4) At this point I use Terminal app and discover that "ping 8.8.8.8" is 
working correctly, "ping google.com" immediately returns "unkown host", i.e. it 
doesn't seem to be waiting for a timeout, it returns pretty fast.

  There are no related crash files in /var/crash

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

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

[Desktop-packages] [Bug 1580146] Re: [touch] Internet connection stops working while WiFi is still connected

[John McAleely]

I have captured the logs requested in #25.

Note that during the session, the problem with 'network error' occured
after a few mins. Unlike in #28, a sleep (power button) cycle did not
recover the issue, but I noted that I was connected via ADB, perhaps
changing the power behaviour.

Therefore toward the end of the log, I used the network indicator pull
down to disable and then re-enable wifi. On rejoining the wifi (which it
did automatically), the browser could successfully refresh a page.

I therefore currently speculate that power cycling the wifi chipset
clears this issue.

I terminated the log gathering shortly after this event.

** Attachment added: "nm-nl.out"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1580146/+attachment/4692926/+files/nm-nl.out

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

Title:
  [touch] Internet connection stops working while WiFi is still
  connected

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

Bug description:
  krillin, rc-proposed, r329

  Description:
  It often happens that the internet connection stops working while the device 
is still connected to a (working) WiFi AP.
  The indicator shows that the phone is connected to the AP, here's the ouput 
of "nmcli d" and "nmcli c" http://pastebin.ubuntu.com/16344985/

  Tapping on the AP in the network indicator resets the connection and
  fixes the issue, which however reappears after a while.

  Here's also a "grep NetworkManager" from syslog
  http://pastebin.ubuntu.com/16344990/

  How to reproduce:
  I don't have a recipe, but here's what usually happens on my phone
  1) I connect to the office WiFi (Canonical's HQ, BlueFin office)
  2) Use browser, perform random google searches to check internet is working
  3) After a while (sometimes I put the phone to sleep, sometimes I checked the 
Updates from system settings a few times), I go back to the browser, and it 
starts returning "Network Error". NM, as you can see from the logs, says WiFi 
is "connected"
  4) At this point I use Terminal app and discover that "ping 8.8.8.8" is 
working correctly, "ping google.com" immediately returns "unkown host", i.e. it 
doesn't seem to be waiting for a timeout, it returns pretty fast.

  There are no related crash files in /var/crash

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

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

[Desktop-packages] [Bug 1580146] Re: [touch] Internet connection stops working while WiFi is still connected

[John McAleely]

In attempting to reproduce #27 again, I have now seen a very similar
sequence, but no passsword prompt for the wifi was made, and the device
has appeared (from indicators) to have been on the wifi throughout.

However, on attempting to access a website, the 'network error' dialog
appeared.

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

Title:
  [touch] Internet connection stops working while WiFi is still
  connected

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

Bug description:
  krillin, rc-proposed, r329

  Description:
  It often happens that the internet connection stops working while the device 
is still connected to a (working) WiFi AP.
  The indicator shows that the phone is connected to the AP, here's the ouput 
of "nmcli d" and "nmcli c" http://pastebin.ubuntu.com/16344985/

  Tapping on the AP in the network indicator resets the connection and
  fixes the issue, which however reappears after a while.

  Here's also a "grep NetworkManager" from syslog
  http://pastebin.ubuntu.com/16344990/

  How to reproduce:
  I don't have a recipe, but here's what usually happens on my phone
  1) I connect to the office WiFi (Canonical's HQ, BlueFin office)
  2) Use browser, perform random google searches to check internet is working
  3) After a while (sometimes I put the phone to sleep, sometimes I checked the 
Updates from system settings a few times), I go back to the browser, and it 
starts returning "Network Error". NM, as you can see from the logs, says WiFi 
is "connected"
  4) At this point I use Terminal app and discover that "ping 8.8.8.8" is 
working correctly, "ping google.com" immediately returns "unkown host", i.e. it 
doesn't seem to be waiting for a timeout, it returns pretty fast.

  There are no related crash files in /var/crash

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

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

[Desktop-packages] [Bug 1580146] Re: [touch] Internet connection stops working while WiFi is still connected

[John McAleely]

I tried to reproduce the original error.

I flashed my vegetahd fresh (--bootstrap) to ubuntu-touch/rc-proposed
/bq-aquaris.en, #366

I walked through the wizard, and added it to the Canonical wifi
(Canonical-2.4GHz-g)

I performed some random google searches, and confirmed all was well.
Over a period of ~10 mins I left the device to idle, powered it on/off
with the power button (just sleep of course), and tried to observe the
'network error' reported.

Eventually, while on the lock screen, I woke the device to see the wifi
password prompt - the device appeared to have forgotten the password for
the canonical wifi. As we know, this is a failure mode that can mean
other things.

I cancelled the dialog, and logged in to the device. Using the indicator
menu, I pulled down the network panel. Observing that the system
appeared to be on cellular data (2G, note that both SIMS are loaded and
registered), I selected the Cannonical-2.4GHz-g wifi network and
observed it turned green, and the indicator switched to the wifi signal
strength view.

Dismissing the indicator Menu, I opened the browser and navigated to a
page.The browser displays 'Network Error', 'It appears you are having
trouble viewing: http://microsoft.com/. Please check your network
settings and try refreshing the page. '

Pressing refresh page, or navigating to other sites, produced the same
error. After a sleep cycle and unlock, the  button started
working - ie the device healed from whatever state it was in, while I
typed this up.

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

Title:
  [touch] Internet connection stops working while WiFi is still
  connected

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

Bug description:
  krillin, rc-proposed, r329

  Description:
  It often happens that the internet connection stops working while the device 
is still connected to a (working) WiFi AP.
  The indicator shows that the phone is connected to the AP, here's the ouput 
of "nmcli d" and "nmcli c" http://pastebin.ubuntu.com/16344985/

  Tapping on the AP in the network indicator resets the connection and
  fixes the issue, which however reappears after a while.

  Here's also a "grep NetworkManager" from syslog
  http://pastebin.ubuntu.com/16344990/

  How to reproduce:
  I don't have a recipe, but here's what usually happens on my phone
  1) I connect to the office WiFi (Canonical's HQ, BlueFin office)
  2) Use browser, perform random google searches to check internet is working
  3) After a while (sometimes I put the phone to sleep, sometimes I checked the 
Updates from system settings a few times), I go back to the browser, and it 
starts returning "Network Error". NM, as you can see from the logs, says WiFi 
is "connected"
  4) At this point I use Terminal app and discover that "ping 8.8.8.8" is 
working correctly, "ping google.com" immediately returns "unkown host", i.e. it 
doesn't seem to be waiting for a timeout, it returns pretty fast.

  There are no related crash files in /var/crash

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

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

[Desktop-packages] [Bug 1591935] Re: audio record works for call audio

[John McAleely]

At the moment, I think this bug has three subtasks:

 - trust-store should have a clear notion of 'call recording' as a
separate permission required of apps.

 - Pulse Audio should use this permission for the voicecall-record
plugin.

If we agree, then there is a third task
 
 - Review our existing devices and confirm that voicecall-record is the only 
way the routing can set this behaviour up.


Alternatively, I think Trust Store can take the view that it does not want to 
support call-recording, and in that case we should arrange all devices to 
disable this feature.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1591935

Title:
  audio record works for call audio

Status in Canonical System Image:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed
Status in trust-store package in Ubuntu:
  Confirmed

Bug description:
  krillin:ubuntu-touch/rc-proposed/bq-aquaris.en,#350

  Install the app 'Recorder' from the Ubuntu Store.

  Confirm it works by opening and making a recording. Note that the app
  requests permission to access the microphone, and you grant this with
  the usual trust store prompt.

  Now move to the phone app, and place a regular phone call. With the
  call active, open Recorder again, and start recording.

  Stop recording after some time, and hang up the call.

  return to the recorder app, and play the recording made during the
  phone call. Audio from both the local microphone and the remote
  handset (Which the user heard during the call) will be present on the
  track.

  It was expected that no audio from the call could be captured by
  applications.

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

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

[Desktop-packages] [Bug 1591935] Re: audio record works for call audio

[John McAleely]

So, as the o/p I would add: jdstrand's note in #5 that we should only do
this on a customer requirement is fine by me. We have a clear anti-
requirement in some regulatory regions.

Specifically that we should either treat call recording as a special
trust domain, and prompt/warn the user about the behaviour, or simply
disable the functionality.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1591935

Title:
  audio record works for call audio

Status in Canonical System Image:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed
Status in trust-store package in Ubuntu:
  Confirmed

Bug description:
  krillin:ubuntu-touch/rc-proposed/bq-aquaris.en,#350

  Install the app 'Recorder' from the Ubuntu Store.

  Confirm it works by opening and making a recording. Note that the app
  requests permission to access the microphone, and you grant this with
  the usual trust store prompt.

  Now move to the phone app, and place a regular phone call. With the
  call active, open Recorder again, and start recording.

  Stop recording after some time, and hang up the call.

  return to the recorder app, and play the recording made during the
  phone call. Audio from both the local microphone and the remote
  handset (Which the user heard during the call) will be present on the
  track.

  It was expected that no audio from the call could be captured by
  applications.

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

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

[Desktop-packages] [Bug 1591935] Re: audio record works for call audio

[John McAleely]

On 28 June 2016 at 16:02, Jamie Strandboge  wrote:

> "On Thu, 2016-06-09 at 09:05 -0400, Pat McGowan wrote:
> Seems Rex understood the plumbing, maybe there is a pulse setting to
> disable it.
> 

I would very much prefer this since this is a very sensitive area and IMHO, we
should only enable voicecall recording if there is a clear customer requirement,
and even then only with proper design.

The oem bug #1569213 references the voicecall-record[1] profile as being newly 
enabled.
Can we simply not disable that profile? Or is Ondrej saying that because of how
we do routing, you might be able to still record without the voicecall-record
profile (I'm guessing this means it would show up in pulse as a different,
recordable profile?)? If that's the case, let's fix the routing. :)

In other words:

 * the microphone is currently mediated by pulseaudio and trust-store

 * call recording recently was added somewhere and doesn't seem to be mediated
   by trust-store on all platforms (someone should confirm)

 * if pulseaudio and trust-store properly mediated call recording then this is
   probably technically enough to satisfy mediation requirements

 * (this bug) indicates it is surprising
   that call audio is lumped in with microphone recording. I agree this is
   surprising and strongly feel we should disable call audio recording until
   there is a clear customer requirement. call audio recording was never a
   consideration by our implementation because it didn't exist at the time--
   if it is something we want, it should be properly designed (likely a 2nd
   trust-store prompt)


[1]https://github.com/mer-hybris/pulseaudio-modules-droid/blob/master/README#L114

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1591935

Title:
  audio record works for call audio

Status in Canonical System Image:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed
Status in trust-store package in Ubuntu:
  Confirmed

Bug description:
  krillin:ubuntu-touch/rc-proposed/bq-aquaris.en,#350

  Install the app 'Recorder' from the Ubuntu Store.

  Confirm it works by opening and making a recording. Note that the app
  requests permission to access the microphone, and you grant this with
  the usual trust store prompt.

  Now move to the phone app, and place a regular phone call. With the
  call active, open Recorder again, and start recording.

  Stop recording after some time, and hang up the call.

  return to the recorder app, and play the recording made during the
  phone call. Audio from both the local microphone and the remote
  handset (Which the user heard during the call) will be present on the
  track.

  It was expected that no audio from the call could be captured by
  applications.

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

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

[Desktop-packages] [Bug 1591935] Re: audio record works for call audio

[John McAleely]

@tvoss could you comment on the trust-store aspects in #5

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1591935

Title:
  audio record works for call audio

Status in Canonical System Image:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed
Status in trust-store package in Ubuntu:
  Confirmed

Bug description:
  krillin:ubuntu-touch/rc-proposed/bq-aquaris.en,#350

  Install the app 'Recorder' from the Ubuntu Store.

  Confirm it works by opening and making a recording. Note that the app
  requests permission to access the microphone, and you grant this with
  the usual trust store prompt.

  Now move to the phone app, and place a regular phone call. With the
  call active, open Recorder again, and start recording.

  Stop recording after some time, and hang up the call.

  return to the recorder app, and play the recording made during the
  phone call. Audio from both the local microphone and the remote
  handset (Which the user heard during the call) will be present on the
  track.

  It was expected that no audio from the call could be captured by
  applications.

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

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

[Desktop-packages] [Bug 1591935] Re: audio record works for call audio

[John McAleely]

Bringing the conversation from email:

On 27 June 2016 at 23:18, Tyler Hicks  wrote:

I've pulled in Jamie Strandboge, who may have some insights about how
the audio recording policy should work. I'm not aware of the intended
functionality in the situation described in the bug.

I don't personally see capturing the audio output in the recording as a
security vulnerability as the user is still in control of audio recording.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1591935

Title:
  audio record works for call audio

Status in Canonical System Image:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed
Status in trust-store package in Ubuntu:
  Confirmed

Bug description:
  krillin:ubuntu-touch/rc-proposed/bq-aquaris.en,#350

  Install the app 'Recorder' from the Ubuntu Store.

  Confirm it works by opening and making a recording. Note that the app
  requests permission to access the microphone, and you grant this with
  the usual trust store prompt.

  Now move to the phone app, and place a regular phone call. With the
  call active, open Recorder again, and start recording.

  Stop recording after some time, and hang up the call.

  return to the recorder app, and play the recording made during the
  phone call. Audio from both the local microphone and the remote
  handset (Which the user heard during the call) will be present on the
  track.

  It was expected that no audio from the call could be captured by
  applications.

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

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

[Desktop-packages] [Bug 1591935] Re: audio record works for call audio

[John McAleely]

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => John McAleely (john.mcaleely)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1591935

Title:
  audio record works for call audio

Status in Canonical System Image:
  New
Status in pulseaudio package in Ubuntu:
  New
Status in trust-store package in Ubuntu:
  New

Bug description:
  krillin:ubuntu-touch/rc-proposed/bq-aquaris.en,#350

  Install the app 'Recorder' from the Ubuntu Store.

  Confirm it works by opening and making a recording. Note that the app
  requests permission to access the microphone, and you grant this with
  the usual trust store prompt.

  Now move to the phone app, and place a regular phone call. With the
  call active, open Recorder again, and start recording.

  Stop recording after some time, and hang up the call.

  return to the recorder app, and play the recording made during the
  phone call. Audio from both the local microphone and the remote
  handset (Which the user heard during the call) will be present on the
  track.

  It was expected that no audio from the call could be captured by
  applications.

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

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

[Desktop-packages] [Bug 1591935] Re: audio record works for call audio

[John McAleely]

** Also affects: trust-store (Ubuntu)
   Importance: Undecided
   Status: New

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1591935

Title:
  audio record works for call audio

Status in Canonical System Image:
  New
Status in pulseaudio package in Ubuntu:
  New
Status in trust-store package in Ubuntu:
  New

Bug description:
  krillin:ubuntu-touch/rc-proposed/bq-aquaris.en,#350

  Install the app 'Recorder' from the Ubuntu Store.

  Confirm it works by opening and making a recording. Note that the app
  requests permission to access the microphone, and you grant this with
  the usual trust store prompt.

  Now move to the phone app, and place a regular phone call. With the
  call active, open Recorder again, and start recording.

  Stop recording after some time, and hang up the call.

  return to the recorder app, and play the recording made during the
  phone call. Audio from both the local microphone and the remote
  handset (Which the user heard during the call) will be present on the
  track.

  It was expected that no audio from the call could be captured by
  applications.

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

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

Re: [Desktop-packages] [Bug 1546310] Re: In CAR bluetooth not working

[John McAleely]

Please open a new bug (actually two, since you appear to wish to report two
problems). Both appear to be different to the original reported here.

Bugs are not discussions for lots of problems. One concrete problem per
bug, and we duplicate those which have the same underlying fix required.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1546310

Title:
  In CAR bluetooth not working

Status in Canonical System Image:
  Fix Released
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1477838] Re: Crackling sound after playing audio and suspended

[John McAleely]

"I noticed the same soft white noise continues a second or two after the
phone plays any sound from any app, but then turns off. I presume there
is some time out turning off some part of the audio subsystem.
Presumably if there is a reason, it should happen even when the app
causing the sound to play is not active."

So, I believe pulseaudio, by design, maintains active status briefly (ie
a second or two) when a connection from an app terminates, so that if
two sounds a played back to back there is continutity for the underlying
hardware.

I think that's a separate bug (and possibly by design) than an annoying
noise happening, which seems to be MX4 specific.

Sadly, so far, finding people with the deep knowledge of the android
underpinnings of MX4 is proving tricky.

** Also affects: arale
   Importance: Undecided
   Status: New

** Changed in: arale
   Status: New => Confirmed

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

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

** Changed in: canonical-devices-system-image
Milestone: 12 => backlog

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1477838

Title:
  Crackling sound after playing audio and suspended

Status in arale:
  Confirmed
Status in Canonical System Image:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  The Meizu MX4 is doing a weird "tic tic tic..." after receive a
  notification (from telegram, mail...) and it's suspended.

  --

  When I press the screen lock button on the MX4 shortly after playing
  music or ending a phone call I hear a radio/fuzzy distorted noise
  coming from the phone. To make it stop I need to unlock and lock the
  screen again but this is not ideal.

  -

  When the screen is locked and the playing song is finished and waiting
  for a stopped signal, MX4 will do a weird lower sound.

  -

  TEST CASE (Thanks to Kamikaze)
  1. Boot the device and wait until it suspends (black screen)
  2. ssh to the device
  3. Run from the command line:
    $ aplay /usr/share/sounds/alsa/Front_Left.wav
  4. Repeat step 3 until you reproduce the issue (3 to 5 times)

  --- Original Case ---
  How to reproduce (Note this does not always work, the phone needs to be in 
some specific state yet to be determined)

  Ensure MX4 is not plugged into USB
  Call the MX4 and hear the ringtone
  Dismiss the call
  Push the power button to turn off the screen
  Tick Tick Tick
  Push the power button to turn on the screen
  hissing
  Push the power button to turn off the screen
  Tick Tick Tick
  etc

  It will not clear until you play another sound
  Does not happen in silent mode of course

  --from the dupe 

  Aquaris E4.5

  Steps to reproduce:

  1. Start playing a podcast.
  2. Switch to a different app.
  3. Lock the screen.
  4. Wait for the Podcast to finish.
  5. Wait a bit longer.

  Expected results:

  No noise from speaker.

  Actual results:

  Soft white noise from speaker. It seems that some part of the audio
  subsystem is still switched on. I am concerned that this could be
  draining battery.

  Workaround:

  After the Podcast finishes, unlock the phone and switch back to the
  Podbird app. This causes the noise to stop.

  Comments:

  I noticed the same soft white noise continues a second or two after
  the phone plays any sound from any app, but then turns off. I presume
  there is some time out turning off some part of the audio subsystem.
  Presumably if there is a reason, it should happen even when the app
  causing the sound to play is not active.

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

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

[Desktop-packages] [Bug 1579098] Re: [touch] Mobile data connection drops, and doesn't automatically reconnect

[John McAleely]

@faenil - I think I read on IRC that your machine lacks MAC addresses
and so forth, for $reasons. Can you confirm this bug on a stock device?

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

Title:
  [touch] Mobile data connection drops, and doesn't automatically
  reconnect

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

Bug description:
  Krillin, rc-proposed, r325

  In the last couple of weeks it often happened that the mobile data
  connection dropped without reconnecting afterwards. I often find my
  device without mobile data connection without apparent reason.

  Switching mobile data connection Off and back On from settings
  restores the connection.

  I don't have any useful additional info to provide, unfortunately.
  Please let me know if you need log/cmd output in particular.

  phablet@ubuntu-phablet:~$ nmcli d status
  DEVICE   TYPE  STATE CONNECTION 
  ril_1gsm   disconnected  -- 
  wlan0wifi  disconnected  -- 
  ril_0gsm   unavailable   -- 
  ifb0 ifb   unmanaged -- 
  ifb1 ifb   unmanaged -- 
  ip6tnl0  ip6tnlunmanaged -- 
  sit0 iptunnel  unmanaged -- 
  lo   loopback  unmanaged -- 
  tunl0unknown   unmanaged --

  Syslog since last time mobile data was connected:
  http://pastebin.ubuntu.com/16259803/

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

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

[Desktop-packages] [Bug 1407928] Re: [phone] Does not auto-switch to available, known WiFi

[John McAleely]

** Changed in: canonical-devices-system-image
Milestone: 11 => backlog

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

Title:
  [phone] Does not auto-switch to available, known WiFi

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

Bug description:
  This might not be the place for this bug, please reassign as
  appropriate.

  I was only able to reproduce this on mako/rtm, krillin/vivid seems to
  behave better (but I do remember the same issue there).

  Steps:
  * connect to a password-protected WiFi network
  * go out of range
  * make sure a GSM connection is established
  * go back in the WiFi range

  Expected:
  * phone connects to the known WiFi automatically

  Current:
  * phone does not connect to WiFi

  Please find attached network-test-session logs from when I toggled
  WiFi and Plane mode to get some data on the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu RTM 14.09
  Package: indicator-network 0.5.1+15.04.20141215~rtm-0ubuntu1
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: armhf
  Date: Tue Jan  6 12:01:55 2015
  InstallationDate: Installed on 2014-12-18 (18 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20141218-163635)
  SourcePackage: indicator-network
  UpgradeStatus: No upgrade log present (probably fresh install)
  indicator-network.log:
   Attempted to unregister path (path[0] = org path[1] = freedesktop) which 
isn't registered
   Attempted to unregister path (path[0] = org path[1] = freedesktop) which 
isn't registered
  upstart.indicator-network.log:
   Attempted to unregister path (path[0] = org path[1] = freedesktop) which 
isn't registered
   Attempted to unregister path (path[0] = org path[1] = freedesktop) which 
isn't registered

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

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

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

[John McAleely]

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

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

** Changed in: canonical-devices-system-image
Milestone: 11 => 12

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio 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:
  Confirmed
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

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

[John McAleely]

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

-- 
You received this bug notification because you are a member of Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1543179] Re: Audio does not get routed to BT headset/speaker

[John McAleely]

** Changed in: canonical-devices-system-image
Milestone: 11 => 12

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1543179

Title:
  Audio does not get routed to BT headset/speaker

Status in Canonical System Image:
  In Progress
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1543179] Re: Audio does not get routed to BT headset/speaker

[John McAleely]

** Changed in: bluez (Ubuntu)
 Assignee: Simon Fels (morphis) => Konrad Zapałowicz (kzapalowicz)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1543179

Title:
  Audio does not get routed to BT headset/speaker

Status in Canonical System Image:
  In Progress
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1578127] Re: Sometimes WLAN detects no SSID after s3

[John McAleely]

May relate to: https://askubuntu.com/questions/761180/wifi-doesnt-work-
after-suspend-after-16-04-upgrade

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

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

Title:
  Sometimes WLAN detects no SSID after s3

Status in NetworkManager:
  New
Status in OEM Priority Project:
  New
Status in network-manager package in Ubuntu:
  New

Bug description:
  [Steps to reproduce]
  1. Boot into OS
  2. Do s3 a few times
  3. Check if wifi is still working after s3

  [Expected results]
  wifi still working correctly after s3

  [Actual results]
  1. Wifi shows "disconnected" in network-manager (both in applet and from 
command "nmcli d status")
  2. Only one random SSID is displayed in network-manager applet, but wifi 
connection cannot be established at all with this SSID. Clicking on the SSID 
results in pop up window in the comment #2 below
  3. "nmcli d wifi rescan" does not resolve issue
  4.  "iwlist [interface] scan" returns nothing and does not reolve issue
  5. "nmcli d wifi connect [any SSID that you know should exist]" results in 
SSID not found and does not resolve issue
  6. "sudo service network-manager restart", warm boot, cold boot resolves issue

  [Details]
  OS: Xenial based OEM image
  WLAN module: Marvel [11ab:2b38]
  network-manager:
  - 1.2.0-0ubuntu0.16.04.1 (fail rate 1/20~ 1/15)
  - 1.1.93 (fail rate 1/15)

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1578127/+subscriptions

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

[Desktop-packages] [Bug 1494230] Re: Audio is not routed to A2DP sink when connected

[John McAleely]

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1494230

Title:
  Audio is not routed to A2DP sink when connected

Status in Canonical System Image:
  Fix Committed
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1521288] Re: Having a TV connected via SlimPort/HDMI does not route sound to it

[John McAleely]

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

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => John McAleely (john.mcaleely)

** Changed in: canonical-pocket-desktop
 Assignee: John McAleely (john.mcaleely) => (unassigned)

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

** Changed in: canonical-devices-system-image
   Importance: Undecided => Wishlist

** Changed in: canonical-devices-system-image
Milestone: None => backlog

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1521288

Title:
  Having a TV connected via SlimPort/HDMI does not route sound to it

Status in Canonical System Image:
  Confirmed
Status in Canonical Pocket Desktop:
  New
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  While a TV is connected to the phone via SlimPort/HDMI, audio should
  be routed to the TV.

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

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

[Desktop-packages] [Bug 1477838] Re: Crackling sound after playing audio and suspended

[John McAleely]

Not yet - our initial investigations have not turned up a fix. I've put
it on the list for 11

** Changed in: canonical-devices-system-image
Milestone: backlog => 11

** Changed in: pulseaudio (Ubuntu)
 Assignee: David Henningsson (diwic) => (unassigned)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1477838

Title:
  Crackling sound after playing audio and suspended

Status in Canonical System Image:
  Triaged
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  The Meizu MX4 is doing a weird "tic tic tic..." after receive a
  notification (from telegram, mail...) and it's suspended.

  --

  When I press the screen lock button on the MX4 shortly after playing
  music or ending a phone call I hear a radio/fuzzy distorted noise
  coming from the phone. To make it stop I need to unlock and lock the
  screen again but this is not ideal.

  -

  When the screen is locked and the playing song is finished and waiting
  for a stopped signal, MX4 will do a weird lower sound.

  -

  TEST CASE (Thanks to Kamikaze)
  1. Boot the device and wait until it suspends (black screen)
  2. ssh to the device
  3. Run from the command line:
    $ aplay /usr/share/sounds/alsa/Front_Left.wav
  4. Repeat step 3 until you reproduce the issue (3 to 5 times)

  --- Original Case ---
  How to reproduce (Note this does not always work, the phone needs to be in 
some specific state yet to be determined)

  Ensure MX4 is not plugged into USB
  Call the MX4 and hear the ringtone
  Dismiss the call
  Push the power button to turn off the screen
  Tick Tick Tick
  Push the power button to turn on the screen
  hissing
  Push the power button to turn off the screen
  Tick Tick Tick
  etc

  It will not clear until you play another sound
  Does not happen in silent mode of course

  --from the dupe 

  Aquaris E4.5

  Steps to reproduce:

  1. Start playing a podcast.
  2. Switch to a different app.
  3. Lock the screen.
  4. Wait for the Podcast to finish.
  5. Wait a bit longer.

  Expected results:

  No noise from speaker.

  Actual results:

  Soft white noise from speaker. It seems that some part of the audio
  subsystem is still switched on. I am concerned that this could be
  draining battery.

  Workaround:

  After the Podcast finishes, unlock the phone and switch back to the
  Podbird app. This causes the noise to stop.

  Comments:

  I noticed the same soft white noise continues a second or two after
  the phone plays any sound from any app, but then turns off. I presume
  there is some time out turning off some part of the audio subsystem.
  Presumably if there is a reason, it should happen even when the app
  causing the sound to play is not active.

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

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

Re: [Desktop-packages] [Bug 1477838] Re: Crackling sound after playing audio and suspended

[John McAleely]

Because work on it has not completed in time for the milestone release.

On 21 March 2016 at 12:03, Dylan Coakley 
wrote:

> Why is this bug being removed from the milestone?
>
> --
> You received this bug notification because you are a bug assignee.
> https://bugs.launchpad.net/bugs/1477838
>
> Title:
>   Crackling sound after playing audio and suspended
>
> Status in Canonical System Image:
>   Triaged
> Status in pulseaudio package in Ubuntu:
>   Confirmed
>
> Bug description:
>   The Meizu MX4 is doing a weird "tic tic tic..." after receive a
>   notification (from telegram, mail...) and it's suspended.
>
>   --
>
>   When I press the screen lock button on the MX4 shortly after playing
>   music or ending a phone call I hear a radio/fuzzy distorted noise
>   coming from the phone. To make it stop I need to unlock and lock the
>   screen again but this is not ideal.
>
>   -
>
>   When the screen is locked and the playing song is finished and waiting
>   for a stopped signal, MX4 will do a weird lower sound.
>
>   -
>
>   TEST CASE (Thanks to Kamikaze)
>   1. Boot the device and wait until it suspends (black screen)
>   2. ssh to the device
>   3. Run from the command line:
> $ aplay /usr/share/sounds/alsa/Front_Left.wav
>   4. Repeat step 3 until you reproduce the issue (3 to 5 times)
>
>   --- Original Case ---
>   How to reproduce (Note this does not always work, the phone needs to be
> in some specific state yet to be determined)
>
>   Ensure MX4 is not plugged into USB
>   Call the MX4 and hear the ringtone
>   Dismiss the call
>   Push the power button to turn off the screen
>   Tick Tick Tick
>   Push the power button to turn on the screen
>   hissing
>   Push the power button to turn off the screen
>   Tick Tick Tick
>   etc
>
>   It will not clear until you play another sound
>   Does not happen in silent mode of course
>
>   --from the dupe 
>
>   Aquaris E4.5
>
>   Steps to reproduce:
>
>   1. Start playing a podcast.
>   2. Switch to a different app.
>   3. Lock the screen.
>   4. Wait for the Podcast to finish.
>   5. Wait a bit longer.
>
>   Expected results:
>
>   No noise from speaker.
>
>   Actual results:
>
>   Soft white noise from speaker. It seems that some part of the audio
>   subsystem is still switched on. I am concerned that this could be
>   draining battery.
>
>   Workaround:
>
>   After the Podcast finishes, unlock the phone and switch back to the
>   Podbird app. This causes the noise to stop.
>
>   Comments:
>
>   I noticed the same soft white noise continues a second or two after
>   the phone plays any sound from any app, but then turns off. I presume
>   there is some time out turning off some part of the audio subsystem.
>   Presumably if there is a reason, it should happen even when the app
>   causing the sound to play is not active.
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/canonical-devices-system-image/+bug/1477838/+subscriptions
>

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1477838

Title:
  Crackling sound after playing audio and suspended

Status in Canonical System Image:
  Triaged
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  The Meizu MX4 is doing a weird "tic tic tic..." after receive a
  notification (from telegram, mail...) and it's suspended.

  --

  When I press the screen lock button on the MX4 shortly after playing
  music or ending a phone call I hear a radio/fuzzy distorted noise
  coming from the phone. To make it stop I need to unlock and lock the
  screen again but this is not ideal.

  -

  When the screen is locked and the playing song is finished and waiting
  for a stopped signal, MX4 will do a weird lower sound.

  -

  TEST CASE (Thanks to Kamikaze)
  1. Boot the device and wait until it suspends (black screen)
  2. ssh to the device
  3. Run from the command line:
    $ aplay /usr/share/sounds/alsa/Front_Left.wav
  4. Repeat step 3 until you reproduce the issue (3 to 5 times)

  --- Original Case ---
  How to reproduce (Note this does not always work, the phone needs to be in 
some specific state yet to be determined)

  Ensure MX4 is not plugged into USB
  Call the MX4 and hear the ringtone
  Dismiss the call
  Push the power button to turn off the screen
  Tick Tick Tick
  Push the power button to turn on the screen
  hissing
  Push the power button to turn off the screen
  Tick Tick Tick
  etc

  It will not clear until you play another sound
  Does not happen in silent mode of course

  --from the dupe 

  Aquaris E4.5

  Steps to reproduce:

  1. Start playing a podcast.
  2. Switch to a different app.
  3. Lock the screen.
  4. Wait for the Podcast to finish.
  5. Wait a bit longer.

  Expected results:

  No noise from speaker.

  Actual results:

  Soft white noise from speaker. 

[Desktop-packages] [Bug 1477838] Re: Crackling sound after playing audio and suspended

[John McAleely]

** Changed in: canonical-devices-system-image
Milestone: ww08-2016 => backlog

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1477838

Title:
  Crackling sound after playing audio and suspended

Status in Canonical System Image:
  Triaged
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  The Meizu MX4 is doing a weird "tic tic tic..." after receive a
  notification (from telegram, mail...) and it's suspended.

  --

  When I press the screen lock button on the MX4 shortly after playing
  music or ending a phone call I hear a radio/fuzzy distorted noise
  coming from the phone. To make it stop I need to unlock and lock the
  screen again but this is not ideal.

  -

  When the screen is locked and the playing song is finished and waiting
  for a stopped signal, MX4 will do a weird lower sound.

  -

  TEST CASE (Thanks to Kamikaze)
  1. Boot the device and wait until it suspends (black screen)
  2. ssh to the device
  3. Run from the command line:
    $ aplay /usr/share/sounds/alsa/Front_Left.wav
  4. Repeat step 3 until you reproduce the issue (3 to 5 times)

  --- Original Case ---
  How to reproduce (Note this does not always work, the phone needs to be in 
some specific state yet to be determined)

  Ensure MX4 is not plugged into USB
  Call the MX4 and hear the ringtone
  Dismiss the call
  Push the power button to turn off the screen
  Tick Tick Tick
  Push the power button to turn on the screen
  hissing
  Push the power button to turn off the screen
  Tick Tick Tick
  etc

  It will not clear until you play another sound
  Does not happen in silent mode of course

  --from the dupe 

  Aquaris E4.5

  Steps to reproduce:

  1. Start playing a podcast.
  2. Switch to a different app.
  3. Lock the screen.
  4. Wait for the Podcast to finish.
  5. Wait a bit longer.

  Expected results:

  No noise from speaker.

  Actual results:

  Soft white noise from speaker. It seems that some part of the audio
  subsystem is still switched on. I am concerned that this could be
  draining battery.

  Workaround:

  After the Podcast finishes, unlock the phone and switch back to the
  Podbird app. This causes the noise to stop.

  Comments:

  I noticed the same soft white noise continues a second or two after
  the phone plays any sound from any app, but then turns off. I presume
  there is some time out turning off some part of the audio subsystem.
  Presumably if there is a reason, it should happen even when the app
  causing the sound to play is not active.

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

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

[Desktop-packages] [Bug 1552128] Re: Music audio is not transferred to headset after it is connected

[John McAleely]

** Changed in: canonical-devices-system-image
   Status: Confirmed => Won't Fix

** Changed in: canonical-devices-system-image
   Status: Won't Fix => In Progress

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio 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:
  In Progress
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1543179] Re: Audio does not get routed to BT headset/speaker

[John McAleely]

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1543179

Title:
  Audio does not get routed to BT headset/speaker

Status in Canonical System Image:
  In Progress
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

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

[John McAleely]

** Changed in: canonical-devices-system-image
Milestone: ww08-2016 => 11

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio 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:
  Confirmed
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1533508] Re: Mobile data doesn't automatically connect after leaving wifi

[John McAleely]

** Changed in: ofono (Ubuntu)
   Status: Confirmed => Incomplete

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

** Changed in: canonical-devices-system-image
 Assignee: Alfonso Sanchez-Beato (alfonsosanchezbeato) => John McAleely 
(john.mcaleely)

** Changed in: canonical-devices-system-image
Milestone: ww08-2016 => 11

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

Title:
  Mobile data doesn't automatically connect after leaving wifi

Status in Canonical System Image:
  Incomplete
Status in network-manager package in Ubuntu:
  Incomplete
Status in ofono package in Ubuntu:
  Incomplete

Bug description:
  The mobile data doesn't automatically connect when leaving wifi.

  Expected Behavior:
  - Leave wifi
  - Mobile data connects automatically

  Observed Behavior:
  - Leave wifi
  - Mobile data is available but user interaction is required to connect. The 
device requires a reboot or airplane mode to be cycled before a connection is 
made.

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

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

[Desktop-packages] [Bug 1407928] Re: [phone] Does not auto-switch to available, known WiFi

[John McAleely]

** Changed in: canonical-devices-system-image
Milestone: ww08-2016 => 11

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

Title:
  [phone] Does not auto-switch to available, known WiFi

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

Bug description:
  This might not be the place for this bug, please reassign as
  appropriate.

  I was only able to reproduce this on mako/rtm, krillin/vivid seems to
  behave better (but I do remember the same issue there).

  Steps:
  * connect to a password-protected WiFi network
  * go out of range
  * make sure a GSM connection is established
  * go back in the WiFi range

  Expected:
  * phone connects to the known WiFi automatically

  Current:
  * phone does not connect to WiFi

  Please find attached network-test-session logs from when I toggled
  WiFi and Plane mode to get some data on the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu RTM 14.09
  Package: indicator-network 0.5.1+15.04.20141215~rtm-0ubuntu1
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: armhf
  Date: Tue Jan  6 12:01:55 2015
  InstallationDate: Installed on 2014-12-18 (18 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20141218-163635)
  SourcePackage: indicator-network
  UpgradeStatus: No upgrade log present (probably fresh install)
  indicator-network.log:
   Attempted to unregister path (path[0] = org path[1] = freedesktop) which 
isn't registered
   Attempted to unregister path (path[0] = org path[1] = freedesktop) which 
isn't registered
  upstart.indicator-network.log:
   Attempted to unregister path (path[0] = org path[1] = freedesktop) which 
isn't registered
   Attempted to unregister path (path[0] = org path[1] = freedesktop) which 
isn't registered

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

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

[Desktop-packages] [Bug 1552128] Re: Music audio is not transferred to headset after it is connected

[John McAleely]

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => John McAleely (john.mcaleely)

** Changed in: canonical-devices-system-image
Milestone: None => ww08-2016

** Changed in: canonical-devices-system-image
   Importance: Undecided => High

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio 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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1532858] Re: Some puritine packaged apps don't open on some devices

[John McAleely]

** Changed in: avila
 Assignee: Christopher Townsend (townsend) => (unassigned)

** Changed in: avila
   Status: Fix Released => Fix Committed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1532858

Title:
  Some puritine packaged apps don't open on some devices

Status in The Avila project:
  Fix Committed
Status in Canonical System Image:
  Fix Committed
Status in Canonical Pocket Desktop:
  Fix Released
Status in Libertine:
  Fix Released
Status in Puritine:
  Invalid
Status in libertine package in Ubuntu:
  Fix Released
Status in libreoffice package in Ubuntu:
  Invalid

Bug description:
  Launch the libre office application from puritine v0.5 in Avila, it reports 
"The application cannot be started. Internal Error ocurred"
  ---
  fwiw, LO in puritine v5 is launching reliably on N4 and N7 with no issues.

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

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

[Desktop-packages] [Bug 1535689] Re: Avila tablet is not recognised by libmtp

[John McAleely]

** Also affects: avila
   Importance: Undecided
   Status: New

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

** Changed in: canonical-devices-system-image
Milestone: None => ww08-2016

** Description changed:

  The Avila tablet (product name is Frieza) is not recognised when in MTP
  file mode by Ubuntu.
  
-  idVendor=2a47, idProduct=200D
+  idVendor=2a47, idProduct=200D
  
  Tested on a trusty/precise/wily laptop and found the device is not
  listed in the desktop interface.
  
  The line below will make it work normally just for testing.
  ATTR{idVendor}=="2a47", ATTR{idProduct}=="200d", SYMLINK+="libmtp-%k", 
MODE="660", GROUP="audio", ENV{ID_MTP_DEVICE}="1", ENV{ID_MEDIA_PLAYER}="1"
  # Avila Frieza (MTP+ADB)
  
  Reproduction Proceedure:
  
-  - Plug a tarblet into the Ubuntu desktop via a USB cable
-  - Expect to see a natuilus window pop up, with the option to browse and copy 
files to the phone's file system
+  - Plug a tarblet into the Ubuntu desktop via a USB cable
+  - Expect to see a natuilus window pop up, with the option to browse and copy 
files to the phone's file system
  
-  - Actual result: no response from the Ubuntu host.
+  - Actual result: no response from the Ubuntu host.
  
- Original bug: https://bugs.launchpad.net/avila-private/+bug/1531494
+ Related OEM bug #1531494

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libmtp in Ubuntu.
https://bugs.launchpad.net/bugs/1535689

Title:
   Avila tablet is not recognised by libmtp

Status in The Avila project:
  New
Status in Canonical System Image:
  New
Status in libmtp package in Ubuntu:
  New

Bug description:
  The Avila tablet (product name is Frieza) is not recognised when in
  MTP file mode by Ubuntu.

   idVendor=2a47, idProduct=200D

  Tested on a trusty/precise/wily laptop and found the device is not
  listed in the desktop interface.

  The line below will make it work normally just for testing.
  ATTR{idVendor}=="2a47", ATTR{idProduct}=="200d", SYMLINK+="libmtp-%k", 
MODE="660", GROUP="audio", ENV{ID_MTP_DEVICE}="1", ENV{ID_MEDIA_PLAYER}="1"
  # Avila Frieza (MTP+ADB)

  Reproduction Proceedure:

   - Plug a tarblet into the Ubuntu desktop via a USB cable
   - Expect to see a natuilus window pop up, with the option to browse and copy 
files to the phone's file system

   - Actual result: no response from the Ubuntu host.

  Related OEM bug #1531494

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

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

[Desktop-packages] [Bug 1477838] Re: Crackling sound after playing audio and suspended

[John McAleely]

@z-admin-angels-gmail-com - are you saying it makes a brief ticking
noise after playing a podcast? And would you know, if you are asleep?
:-)

Otherwise this sounds like a different bug

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1477838

Title:
  Crackling sound after playing audio and suspended

Status in Canonical System Image:
  Triaged
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  The Meizu MX4 is doing a weird "tic tic tic..." after receive a
  notification (from telegram, mail...) and it's suspended.

  --

  When I press the screen lock button on the MX4 shortly after playing
  music or ending a phone call I hear a radio/fuzzy distorted noise
  coming from the phone. To make it stop I need to unlock and lock the
  screen again but this is not ideal.

  -

  When the screen is locked and the playing song is finished and waiting
  for a stopped signal, MX4 will do a weird lower sound.

  -

  TEST CASE (Thanks to Kamikaze)
  1. Boot the device and wait until it suspends (black screen)
  2. ssh to the device
  3. Run from the command line:
    $ aplay /usr/share/sounds/alsa/Front_Left.wav
  4. Repeat step 3 until you reproduce the issue (3 to 5 times)

  --- Original Case ---
  How to reproduce (Note this does not always work, the phone needs to be in 
some specific state yet to be determined)

  Ensure MX4 is not plugged into USB
  Call the MX4 and hear the ringtone
  Dismiss the call
  Push the power button to turn off the screen
  Tick Tick Tick
  Push the power button to turn on the screen
  hissing
  Push the power button to turn off the screen
  Tick Tick Tick
  etc

  It will not clear until you play another sound
  Does not happen in silent mode of course

  --from the dupe 

  Aquaris E4.5

  Steps to reproduce:

  1. Start playing a podcast.
  2. Switch to a different app.
  3. Lock the screen.
  4. Wait for the Podcast to finish.
  5. Wait a bit longer.

  Expected results:

  No noise from speaker.

  Actual results:

  Soft white noise from speaker. It seems that some part of the audio
  subsystem is still switched on. I am concerned that this could be
  draining battery.

  Workaround:

  After the Podcast finishes, unlock the phone and switch back to the
  Podbird app. This causes the noise to stop.

  Comments:

  I noticed the same soft white noise continues a second or two after
  the phone plays any sound from any app, but then turns off. I presume
  there is some time out turning off some part of the audio subsystem.
  Presumably if there is a reason, it should happen even when the app
  causing the sound to play is not active.

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

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

[Desktop-packages] [Bug 1532868] Re: [Avila] OSK generates random touch events after switching from physical keyboard

[John McAleely]

** Changed in: avila
   Importance: Critical => High

** Changed in: avila
Milestone: ww04-2016 => ww06-2016

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1532868

Title:
  [Avila] OSK generates random touch events after switching from
  physical keyboard

Status in The Avila project:
  New
Status in Canonical System Image:
  Incomplete
Status in canonical-pocket-desktop:
  New
Status in Mir:
  Opinion
Status in mir package in Ubuntu:
  Opinion
Status in xorg-server package in Ubuntu:
  New

Bug description:
  Steps:
  connect a USB keyboard 
  Use for a bit
  Disconnect keyboard
  try using the onboard keyboard

  Result:
  The keyboard starts producing random touch events as soon as you try to use 
it.

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

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

[Desktop-packages] [Bug 1532858] Re: [Avila] Libre office not working

[John McAleely]

Silo 13 works for me.

** Changed in: avila
Milestone: ww02-2016 => ww04-2016

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1532858

Title:
  [Avila] Libre office not working

Status in The Avila project:
  In Progress
Status in canonical-pocket-desktop:
  New
Status in Libertine:
  Fix Committed
Status in Puritine:
  Invalid
Status in libertine package in Ubuntu:
  In Progress
Status in libreoffice package in Ubuntu:
  Invalid

Bug description:
  Launch the libre office application from puritine v0.5 in Avila, it reports 
"The application cannot be started. Internal Error ocurred"
  ---
  fwiw, LO in puritine v5 is launching reliably on N4 and N7 with no issues.

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

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

[Desktop-packages] [Bug 1532858] Re: [Avila] Libre office not working

[John McAleely]

So, with Silo 13 installed, I can open firefox and browse to
www,.ubuntu.com (after seeing the mozilla welcome page). In Libreoffice
I opened Impress, and created a new (blank) presentation. Edited a slide
and then saved it to Documents.

I could then close libreoffice, re-open it and open the saved slide from
the document picker it presented.

Given the workaround, is there anything specific to check?

** Summary changed:

- [Avila] Libre office not working
+ Some puritine packaged apps don't open on some devices

** Changed in: canonical-pocket-desktop
   Status: New => In Progress

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1532858

Title:
  Some puritine packaged apps don't open on some devices

Status in The Avila project:
  In Progress
Status in canonical-pocket-desktop:
  In Progress
Status in Libertine:
  Fix Committed
Status in Puritine:
  Invalid
Status in libertine package in Ubuntu:
  In Progress
Status in libreoffice package in Ubuntu:
  Invalid

Bug description:
  Launch the libre office application from puritine v0.5 in Avila, it reports 
"The application cannot be started. Internal Error ocurred"
  ---
  fwiw, LO in puritine v5 is launching reliably on N4 and N7 with no issues.

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

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

[Desktop-packages] [Bug 1532858] Re: [Avila] Libre office not working

[John McAleely]

ok, sounds good. can you be sure to email me a silo number when it's
ready.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1532858

Title:
  [Avila] Libre office not working

Status in The Avila project:
  In Progress
Status in canonical-pocket-desktop:
  New
Status in Libertine:
  Fix Committed
Status in Puritine:
  Invalid
Status in libertine package in Ubuntu:
  In Progress
Status in libreoffice package in Ubuntu:
  Invalid

Bug description:
  Launch the libre office application from puritine v0.5 in Avila, it reports 
"The application cannot be started. Internal Error ocurred"
  ---
  fwiw, LO in puritine v5 is launching reliably on N4 and N7 with no issues.

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

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

[Desktop-packages] [Bug 1532858] Re: [Avila] Libre office not working

[John McAleely]

awesome news. Which parts do we need to update to use this workaround?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1532858

Title:
  [Avila] Libre office not working

Status in The Avila project:
  In Progress
Status in canonical-pocket-desktop:
  New
Status in Libertine:
  Fix Committed
Status in Puritine:
  Invalid
Status in libertine package in Ubuntu:
  In Progress
Status in libreoffice package in Ubuntu:
  Invalid

Bug description:
  Launch the libre office application from puritine v0.5 in Avila, it reports 
"The application cannot be started. Internal Error ocurred"
  ---
  fwiw, LO in puritine v5 is launching reliably on N4 and N7 with no issues.

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

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

[Desktop-packages] [Bug 1283871] Re: Default mount points not suitable for photo import

[John McAleely]

". It just so happens it's only one of the few "well-known directories"
that Shotwell defines."

I'm surprised at this assumption. DCIM (and filename rules) are part of
now-ancient standards for digital cameras:

https://en.wikipedia.org/wiki/Design_rule_for_Camera_File_system

Mobile phones with cameras have by long convention also offered this
filesystem layout. My current iOS 9 device still does this, for example.

This is nothing to do with Shotwell's preferences.

** Changed in: shotwell (Ubuntu)
   Status: New => Invalid

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to shotwell in Ubuntu.
https://bugs.launchpad.net/bugs/1283871

Title:
  Default mount points not suitable for photo import

Status in Canonical System Image:
  New
Status in mtp package in Ubuntu:
  Triaged
Status in shotwell package in Ubuntu:
  Invalid

Bug description:
  When I plug my Ubuntu Phone into my desktop I want to be able to
  import photos easily into my photo manager of choice (Shotwell in my
  case but others are available apparently). The photos should be
  available via a "DCIM" folder, but they're in "Photos" which Shotwell
  doesn't find. While I could use the "Import from folder" and navigate
  my way to Photos, I'd rather it Just Worked.

  Could we export photos over the "standard" DCIM folder to make this
  easier for everyone?

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: mtp-server 0.0.2+14.04.20131205-0ubuntu1
  Uname: Linux 3.4.0-4-mako armv7l
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: armhf
  Date: Mon Feb 24 01:01:39 2014
  InstallationDate: Installed on 2014-02-23 (0 days ago)
  InstallationMedia: Ubuntu Trusty Tahr (development branch) - armhf 
(20140223.1)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
  SourcePackage: mtp
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1485522] Re: Volume obtained is 100% in multimedia sink for sounds from app

[John McAleely]

@pmcgowan I've added qtubuntu as a task, but maybe there is a better
proxy for QT?

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1485522

Title:
  Volume obtained is 100% in multimedia sink for sounds from app

Status in Canonical System Image:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed
Status in qtubuntu package in Ubuntu:
  New

Bug description:
  I'm not sure 100% this is a bug but it is related to
  https://bugs.launchpad.net/canonical-devices-system-image/+bug/1478506

  When the "Marron in trouble" games launches a sound the multimedia
  sink it's updated and when reading the volume it's always 100%.

  I'ts not 100% for other applications using the multimedia role, like
  the music app or other games/apps. The volume in that case is in sync
  with the volume that was previously set for it.

  This is the code from the indicator-sound where we get the 100%
  volume.

  var props_variant = yield _pconn.call 
("org.PulseAudio.Ext.StreamRestore1.RestoreEntry",
sink_input_objp, 
"org.freedesktop.DBus.Properties", "Get",
new Variant ("(ss)", 
"org.PulseAudio.Ext.StreamRestore1.RestoreEntry", "Volume"),
null, DBusCallFlags.NONE, -1);
Variant tmp;
props_variant.get ("(v)", out tmp);
uint32 type = 0, volume = 0;
VariantIter iter = tmp.iterator ();
iter.next ("(uu)", , );

  I did a workaround branch in the indicator-sound that reads the volume
  at initilaization for every role and stores any change When the sink
  is updated I read the volume in it that is already stored instead of
  reading the volume from pulse.

  I'm not convinced of that, and would like to know why I get 100%
  volume only for this particular game.

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

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

[Desktop-packages] [Bug 1485522] Re: Volume obtained is 100% in multimedia sink for sounds from app

[John McAleely]

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

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => John McAleely (john.mcaleely)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1485522

Title:
  Volume obtained is 100% in multimedia sink for sounds from app

Status in Canonical System Image:
  New
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I'm not sure 100% this is a bug but it is related to
  https://bugs.launchpad.net/canonical-devices-system-image/+bug/1478506

  When the "Marron in trouble" games launches a sound the multimedia
  sink it's updated and when reading the volume it's always 100%.

  I'ts not 100% for other applications using the multimedia role, like
  the music app or other games/apps. The volume in that case is in sync
  with the volume that was previously set for it.

  This is the code from the indicator-sound where we get the 100%
  volume.

  var props_variant = yield _pconn.call 
("org.PulseAudio.Ext.StreamRestore1.RestoreEntry",
sink_input_objp, 
"org.freedesktop.DBus.Properties", "Get",
new Variant ("(ss)", 
"org.PulseAudio.Ext.StreamRestore1.RestoreEntry", "Volume"),
null, DBusCallFlags.NONE, -1);
Variant tmp;
props_variant.get ("(v)", out tmp);
uint32 type = 0, volume = 0;
VariantIter iter = tmp.iterator ();
iter.next ("(uu)", , );

  I did a workaround branch in the indicator-sound that reads the volume
  at initilaization for every role and stores any change When the sink
  is updated I read the volume in it that is already stored instead of
  reading the volume from pulse.

  I'm not convinced of that, and would like to know why I get 100%
  volume only for this particular game.

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

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

[Desktop-packages] [Bug 1496434] Re: network-manager crash on boot on krillin/devel-proposed

[John McAleely]

@awe, it seems I lack assign-fu. can you take a look at this, but not
ahead of the ota-7 wifi related bugs?

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

Title:
  network-manager crash on boot on krillin/devel-proposed

Status in network-manager package in Ubuntu:
  New

Bug description:
  current build number: 198
  device name: krillin
  channel: ubuntu-touch/devel-proposed/krillin.en

  network-manager:
Installed: 1.0.4-0ubuntu3

  network-manager crashes and keeps re-spawning, making the device
  unusable.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1496434/+subscriptions

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

[Desktop-packages] [Bug 1413818] Re: Notification sounds aren't being played back on E4.5

[John McAleely]

** Package changed: pulseaudio (Ubuntu RTM) => pulseaudio (Ubuntu)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1413818

Title:
  Notification sounds aren't being played back on E4.5

Status in Canonical System Image:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  This affects mostly the push notifications based alerts, SMS et.al.
  work fine.

  With export PULSE_PROP='media.role=alert'

  This has no audible output: paplay 
/usr/share/sounds/ubuntu/notifications/Slick.ogg
  This does:  paplay /usr/share/sounds/ubuntu/ringtones/Soul.ogg

  $ system-image-cli -i
  current build number: 14
  device name: mako
  channel: ubuntu-touch/stable
  alias: ubuntu-touch/ubuntu-rtm/14.09
  last update: 2015-01-16 13:12:29
  version version: 14
  version ubuntu: 20150116
  version device: 20141119
  version custom: mako-1.1

  The hunch is some buffering going on on the android side for short
  sound bytes.

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

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

[Desktop-packages] [Bug 1438486] Re: Turning off sound in Pathwind mutes other apps too

[John McAleely]

** Changed in: pulseaudio (Ubuntu RTM)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1438486

Title:
   Turning off sound in Pathwind mutes other apps too

Status in Canonical System Image:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Confirmed
Status in ubuntu-touch-session package in Ubuntu:
  Fix Released
Status in pulseaudio package in Ubuntu RTM:
  Invalid
Status in ubuntu-touch-session package in Ubuntu RTM:
  Fix Released

Bug description:
  current build number: 260
  device name: krillin
  channel: ubuntu-touch/ubuntu-rtm/14.09-proposed
  last update: 2015-03-30 18:17:44
  version version: 260
  version ubuntu: 20150330
  version device: 20150327-f7072d0
  version custom: 20150216-561-29-186

  In Pathwind (part of the custom tarball installed with newer flashes but also 
in the store) one can toggle sound on/off.
  If set to off sound won't be heard in youtube playbacks in the browser, cut 
the rope, media player. It still works for keyboard press sounds if enabled, 
and ringtones work as well.
  This may be intentional, but at least on one occasion it persisted even after 
pathwind quit, and sound did not work in the rest of the apps.

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

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

[Desktop-packages] [Bug 1413818] Re: Notification sounds aren't being played back on E4.5

[John McAleely]

@chipaca, assuming yours is one, and it still does it, can you provide
the output from system-image-cli -i please?

This will be software, not hardware :-)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1413818

Title:
  Notification sounds aren't being played back on E4.5

Status in Canonical System Image:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  This affects mostly the push notifications based alerts, SMS et.al.
  work fine.

  With export PULSE_PROP='media.role=alert'

  This has no audible output: paplay 
/usr/share/sounds/ubuntu/notifications/Slick.ogg
  This does:  paplay /usr/share/sounds/ubuntu/ringtones/Soul.ogg

  $ system-image-cli -i
  current build number: 14
  device name: mako
  channel: ubuntu-touch/stable
  alias: ubuntu-touch/ubuntu-rtm/14.09
  last update: 2015-01-16 13:12:29
  version version: 14
  version ubuntu: 20150116
  version device: 20141119
  version custom: mako-1.1

  The hunch is some buffering going on on the android side for short
  sound bytes.

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

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

[Desktop-packages] [Bug 1487111] Re: camera app unresponsive if trusted prompt left for some time

[John McAleely]

@mandel, it seems I don't have the power of assignment here. Can you
pick this up, and pull in Diwic as needed?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1487111

Title:
  camera app unresponsive if trusted prompt left for some time

Status in Canonical System Image:
  Confirmed
Status in camera-app package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  image95/arale (also on mako)
  i see this for both the audio trust prompt and the video trust prompt
  steps
  1. launch camera
  2. don't touch trust prompt - set phone down for 5 min
  3. after time, select accept
  (alternately - select accept on camera, hit record and wait for audio prompt, 
step2)

  expected - app continues
  result - app is frozen, shell is still responsive, camera service spinning 
50% cpu

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

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

[Desktop-packages] [Bug 1487129] Re: camera-app mic permission item blank

[John McAleely]

@mpt, we may have to iterate on what we have to get to the desired aim
of one prompt for two trust store requests.

** Changed in: pulseaudio (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 Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1487129

Title:
  camera-app mic permission item blank

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

Bug description:
  Working through camera/mic trust issues, discovering that the camera-
  app's mic item under Other app access is blank, will attach a
  screenie.

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

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

[Desktop-packages] [Bug 1487129] Re: camera-app mic permission item blank

[John McAleely]

I've subscribed tvoss who designed this arrangement, in case the bug is
in the architecture, and not a boring string cockup.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1487129

Title:
  camera-app mic permission item blank

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

Bug description:
  Working through camera/mic trust issues, discovering that the camera-
  app's mic item under Other app access is blank, will attach a
  screenie.

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

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

[Desktop-packages] [Bug 1487129] Re: camera-app mic permission item blank

[John McAleely]

Is this actually fixable? ie, does pulse know the camera (and not the
plain audio subsystem) is the accessing party here?

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

** Changed in: canonical-devices-system-image
   Importance: High = Critical

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1487129

Title:
  camera-app mic permission item blank

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

Bug description:
  Working through camera/mic trust issues, discovering that the camera-
  app's mic item under Other app access is blank, will attach a
  screenie.

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

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

[Desktop-packages] [Bug 1224756] Re: Pulseaudio should integrate with trust-store

[John McAleely]

** Changed in: pulseaudio (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 Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1224756

Title:
  Pulseaudio should integrate with trust-store

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

Bug description:
  Currently the 'audio' policy group allows access to pulseaudio which
  allows apps to use the microphone and eavesdrop on the user.
  Pulseaudio needs to be modified to use trust-store, like location-
  service does. Integrating with trust-store means that when an app
  tries use the microphone via pulseaudio, pulseaudio will contact
  trust-store, the trust-store will prompt the user (Foo wants to use
  the microphone. Is this ok? Yes|No), optionally cache the result and
  return the result to pulseaudio. In this manner the user is given a
  contextual prompt at the time of access by the app. Using caching this
  decision can be remembered the next time. If caching is used, there
  should be a method to change the decision in settings.

  Targeting to T-Series for now, since the trust-store is not in a
  reusable form yet.

  Original description:
  David and the security team (inspired by an observation from Rick) discussed 
that when recording, pulseaudio should somehow unobtrusively show the user that 
it is recording. The easiest thing to do would be for pulseaudio to alert 
indicator-sound which would then turn its icon red (similar to 
indicator-message turning blue with new messages). Marking 'high' because apps 
with access to pulseaudio can currently eavedrop on users. If the app is 
allowed to do networking (the default for apps), then it can ship that 
information off to a server somewhere.

  Note 1, the alert to indicator-sound must happen via the out of
  process pulseaudio server and not the confined app itself to be
  effective.

  Note 2, we should consider how to enforce this for foreground apps
  only. Application lifecycle should probably handle this for 13.10
  (apps are suspended if not in foreground or if the screensaver is on),
  but we don't want an app on the converged device to record in the
  background when the user isn't paying attention. Example eavesdropping
  attack: start recording only when the screensaver is on (perhaps
  inhibiting the screensaver during recording would be enough).

  https://wiki.ubuntu.com/AccountPrivileges#Phone: On the phone, if
  an app tries to access your ... microphone ... or video recording,
  this should be subject to permission. “Video recording” should be
  separate from “Camera” so that an app does not need two permissions
  when recording video, one for the camera and one for the microphone.
  If an app has permission to record video, it should have access to the
  microphone whenever it is recording video...

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

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

[Desktop-packages] [Bug 1230391] Re: please provide visual cue during background recording

[John McAleely]

Responding here to #4, I see your concern jdstrand. I guess the urgency
will depend on the behaviour of the client APIs when the app calling
them is backgrounded. do they continue, or do they move into some error
state. I've assumed the latter so far, but I can see that may not be the
case.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1230391

Title:
  please provide visual cue during background recording

Status in Canonical System Image:
  New
Status in pulseaudio package in Ubuntu:
  Confirmed
Status in qtubuntu-camera package in Ubuntu:
  New

Bug description:
  After bug #1224756 is fixed, we should provide a visual cue for when
  an app moves to the background and is recording audio. This will allow
  an app like Skype to work normally in the foreground, but if the user
  launches another app into the foreground, the user is able to see that
  he/she is still on the Skype call. In addition to the usability
  benefit, this provides a security benefit because it stops
  eavesdropping because the user will have a visual cue that the
  malicious/misbehaving app is recording audio.

  This needs design.

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

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

[Desktop-packages] [Bug 1224756] Re: Pulseaudio should integrate with trust-store

[John McAleely]

Responded to #36 on bug #1230391

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1224756

Title:
  Pulseaudio should integrate with trust-store

Status in Canonical System Image:
  In Progress
Status in pulseaudio package in Ubuntu:
  In Progress

Bug description:
  Currently the 'audio' policy group allows access to pulseaudio which
  allows apps to use the microphone and eavesdrop on the user.
  Pulseaudio needs to be modified to use trust-store, like location-
  service does. Integrating with trust-store means that when an app
  tries use the microphone via pulseaudio, pulseaudio will contact
  trust-store, the trust-store will prompt the user (Foo wants to use
  the microphone. Is this ok? Yes|No), optionally cache the result and
  return the result to pulseaudio. In this manner the user is given a
  contextual prompt at the time of access by the app. Using caching this
  decision can be remembered the next time. If caching is used, there
  should be a method to change the decision in settings.

  Targeting to T-Series for now, since the trust-store is not in a
  reusable form yet.

  Original description:
  David and the security team (inspired by an observation from Rick) discussed 
that when recording, pulseaudio should somehow unobtrusively show the user that 
it is recording. The easiest thing to do would be for pulseaudio to alert 
indicator-sound which would then turn its icon red (similar to 
indicator-message turning blue with new messages). Marking 'high' because apps 
with access to pulseaudio can currently eavedrop on users. If the app is 
allowed to do networking (the default for apps), then it can ship that 
information off to a server somewhere.

  Note 1, the alert to indicator-sound must happen via the out of
  process pulseaudio server and not the confined app itself to be
  effective.

  Note 2, we should consider how to enforce this for foreground apps
  only. Application lifecycle should probably handle this for 13.10
  (apps are suspended if not in foreground or if the screensaver is on),
  but we don't want an app on the converged device to record in the
  background when the user isn't paying attention. Example eavesdropping
  attack: start recording only when the screensaver is on (perhaps
  inhibiting the screensaver during recording would be enough).

  https://wiki.ubuntu.com/AccountPrivileges#Phone: On the phone, if
  an app tries to access your ... microphone ... or video recording,
  this should be subject to permission. “Video recording” should be
  separate from “Camera” so that an app does not need two permissions
  when recording video, one for the camera and one for the microphone.
  If an app has permission to record video, it should have access to the
  microphone whenever it is recording video...

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

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

[Desktop-packages] [Bug 1468811] Re: headphone volume auto-set to loudest

[John McAleely]

** Changed in: canonical-devices-system-image
Milestone: ww34-2015 = ww40-2015

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1468811

Title:
  headphone volume auto-set to loudest

Status in Canonical System Image:
  Incomplete
Status in Ubuntu Music App:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  since OTA-4 i get the headphone volume randomly set to the highest
  setting. it can only be set when headphones are plugged in and
  playback has started, so I have no way of checking beforehand. (of
  course I can choose to keep headphones away from the ears.)

  
  this occurs both in the music app and in the podcast app podbird. also occurs 
sometimes during playback, when notification sound is played. 

  not a security issue, but rather a quite serious hearing health issue. 
  I'm on BQ Aquaris E4.5

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

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

Re: [Desktop-packages] [Bug 1224756] Re: Pulseaudio should integrate with trust-store

[John McAleely]

certainly. is there actually any way to *do* background recording, in the
current app lifecycle?

On 14 August 2015 at 19:23, Jamie Strandboge ja...@ubuntu.com wrote:

 Should bug #1230391 be revisited now that this is landing (show a visual
 cue if background recording)?

 --
 You received this bug notification because you are subscribed to the bug
 report.
 https://bugs.launchpad.net/bugs/1224756

 Title:
   Pulseaudio should integrate with trust-store

 Status in Canonical System Image:
   In Progress
 Status in pulseaudio package in Ubuntu:
   In Progress

 Bug description:
   Currently the 'audio' policy group allows access to pulseaudio which
   allows apps to use the microphone and eavesdrop on the user.
   Pulseaudio needs to be modified to use trust-store, like location-
   service does. Integrating with trust-store means that when an app
   tries use the microphone via pulseaudio, pulseaudio will contact
   trust-store, the trust-store will prompt the user (Foo wants to use
   the microphone. Is this ok? Yes|No), optionally cache the result and
   return the result to pulseaudio. In this manner the user is given a
   contextual prompt at the time of access by the app. Using caching this
   decision can be remembered the next time. If caching is used, there
   should be a method to change the decision in settings.

   Targeting to T-Series for now, since the trust-store is not in a
   reusable form yet.

   Original description:
   David and the security team (inspired by an observation from Rick)
 discussed that when recording, pulseaudio should somehow unobtrusively show
 the user that it is recording. The easiest thing to do would be for
 pulseaudio to alert indicator-sound which would then turn its icon red
 (similar to indicator-message turning blue with new messages). Marking
 'high' because apps with access to pulseaudio can currently eavedrop on
 users. If the app is allowed to do networking (the default for apps), then
 it can ship that information off to a server somewhere.

   Note 1, the alert to indicator-sound must happen via the out of
   process pulseaudio server and not the confined app itself to be
   effective.

   Note 2, we should consider how to enforce this for foreground apps
   only. Application lifecycle should probably handle this for 13.10
   (apps are suspended if not in foreground or if the screensaver is on),
   but we don't want an app on the converged device to record in the
   background when the user isn't paying attention. Example eavesdropping
   attack: start recording only when the screensaver is on (perhaps
   inhibiting the screensaver during recording would be enough).

   https://wiki.ubuntu.com/AccountPrivileges#Phone: On the phone, if
   an app tries to access your ... microphone ... or video recording,
   this should be subject to permission. “Video recording” should be
   separate from “Camera” so that an app does not need two permissions
   when recording video, one for the camera and one for the microphone.
   If an app has permission to record video, it should have access to the
   microphone whenever it is recording video...

 To manage notifications about this bug go to:

 https://bugs.launchpad.net/canonical-devices-system-image/+bug/1224756/+subscriptions


-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1224756

Title:
  Pulseaudio should integrate with trust-store

Status in Canonical System Image:
  In Progress
Status in pulseaudio package in Ubuntu:
  In Progress

Bug description:
  Currently the 'audio' policy group allows access to pulseaudio which
  allows apps to use the microphone and eavesdrop on the user.
  Pulseaudio needs to be modified to use trust-store, like location-
  service does. Integrating with trust-store means that when an app
  tries use the microphone via pulseaudio, pulseaudio will contact
  trust-store, the trust-store will prompt the user (Foo wants to use
  the microphone. Is this ok? Yes|No), optionally cache the result and
  return the result to pulseaudio. In this manner the user is given a
  contextual prompt at the time of access by the app. Using caching this
  decision can be remembered the next time. If caching is used, there
  should be a method to change the decision in settings.

  Targeting to T-Series for now, since the trust-store is not in a
  reusable form yet.

  Original description:
  David and the security team (inspired by an observation from Rick) discussed 
that when recording, pulseaudio should somehow unobtrusively show the user that 
it is recording. The easiest thing to do would be for pulseaudio to alert 
indicator-sound which would then turn its icon red (similar to 
indicator-message turning blue with new messages). Marking 'high' because apps 
with access to pulseaudio can currently eavedrop on users. If the app is 
allowed to do networking (the default for apps), then it 

[Desktop-packages] [Bug 1230391] Re: please provide visual cue during background recording

[John McAleely]

I am currently aware of no way for an application to record 'in the
background' due to the app lifecycle.

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

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) = John McAleely (john.mcaleely)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1230391

Title:
  please provide visual cue during background recording

Status in Canonical System Image:
  New
Status in pulseaudio package in Ubuntu:
  Confirmed
Status in qtubuntu-camera package in Ubuntu:
  New

Bug description:
  After bug #1224756 is fixed, we should provide a visual cue for when
  an app moves to the background and is recording audio. This will allow
  an app like Skype to work normally in the foreground, but if the user
  launches another app into the foreground, the user is able to see that
  he/she is still on the Skype call. In addition to the usability
  benefit, this provides a security benefit because it stops
  eavesdropping because the user will have a visual cue that the
  malicious/misbehaving app is recording audio.

  This needs design.

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

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

[Desktop-packages] [Bug 1224756] Re: Pulseaudio should integrate with trust-store

[John McAleely]

This is in silo 30 as I type, blocked by bug #1483752

** Changed in: canonical-devices-system-image
   Importance: High = Critical

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1224756

Title:
  Pulseaudio should integrate with trust-store

Status in Canonical System Image:
  In Progress
Status in pulseaudio package in Ubuntu:
  In Progress

Bug description:
  Currently the 'audio' policy group allows access to pulseaudio which
  allows apps to use the microphone and eavesdrop on the user.
  Pulseaudio needs to be modified to use trust-store, like location-
  service does. Integrating with trust-store means that when an app
  tries use the microphone via pulseaudio, pulseaudio will contact
  trust-store, the trust-store will prompt the user (Foo wants to use
  the microphone. Is this ok? Yes|No), optionally cache the result and
  return the result to pulseaudio. In this manner the user is given a
  contextual prompt at the time of access by the app. Using caching this
  decision can be remembered the next time. If caching is used, there
  should be a method to change the decision in settings.

  Targeting to T-Series for now, since the trust-store is not in a
  reusable form yet.

  Original description:
  David and the security team (inspired by an observation from Rick) discussed 
that when recording, pulseaudio should somehow unobtrusively show the user that 
it is recording. The easiest thing to do would be for pulseaudio to alert 
indicator-sound which would then turn its icon red (similar to 
indicator-message turning blue with new messages). Marking 'high' because apps 
with access to pulseaudio can currently eavedrop on users. If the app is 
allowed to do networking (the default for apps), then it can ship that 
information off to a server somewhere.

  Note 1, the alert to indicator-sound must happen via the out of
  process pulseaudio server and not the confined app itself to be
  effective.

  Note 2, we should consider how to enforce this for foreground apps
  only. Application lifecycle should probably handle this for 13.10
  (apps are suspended if not in foreground or if the screensaver is on),
  but we don't want an app on the converged device to record in the
  background when the user isn't paying attention. Example eavesdropping
  attack: start recording only when the screensaver is on (perhaps
  inhibiting the screensaver during recording would be enough).

  https://wiki.ubuntu.com/AccountPrivileges#Phone: On the phone, if
  an app tries to access your ... microphone ... or video recording,
  this should be subject to permission. “Video recording” should be
  separate from “Camera” so that an app does not need two permissions
  when recording video, one for the camera and one for the microphone.
  If an app has permission to record video, it should have access to the
  microphone whenever it is recording video...

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

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

[Desktop-packages] [Bug 1224756] Re: Pulseaudio should integrate with trust-store

[John McAleely]

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1224756

Title:
  Pulseaudio should integrate with trust-store

Status in Canonical System Image:
  In Progress
Status in pulseaudio package in Ubuntu:
  In Progress

Bug description:
  Currently the 'audio' policy group allows access to pulseaudio which
  allows apps to use the microphone and eavesdrop on the user.
  Pulseaudio needs to be modified to use trust-store, like location-
  service does. Integrating with trust-store means that when an app
  tries use the microphone via pulseaudio, pulseaudio will contact
  trust-store, the trust-store will prompt the user (Foo wants to use
  the microphone. Is this ok? Yes|No), optionally cache the result and
  return the result to pulseaudio. In this manner the user is given a
  contextual prompt at the time of access by the app. Using caching this
  decision can be remembered the next time. If caching is used, there
  should be a method to change the decision in settings.

  Targeting to T-Series for now, since the trust-store is not in a
  reusable form yet.

  Original description:
  David and the security team (inspired by an observation from Rick) discussed 
that when recording, pulseaudio should somehow unobtrusively show the user that 
it is recording. The easiest thing to do would be for pulseaudio to alert 
indicator-sound which would then turn its icon red (similar to 
indicator-message turning blue with new messages). Marking 'high' because apps 
with access to pulseaudio can currently eavedrop on users. If the app is 
allowed to do networking (the default for apps), then it can ship that 
information off to a server somewhere.

  Note 1, the alert to indicator-sound must happen via the out of
  process pulseaudio server and not the confined app itself to be
  effective.

  Note 2, we should consider how to enforce this for foreground apps
  only. Application lifecycle should probably handle this for 13.10
  (apps are suspended if not in foreground or if the screensaver is on),
  but we don't want an app on the converged device to record in the
  background when the user isn't paying attention. Example eavesdropping
  attack: start recording only when the screensaver is on (perhaps
  inhibiting the screensaver during recording would be enough).

  https://wiki.ubuntu.com/AccountPrivileges#Phone: On the phone, if
  an app tries to access your ... microphone ... or video recording,
  this should be subject to permission. “Video recording” should be
  separate from “Camera” so that an app does not need two permissions
  when recording video, one for the camera and one for the microphone.
  If an app has permission to record video, it should have access to the
  microphone whenever it is recording video...

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

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

[Desktop-packages] [Bug 1425172] Re: Network indicator lists the non-exist AP (timeout for the AP to be removed is too big, ~6min)

[John McAleely]

** Changed in: canonical-devices-system-image
 Assignee: Canonical Phone Foundations (canonical-phonedations-team) = 
John McAleely (john.mcaleely)

** Changed in: network-manager (Ubuntu RTM)
   Status: Confirmed = Invalid

** Changed in: network-manager (Ubuntu RTM)
 Assignee: Canonical Phone Foundations (canonical-phonedations-team) = 
(unassigned)

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

Title:
  Network indicator lists the non-exist AP (timeout for the AP to be
  removed is too big, ~6min)

Status in Canonical System Image:
  Confirmed
Status in indicator-network package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu RTM:
  Invalid

Bug description:
  Summary: Network indicator lists the non-exist AP
  Steps to reproduce:
  1. Boot to system
  2. Scroll down the Network indicator
  3. It lists about 10 AP (In Taipei office)
  4. Go to another place and check network indicator again

  Expected Result:
  It should not list non-exist AP and only show available AP

  Actual Result:
  It shows about 12 AP on the screen but only two are real AP for connecting, 
and others 10 are from last list.

  This is reproducible on mako/krillin on both RTM and vivid.

  The main issue is that the timeout for the AP to be removed from the
  known AP list is too big when comparing with other phones.

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

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

[Desktop-packages] [Bug 1378814] Re: greeter does not properly update infographic after unlock

[John McAleely]

One particular frustration for our user group is that this seems to
reveal 'stale translations', so if you change your language, I
understand that the strings can appear in the 'old' language.

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

** Changed in: canonical-devices-system-image
   Importance: Undecided = High

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) = Pat McGowan (pat-mcgowan)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-greeter in Ubuntu.
https://bugs.launchpad.net/bugs/1378814

Title:
  greeter does not properly update infographic after unlock

Status in the base for Ubuntu mobile products:
  Confirmed
Status in unity-greeter package in Ubuntu:
  Confirmed

Bug description:
  This bug has been here since forever, but really needs to get cleaned
  up for rtm.

  Steps to reproduce:
  - send 2 text messages
  - lock your phone
  - unlock your phone
  - confirm infographic says 2 text messages sent today
  - lock your phone for the night and go to sleep
  - unlock your phone the next day

  Expected results:
  - infographic should be cleared, or show relevant information for today

  Actual results:
  - infographic still says 2 text messages sent today

  When the phone is unlocked the greeter should update the infographic
  text

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

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

[Desktop-packages] [Bug 1378814] Re: greeter does not properly update infographic after unlock

[John McAleely]

@Pat, where does this belong?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-greeter in Ubuntu.
https://bugs.launchpad.net/bugs/1378814

Title:
  greeter does not properly update infographic after unlock

Status in the base for Ubuntu mobile products:
  Confirmed
Status in unity-greeter package in Ubuntu:
  Confirmed

Bug description:
  This bug has been here since forever, but really needs to get cleaned
  up for rtm.

  Steps to reproduce:
  - send 2 text messages
  - lock your phone
  - unlock your phone
  - confirm infographic says 2 text messages sent today
  - lock your phone for the night and go to sleep
  - unlock your phone the next day

  Expected results:
  - infographic should be cleared, or show relevant information for today

  Actual results:
  - infographic still says 2 text messages sent today

  When the phone is unlocked the greeter should update the infographic
  text

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

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

[Desktop-packages] [Bug 1465806] Re: Alarms not shown in indicator datetime after upgrade to ota4

[John McAleely]

@pmcgowan, is this in vivid-overlay? It's hard to tell from the bug text

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evolution-data-server in Ubuntu.
https://bugs.launchpad.net/bugs/1465806

Title:
  Alarms not shown in indicator datetime after upgrade to ota4

Status in the base for Ubuntu mobile products:
  Fix Released
Status in evolution-data-server package in Ubuntu:
  Fix Released
Status in indicator-datetime package in Ubuntu:
  Fix Released
Status in indicator-datetime source package in Vivid:
  New

Bug description:
  STEPS:
  1. Flash image 22 from stable
  2. Set a one time alarm and a recurring alarm
  3. Update to 23

  EXPECTED:
  Alarms should be up and running as expected

  ACTUAL:
  Alarms are not shown in the datetime indicator but show up as active in and 
available in the clock.  Because the indicator is in control of the alarm 
trigger the alarm never goes off.

  TEMPORARY WORK AROUND:
  Disable and enable all your alarms and then they work as expected.

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

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