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

2018-11-12 Thread Daniel van Vugt
Ubuntu Touch is no longer supported.

** Changed in: pulseaudio (Ubuntu)
   Status: Confirmed => Won't Fix

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/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:
  Won't Fix

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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


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

2018-11-12 Thread Daniel van Vugt
** Changed in: pulseaudio (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  Multiple bluetooth audio devices break audio routing

Status in Canonical System Image:
  Confirmed
Status in bluez package in Ubuntu:
  Won't Fix
Status in pulseaudio package in Ubuntu:
  Won't Fix
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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1398560] Re: Music playback randomly stops working

2018-11-12 Thread Daniel van Vugt
Ubuntu Touch is no longer supported.

** Changed in: pulseaudio (Ubuntu)
   Status: Incomplete => Won't Fix

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

Title:
  Music playback randomly stops working

Status in Canonical System Image:
  Fix Released
Status in Media Hub:
  Invalid
Status in qtubuntu-camera:
  New
Status in pulseaudio package in Ubuntu:
  Won't Fix
Status in ubuntu-touch-session package in Ubuntu:
  Fix Released
Status in ubuntu-touch-session package in Ubuntu RTM:
  Fix Released

Bug description:
  While listening to music media-hub stops randomly. Restart of the job
  and reboots don't fix it. Video works fine. Also, 320 kbps music
  pauses randomly, might be related. I have also talked about this on
  the mailing list.

  This is probably a side effect of bug 1438486 (or similar), as pulse
  is working but without sound just for the multimedia related roles.

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

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


[Touch-packages] [Bug 1421448] Re: problem pairing Jabra BT2050

2018-11-12 Thread Daniel van Vugt
Ubuntu Touch is no longer supported.

** Changed in: bluez (Ubuntu)
   Status: New => Won't Fix

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

Title:
  problem pairing Jabra BT2050

Status in bluez package in Ubuntu:
  Won't Fix

Bug description:
  This is tested on:

  nexus4 (vivid-proposed) #96
  bq (stable) #17

  Steps taken:

  1. turn on Bluetooth on device.
  2. put Jabra BT2050 on pairing mode.
  3. click on "Jabra BT2050..." in Bluetooth setting on device
  4. prompted with new page, click on "Connect" button.
  5. New popover with this message "Bluetooth Pairing Request  PIN for 'Jabra 
BT2050'   [textfield: ], click on "Pair" button.
  [ at this point new handset is added to the list and "connected" sound is 
played in handset but whole settings UI on device is frozen for about 15sec. 
bluetooth icon in topbar is white-connected. ]
  6. In bluetooth setting Click on ">" next to Jabra BT2050 to see more info.
  7. Status on that page is saying: "Connecting..." while button at the bottom 
says: "Disconnect" see attached picture.
  8. open Phone app and try to call anyone, sound is coming out from phone 
speakers.

  After "forgetting this device" and pairing it again for few times I
  managed to connect it and it worked but only to make one phone call
  after I hangup I wasn't able to use bluetooth again.

  If I good remember this time then it worked I was't prompted for
  pairing password.

  Any more info you need please let me know.
  I must add that this handset works well on nexus4 and other phones.

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

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


[Touch-packages] [Bug 1586302] Re: Bluetooth and other issues connecting to Bluetooth speaker

2018-11-12 Thread Daniel van Vugt
Ubuntu Touch is no longer supported.

** Changed in: bluez (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  Bluetooth and other issues connecting to Bluetooth speaker

Status in Canonical System Image:
  Confirmed
Status in bluez package in Ubuntu:
  Won't Fix

Bug description:
  Aquaris E4.5 @ OTA 10.1

  Attempting to connect to EasyAcc Bluetooth Speaker

  (https://www.amazon.co.uk/EasyAcc-Portable-Rechargeable-Bluetooth-
  
Microphone/dp/B00JK6MQEI/ref=sr_1_3?ie=UTF8&qid=1464297589&sr=8-3&keywords=easyacc)

  Phone finds speaker and connects (no pin required). Audio is heard
  from the speaker for 1 second, then stops.

  The volume control stills says audio is routed to bluetooth speaker,
  but no sound output.

  Bluetooth cannot then be turned off (button appears to function to
  “off” position , but bluetooth remains active and button returns to
  “on” position after exactly 30 seconds)

  Attempting to switch to flight mode – the button “greys out” for 30
  seconds, then appears as “on”. Wifi is disconnected but mobile network
  connections are still active.

  Switching off the bluetooth speaker has no effect, the phone still
  appears to be connected to it.

  Attempting  to restart does not work – The phone switches off and does
  not restart. Hard reset is required to get the phone to boot again.
  Also if the phone is powered off, it will not restart until a hard
  reset is performed.

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

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


[Touch-packages] [Bug 1394105] Re: Sometimes significant lag between snap dialog and ringtone start

2018-11-12 Thread Daniel van Vugt
Ubuntu Touch is no longer supported.

** Changed in: pulseaudio (Ubuntu)
   Status: Incomplete => Won't Fix

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

Title:
  Sometimes significant lag between snap dialog and ringtone start

Status in Canonical System Image:
  Won't Fix
Status in indicator-messages package in Ubuntu:
  Invalid
Status in ofono package in Ubuntu:
  Expired
Status in pulseaudio package in Ubuntu:
  Won't Fix

Bug description:
  Version: ubuntu-touch/ubuntu-rtm/14.09-proposed r140 krillin

  When testing a large number of phone calls it could be seen that on
  certain calls there would be a significant delay between the snap
  decision dialog being displayed and the ringtone beginning to play.

  In extreme circumstances this could cause calls to be missed as there
  would not be enough time to answer.

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

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


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

2018-11-12 Thread Daniel van Vugt
Ubuntu Touch is no longer supported.

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

Title:
  Call audio is not routed to headset with HFP

Status in Canonical System Image:
  Won't Fix
Status in bluez package in Ubuntu:
  Won't Fix
Status in media-hub package in Ubuntu:
  Invalid
Status in ofono package in Ubuntu:
  Won't Fix
Status in pulseaudio package in Ubuntu:
  Won't Fix

Bug description:
  With bluez 5.33 on Nexus 4 and silo 43 installed:

  * pair and connect a headset over HFP
  * Establish an outgoing call or accept an incoming one
  * Once the call is established the call audio isn't routed through the 
handsfree device

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

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


[Touch-packages] [Bug 1492368] Re: Calls made through car bluetooth drop out

2018-11-12 Thread Daniel van Vugt
Ubuntu Touch is no longer supported.

** Changed in: bluez (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  Calls made through car bluetooth drop out

Status in Canonical System Image:
  Confirmed
Status in bluez package in Ubuntu:
  Won't Fix

Bug description:
  Calls made through car bluetooth connection always drop out after
  about 3 minutes. The phone becomes unusable and I have to hold the
  power button for 15 seconds to reboot it. Car is Skoda Octavia.

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

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


[Touch-packages] [Bug 1578178] Re: Caller ID not displayed using in-car bluetooth system when recieving a call

2018-11-12 Thread Daniel van Vugt
Ubuntu Touch is no longer supported.

** Changed in: bluez (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  Caller ID not displayed using in-car bluetooth system when recieving a
  call

Status in bluez package in Ubuntu:
  Won't Fix

Bug description:
  When the phone is connected to the in-car hands free bluetooth system and I 
receive a call, I expect the caller ID to be displayed in the car's 
infotainment system. This was working until OTA9, which has made the system 
display "Unknown" when receiving a call.
  I can use the phone's contacts from the car, so no everything is broken in 
that respect.

  Would a verbose bluetooth log be helpful
  (https://wiki.ubuntu.com/DebuggingBluetooth), or would something else
  be required to help further investigate?

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

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


[Touch-packages] [Bug 1364647] Re: Can't hear clock alarm when headphones are plugged in but not in your ears

2018-11-12 Thread Daniel van Vugt
Ubuntu Touch is no longer supported.

** Changed in: pulseaudio (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  Can't hear clock alarm when headphones are plugged in but not in your
  ears

Status in Band-aids for Ubuntu Phone:
  In Progress
Status in Canonical System Image:
  Confirmed
Status in Ubuntu Clock App:
  Invalid
Status in Ubuntu UX:
  Triaged
Status in indicator-datetime package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Won't Fix

Bug description:
  When a bluetooth or wired headset the phone embedded speakerphone
  should ring anyway as you probably won't wear an headset while
  sleeping, while you prefer keeping your headset connected all the
  times.

  -- SOLUTION --
  Alarms should *always* be played to the speaker phones, as well as in the 
wired/wireless headset.

  (The equivalent for the ringtone is bug 1583981.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/band-aids-uphone/+bug/1364647/+subscriptions

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


[Touch-packages] [Bug 1335342] Re: Image #100 is sufferring audio dropouts and high CPU usage on mako

2018-11-12 Thread Daniel van Vugt
Ubuntu Touch is no longer supported.

** Changed in: pulseaudio (Ubuntu)
   Status: New => Won't Fix

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

Title:
  Image #100 is sufferring audio dropouts and high CPU usage on mako

Status in pulseaudio package in Ubuntu:
  Won't Fix

Bug description:
  1) Ensure the device is on utopic #100 or above
  2) Start the music app
  3) Start playing music (flac files are easier to hear)
  4) Notice that audible drops/pops/glitches can be heard in the output 
(changing the volume also causes more drops)
  5) Note when running a terminal with top that the CPU usage of pulseaudio is 
~25% (this may be related to the dropouts)

  It was expected that the audio should be played without any dropouts.

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

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


[Touch-packages] [Bug 1435040] Re: Ubuntu Phone does not connect to car-bluetooth

2018-11-12 Thread Daniel van Vugt
Ubuntu Touch is no longer supported.

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

Title:
  Ubuntu Phone does not connect to car-bluetooth

Status in Canonical System Image:
  Won't Fix
Status in bluez package in Ubuntu:
  Won't Fix
Status in ubuntu-system-settings package in Ubuntu:
  Won't Fix

Bug description:
  With my FORD Focus Car, pairing does not work. The bluetooth system in
  the car searches for devices and shows "Aquaris E4.5 Ubuntu Edition"
  and then prompts me to connect with a 4-digit pin code, but the Ubuntu
  phone doesn't react at all and after a while the car system says that
  it failed to connect.

  image: 20150310-3201c0a
  KRILIN01A-S15A_BQ_L100EN_2020_150312
  OS Build 20

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

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


[Touch-packages] [Bug 1579025] Re: Nexus4 Car Kit com_comp V12b reboots when tries to reconnect

2018-11-12 Thread Daniel van Vugt
Ubuntu Touch is no longer supported.

** Changed in: bluez (Ubuntu)
   Status: New => Won't Fix

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

Title:
  Nexus4 Car Kit com_comp V12b reboots when tries to reconnect

Status in bluez package in Ubuntu:
  Won't Fix

Bug description:
  When I detect the hands free blue tooth generic comf_comp V12b and enter pin 
it connects great.
  After turning off the car and reentering, the Nexus4 dual boot touch reboots 
into Android when it automatically tries to reconnect to the hands free unit.
  From Android it says Version 12 stable ubuntu=20160401.1 but also occurred on 
previous version. 
  In the Ubuntu About it say 15.04 (OTA-10)

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

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


[Touch-packages] [Bug 1359806] Re: mismatched audio profile when a call hits and music is playing

2018-11-12 Thread Daniel van Vugt
Ubuntu Touch is no longer supported.

** Changed in: pulseaudio (Ubuntu)
   Status: New => Won't Fix

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

Title:
  mismatched audio profile when a call hits and music is playing

Status in pulseaudio package in Ubuntu:
  Won't Fix

Bug description:
  STEPS:
  1. Open music app or play music from a scope
  2. Recieve a call
  3. The audio is switched to the earpiece
  4. now end the call and restart the music.

  EXPECTED:
  I expect the music to playback from the loud speaker

  ACTUAL:
  The music continues to play but through the ear piece.

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

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


[Touch-packages] [Bug 1547978] Re: Bluetooth does not forward metadata to slave devices.

2018-11-12 Thread Daniel van Vugt
Ubuntu Touch is no longer supported.

** Changed in: bluez (Ubuntu)
   Status: New => Won't Fix

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

Title:
  Bluetooth does not forward metadata to slave devices.

Status in Canonical System Image:
  Confirmed
Status in bluez package in Ubuntu:
  Won't Fix

Bug description:
  Tested using the bluetooth stereo in a Mitsubishi FUSO Rosa and a Ford
  Territory (both less than three years old, Australian models), using a
  bluetooth-stereo (A2DP) connection.

  With other (Android) devices, the Mitsubishi FUSO Rosa displays
  complete metadata, whilst the Ford Territory displays only basic
  metadata (artist/group and track information).

  bq Aquaris E5 HD Ubuntu Edition:
  * OS build number: OTA-9
  * Ubuntu Image part: 20160123.1
  * Ubuntu build description: Ubuntu 15.04 - armhf (20160123-115651)
  * Device Image part: 20160108-efc96d8
  * Device build description: VEGETA01A-S23A_BQ_L100EN_2009_160123
  * Customization Image part: 20160111-926-36--vivid

  Reproduce:
  - "Pair" Ubuntu mobile device with another device, which has a display and is 
capable of displaying metadata (artist/group, track, album and/or coverart 
information) from bluetooth audio input.
  - Play music on Ubuntu mobile device.

  Result:
  Music plays through slave device, however no metadata is displayed.

  Expectation:
  To be able to see artist/group, track, album and/or coverart information 
whilst listening to music over a bluetooth connection.

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

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


[Touch-packages] [Bug 1432788] Re: Race in vivid means sometimes bluetooth is no available

2018-11-12 Thread Daniel van Vugt
Ubuntu Touch is no longer supported.

** Changed in: bluez (Ubuntu)
   Status: New => Won't Fix

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

Title:
  Race in vivid means sometimes bluetooth is no available

Status in Canonical System Image:
  Invalid
Status in bluez package in Ubuntu:
  Won't Fix

Bug description:
  STEPS:
  1. Flash a fresh image of vivid on a krillin device
  2. Check if bluetooth is on
  3. Reboot

  EXPECTED:
  I always expect bluetooth to be on

  ACTUAL:
  Bluetooth was turned off, I couldn't tur it on, when I rebooted it was on how 
ever it wouldn't connect to anything.

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

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


[Touch-packages] [Bug 1479453] Re: IN CAR: Bluetooth is connected but occasionally a call comes in and there is no audio on bluetooth

2018-11-12 Thread Daniel van Vugt
Ubuntu Touch is no longer supported.

** Changed in: bluez (Ubuntu)
   Status: Confirmed => Won't Fix

** Changed in: pulseaudio (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  IN CAR: Bluetooth is connected but occasionally a call comes in and
  there is no audio on bluetooth

Status in Canonical System Image:
  Confirmed
Status in bluez package in Ubuntu:
  Won't Fix
Status in pulseaudio package in Ubuntu:
  Won't Fix

Bug description:
  STEPS:
  Requirements: DUT, a second device and a car that supports bluetooth phones 
(Skoda Superb 2013 in my case)

  1. Connect the DUT to the car
  2. Receive multiple calls

  EXPECTED:
  I expect the call audio to always be routed through the car audio and be 
audible

  ACTUAL:
  After a number of calls all of a sudden you can accept the call but you get 
no audio from the call at all, the mic is still working as expected.

  VERSIONS:
  current build number: 71
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.en
  last update: 2015-07-28 18:01:08
  version version: 71
  version ubuntu: 20150728
  version device: 20150709-8965e37
  version custom: 20150716-819-8-42

  MODIFICATIONS:
  Installation of silo19 for in car bt fix

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

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


[Touch-packages] [Bug 1546994] Re: Backward key on Bluetooth mouse causes Ubuntu-Touch to reboot.

2018-11-12 Thread Daniel van Vugt
Ubuntu Touch is no longer supported.

** Changed in: bluez (Ubuntu)
   Status: New => Won't Fix

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

Title:
  Backward key on Bluetooth mouse causes Ubuntu-Touch to reboot.

Status in bluez package in Ubuntu:
  Won't Fix

Bug description:
  First I connect a bluetooth mouse to my UbuntuPhone.

  Then everything works pretty fine until I use the 'backward' key on the 
mouse, which is normally used to navigate in web browser. If I press this 
'backward' key, the UbuntuPhone just crashes and restarts immediatly.  
  It is the same for the forward key.

   I use the Memteq Bluetooth Mouse: http://www.amazon.com/Wireless-
  Bluetooth-Ergonomic-Computer-Bluetooth-
  
enabled/dp/B00WM9MNMA/ref=sr_1_4?ie=UTF8&qid=1455796902&sr=8-4&keywords=memteq+bluetooth+mouse

  This happened on Ubuntu-Touch-Device Nexus 4 with OTA9 installed.

  If any logfiles or further information are needed, just ask me. :-)

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

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


[Touch-packages] [Bug 1303721] Re: audio can be heard despite volume set to minimum #280

2018-11-12 Thread Daniel van Vugt
Ubuntu Touch is no longer supported.

** Changed in: pulseaudio (Ubuntu)
   Status: New => Won't Fix

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

Title:
  audio can be heard despite volume set to minimum  #280

Status in pulseaudio package in Ubuntu:
  Won't Fix

Bug description:
  I set my volume to very low while running music-app autopilot tests
  because the tracks are annoying when heard repeatedly.

  I dialled down the volume (as can be seen in the screenshot) with the
  hardware Vol- button.

  I then ran the Music app autopilot tests and the music played at a
  loud / normal volume, that I'd expect if the sound was turned way up.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: pulseaudio 1:4.0-0ubuntu11
  Uname: Linux 3.4.0-5-mako armv7l
  AlsaInfo: This script requires lspci. Please install it, and re-run this 
script.
  ApportVersion: 2.14.1-0ubuntu1
  Architecture: armhf
  AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser'
  CurrentDmesg: dmesg: klogctl failed: Operation not permitted
  Date: Mon Apr  7 11:32:26 2014
  InstallationDate: Installed on 2014-04-07 (0 days ago)
  InstallationMedia: Ubuntu Trusty Tahr (development branch) - armhf (20140407)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1551858] Re: [bluetooth] Connecting to Apple BT keyboard fails due to PIN prompt

2018-11-12 Thread Daniel van Vugt
Ubuntu Touch is no longer supported.

** Changed in: bluez (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  [bluetooth] Connecting to Apple BT keyboard fails due to PIN prompt

Status in Canonical System Image:
  Confirmed
Status in bluez package in Ubuntu:
  Won't Fix
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed

Bug description:
  Connecting to the latest generation Apple BT keyboard ( the one with
  the USB port & no batteries ) fails on an Ubuntu Touch device, as when
  you press the "Connect" button on the device page, a dialog titled
  "Bluetooth Pairing Request" is displayed, with the following text:

  Please confirm that the PIN displayed on 'Magic Keyboard' matches this
  one: XX

  The dialog has "Cancel" and "Confirm PIN" buttons.

  The keyboard has no display on which a PIN could be displayed.

  When using other devices ( Ubuntu Desktop 15.10, 16.04, Android, OS X,
  ... ) to connect this keyboard all that's necessary is to click/press
  the 'Connect' button in the appropriate place, and the keyboard
  automatically connects, and is usable with no other actions required
  from the user.

  Reproduced on krillin ( rc-proposed/bq-aquris.en/270 ) which has bluez
  5.36-0ubuntu2~overlay1 installed.

  Reproduced on arale ( rc-proposed/meizu.en/258 ) which has bluez 5.37
  installed from silo 39.

  Note, after dismissing the dialog, subsequent attempts to connect may
  not re-display the PIN dialog, instead nothing happens.  I've found
  that this requires power cycling the keyboard to clear and cause the
  PIN dialog to be displayed again.

  [bluetooth]# show
  Controller B8:64:91:48:2B:1E
Name: Aquaris E4.5 Ubuntu Edition
Alias: Aquaris E4.5 Ubuntu Edition
Class: 0x1c020c
Powered: yes
Discoverable: no
Pairable: yes
UUID: Headset AG(1112--1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb)
UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb)
UUID: PnP Information   (1200--1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
UUID: Audio Source  (110a--1000-8000-00805f9b34fb)
UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
UUID: Message Notification Se.. (1133--1000-8000-00805f9b34fb)
UUID: Phonebook Access Server   (112f--1000-8000-00805f9b34fb)
Modalias: usb:v1D6Bp0246d0525
Discovering: no

  [bluetooth]# devices
  Device 18:EE:69:21:6C:D3 18-EE-69-21-6C-D3
  Device DE:76:E2:04:9D:6F BB-9D6F
  Device 7C:D1:C3:1C:B4:03 7C-D1-C3-1C-B4-03
  Device 7C:D1:C3:19:2B:D8 7C-D1-C3-19-2B-D8
  Device 84:38:35:67:0C:3D ubuntu-0
  Device 04:69:F8:C2:A0:09 tony espy’s Keyboard
  Device 00:21:3C:A0:14:A6 Jawbone ERA
  Device 1C:1A:C0:B2:9A:D7 1C-1A-C0-B2-9A-D7

  Device info *before* pairing attempt:

  Device 04:69:F8:C2:A0:09
Name: tony espy’s Keyboard
Alias: tony espy’s Keyboard
Class: 0x002540
Icon: input-keyboard
Paired: no
Trusted: no
Blocked: no
Connected: no
LegacyPairing: no
Modalias: bluetooth:v004Cp0267d0066

  No changes in any of the attributes after *after* the pairing attempt
  ( output of info command is the same ).

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

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


[Touch-packages] [Bug 1551131] Re: Cannot pair Jabra Classic headset

2018-11-12 Thread Daniel van Vugt
Ubuntu Touch is no longer supported.

** Changed in: bluez (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  Cannot pair Jabra Classic headset

Status in bluez package in Ubuntu:
  Won't Fix

Bug description:
  I cannot pair a jabra classic headset. When I try to connect,
  initially it all looks good: the bluetooth icon on the top bar changed
  to a white background. But after a couple of seconds the device is
  disconnected.

  This headset used to work well previously, although I do not remember
  if it was with bluez 4 or 5 too.

  This happens in

  current build number: 269
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2016-02-29 08:59:57
  version version: 269
  version ubuntu: 20160227
  version device: 20160108-efc96d8
  version custom: 20160111-926-36--vivid

  I see errors like this in syslog (see attached file):

  Feb 29 08:27:43 ubuntu-phablet bluetoothd[902]: Not enough free handles to 
register service
  Feb 29 08:27:43 ubuntu-phablet bluetoothd[902]: Error adding Link Loss service
  Feb 29 08:27:43 ubuntu-phablet bluetoothd[902]: Not enough free handles to 
register service
  Feb 29 08:27:43 ubuntu-phablet bluetoothd[902]: message repeated 2 times: [ 
Not enough free handles to register service]
  Feb 29 08:27:43 ubuntu-phablet bluetoothd[902]: Current Time Service could 
not be registered
  Feb 29 08:27:43 ubuntu-phablet bluetoothd[902]: gatt-time-server: 
Input/output error (5)
  Feb 29 08:27:43 ubuntu-phablet bluetoothd[902]: Not enough free handles to 
register service
  Feb 29 08:27:43 ubuntu-phablet bluetoothd[902]: Not enough free handles to 
register service
  Feb 29 08:27:43 ubuntu-phablet bluetoothd[902]: Sap driver initialization 
failed.
  Feb 29 08:27:43 ubuntu-phablet bluetoothd[902]: sap-server: Operation not 
permitted (1)

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

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


[Touch-packages] [Bug 1762233] Re: Xorg freeze

2018-11-12 Thread Daniel van Vugt
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:

1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where
ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
Do you find any links to recent problems on that page? If so then please
send the links to us.

3. If step 2 also failed then apply the workaround from bug 994921,
reboot, reproduce the crash, and retry step 1.

Please take care to avoid attaching .crash files to bugs as we are
unable to process them as file attachments. It would also be a security
risk for yourself.

** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)

** Changed in: xorg-server (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  Xorg freeze

Status in xorg-server package in Ubuntu:
  Won't Fix

Bug description:
  system completely freezes in middle of doing something 
  cant switch even to tty1 or any other in order to restart the lightdm service 
  nothing works or respond
  it needs a hard shutdown.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16
  Uname: Linux 4.13.0-38-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CompizPlugins: 
[core,ccp,composite,opengl,decor,dbus,snap,mousepoll,resize,move,gnomecompat,grid,compiztoolbox,regex,imgpng,animation,fade,place,vpswitch,workarounds,expo,scale,ezoom,session,switcher,widget]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Mon Apr  9 00:14:54 2018
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.13.0-37-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.13.0-38-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GconfCompiz:
   /apps/compiz-1/general:
 /apps/compiz-1/general/screen0:
  /apps/compiz-1/general/screen0/options:
   active_plugins = 
[core,ccp,composite,opengl,decor,dbus,snap,mousepoll,resize,move,gnomecompat,grid,compiztoolbox,regex,imgpng,animation,fade,place,vpswitch,workarounds,expo,scale,ezoom,session,switcher,widget]
  GpuHangFrequency: Very infrequently
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 12) (prog-if 00 [VGA controller])
 Subsystem: Dell Core Processor Integrated Graphics Controller [1028:0447]
  InstallationDate: Installed on 2016-10-21 (534 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Dell Inc. Inspiron N5010
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-38-generic 
root=UUID=77904eae-fd02-415d-9877-402e4ea84d13 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/19/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A15
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A15
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A15
  dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd07/19/2011:svnDellInc.:pnInspironN5010:pvrA15:rvnDellInc.:rn:rvrA15:cvnDellInc.:ct8:cvrA15:
  dmi.product.name: Inspiron N5010
  dmi.product.version: A15
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~17.10.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~17.10.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1762233/+subscriptions

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


[Touch-packages] [Bug 1562269] Re: On Ubuntu touch start bluetooth / stop bluetooth hangs

2018-11-12 Thread Daniel van Vugt
Ubuntu Touch is no longer supported.

** Changed in: bluez (Ubuntu)
   Status: New => Won't Fix

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

Title:
  On Ubuntu touch start bluetooth / stop bluetooth hangs

Status in bluez package in Ubuntu:
  Won't Fix

Bug description:
  When trying to start or stop the bluetooth subsystem, the start or
  stop command just hangs.

  A couple of upgrades back, we already *had* a similar situation, now
  it re-appeared.

  However, when Control-C'ing the start command, and then trying it
  again, it says "start: Job is already running: bluetooth"

  Likewise, when Control-C'ing the stop command and then trying it
  again, it says:  "stop: Job has already been stopped: bluetooth"

  
  root@alains-pocket-penguin:~# lsb_release -rd
  Description:Ubuntu 15.04
  Release:15.04
  root@alains-pocket-penguin:~# apt-cache policy bluez
  bluez:
Installed: 5.37-0ubuntu5~overlay1
Candidate: 5.37-0ubuntu5~overlay1
Version table:
   *** 5.37-0ubuntu5~overlay1 0
 1001 
http://ppa.launchpad.net/ci-train-ppa-service/emergency-snapshot/ubuntu/ 
vivid/main armhf Packages
  100 /var/lib/dpkg/status
   4.101-0ubuntu25 0
  500 http://ports.ubuntu.com/ubuntu-ports/ vivid/main armhf Packages

  What I expected to happen
   start bluetooth should start the bluetooth subsystem, and then return as 
quickly as possible
   stop bluetooth should stop the bluetooth subsystem, and then return as 
quickly as possible

  What happened instead
start bluetooth hangs... and after control-C'ing it, status bluetooth is 
"bluetooth start/starting"
stop bluetooth hangs... and after control-C'ing it, status bluetooth is 
"bluetooth stop/starting"

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

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


[Touch-packages] [Bug 1543960] Re: virtual keyboard inserts endless "1" in text field

2018-11-12 Thread Daniel van Vugt
Ubuntu Touch is no longer supported.

** Changed in: bluez (Ubuntu)
   Status: New => Won't Fix

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

Title:
  virtual keyboard inserts endless "1" in text field

Status in Canonical System Image:
  Confirmed
Status in bluez package in Ubuntu:
  Won't Fix

Bug description:
  Ubuntu Touch OTA 9 on BQ Aquarie E4.5
  When the phone runs for a while - as soon as a text-field is selected and the 
virtual keyboard shows up, it is automatically filled with 1 (number 1). No 
possibility to interrupt the process.  All applications using the virtual 
keyboard are affected.
  By example the dial-pad is not affected but browser, search button etc. 
everything gets filled with 1.

  Only fix so far is to reboot the phone.
  Cause yet unknown, and no direct way identified that triggers this behavior.
  Still searching.

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

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


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

2018-11-12 Thread Daniel van Vugt
Ubuntu Touch is no longer supported.

** Changed in: bluez (Ubuntu)
   Status: Confirmed => Won't Fix

** Changed in: pulseaudio (Ubuntu)
   Status: Confirmed => Won't Fix

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/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:
  Won't Fix
Status in phone-app package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Won't Fix

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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1524939] Re: Using telephony in car with bluetooth not possible after second connection

2018-11-12 Thread Daniel van Vugt
Ubuntu Touch is no longer supported.

** Changed in: bluez (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  Using telephony in car with bluetooth not possible after second
  connection

Status in bluez package in Ubuntu:
  Won't Fix
Status in ofono package in Ubuntu:
  Confirmed

Bug description:
  I've a problem using telephony with bluetooth in my car

  I explain : 
  I can connect in bluetooth with my car
  At the first connection everything works fine (I can do a call, play music 
normally in car speakers)
  At the second automatic connection (ie. I leave the car and go away, lost the 
bluetooth connection, and come back in the car --> the phone reconnect 
automatically to the car bluetooth)

  At this second connection, I loose the possibility to do a call with
  audio in car speakers. Telephony app detect the bluetooth well
  (bluetooth icon in app), but this doesn’t cut the sound already
  playing in car speaker and phone call is not redirected to car
  speakers. When I hangout the sound playing in car speaker is cut (for
  2sec) but if do an other call this still not working.

  
  So to solve the problem, I have to manually disconnect from car bluetooth and 
reconnect again (in settings). If I just turn off bluetooth then turn it back 
on, the problem is not solved.

  Does someone have the same issue or am I not clear ? 
  I could try to add a syslog if it could help.

  Device : mako rc-proposed; Bluetooth car module :  XCARLink Smart BT
  in 207 Peugeot

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

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


[Touch-packages] [Bug 1519681] Re: Some media keys on keyboards do not work as expected

2018-11-12 Thread Daniel van Vugt
Ubuntu Touch is no longer supported.

** Changed in: bluez (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  Some media keys on keyboards do not work as expected

Status in The Avila project:
  Confirmed
Status in Band-aids for Ubuntu Phone:
  New
Status in Canonical System Image:
  Confirmed
Status in Canonical Pocket Desktop:
  New
Status in bluez package in Ubuntu:
  Won't Fix
Status in qtubuntu-media package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  $ system-image-cli -i
  current build number: 75
  device name: mako
  channel: ubuntu-touch/rc-proposed/ubuntu-pd
  last update: 2015-11-24 05:39:02
  version version: 75
  version ubuntu: 20151124
  version device: 20150911
  version custom: 20150929-2-vivid

  Steps to reproduce:
  1. Windowed mode is enabled with BT mouse/keyboard connected
  2. Launch music app to play all of a playlist
  3. Press Pause/Play, Fast forward/Rewind keys on BT keyboard

  Actual results:
  Press media keys(Pause/Play, Fast forward/Rewind) on BT keyboard has no 
control for playback 
  currently only Volume Up/ Down and Mute/Unmute media keys work

  BT keyboard type: Logitech K480 and Rapoo E6350

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

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


[Touch-packages] [Bug 1535646] Re: BLUETOOTH MOUSE: with a mouse connected lock the device and leave for some time when you return the mouse is in sleep mode and the phone is in normal not windowed mo

2018-11-12 Thread Daniel van Vugt
Ubuntu Touch is no longer supported.

** Changed in: bluez (Ubuntu)
   Status: New => Won't Fix

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

Title:
  BLUETOOTH MOUSE: with a mouse connected lock the device and leave for
  some time when you return the mouse is in sleep mode and the phone is
  in normal not windowed mode

Status in Canonical Pocket Desktop:
  New
Status in bluez package in Ubuntu:
  Won't Fix

Bug description:
  STEPS:
  1. Flash a device
  2. Connect a bluetooth mouse
  3. Let the device sleep
  4. Leave it for a couple of minutes
  5. Wake the device do not move the mouse
  6. Device is in phone mode
  7. UNlock the device and move the mouse
  8. Device after 30+ seconds flips back to windowed mode

  EXPECTED:
  When a mouse is connected I expect the device to always be in windows mode 
regardless of if the mouse is in sleep mode

  ACTUAL:
  When the mouse is in sleep mode it is like it is disconnected and the 
windowed mode is no longer active.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-pocket-desktop/+bug/1535646/+subscriptions

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


[Touch-packages] [Bug 1535654] Re: BLUETOOTH MOUSE: with a mouse connected leave the device with a window on top

2018-11-12 Thread Daniel van Vugt
Ubuntu Touch is no longer supported.

** Changed in: bluez (Ubuntu)
   Status: New => Won't Fix

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

Title:
  BLUETOOTH MOUSE: with a mouse connected leave the device with a window
  on top

Status in bluez package in Ubuntu:
  Won't Fix

Bug description:
  STEPS:
  1. Flash a device
  2. Connect a bluetooth mouse
  3. Open the web browser (It should be in windowed mode)
  4. Goto ubuntu.com and now leave the device and watch the window
  5. Around the time that the screen starts to dim the Window wil flash 
Fullscreen and then back to windowed mode again

  EXPECTED:
  I expect the device to remain in windowed mode as long as the mouse is 
connected

  ACTUAL:
  The mouse is allowed to disconnect while idle meaning that normal mode is 
triggered this then triggers the system to rewake and register the mouse again 
and flips back to windowed mode.

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

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


[Touch-packages] [Bug 1528856] Re: bluetooth & car handsfree issue

2018-11-12 Thread Daniel van Vugt
** Changed in: bluez (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  bluetooth & car handsfree issue

Status in bluez package in Ubuntu:
  Won't Fix

Bug description:
  When playing music through headphone output connected to aux car radio
  input and going to call someone while driving, i only hear some
  "beeps" and apparently the call was succesfull but i can't hear
  anything and no sound is transmitted . In the phone screen appears the
  speaker icon with an x (like there is no speaker connected) but phone
  and car are paired correctly.

  In addition to, when to SIM cards are inserted y only receive call
  through bluetooth for the one i have selected as default, for the
  other SIM, ring tones sounds in phone speaker and no through bluetooth
  device.

  Device: BQ Aquaris E4.5 Ubuntu Edition
  Channel: RC-proposed
  Version: r604

  Thanks in advance.

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

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


[Touch-packages] [Bug 1603150] Re: bluetooth HFP static noise

2018-11-12 Thread Daniel van Vugt
Ubuntu Touch is no longer supported.

** Changed in: bluez (Ubuntu)
   Status: Confirmed => Won't Fix

** Changed in: pulseaudio (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  bluetooth HFP static noise

Status in Canonical System Image:
  New
Status in bluez package in Ubuntu:
  Won't Fix
Status in ofono package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Won't Fix

Bug description:
  When I have a headset connected and a phone call starts, all I hear is
  static noise. Seems like the wrong codec is selected.

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

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


[Touch-packages] [Bug 1762014] Re: apport

2018-11-12 Thread Daniel van Vugt
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:

1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where
ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
Do you find any links to recent problems on that page? If so then please
send the links to us.

3. If step 2 also failed then apply the workaround from bug 994921,
reboot, reproduce the crash, and retry step 1.

Please take care to avoid attaching .crash files to bugs as we are
unable to process them as file attachments. It would also be a security
risk for yourself.

** Package changed: xorg (Ubuntu) => ubuntu

** Changed in: ubuntu
   Status: New => Incomplete

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

Title:
  apport

Status in Ubuntu:
  Incomplete

Bug description:
  program crash

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Sat Apr  7 17:35:23 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.2.8, 4.15.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Acer Incorporated [ALI] HD Graphics 620 [1025:118c]
  InstallationDate: Installed on 2018-04-06 (1 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
  MachineType: Acer Swift SF314-52
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic 
root=/dev/mapper/kubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/18/2017
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.06
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Suntory_KL
  dmi.board.vendor: KBL
  dmi.board.version: V1.06
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.06:bd07/18/2017:svnAcer:pnSwiftSF314-52:pvrV1.06:rvnKBL:rnSuntory_KL:rvrV1.06:cvnAcer:ct10:cvrChassisVersion:
  dmi.product.family: Swift 3
  dmi.product.name: Swift SF314-52
  dmi.product.version: V1.06
  dmi.sys.vendor: Acer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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


[Touch-packages] [Bug 1799206] Re: SRU: update python3.6 to the new minor release 3.6.7

2018-11-12 Thread Matthias Klose
** Description changed:

  SRU: update python3.6 to the new minor release 3.6.7
  
  See LP: #1792143 for the rationale, going one minor release ahead (and
  planning to do 3.6.8 in January, the last source release from the 3.6
  branch).
  
  [Impact]
  Provide the branch updates for the stable 3.6 branch in the LTS release.
  
  [Regression Potential]
  There is regression potential, but this version is in use in 18.10, which 
didn't show regressions.
  
  [Test Case]
  No regressions in the Python 3.6 test suite, no regressions in the autopkg 
tests
+ 
+ Failing autopkg tests:
+  - http://autopkgtest.ubuntu.com/packages/p/python-asdf/bionic/armhf
+failed before, flaky autopkg tests history, now passes in disco.
+  - snapcraft: amd64 and i386 try to download some rust installation,
+which then fails to build some downloaded code. This doesn't look
+like a reliable test.
+  - python-mechanicalsoup: unrelated, fails in both 2.7 and 3.6.
+Fixed in cosmic, filed LP: #1802835 for a fix anyway.
+  - http://autopkgtest.ubuntu.com/packages/l/lxd/bionic/arm64
+doesn't look like a regression in the autopkg test history.
+pinged the lxd maintainers, but no response yet.
+  - ocrmypdf has a hint: adconrad:unblock ocrmypdf/6.1.2-1ubuntu1
+This does not seem to be a regression, although fixed in disco via
+a new upstream version 6.2.5.

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

Title:
  SRU: update python3.6 to the new minor release 3.6.7

Status in python3-defaults package in Ubuntu:
  Fix Committed
Status in python3.6 package in Ubuntu:
  Fix Committed
Status in python3-defaults source package in Bionic:
  Fix Committed
Status in python3.6 source package in Bionic:
  Fix Committed
Status in python3-defaults source package in Cosmic:
  Fix Released
Status in python3.6 source package in Cosmic:
  Fix Released

Bug description:
  SRU: update python3.6 to the new minor release 3.6.7

  See LP: #1792143 for the rationale, going one minor release ahead (and
  planning to do 3.6.8 in January, the last source release from the 3.6
  branch).

  [Impact]
  Provide the branch updates for the stable 3.6 branch in the LTS release.

  [Regression Potential]
  There is regression potential, but this version is in use in 18.10, which 
didn't show regressions.

  [Test Case]
  No regressions in the Python 3.6 test suite, no regressions in the autopkg 
tests

  Failing autopkg tests:
   - http://autopkgtest.ubuntu.com/packages/p/python-asdf/bionic/armhf
 failed before, flaky autopkg tests history, now passes in disco.
   - snapcraft: amd64 and i386 try to download some rust installation,
 which then fails to build some downloaded code. This doesn't look
 like a reliable test.
   - python-mechanicalsoup: unrelated, fails in both 2.7 and 3.6.
 Fixed in cosmic, filed LP: #1802835 for a fix anyway.
   - http://autopkgtest.ubuntu.com/packages/l/lxd/bionic/arm64
 doesn't look like a regression in the autopkg test history.
 pinged the lxd maintainers, but no response yet.
   - ocrmypdf has a hint: adconrad:unblock ocrmypdf/6.1.2-1ubuntu1
 This does not seem to be a regression, although fixed in disco via
 a new upstream version 6.2.5.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1799206/+subscriptions

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


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

2018-11-12 Thread Daniel van Vugt
Ubuntu Touch is no longer supported.

** Changed in: pulseaudio (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  [CTA] audio record works for call audio

Status in Canonical System Image:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Won't Fix
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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


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

2018-11-12 Thread Daniel van Vugt
** Changed in: pulseaudio (Ubuntu)
   Status: Confirmed => Won't Fix

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/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:
  Won't Fix
Status in pulseaudio package in Ubuntu:
  Won't Fix
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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1597755] Re: No ringtone or message tone in headphones in silent mode

2018-11-12 Thread Daniel van Vugt
Ubuntu Touch is no longer supported.

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

** Changed in: pulseaudio (Ubuntu)
   Status: Incomplete => Won't Fix

** Changed in: pulseaudio (Ubuntu RTM)
   Status: Confirmed => Won't Fix

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

Title:
  No ringtone or message tone in headphones in silent mode

Status in pulseaudio package in Ubuntu:
  Won't Fix
Status in pulseaudio package in Ubuntu RTM:
  Won't Fix

Bug description:
  When in silent mode, ringtones and message tones do not play in
  headphones.

  They are supposed to according to: https://wiki.ubuntu.com/Sound

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

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


[Touch-packages] [Bug 1493851] Re: Port to upstreamed versions of Audio Role patch

2018-11-12 Thread Daniel van Vugt
Ubuntu Touch is no longer supported.

** Changed in: pulseaudio (Ubuntu)
   Status: Incomplete => Won't Fix

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

Title:
  Port to upstreamed versions of Audio Role patch

Status in Ubuntu Clock App:
  Fix Released
Status in dropping-letters package in Ubuntu:
  Fix Released
Status in media-hub package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Won't Fix
Status in qtubuntu-camera package in Ubuntu:
  Fix Released
Status in qtubuntu-media package in Ubuntu:
  Fix Released
Status in telephony-service package in Ubuntu:
  Fix Released
Status in ubuntu-clock-app package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  The Qt 5.5 packages at https://launchpad.net/~ci-train-ppa-
  service/+archive/ubuntu/landing-012 now include the upstream versions
  of QML Playlist and Audio Role patches that went in to Qt 5.6.

  There are some differences in the Audio Role patch compared to the
  version on vivid-overlay PPA that requires changes.

  Qt 5.5 targets landing soon after xenial opens.

  For reference,
  Old API: 
http://anonscm.debian.org/cgit/pkg-kde/qt/qtmultimedia.git/diff/debian/patches/adding_media_role_property.patch?h=ubuntu&id=d5149eefcd093d96be3191d5f8a7f622f788e1f4
  New, upstreamed API: 
http://anonscm.debian.org/cgit/pkg-kde/qt/qtmultimedia.git/tree/debian/patches/Add-audio-role-API-to-QMediaPlayer.patch?h=ubuntu

  More information about Qt 5.5 at
  https://wiki.ubuntu.com/Touch/QtTesting

  The plan (2015-11-02):

  Patch some components to work with both old API & Qt 5.4 + new API &
  Qt 5.5 - qtubuntu-camera, qtubuntu-media to detect at compile time and
  Unity 8 at runtime.

  Pulseaudio and media-hub would land only to xenial, switching to the
  new API as part of the Qt 5.5 silo.

  Clock and dropping-letters drop the audio role usage as it's not
  supposed to be used in those.

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

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


[Touch-packages] [Bug 1799206] Re: SRU: update python3.6 to the new minor release 3.6.7

2018-11-12 Thread Matthias Klose
summarized the failing autopkg tests in the bug description. These look
like not being triggered by the 3.6 update.


** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic

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

Title:
  SRU: update python3.6 to the new minor release 3.6.7

Status in python3-defaults package in Ubuntu:
  Fix Committed
Status in python3.6 package in Ubuntu:
  Fix Committed
Status in python3-defaults source package in Bionic:
  Fix Committed
Status in python3.6 source package in Bionic:
  Fix Committed
Status in python3-defaults source package in Cosmic:
  Fix Released
Status in python3.6 source package in Cosmic:
  Fix Released

Bug description:
  SRU: update python3.6 to the new minor release 3.6.7

  See LP: #1792143 for the rationale, going one minor release ahead (and
  planning to do 3.6.8 in January, the last source release from the 3.6
  branch).

  [Impact]
  Provide the branch updates for the stable 3.6 branch in the LTS release.

  [Regression Potential]
  There is regression potential, but this version is in use in 18.10, which 
didn't show regressions.

  [Test Case]
  No regressions in the Python 3.6 test suite, no regressions in the autopkg 
tests

  Failing autopkg tests:
   - http://autopkgtest.ubuntu.com/packages/p/python-asdf/bionic/armhf
 failed before, flaky autopkg tests history, now passes in disco.
   - snapcraft: amd64 and i386 try to download some rust installation,
 which then fails to build some downloaded code. This doesn't look
 like a reliable test.
   - python-mechanicalsoup: unrelated, fails in both 2.7 and 3.6.
 Fixed in cosmic, filed LP: #1802835 for a fix anyway.
   - http://autopkgtest.ubuntu.com/packages/l/lxd/bionic/arm64
 doesn't look like a regression in the autopkg test history.
 pinged the lxd maintainers, but no response yet.
   - ocrmypdf has a hint: adconrad:unblock ocrmypdf/6.1.2-1ubuntu1
 This does not seem to be a regression, although fixed in disco via
 a new upstream version 6.2.5.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1799206/+subscriptions

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


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

2018-11-12 Thread Daniel van Vugt
Ubuntu Touch is no longer supported.

** Changed in: pulseaudio (Ubuntu)
   Status: New => Won't Fix

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/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:
  Won't Fix

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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1762114] Re: not able to download any app

2018-11-12 Thread Daniel van Vugt
Can you please show what error you are experiencing?

** Package changed: xorg (Ubuntu) => ubuntu

** Changed in: ubuntu
   Status: New => Incomplete

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

Title:
  not able to download any app

Status in Ubuntu:
  Incomplete

Bug description:
  getting error while downloading app through terminal

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-40.60-generic 4.4.21
  Uname: Linux 4.4.0-40-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sun Apr  8 10:15:09 2018
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   btusb-qca-rome, 1.3, 4.4.0-40-generic, x86_64: installed
   intel-hid, 3.1, 4.4.0-40-generic, x86_64: installed
   oem-audio-hda-daily, 0.201608070501~ubuntu16.04.1, 4.4.0-40-generic, x86_64: 
installed
   radeon-si, 1a, 4.4.0-38-generic, x86_64: built
   radeon-si, 1a, 4.4.0-40-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: Dell Skylake Integrated Graphics [1028:078a]
  InstallationDate: Installed on 2017-11-26 (132 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Atheros Communications, Inc. 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a05 Microdia 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 14-3467
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-40-generic.efi.signed 
root=UUID=dd0575d4-547a-4de3-a814-a51e96e61653 ro locale=en_US quiet splash 
vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/07/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.07.00
  dmi.board.name: 0WPN9K
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.07.00:bd04/07/2017:svnDellInc.:pnInspiron14-3467:pvr:rvnDellInc.:rn0WPN9K:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 14-3467
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sun Apr  8 09:29:44 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1718 
   vendor BOE
  xserver.version: 2:1.18.4-0ubuntu0.7

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

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


[Touch-packages] [Bug 1533251] Re: Ubuntu phone / Aquaris E5: no ringtones when receiving calls, no sound when receiving messages; no sound on speakers

2018-11-12 Thread Daniel van Vugt
Ubuntu Touch is no longer supported.

** Changed in: pulseaudio (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  Ubuntu phone / Aquaris E5: no ringtones when receiving calls, no sound
  when receiving messages; no sound on speakers

Status in indicator-sound package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Won't Fix

Bug description:
  Aquaris E5 HD, Ubuntu Edition; Ubuntu 15.04, OTA-8.5

  My phone does not ring / play sound on speakers. No problems to answer
  calls, when having notice by vibrating / display notification; Have
  phone for some weeks now - at very beginning it worked; short after it
  stopped playing sounds; swithched sound on in pathwind & uninstalled
  pathwind - no difference; sometimes it plays ringtones - but have no
  idea under which circumstances; even when it rang for one time it does
  not anymore one call later, although I did not make any changes in
  settings between the calls; does not play sounds / ringtones when
  selecting them in settings (no difference which ringtone).

  Today I made full reset on phone (by Settings) - still no sounds.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1533251/+subscriptions

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


[Touch-packages] [Bug 1558554] Re: In CAR - media streaming via bluetooth not working after second connection

2018-11-12 Thread Daniel van Vugt
Ubuntu Touch is no longer supported.

** Changed in: pulseaudio (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  In CAR - media streaming via bluetooth not working after second
  connection

Status in pulseaudio package in Ubuntu:
  Won't Fix

Bug description:
  I am on:

  current build number: 284
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2016-03-17 05:53:48
  version version: 284
  version ubuntu: 20160317
  version device: 20160108-efc96d8
  version custom: 20160111-926-36--vivid

  I am encountering the following issue while I am connected to a
  bluetooth device (in my car, Seat Alhambra 2012):

  I am connecting the phone to my in car bluetooth system
  I am opening a music playing app (music player, podbird, webapp (KlassikRadio)
  I am playing music and this music is played via my in car loudspeakers
  (as expected)

  The second time (the apps are still open) I am connecting my phone to my in 
car bluetooth system I experience the following:
  The sound in not routed via my in car loud speakers. I hear the music via my 
in phone speaker (eventhough i am connected via bluetooth). 
  The only way is to close the app and restart the app while I am still 
connected. Then the sound is played again on my in car loudspeakers.

  Expectation:
  Whenever I am connecting to a bluetooth device sound is routed via this 
device even if an app was open.

  Logs are attached. You should be able to see this behaviour starting
  from March, 17th 2016, 10:22 h CET to 11:30 CET when I have tested
  this several times.

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

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


[Touch-packages] [Bug 1799202] Re: SRU: update Python 3.7 to the 3.7.1 release

2018-11-12 Thread Matthias Klose
python3.7 was already accepted into cosmic-updates


** Changed in: python3.7 (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  SRU: update Python 3.7 to the 3.7.1 release

Status in python3-defaults package in Ubuntu:
  New
Status in python3-stdlib-extensions package in Ubuntu:
  Fix Committed
Status in python3.7 package in Ubuntu:
  Fix Committed
Status in python3-defaults source package in Bionic:
  New
Status in python3-stdlib-extensions source package in Bionic:
  Fix Committed
Status in python3.7 source package in Bionic:
  Fix Committed
Status in python3-defaults source package in Cosmic:
  Fix Released
Status in python3-stdlib-extensions source package in Cosmic:
  Fix Released
Status in python3.7 source package in Cosmic:
  Fix Released

Bug description:
  SRU: update Python 3.7 to the 3.7.1 release.  3.7.1 is the first
  maintenance release, update both 18.04 LTS and 18.10 to the release.
  For 18.10 it's just one bug fix compared to the release candidate 2.

  python3-stdlib-extensions also updates the modules to the 3.6.7
  release for Python 3.6.

  Acceptance Criteria: The package builds, and the test suite doesn't
  show regressions.  The test suite passes in the autopkg tests.

  Regression Potential: Python 3.7 isn't used by default, so we don't
  have many default users.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1799202/+subscriptions

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


[Touch-packages] [Bug 1520584] Re: [Meizu MX4] Sound shuttering using Bluetooth car connection

2018-11-12 Thread Daniel van Vugt
Ubuntu Touch is no longer supported.

** Changed in: bluez (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  [Meizu MX4] Sound shuttering using Bluetooth car connection

Status in bluez package in Ubuntu:
  Won't Fix

Bug description:
  There is a problem with playing music (or other sounds) using
  Bluetooth connected to a car, in my case it is Chevrolet Sonic (or
  Aveo T300). Music shutters all the time.

  Everything is fine playing sounds from other devices connected to this
  car (for ex. Samsung Galaxy Nexus, Sony Xperia Z).

  Tested with Wi-Fi/GPS ON and OFF. So it is not the problem.

  Problem is actual al least since OTA 6, now tested on r188.

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

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


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

2018-11-12 Thread Daniel van Vugt
Ubuntu Touch is no longer supported.

** Changed in: bluez (Ubuntu)
   Status: New => Won't Fix

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

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

Status in bluez package in Ubuntu:
  Won't Fix
Status in ubuntu-system-settings package in Ubuntu:
  Incomplete

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

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

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

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

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

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


[Touch-packages] [Bug 1799202] Re: SRU: update Python 3.7 to the 3.7.1 release

2018-11-12 Thread Matthias Klose
same with python3-stdlib-extensions and python3-defaults


** Changed in: python3-defaults (Ubuntu Cosmic)
   Status: New => Fix Released

** Tags removed: upgrade-software-version

** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic

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

Title:
  SRU: update Python 3.7 to the 3.7.1 release

Status in python3-defaults package in Ubuntu:
  New
Status in python3-stdlib-extensions package in Ubuntu:
  Fix Committed
Status in python3.7 package in Ubuntu:
  Fix Committed
Status in python3-defaults source package in Bionic:
  New
Status in python3-stdlib-extensions source package in Bionic:
  Fix Committed
Status in python3.7 source package in Bionic:
  Fix Committed
Status in python3-defaults source package in Cosmic:
  Fix Released
Status in python3-stdlib-extensions source package in Cosmic:
  Fix Released
Status in python3.7 source package in Cosmic:
  Fix Released

Bug description:
  SRU: update Python 3.7 to the 3.7.1 release.  3.7.1 is the first
  maintenance release, update both 18.04 LTS and 18.10 to the release.
  For 18.10 it's just one bug fix compared to the release candidate 2.

  python3-stdlib-extensions also updates the modules to the 3.6.7
  release for Python 3.6.

  Acceptance Criteria: The package builds, and the test suite doesn't
  show regressions.  The test suite passes in the autopkg tests.

  Regression Potential: Python 3.7 isn't used by default, so we don't
  have many default users.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1799202/+subscriptions

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


[Touch-packages] [Bug 1536595] Re: Bluetooth disconnects and phone not found after disconnection

2018-11-12 Thread Daniel van Vugt
Ubuntu Touch is no longer supported.

** Changed in: bluez (Ubuntu)
   Status: New => Won't Fix

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

Title:
  Bluetooth disconnects and phone not found after disconnection

Status in bluez package in Ubuntu:
  Won't Fix

Bug description:
  Phone information:

  BQ Aquaris E5
  Bluetooth: 4.0
  Ubuntu 15.04 OTA 8.5 

  Bug details:
  The phone will connect to the in-car Bluetooth hands free. Making calls from 
the touch screen will initialize a call on the phone, but soon after the call 
connection, the Bluetooth drops. The caller only hears static. The phone will 
not reconnect with the Bluetooth hands free device, unless the phone is 
rebooted. 

  Expected.
  A call is successfully placed using a hands free device and the Bluetooth 
connection will remain connected to the phone.

  Bluetooth device details of hands free unit.
  VW Composition Media with bluetooth 4.0. Touch screen in-car entertainment.

  Other information:
  Some have reported phones that will not connect to hands free devices.
  Some device pairing can take some time to connect and can be unsuccessful. 
  Attached is the phones system log after the final test was done.

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

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


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

2018-11-12 Thread Daniel van Vugt
Ubuntu Touch is no longer supported.

** Changed in: bluez (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  Multiple bluetooth audio devices break audio routing

Status in Canonical System Image:
  Confirmed
Status in bluez package in Ubuntu:
  Won't Fix
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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1799202] Re: SRU: update Python 3.7 to the 3.7.1 release

2018-11-12 Thread Matthias Klose
the python3.7 testsuite run looks fine for bionic as well.

** Changed in: python3.7 (Ubuntu Bionic)
   Status: Fix Released => Fix Committed

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

Title:
  SRU: update Python 3.7 to the 3.7.1 release

Status in python3-defaults package in Ubuntu:
  New
Status in python3-stdlib-extensions package in Ubuntu:
  Fix Committed
Status in python3.7 package in Ubuntu:
  Fix Committed
Status in python3-defaults source package in Bionic:
  New
Status in python3-stdlib-extensions source package in Bionic:
  Fix Committed
Status in python3.7 source package in Bionic:
  Fix Committed
Status in python3-defaults source package in Cosmic:
  Fix Released
Status in python3-stdlib-extensions source package in Cosmic:
  Fix Released
Status in python3.7 source package in Cosmic:
  Fix Released

Bug description:
  SRU: update Python 3.7 to the 3.7.1 release.  3.7.1 is the first
  maintenance release, update both 18.04 LTS and 18.10 to the release.
  For 18.10 it's just one bug fix compared to the release candidate 2.

  python3-stdlib-extensions also updates the modules to the 3.6.7
  release for Python 3.6.

  Acceptance Criteria: The package builds, and the test suite doesn't
  show regressions.  The test suite passes in the autopkg tests.

  Regression Potential: Python 3.7 isn't used by default, so we don't
  have many default users.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1799202/+subscriptions

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


[Touch-packages] [Bug 1537737] Re: Since Bluez5, headsets don't reconnect audio when reconnecting

2018-11-12 Thread Daniel van Vugt
Ubuntu Touch is no longer supported.

** Changed in: bluez (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  Since Bluez5, headsets don't reconnect audio when reconnecting

Status in Canonical System Image:
  Confirmed
Status in bluez package in Ubuntu:
  Won't Fix

Bug description:
  Pairing a Bluetooth headset (A2DP) seems to work fine. After pairing,
  the phone successfully switches to transmit audio over Bluetooth. When
  disconnecting the Headset again, the phone successfully switches audio
  back to the integrated speaker. However, on a reconnect without
  pairing, the headset seems to connect properly, but it doesn't route
  audio any more to the headset. Despite the headset being connected,
  audio is still routed to the integrated speaker. A reboot does not
  seem to help. The only way to get back to Bluetooth audio streaming is
  to delete the device from the settings, and pair it again, which makes
  it work once again.

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

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


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

2018-11-12 Thread Daniel van Vugt
Ubuntu Touch is no longer supported.

** Changed in: bluez (Ubuntu)
   Status: New => Won't Fix

** Changed in: pulseaudio (Ubuntu)
   Status: New => Won't Fix

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/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:
  Won't Fix
Status in pulseaudio package in Ubuntu:
  Won't Fix
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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


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

2018-11-12 Thread Daniel van Vugt
Ubuntu Touch is no longer supported.

** Changed in: pulseaudio (Ubuntu)
   Status: Confirmed => Won't Fix

** Changed in: pulseaudio (Ubuntu RTM)
   Status: Confirmed => Won't Fix

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/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:
  Won't Fix
Status in media-hub package in Ubuntu RTM:
  Invalid
Status in pulseaudio package in Ubuntu RTM:
  Won't Fix

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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1551326] Re: No "Answer" button in bluetooth phone car onboard screen

2018-11-12 Thread Daniel van Vugt
Ubuntu Touch is no longer supported.

** Changed in: bluez (Ubuntu)
   Status: New => Won't Fix

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

Title:
  No "Answer" button in bluetooth phone car onboard screen

Status in bluetooth-touch:
  New
Status in Phablet Tools:
  New
Status in bluez package in Ubuntu:
  Won't Fix
Status in phablet-tools package in Ubuntu:
  New

Bug description:
  Bluetooth connection is well automatically established since OTA 8.5. Adress 
book is populated and to give a call works nice.
  But when it is an entry call, the phone car system rings and the onboard 
screen menu only permits to hang up the call. There is no button to pick up the 
call. You have to push the answer button on the mobile phone if you want to 
answer. Not very useful when the phone is in your pocket.

To manage notifications about this bug go to:
https://bugs.launchpad.net/bluetooth-touch/+bug/1551326/+subscriptions

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


[Touch-packages] [Bug 1515179] Re: [nexus7][bluez5] Unable to pair with Arc Touch Bluetooth

2018-11-12 Thread Daniel van Vugt
Ubuntu Touch is no longer supported.

** Changed in: bluez (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  [nexus7][bluez5] Unable to pair with Arc Touch Bluetooth

Status in ubuntu-nexus7:
  Confirmed
Status in bluez package in Ubuntu:
  Won't Fix

Bug description:
  Unable to pair arc touch bluetooth mouse with nexus 7.

  Steps to reproduce:

  1. install bluez5 stack on nexus7(fresh flashed), instruction: 
https://wiki.ubuntu.com/Bluetooth/TouchBluez5Testing
  2. adb shell into nexus7, then type following commands:
  $ bluetoothctl (entering interactive mode)
  $ discoverable on
  $ pairable on
  $ scan on
  $ devices (to see the device mac that you want to pair)
  $ pair 
  $ trust 
  $ connect 

  Device seems to paired and connected but still not working.

  Device 
   Name: Arc Touch Mouse SE
   Alias: Arc Touch Mouse SE
   Appearance: 0x03c2
   Icon: input-mouse
   Paired: yes
   Trusted: yes
   Blocked: no
   Connected: no
   ConnectedProfiles:
     None
   LegacyPairing: no
   UUIDs:
     Generic Access Profile(1800--1000-8000-00805f9b34fb)
     Generic Attribute Profile (1801--1000-8000-00805f9b34fb)
     Device Information(180a--1000-8000-00805f9b34fb)
     Battery Service   (180f--1000-8000-00805f9b34fb)
     Human Interface Device(1812--1000-8000-00805f9b34fb)

  Additional note:
  I did managed to get the mouse work once, but it is in an messy status.
  There is a similar bug on X86: bug #1510570
  And also a bug in upstream: Bluetooth: SMP security requested but not 
available https://bugzilla.kernel.org/show_bug.cgi?id=104011

  As a control test, I happen to had set of Microsoft designer keyboard
  and mouse. They are still not able to visible via system setting, but
  pairing by bluetoothctl there are no any problems, they work

  
  Versions:
  ii  bluez
5.35+15.04.20151023-0ubuntu1   armhf
Bluetooth tools and daemons
  ii  bluez-obexd  
5.35+15.04.20151023-0ubuntu1   armhfbluez 
obex daemon
  (latest verifying with)
  bluez 5.36-0ubuntu2~overlay1

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

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


[Touch-packages] [Bug 1535335] Re: [App permissions] Change prompt "wants to record audio" to "wants to use the microphone"

2018-11-12 Thread Daniel van Vugt
Ubuntu Touch is no longer supported.

** Changed in: pulseaudio (Ubuntu)
   Status: Triaged => Won't Fix

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

Title:
  [App permissions] Change prompt "wants to record audio" to "wants to
  use the microphone"

Status in Canonical System Image:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Won't Fix

Bug description:
  The prompt when the camera wants to access the hardware to record
  audio is currently "wants to record audio". This is not really
  accurate since an app can request access to the microphone without
  actually recording anything. furthermore the direct translation to
  French as an example is not really meaningful.

  "Microphone" is also consistent with the word used in system-
  settings/security & privacy/app permissions

  : “Prompt
  text … wants to use the microphone”

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

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


[Touch-packages] [Bug 1556274] Re: MX4 bluetooth not pairing with Jaguar XKR 2007

2018-11-12 Thread Daniel van Vugt
Ubuntu Touch is no longer supported.

** Changed in: bluez (Ubuntu)
   Status: New => Won't Fix

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

Title:
  MX4 bluetooth not pairing with Jaguar XKR 2007

Status in bluez package in Ubuntu:
  Won't Fix

Bug description:
  Hi I have an MX4 with OTA-9.1 update installed. The phone has never
  been able to pair with my Jaguar XKR 2007. The car finds the Meizu MX4
  and displays the phone type, but will not pair to it Any help to
  improve this would be appreciated.

  Just to say, really enjoying Ubuntu Touch, once miracast is added it
  will be the one to beat.

  Regards

  Dave H

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

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


[Touch-packages] [Bug 1559201] Re: Bluetooth connection broken while autoconnect

2018-11-12 Thread Daniel van Vugt
Ubuntu Touch is no longer supported.

** Changed in: bluez (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  Bluetooth connection broken while autoconnect

Status in Bluez Utilities:
  New
Status in Canonical System Image:
  Confirmed
Status in PulseAudio:
  New
Status in bluez package in Ubuntu:
  Won't Fix

Bug description:
  Hello,

  When I set up phone and click connect - music plays fine. But when I
  turn off bluetooth (and mark 'connect automatically to that device'),
  turn it again - phone connect to that device again, but music don't
  play at all or plays with big disruptions. This issue does not occur
  when I've got 'automatically connect' turned off and manually click
  'connect'.

  Maybe this is related to bug [1]
  https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1494225 (because
  this problem happen to me only in device also affected by [1] - in
  other devices working correctly (not affected by [1]) there is no
  problem).

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

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


[Touch-packages] [Bug 1762447] Re: System sometimes freezes after startup

2018-11-12 Thread Daniel van Vugt
Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.

** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)

** Changed in: xorg-server (Ubuntu)
   Status: New => Won't Fix

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

Title:
  System sometimes freezes after startup

Status in xorg-server package in Ubuntu:
  Won't Fix

Bug description:
  I'm not sure if this bug belongs in this section.

  System sometimes freezes after startup, but it's still active. I can
  see visual changes made around the UI when the cursor is moved, but
  it's still very stuttered and unusable. Perhaps some process is using
  too much of the hardware (or something similar). This happens
  occasionally, at other times it works just fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16
  Uname: Linux 4.13.0-38-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
   GCC version:  gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu3.2)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not supported.
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Mon Apr  9 20:39:52 2018
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a week
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Since before I upgraded
  GraphicsCard:
   NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] GP107 [GeForce GTX 
1050 Ti] [1462:8c96]
  InstallationDate: Installed on 2017-10-29 (162 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 1bcf:0053 Sunplus Innovation Technology Inc. 
   Bus 001 Device 002: ID 0c45:7603 Microdia 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Gigabyte Technology Co., Ltd. H270M-D3H
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-38-generic.efi.signed 
root=UUID=e8baebae-f621-46e4-886f-9276f8bdb093 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/09/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: Default string
  dmi.board.name: H270M-D3H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd02/09/2017:svnGigabyteTechnologyCo.,Ltd.:pnH270M-D3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnH270M-D3H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: H270M-D3H
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~17.10.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~17.10.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-

[Touch-packages] [Bug 1438486] Re: Turning off sound in Pathwind mutes other apps too

2018-11-12 Thread Daniel van Vugt
Ubuntu Touch is no longer supported.

** Changed in: pulseaudio (Ubuntu)
   Status: Incomplete => Won't Fix

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-touch-session 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:
  Won't Fix
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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1578748] Re: Magic Mouse crashes device

2018-11-12 Thread Daniel van Vugt
Ubuntu Touch is no longer supported.

** Changed in: bluez (Ubuntu)
   Status: New => Won't Fix

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

Title:
  Magic Mouse crashes device

Status in bluez package in Ubuntu:
  Won't Fix

Bug description:
  When connecting an Apple Magic Mouse via bt  to my M10 tablet, the
  device hangs. It will eventually reboot if left alone.

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

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


[Touch-packages] [Bug 1438255] Re: Phone Vivid reattaching to bt speaker fails to create a sink/source

2018-11-12 Thread Daniel van Vugt
Ubuntu Touch is no longer supported.

** Changed in: pulseaudio (Ubuntu)
   Status: New => Won't Fix

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

Title:
  Phone Vivid reattaching to bt speaker fails to create a sink/source

Status in pulseaudio package in Ubuntu:
  Won't Fix

Bug description:
  REQUIREMENTS:
  Mp3s
  BT Speaker
  Krillin

  STEPS:
  1. Install the latest image from ubuntu-touch/devel-proposed/krillin.en
  2. Transfer some mp3s to the device
  3. Drag down the BT indicator
  4. Tap on settings
  5. Turn on the BT Speaker
  6. Tap on it when the phone finds it
  7. Tap on connect
  8. Open the music player
  9. play music
  10. After a little while turn off the Bluetooth speaker
  11. Music pauses
  12. eventually there is a short burst of music from the loud speaker as the 
bt connection is dropped
  13. Tap on play music plays from loud speaker
  14. Turn the bt speaker back on
  15. The speaker autoconnets
  16. The music stops playing
  17. Eventually it will start playing again from the phones loud speaker not 
the bluetooth speaker

  EXPECTED:
  I expect it to automatically change over to bt speaker once it has connected

  ACTUAL:
  I plays back though the loud speaker rather than the connected bluetooth 
speaker.

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

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


[Touch-packages] [Bug 1446738] Re: 3.5mm audio jack output not working (on Nexus10-UT 15.04 r2)

2018-11-12 Thread Daniel van Vugt
Ubuntu Touch is no longer supported.

** Changed in: pulseaudio (Ubuntu)
   Status: New => Won't Fix

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

Title:
  3.5mm audio jack output not working (on Nexus10-UT 15.04 r2)

Status in pulseaudio package in Ubuntu:
  Won't Fix

Bug description:
  On Nexus 10 with UT 15.04 r2 audio output by 3.5 audio jack don't
  work. Instead speakers work properly and sound is very good.

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

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


[Touch-packages] [Bug 1608115] Re: (Pro 5) Bluetooth speaker interupts and mouse and keyboard loses connection

2018-11-12 Thread Daniel van Vugt
Ubuntu Touch is no longer supported.

** Changed in: bluez (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  (Pro 5) Bluetooth speaker interupts and mouse and keyboard loses
  connection

Status in bluez package in Ubuntu:
  Won't Fix

Bug description:
  Still the bluetooth aren't stable in the pro 5. Music interrupted
  when playing on bluetooth speakers and the phone loses connection to
  keyboard and mouse.

  The same speaker, keyboard and mouse works well on the Bq units M10
  and e4.5

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

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


[Touch-packages] [Bug 1435040] Re: Ubuntu Phone does not connect to car-bluetooth

2018-11-12 Thread Daniel van Vugt
Ubuntu Touch is no longer a supported.

** Changed in: bluez (Ubuntu)
   Status: Confirmed => Won't Fix

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

** Changed in: ubuntu-system-settings (Ubuntu)
   Status: Incomplete => Won't Fix

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

Title:
  Ubuntu Phone does not connect to car-bluetooth

Status in Canonical System Image:
  Won't Fix
Status in bluez package in Ubuntu:
  Won't Fix
Status in ubuntu-system-settings package in Ubuntu:
  Won't Fix

Bug description:
  With my FORD Focus Car, pairing does not work. The bluetooth system in
  the car searches for devices and shows "Aquaris E4.5 Ubuntu Edition"
  and then prompts me to connect with a 4-digit pin code, but the Ubuntu
  phone doesn't react at all and after a while the car system says that
  it failed to connect.

  image: 20150310-3201c0a
  KRILIN01A-S15A_BQ_L100EN_2020_150312
  OS Build 20

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

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


[Touch-packages] [Bug 1494242] Re: Try to auto connect devices when user enables bluetooth

2018-11-12 Thread Daniel van Vugt
Ubuntu Touch is no longer supported.

** Changed in: bluez (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  Try to auto connect devices when user enables bluetooth

Status in Canonical System Image:
  Confirmed
Status in bluez package in Ubuntu:
  Won't Fix

Bug description:
  When bluetooth gets enabled by the user we should try to connect all
  devices we're currently paired with and which are marked as trusted.
  This will help to improve the user experience that the user will get
  his configured devices connected right away.

  Android does this similar.

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

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


[Touch-packages] [Bug 1763975] Re: DP1.2 daisy-chain flickering

2018-11-12 Thread Daniel van Vugt
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)

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

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

Title:
  DP1.2 daisy-chain flickering

Status in linux package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  New

Bug description:
  Hi all,

  I have a NUC7i7BNH with the latest BIOS (0062) running Ubuntu 18.04
  (uname -r = 4.15.0-15-generic). I have the NUC connected via USB-C to
  DisplayPort, to an Avocent SV340D KVM, then to a Dell U2415 which has
  DP1.2 enabled and is daisy-chainged to another Dell U2415 (DP1.2
  disabled on the second monitor as per Dell instructions).

  I am getting flickering whereby randomly display1 or display2 turn
  black and then back on again. When I disable DP1.2 on the display1,
  and therefore get a duplicate display (as opposed to extended) on
  display2, I get no flickering at all.

  The same setup yields no flickering when running from a Windows 10
  box, so don't think it is the monitors.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 14 12:52:24 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:5927] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: Intel Corporation Device [8086:2068]
  InstallationDate: Installed on 2018-04-01 (12 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180401)
  MachineType: Intel Corporation NUC7i7BNH
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-15-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/22/2018
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BNKBL357.86A.0062.2018.0222.1644
  dmi.board.name: NUC7i7BNB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J31145-307
  dmi.chassis.type: 3
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBNKBL357.86A.0062.2018.0222.1644:bd02/22/2018:svnIntelCorporation:pnNUC7i7BNH:pvrJ31153-308:rvnIntelCorporation:rnNUC7i7BNB:rvrJ31145-307:cvnIntelCorporation:ct3:cvr2:
  dmi.product.family: Intel NUC
  dmi.product.name: NUC7i7BNH
  dmi.product.version: J31153-308
  dmi.sys.vendor: Intel Corporation
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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


[Touch-packages] [Bug 1449059] Re: [mako] Music stays 'ducked' for 15s after selecting dialpad buttons with dialpad tones

2018-11-12 Thread Daniel van Vugt
Ubuntu Touch is no longer supported.

** Changed in: pulseaudio (Ubuntu)
   Status: New => Won't Fix

** Changed in: pulseaudio (Ubuntu RTM)
   Status: New => Won't Fix

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

Title:
  [mako] Music stays 'ducked' for 15s after selecting dialpad buttons
  with dialpad tones

Status in pulseaudio package in Ubuntu:
  Won't Fix
Status in pulseaudio package in Ubuntu RTM:
  Won't Fix

Bug description:
  Steps:
  1) Start playing music in the music-app
  2) Ensure that 'Dialpad tones' are enabled in the sound settings
  3) Open the dialer-app
  4) Press one of the numbers on the dialer
  5) Notice that the audio 'ducks' to allow for the dialpad tone, but then the 
audio takes ~15s to then be restored to its original value

  It was expected that the audio would be restored as soon as the
  dialpad tone ended.

  $ system-image-cli -i
  current build number: 181
  device name: mako
  channel: ubuntu-touch/devel-proposed-customized-here
  alias: ubuntu-touch/vivid-proposed-customized-here
  last update: 2015-04-26 17:27:16
  version version: 181
  version ubuntu: 20150424.1
  version device: 20150210
  version custom: mako-1.1

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

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


[Touch-packages] [Bug 1650860] Re: I can't forget devices

2018-11-12 Thread Daniel van Vugt
Ubuntu Touch is no longer supported.

** Changed in: bluez (Ubuntu)
   Status: New => Won't Fix

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

Title:
  I can't forget devices

Status in bluez package in Ubuntu:
  Won't Fix

Bug description:
  I can't forget some devices no matter whether BT is on or off (Bug #1535829). 
There are two devices on my list at the moment: a car audio which I can't 
forget no matter what I do
  and a Garmin navigation device which I can forget only when BT is on.

  Reported for krillin E4.5 on OTA-14

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

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


[Touch-packages] [Bug 1387949] Re: power cycling Emerson EM229 headset caused phone to reboot

2018-11-12 Thread Daniel van Vugt
Ubuntu Touch is no longer supported.

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

Title:
  power cycling Emerson EM229 headset caused phone to reboot

Status in Canonical System Image:
  Won't Fix
Status in bluez package in Ubuntu:
  Won't Fix

Bug description:
  While sanity testing krillin rtm image 139, I paired a bluetooth
  headset.  I made a call with it, hung up, then turned the headset off.
  I noticed this caused the BT indicator icon to invert, which is a nice
  way to indicate whether something is connected.  So, I turned the
  device back on, waited for the icon to invert, turned the device off,
  waited, and instead of inverting the icon...  the phone rebooted.

  Not sure what exactly failed here, like which component, but it's
  definitely not good when a paired headset can cause the phone to
  spontaneously reboot.

  I don't see any relevant .crash files, and all I see in syslog from
  that time is this:

  Oct 30 23:42:27 ubuntu-phablet NetworkManager[1429]:  Activation 
(/ril_1) failed for connection '/310410695117999/context1'
  Oct 30 23:42:27 ubuntu-phablet NetworkManager[1429]:  (/ril_1): device 
state change: failed -> disconnected (reason 'none') [120 30 0]
  Oct 30 23:42:27 ubuntu-phablet NetworkManager[1429]:  (/ril_1): 
deactivating device (reason 'none') [0]
  Oct 30 23:43:01 ubuntu-phablet kernel: [  
747.229681][Ker_PM][request_suspend_state]wakeup (3->0) at 747214006509 
(2014-10-31 05:43:01.704759580 UTC)
  Oct 30 23:43:02 ubuntu-phablet kernel: [  747.779813]mtk-tpd: TPD wake up
  Oct 30 23:43:02 ubuntu-phablet kernel: [  747.816572]mtk-tpd: TPD wake up done
  Oct 30 23:43:02 ubuntu-phablet kernel: [  747.816593]  
mag_context_obj ok--->hwm_obj->early_suspend=0 
  Oct 30 23:43:09 ubuntu-phablet dbus[769]: [system] Activating service 
name='org.freedesktop.systemd1' (using servicehelper)
  Oct 30 23:43:09 ubuntu-phablet dbus[769]: [system] Successfully activated 
service 'org.freedesktop.systemd1'
  Oct 30 23:43:09 ubuntu-phablet rsyslogd: [origin software="rsyslogd" 
swVersion="7.4.4" x-pid="771" x-info="http://www.rsyslog.com";] exiting on 
signal 15.
  Oct 30 23:43:42 ubuntu-phablet rsyslogd: [origin software="rsyslogd" 
swVersion="7.4.4" x-pid="785" x-info="http://www.rsyslog.com";] start
  Oct 30 23:43:42 ubuntu-phablet rsyslogd-2307: warning: ~ action is 
deprecated, consider using the 'stop' statement instead [try 
http://www.rsyslog.com/e/2307 ]
  Oct 30 23:43:42 ubuntu-phablet rsyslogd-2307: warning: ~ action is 
deprecated, consider using the 'stop' statement instead [try 
http://www.rsyslog.com/e/2307 ]
  Oct 30 23:43:42 ubuntu-phablet rsyslogd: rsyslogd's groupid changed to 103
  Oct 30 23:43:42 ubuntu-phablet rsyslogd: rsyslogd's userid changed to 100
  Oct 30 23:43:42 ubuntu-phablet kernel: [0.00]Booting Linux on 
physical CPU 0
  Oct 30 23:43:42 ubuntu-phablet kernel: [0.00]Initializing cgroup 
subsys cpu
  Oct 30 23:43:42 ubuntu-phablet kernel: [0.00]Linux version 3.4.67 
(root@android-barajas_1414177384) (gcc version 4.7 (GCC) ) #1 SMP PREEMPT Tue 
Oct 28 11:57:42 UTC 2014

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

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


[Touch-packages] [Bug 1423266] Re: Fails to set the HSP/HFP profile with Ford New Fiesta Sedan 2014 (Brazil)

2018-11-12 Thread Daniel van Vugt
Ubuntu Touch is no longer supported.

** Changed in: bluez (Ubuntu)
   Status: New => Won't Fix

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

Title:
  Fails to set the HSP/HFP profile with Ford New Fiesta Sedan 2014
  (Brazil)

Status in Canonical System Image:
  Confirmed
Status in bluez package in Ubuntu:
  Won't Fix

Bug description:
  Car: Ford New Fiesta Sedan 2014 (the one sold in Brazil)
  Image: RTM 239
  Device: krillin

  I paired the device, and tried to start a call but noticed there was
  no audio, so with help from Salveti we figured out switching to the
  hsp profile is faling, so the attached syslog is after running the
  following command:

  pactl set-card-profile bluez_card.00_21_CC_E9_02_39 hsp

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

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


[Touch-packages] [Bug 1409047] Re: Bluetooth audio not working with Volvo multimedia

2018-11-12 Thread Daniel van Vugt
Ubuntu Touch is no longer supported.

** Changed in: bluez (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  Bluetooth audio not working with Volvo multimedia

Status in bluez package in Ubuntu:
  Won't Fix

Bug description:
  Calls work just fine, which is in the "Telephone" part of the car's UI.
  When changing to Multimedia mode and pairing with a Nexus 4, no audio is 
played, nor is any audio playable later through the phone's own speakers.

  This is a 2012 Volvo S60 (Norwegian)

  Steps to reproduce:
  1. Pair with car multimedia system
  2. Confirm that the car display shows "Playing on Nexus 4" (or something to 
that effect)
  3. Play song

  What I expected to happen:
  Audio should have been played through the car's speakers

  What happened instead:
  No audio was played
  Playing any audio, even after turning off bluetooth, does not work

  Phone:
  mako using Vivid @ r58

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

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


[Touch-packages] [Bug 1471705] Re: when playing path wind , press the volume down to silience, but after playing a while , we can still hear the sound

2018-11-12 Thread Daniel van Vugt
Ubuntu Touch is no longer supported.

** Changed in: pulseaudio (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  when playing path wind , press the volume down to silience, but after
  playing a while ,we can still hear the sound

Status in pulseaudio package in Ubuntu:
  Won't Fix

Bug description:
  current build number: 47
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.en
  last update: 2015-07-06 05:43:41
  version version: 47
  version ubuntu: 20150706
  version device: 20150701-cdd791c
  version custom: 20150602-731-5-32

  Steps:
1.open the path wind app
2.play the game , turn off the music by pressing down the volume key to 
zero 
3.continue playing the game 

  Expectation:

as long as i play this game without quiting, there shouldn't be any
  sound

  Actual result:

After playing this game a while , the sound appears again
  automaticly

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

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


[Touch-packages] [Bug 1480274] Re: Music plays for about 0.5 seconds through speakers when headphones removed

2018-11-12 Thread Daniel van Vugt
Ubuntu Touch is no longer supported.

** Changed in: pulseaudio (Ubuntu)
   Status: Confirmed => Won't Fix

** Changed in: pulseaudio (Ubuntu RTM)
   Status: Confirmed => Won't Fix

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

Title:
  Music plays for about 0.5 seconds through speakers when headphones
  removed

Status in Canonical System Image:
  Confirmed
Status in Ubuntu Music App:
  Invalid
Status in pulseaudio package in Ubuntu:
  Won't Fix
Status in pulseaudio package in Ubuntu RTM:
  Won't Fix

Bug description:
  Device: mako, vegetahd

  If you remove the headphones while music is playing, the sound comes
  out of the loudspeakers for about 0.5 seconds before stopping.

  Steps to reproduce it:

  1] Connect headphones
  2] Start playing any track from the Music app
  3] Make sure volume is 100% so you can hear it easily
  4] Listen to the phone speaker and disconnect headphones, right after 
disconnecting you should hear a sound on the speaker which is a bug.

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

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


[Touch-packages] [Bug 1414142] Re: Continuous skipping of audio track after reconnecting bluetooth to Car

2018-11-12 Thread Daniel van Vugt
Ubuntu Touch is no longer supported.

** Changed in: bluez (Ubuntu)
   Status: New => Won't Fix

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

Title:
  Continuous skipping of audio track after reconnecting bluetooth to Car

Status in bluez package in Ubuntu:
  Won't Fix

Bug description:
  In my car I am seeing a very weird issue with bluetooth playback.
  After connecting with car bluetooth the second time, the audio
  playback from my phone in the car speakers starts to skip.

  I am sure not everyone will be able to reproduce this bug with the
  below steps but still I should mentions them.

  1. Connect mobile bluetooth to the car and play a track
  Verify: it plays the track fine.
  2. Disconnect the bluetooth from the phone and make sure it actually gets 
disconnected from the car.
  3. Re-enable bluetooth and connect to the car.

  Now when I play the sound track it keeps skipping and I can't really
  hear much of the song.

  I have attached hcidump, syslog and 'hcitool lq'.

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

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


[Touch-packages] [Bug 1370911] Re: bluetooth headset (Motorola S10-HD) remains connected despite it appears disconnected

2018-11-12 Thread Daniel van Vugt
Ubuntu Touch is no longer supported.

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

Title:
  bluetooth headset (Motorola S10-HD) remains connected despite it
  appears disconnected

Status in bluez package in Ubuntu:
  Won't Fix

Bug description:
  bluetooth headset (Motorola S10-HD) remains connected despite it
  appears disconnected

  Steps to reproduce:

  1. Pair the Motorola S10-HD with krillin
  2. Now disconnect the headtset form bluetooth settings page.
  3. Note that bt headset settings page shows that device is disconnected.
  4. Now play some music track
  Observe that music is still playing through bt headset while it is 
disconnected.

  Build/Device Info:

  phablet@ubuntu-phablet:~$ system-image-cli -i
  current build number: 1
  device name: krillin
  channel: ubuntu-touch/ubuntu-rtm/14.09
  last update: 2014-09-16 17:43:20
  version version: 1
  version ubuntu: 20140916
  version device: 20140912-23825b8
  version custom: 1410739265

  Bluetooth Headset: Motorola S10-HD

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

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


[Touch-packages] [Bug 1625606] Re: Removed apps not deleted from list of available GPS app

2018-11-12 Thread Daniel van Vugt
Ubuntu Touch is no longer supported.

** Changed in: bluez (Ubuntu)
   Status: New => Won't Fix

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

Title:
  Removed apps not deleted from list of available GPS app

Status in bluez package in Ubuntu:
  Won't Fix

Bug description:
  Aquarius E5
  OTA-13:
  Removed apps will not deleted on list of available GPS apps.

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

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


[Touch-packages] [Bug 1370911] Re: bluetooth headset (Motorola S10-HD) remains connected despite it appears disconnected

2018-11-12 Thread Daniel van Vugt
Ubuntu Touch is no longer a supported.

** Changed in: bluez (Ubuntu)
   Status: New => Won't Fix

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

Title:
  bluetooth headset (Motorola S10-HD) remains connected despite it
  appears disconnected

Status in bluez package in Ubuntu:
  Won't Fix

Bug description:
  bluetooth headset (Motorola S10-HD) remains connected despite it
  appears disconnected

  Steps to reproduce:

  1. Pair the Motorola S10-HD with krillin
  2. Now disconnect the headtset form bluetooth settings page.
  3. Note that bt headset settings page shows that device is disconnected.
  4. Now play some music track
  Observe that music is still playing through bt headset while it is 
disconnected.

  Build/Device Info:

  phablet@ubuntu-phablet:~$ system-image-cli -i
  current build number: 1
  device name: krillin
  channel: ubuntu-touch/ubuntu-rtm/14.09
  last update: 2014-09-16 17:43:20
  version version: 1
  version ubuntu: 20140916
  version device: 20140912-23825b8
  version custom: 1410739265

  Bluetooth Headset: Motorola S10-HD

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

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


[Touch-packages] [Bug 1396973] Re: Audio not switched when headset disabled via bluetooth on/off

2018-11-12 Thread Daniel van Vugt
Ubuntu Touch is no longer supported.

** Changed in: bluez (Ubuntu)
   Status: New => Won't Fix

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

Title:
  Audio not switched when headset disabled via bluetooth on/off

Status in Canonical System Image:
  Confirmed
Status in bluez package in Ubuntu:
  Won't Fix

Bug description:
  Version: ubuntu-touch/ubuntu-rtm/14.09-proposed r169 krillin

  Steps to reproduce:
   * Pair krillin with BT Headset (Sony MDR-10RBT used in test)
   * Call the handset
   * Answer call
   * Check headset input/output
   * Disable Bluetooth on the krillin
   * Audio routed to phone speaker/mic
   * Re-enable Bluetooth

  Expected result:
   - Bluetooth re-connects to headset audio routed back to headset input/output

  Actual result:
   - Audio seems to be routed badly - no audio on call at all from krillin

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

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


[Touch-packages] [Bug 1445376] Re: A2DP skips when conneted to handsfree device

2018-11-12 Thread Daniel van Vugt
Ubuntu Touch is no longer supported.

** Changed in: bluez (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  A2DP skips when conneted to handsfree device

Status in Canonical System Image:
  Incomplete
Status in bluez package in Ubuntu:
  Won't Fix

Bug description:
  When I connect my Aquaris E4.5 to my car's handsfree device (Funkwerk
  Ego Flash) via Bluetooth I experience a skipping problem when playing
  sound files through A2DP.

  Half a second for each second there is a pause. The rest of that half
  second seems to clear a buffer which results in "extra fast" audio.

  To illustrate, listening to a podcast I would expect to hear something
  like "bla bla bla". However, what I do get to hear sounds more like
  "flapflapflap - pause - flapflapflap - pause - ...".

  When I connect my Aquaris to my A2DP speakers at home, the audio is
  perfect.

  Also, handsfree telephony in my car works like a charm.

  So I guess it's just the combination of A2DP while connected to the
  handsfree device which causes the trouble.

  In the past I've used several phones with the Funkwerk device (always
  with handsfree *and* A2DP functionality) including an N900 running
  Maemo. There have never been any problems with those.

  OS build number 21
  KRILIN01A-S15A_BQ_L100EN_2021_150410

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

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


[Touch-packages] [Bug 1763710] Re: lightdm-gnome-gdm not working

2018-11-12 Thread Daniel van Vugt
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at
http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:
1. The specific steps or actions you took that caused you to encounter the 
problem.
2. The behavior you expected. 
3. The behavior you actually encountered (in as much detail as possible).
Thanks!


** Package changed: xorg (Ubuntu) => ubuntu

** Changed in: ubuntu
   Status: New => Incomplete

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

Title:
  lightdm-gnome-gdm not working

Status in Ubuntu:
  Incomplete

Bug description:
  lightdm-gnome-gdm not working

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-38-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Fri Apr 13 19:04:40 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox-guest, 5.1.34, 4.13.0-37-generic, x86_64: installed
   virtualbox-guest, 5.1.34, 4.13.0-38-generic, x86_64: installed
   virtualbox-guest, 5.1.34, 4.15.0-13-generic, x86_64: installed
   virtualbox-guest, 5.1.34, 4.4.0-119-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation G84 [GeForce 8600 GT] [10de:0402] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. G84 [GeForce 8600 GT] [1043:8243]
  InstallationDate: Installed on 2017-11-06 (158 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: System manufacturer P5K SE
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-38-generic 
root=UUID=27389c94-1e8b-4c77-9bc7-c34de7e09ec2 ro splash plymouth:debug quiet
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/31/2007
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0604
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5K SE
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0604:bd10/31/2007:svnSystemmanufacturer:pnP5KSE:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5KSE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: P5K SE
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Tue Apr 10 19:10:04 2018
  xserver.configfile: /etc/X11/xorg.conf
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputLogitech USB Receiver MOUSE, id 8
   inputLogitech USB Receiver KEYBOARD, id 9
   inputLITEON Technology USB Keyboard KEYBOARD, id 10
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.7
  xserver.video_driver: nouveau

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

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


[Touch-packages] [Bug 1387949] Re: power cycling Emerson EM229 headset caused phone to reboot

2018-11-12 Thread Daniel van Vugt
Ubuntu Touch is no longer a supported.

** Changed in: bluez (Ubuntu)
   Status: Confirmed => Won't Fix

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

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

Title:
  power cycling Emerson EM229 headset caused phone to reboot

Status in Canonical System Image:
  Won't Fix
Status in bluez package in Ubuntu:
  Won't Fix

Bug description:
  While sanity testing krillin rtm image 139, I paired a bluetooth
  headset.  I made a call with it, hung up, then turned the headset off.
  I noticed this caused the BT indicator icon to invert, which is a nice
  way to indicate whether something is connected.  So, I turned the
  device back on, waited for the icon to invert, turned the device off,
  waited, and instead of inverting the icon...  the phone rebooted.

  Not sure what exactly failed here, like which component, but it's
  definitely not good when a paired headset can cause the phone to
  spontaneously reboot.

  I don't see any relevant .crash files, and all I see in syslog from
  that time is this:

  Oct 30 23:42:27 ubuntu-phablet NetworkManager[1429]:  Activation 
(/ril_1) failed for connection '/310410695117999/context1'
  Oct 30 23:42:27 ubuntu-phablet NetworkManager[1429]:  (/ril_1): device 
state change: failed -> disconnected (reason 'none') [120 30 0]
  Oct 30 23:42:27 ubuntu-phablet NetworkManager[1429]:  (/ril_1): 
deactivating device (reason 'none') [0]
  Oct 30 23:43:01 ubuntu-phablet kernel: [  
747.229681][Ker_PM][request_suspend_state]wakeup (3->0) at 747214006509 
(2014-10-31 05:43:01.704759580 UTC)
  Oct 30 23:43:02 ubuntu-phablet kernel: [  747.779813]mtk-tpd: TPD wake up
  Oct 30 23:43:02 ubuntu-phablet kernel: [  747.816572]mtk-tpd: TPD wake up done
  Oct 30 23:43:02 ubuntu-phablet kernel: [  747.816593]  
mag_context_obj ok--->hwm_obj->early_suspend=0 
  Oct 30 23:43:09 ubuntu-phablet dbus[769]: [system] Activating service 
name='org.freedesktop.systemd1' (using servicehelper)
  Oct 30 23:43:09 ubuntu-phablet dbus[769]: [system] Successfully activated 
service 'org.freedesktop.systemd1'
  Oct 30 23:43:09 ubuntu-phablet rsyslogd: [origin software="rsyslogd" 
swVersion="7.4.4" x-pid="771" x-info="http://www.rsyslog.com";] exiting on 
signal 15.
  Oct 30 23:43:42 ubuntu-phablet rsyslogd: [origin software="rsyslogd" 
swVersion="7.4.4" x-pid="785" x-info="http://www.rsyslog.com";] start
  Oct 30 23:43:42 ubuntu-phablet rsyslogd-2307: warning: ~ action is 
deprecated, consider using the 'stop' statement instead [try 
http://www.rsyslog.com/e/2307 ]
  Oct 30 23:43:42 ubuntu-phablet rsyslogd-2307: warning: ~ action is 
deprecated, consider using the 'stop' statement instead [try 
http://www.rsyslog.com/e/2307 ]
  Oct 30 23:43:42 ubuntu-phablet rsyslogd: rsyslogd's groupid changed to 103
  Oct 30 23:43:42 ubuntu-phablet rsyslogd: rsyslogd's userid changed to 100
  Oct 30 23:43:42 ubuntu-phablet kernel: [0.00]Booting Linux on 
physical CPU 0
  Oct 30 23:43:42 ubuntu-phablet kernel: [0.00]Initializing cgroup 
subsys cpu
  Oct 30 23:43:42 ubuntu-phablet kernel: [0.00]Linux version 3.4.67 
(root@android-barajas_1414177384) (gcc version 4.7 (GCC) ) #1 SMP PREEMPT Tue 
Oct 28 11:57:42 UTC 2014

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

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


[Touch-packages] [Bug 1479442] Re: IN CAR: Previous Calls log is not shown in the car display

2018-11-12 Thread Daniel van Vugt
Ubuntu Touch is no longer supported.

** Changed in: bluez (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  IN CAR: Previous Calls log is not shown in the car display

Status in Canonical System Image:
  Triaged
Status in bluez package in Ubuntu:
  Won't Fix

Bug description:
  STEPS:
  Requirements: DUT a list of previous calls and a car that support bluetooth 
phones (Skoda Superb 2013 in my case)

  1. Connect DUT to the car
  2. In the car menu navigate to previous calls log

  EXPECTED:
  I expect to see a list of past calls similar to those I see on the phone 
itself

  ACTUAL:
  Car shows no previous calls log at all

  VERSIONS:
  current build number: 71
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.en
  last update: 2015-07-28 18:01:08
  version version: 71
  version ubuntu: 20150728
  version device: 20150709-8965e37
  version custom: 20150716-819-8-42

  MODIFICATIONS:
  Installation of silo19 for in car bt fix

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

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


[Touch-packages] [Bug 1398193] Re: The bluetooth headset cannot control media playback (AVRCP)

2018-11-12 Thread Daniel van Vugt
Ubuntu Touch is no longer a supported.

** Changed in: bluez (Ubuntu)
   Status: Triaged => Won't Fix

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

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

Title:
  The bluetooth headset cannot control media playback (AVRCP)

Status in Canonical System Image:
  Won't Fix
Status in bluez package in Ubuntu:
  Won't Fix
Status in media-hub package in Ubuntu:
  Invalid
Status in media-hub package in Ubuntu RTM:
  Invalid

Bug description:
  [Preconditions]
  1.The DUT pair with bluetooth headset

  [Procedures]
  1.Play a video using the mediaplayer-app
  2.Play/pause video by bluetooth headset

  [Expect results]
  The bluetooth headset can play/pause video
  [Actual results]
  The bluetooth headset can not control the video playback.

  [Reproduce]
  Always

  Same for audio playback

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

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


[Touch-packages] [Bug 1398193] Re: The bluetooth headset cannot control media playback (AVRCP)

2018-11-12 Thread Daniel van Vugt
Ubuntu Touch is no longer supported.

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

Title:
  The bluetooth headset cannot control media playback (AVRCP)

Status in Canonical System Image:
  Won't Fix
Status in bluez package in Ubuntu:
  Won't Fix
Status in media-hub package in Ubuntu:
  Invalid
Status in media-hub package in Ubuntu RTM:
  Invalid

Bug description:
  [Preconditions]
  1.The DUT pair with bluetooth headset

  [Procedures]
  1.Play a video using the mediaplayer-app
  2.Play/pause video by bluetooth headset

  [Expect results]
  The bluetooth headset can play/pause video
  [Actual results]
  The bluetooth headset can not control the video playback.

  [Reproduce]
  Always

  Same for audio playback

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

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


[Touch-packages] [Bug 1763580] Re: Xorg crash

2018-11-12 Thread Daniel van Vugt
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:

1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where
ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
Do you find any links to recent problems on that page? If so then please
send the links to us.

3. If step 2 also failed then apply the workaround from bug 994921,
reboot, reproduce the crash, and retry step 1.

Please take care to avoid attaching .crash files to bugs as we are
unable to process them as file attachments. It would also be a security
risk for yourself.

** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)

** Changed in: xorg-server (Ubuntu)
   Status: New => Incomplete

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

Title:
  Xorg crash

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  Crash occurs every time when booting from Xubuntu 18.04 installation
  stick and choosing "Install Xubuntu". Shortly after selecting "Install
  Xubuntu", the installer is started, the installation screen is visible
  for a few seconds, then the display quickly blanks and drops the user
  into a frozen view of the virtual terminal. Shortly thereafter, a
  Xubuntu session is automatically started, similarly to having chosen
  "Try Xubuntu without installing". Executing "Install Xubuntu" from the
  desktop does successfully start the ubiquity installer.

  Verifying the installation logs under /var/log/installer shows Xorg as
  having crashed with error:

  xf860OpenConsole: Switching VT failed

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperVersion: 1.393
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Fri Apr 13 05:42:46 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:2063]
  LiveMediaBuild: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180411)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 045e:00cb Microsoft Corp. Basic Optical Mouse v2.0
   Bus 001 Device 003: ID 04f2:0408 Chicony Electronics Co., Ltd 
   Bus 001 Device 002: ID 058f:6387 Alcor Micro Corp. Flash Drive
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper 
only-ubiquity initrd=/casper/initrd.lz quiet splash ---
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.vendor: Intel Corp.
  dmi.board.vendor: Intel corporation
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1763580/+subscriptions

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


[Touch-packages] [Bug 1763273] Re: kernel panic in Radeon driver while screen blank

2018-11-12 Thread Daniel van Vugt
** No longer affects: xorg (Ubuntu)

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

Title:
  kernel panic in Radeon driver while screen blank

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I maintain a set of older kiosks running a mix of stock Ubuntu 14.04
  LTS and 16.04.  As we have gradually transitioned them to 16.04, we
  have noticed that the machines running 16.04.1 now regularly exhibit
  problems restoring from the blank screen which appears after a period
  of inactivity.

  This only occurs on the machines where we've installed 16.04.  All of
  the 16.04.1 installations are "fresh", that is, complete re-installs
  from scratch, and we install all security and other updates on a
  regular basis.  This problem has persisted right from the beginning
  when we started using 16.04.

  Following a period of user inactivity, the screen goes blank; this is,
  of course, expected.  When the user tries to restore the session by
  typing a key or moving the mouse, one of three outcomes occurs.

  Sometimes, the session restores normally.  Other times, the screen
  remains blank regardless of all normal keyboard input, until a magic
  SysRq  sequence is performed.  After Alt-SysRq-k, either the virtual
  console resets to a login screen (as expected after this SysRq
  sequence), or we get a kernel panic text screen (see attached screen
  photo) and can only restore via a hard power-cycle reboot.

  I will continue to try to capture a better trace output from one of
  these conditions, perhaps from /var/log/kern.log or by installing
  linux-crashdump (although these old machines may not have enough
  memory for the stock package).  But in the meantime, I'm attaching a
  photo of the kernel panic we see, which suggests a problem may reside
  in the Radeon driver ... which would seem possible, given the general
  blank-screen no-resume problem on these systems.

  Any advice on how to further capture any other needed details would be
  appreciated.  Thanks very much!

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

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


[Touch-packages] [Bug 1379485] Re: bluez only manages one modem with HSP (not dual as we have on krillin)

2018-11-12 Thread Daniel van Vugt
Ubuntu Touch is no longer supported.

** Changed in: bluez (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  bluez only manages one modem with HSP (not dual as we have on krillin)

Status in bluez package in Ubuntu:
  Won't Fix

Bug description:
  STEPS:
  1. Have a device with 2 sim cards
  2. Connect to a bluetooth car/headset
  (car is better it shows the network you are connected to)
  3. Call sim number one (rings on phone but not bt device)
  4. Call sim number two (rings on phone and bt device)

  EXPECTED:
  In both situations you expect the call to trigger the ringer on both of the 
sims numbers

  ACTUAL:
  For me only sim number 2 triggers the ringer on the device and the mobile.

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

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


[Touch-packages] [Bug 1479440] Re: IN CAR: Missed calls are not shared with the car via bluetooth

2018-11-12 Thread Daniel van Vugt
Ubuntu Touch is no longer supported.

** Changed in: bluez (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  IN CAR: Missed calls are not shared with the car via bluetooth

Status in bluez package in Ubuntu:
  Won't Fix

Bug description:
  STEPS:
  Requirements: DUT, a secondary device and a car with bluetooth phone 
capabilities (Skoda Superb 2013 in my case)

  1. Connect the DUT to the car
  2. Using the menu system in the car navigate to missed calls
  3. Message There are no missed calls
  4. Call the DUT from the secondary device
  5. Hang up the secondary device once the call is received
  6. Check the missed calls log again (shows on the phone but not on the car)

  EXPECTED:
  I expect to see a list of missed calls

  ACTUAL:
  No missed call are available 

  VERSIONS:
  current build number: 71
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.en
  last update: 2015-07-28 18:01:08
  version version: 71
  version ubuntu: 20150728
  version device: 20150709-8965e37
  version custom: 20150716-819-8-42

  MODIFICATIONS:
  Installation of silo19 for in car bt fix

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

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


[Touch-packages] [Bug 1479438] Re: IN CAR: Battery levels not shared via bluetooth for in car experience

2018-11-12 Thread Daniel van Vugt
Ubuntu Touch is no longer supported.

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

Title:
  IN CAR: Battery levels not shared via bluetooth for in car experience

Status in Canonical System Image:
  Won't Fix
Status in bluez package in Ubuntu:
  Won't Fix
Status in ofono package in Ubuntu:
  Won't Fix
Status in ofono package in Ubuntu RTM:
  Won't Fix

Bug description:
  STEPS:
  Requirements: DUT a car with bluetooth and phone connection kit (Skoda Superb 
2013 in my instance)

  1. Connect the DUT to the car
  2. On the display panel the battery always shows full

  EXPECTED:
  I expect to see the actual level of the battery on the device

  ACTUAL:
  The display always shows the battery at 100% I assume the default if no info 
is available.

  VERSIONS:
  current build number: 71
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.en
  last update: 2015-07-28 18:01:08
  version version: 71
  version ubuntu: 20150728
  version device: 20150709-8965e37
  version custom: 20150716-819-8-42

  MODIFICATIONS:
  Installation of silo19 for in car bt fix

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

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


[Touch-packages] [Bug 1496102] Re: Bluetooth connection breaks in a few seconds

2018-11-12 Thread Daniel van Vugt
Ubuntu Touch is no longer supported.

** Changed in: bluez (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  Bluetooth connection breaks in a few seconds

Status in Canonical System Image:
  Confirmed
Status in bluez package in Ubuntu:
  Won't Fix

Bug description:
  Tried to connect with my MX4 to an Android, then to a Lumia phone.
  Devices discover each other, they get "Connected", but in about 5-15
  seconds they get "Disconnected" again.

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

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


[Touch-packages] [Bug 1240585] Re: After rebooting while in a voice call, there is no sound until the next call

2018-11-12 Thread Daniel van Vugt
Ubuntu Touch is no longer supported.

** Changed in: pulseaudio (Ubuntu)
   Status: New => Won't Fix

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

Title:
  After rebooting while in a voice call, there is no sound until the
  next call

Status in pulseaudio package in Ubuntu:
  Won't Fix

Bug description:
  Today I upgraded to image 99 and no sound worked in the music and
  settings app (testing phone sounds). Rebooted multiple times and same
  issue. I saw the indicator and volume control as expected, and ensured
  it was up.

  When putting my phone up to my ear I also heard light crackling from
  the speaker.

  I then called my phone to test if calls could be heard and it worked
  as expected, and then the music app worked fine. It seemed to unblock
  the sound.

  ogre seems to think it is something to do with transitioning between
  sound profiles and asked me to file a bug. :-)

  Update: before I had this issue I had to hang up while on a call, so
  that may be the cause.

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

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


[Touch-packages] [Bug 1740134] Re: File received with "bluetooth file transfer" cannot be saved

2018-11-12 Thread Daniel van Vugt
Ubuntu Touch is no longer supported.

** Changed in: bluez (Ubuntu)
   Status: New => Won't Fix

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

Title:
  File received with "bluetooth file transfer" cannot be saved

Status in bluez package in Ubuntu:
  Won't Fix

Bug description:
  Receiving files with "bluetooth file transfer" works fine -- but just that. 
The files received appear in the lower part of the app window, but you cannot 
save them anywhere! Swiping to the right only shows the trash can symbol, so 
literally the only thing I can do with the received files is delete them! You 
can't even save them to the "Downloads" folder. What good is a file transfer 
tool, if the received file cannot be used any further?
  I am quite puzzled -- or am I missing something essential?

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

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


[Touch-packages] [Bug 1411437] Re: [mako] crash right after the boot (segfault in plugins/hciops.c:2910)

2018-11-12 Thread Daniel van Vugt
Ubuntu Touch is no longer supported.

** Changed in: bluez (Ubuntu)
   Status: New => Won't Fix

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

Title:
  [mako] crash right after the boot (segfault in plugins/hciops.c:2910)

Status in bluez package in Ubuntu:
  Won't Fix

Bug description:
  current build number: 66
  device name: mako
  channel: ubuntu-touch/vivid-proposed
  last update: 2015-01-15 21:43:12
  version version: 66
  version ubuntu: 20150115
  version device: 20141213
  version custom: 20150115

  Right after a clean flash.

  Backtrace:
  #0  device_event (event=, index=0) at plugins/hciops.c:2910
  No locals.
  #1  0xb6f76b5c in io_stack_event (chan=, cond=, 
data=) at plugins/hciops.c:3027
  buf = 
"\004\375\006\001\000\003\000\000\000\000\000\000\237\366߶\200\067\370\276T8\370\276\020\237\363\266_\366߶+\000\000\000\a\000\000\000T8\370\276E\333߶\240\067\370\276$/;\270\000\000\000\000p7\370\276\310\067\370\276\000#a\b\300\067\370\276\001\000\000\000\t\000\000\000\003\237\363\266\001\000\000\000$/;\270/\000\000\000\207\327\340\266\000\000\000\000\001\000\000\000\060\000\000\000$/;\270/\000\000\000\343\327\340\266\020\237\363\266\000#a>\374\001\000\000\b\000\000\000\240\070\370\276g\000\000\000T8\370\276W\332\340\266\060\000\000\000\000#a>\002\000\000\000\a0;\270\002\000\000\000\235\327\340\266$/;\270\002\000\000\000$/;\270\000\000\000\000$8\370"...
  ptr = 0xbef8372b "\001"
  si = 0xbef8372b
  eh = 0xbef83729
  type = 
  fd = 
  #2  0xb6e630f8 in g_main_dispatch (context=0xb83ac100) at 
/build/buildd/glib2.0-2.43.2/./glib/gmain.c:3122
  dispatch = 0xb6e9350d 
  prev_source = 0x0
  was_in_call = 0
  user_data = 0x0
  callback = 0xb6f76b01 
  cb_funcs = 0xb6f01594 
  cb_data = 0xb83b5748
  need_destroy = 
  source = 0xb83b56e8
  current = 0xb83b51e0
  i = 2
  #3  g_main_context_dispatch (context=context@entry=0xb83ac100) at 
/build/buildd/glib2.0-2.43.2/./glib/gmain.c:3737
  No locals.
  #4  0xb6e6337c in g_main_context_iterate (context=0xb83ac100, 
block=block@entry=1, dispatch=dispatch@entry=1, self=) at 
/build/buildd/glib2.0-2.43.2/./glib/gmain.c:3808
  max_priority = 0
  timeout = 0
  some_ready = 1
  nfds = 
  allocated_nfds = 
  fds = 0xb83b5880
  #5  0xb6e63618 in g_main_loop_run (loop=0xb83ab018) at 
/build/buildd/glib2.0-2.43.2/./glib/gmain.c:4002
  __FUNCTION__ = "g_main_loop_run"
  #6  0xb6f473ba in main (argc=1, argv=0xbef83e14) at src/main.c:542
  context = 
  err = 0x0
  __FUNCTION__ = "main"

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

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


[Touch-packages] [Bug 1638270] Re: carkit bluetooth reboots ubuntu touch on Nexus4 when switched on/off a couple of times

2018-11-12 Thread Daniel van Vugt
Ubuntu Touch is no longer supported.

** Changed in: bluez (Ubuntu)
   Status: New => Won't Fix

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

Title:
  carkit bluetooth reboots ubuntu touch on Nexus4 when switched on/off a
  couple of times

Status in bluez package in Ubuntu:
  Won't Fix

Bug description:
  My bluetooth car hands free system reboots my Nexus4 phone when set to auto 
reconnect and then the ignition switch is turned on and off a couple of times. 
The carkit is recognized as "comf_comp_V12b".
  I am using the Aquarius image (though it previously occurs with the standard 
Nexus4 image). I am dual booting with Android.
   What other information can I give to help find the problem?
  Thanks 

  bluetoothctl --version 
5.41

  uname -a
Linux ubuntu-phablet 3.4.0-7-mako #1-Ubuntu SMP PREEMPT Thu Sep 3 15:30:20  
 UTC 2015 armv7l armv7l armv7l GNU/Linux

  hciconfig -a
  hci0: Type: Primary  Bus: SPI
BD Address: BC:F5:AC:47:69:30  ACL MTU: 1024:6  SCO MTU: 50:8
UP RUNNING PSCAN 
RX bytes:0 acl:0 sco:0 events:167 errors:0
TX bytes:0 acl:0 sco:0 commands:0 errors:0
Features: 0xff 0xfe 0x8f 0xfe 0xd8 0x3f 0x5b 0x87
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 
Link policy: RSWITCH HOLD SNIFF 
Link mode: SLAVE ACCEPT 
Name: 'Nexus 4'
Class: 0x5c
Service Classes: Rendering, Capturing, Object Transfer, Telephony
Device Class: Miscellaneous, 
HCI Version: 4.0 (0x6)  Revision: 0x0
LMP Version: 4.0 (0x6)  Subversion: 0x7d3
Manufacturer: Qualcomm (29)
  bluetoothctl
  [NEW] Controller BC:F5:AC:47:69:30 Nexus 4 [default]
  [NEW] Device 00:16:73:21:50:AE comf_comp V12b

  unity8.log:
  [2016-11-01:12:21:50.790] qtmir.mir: SessionListener::stopping - this= 
SessionListener(0xb02d92fc) session= 0x10fde84
  g_dbus_connection_real_closed: Remote peer vanished with error: Error 
receiving message: Connection reset by peer (g-io-error-quark, 44). Exiting.
  [2016-11-01:12:21:50.802] qtmir.mir: SessionListener::stopping - this= 
SessionListener(0xb02d92fc) session= 0x10e3d44
  [2016-11-01:12:21:52.655] qtmir.mir: SessionListener::stopping - this= 
SessionListener(0xb02d92fc) session= 0xad03408c
  [2016-11-01:12:21:52.695] qtmir.screens: Destroying ScreenWindow 0x16d9f58
  [2016-11-01:12:21:52.989] qtmir.surfaces: 
MirSurfaceManager::~MirSurfaceManager - this= 
qtmir::MirSurfaceManager(0x127f740, name = "qtmir::SurfaceManager")

  
  bluez-mpris-proxy.log.1:
  Bluetooth Adapter /org/bluez/hci0 removed
  org.bluez disappeared
  org.bluez appeared
  Bluetooth Adapter /org/bluez/hci0 found
  player core.ubuntu.media.Service at :1.42 found
  org.bluez appeared
  Bluetooth Adapter /org/bluez/hci0 found
  player core.ubuntu.media.Service at :1.34 found

  
  Loading module: 'libubuntu_application_api_touch_mirclient.so.3.0.0'
  qml: Page_QMLTYPE_44(0x12ce3f0, "systemSettingsPage")"System Settings": In 
Ubuntu.Components 1.3, the use of Page.title, Page.flickable and Page.head is 
deprecated. Use Page.header and the PageHeader component instead.
  BrightnessItem::BrightnessItem(const QVariantMap&, QObject*) 
ubuntu.widi.supported: 0
  2016-11-01 13:23:59,230 - WARNING - 
file:///usr/lib/arm-linux-gnueabihf/qt5/qml/Ubuntu/Components/1.3/PageStack.qml:230:9:
 QML PageWrapper: Could not assign value: QVariant(QVariantMap, QMap())  to 
property:  "pluginOptions" 
  2016-11-01 13:23:59,558 - WARNING - 
file:///usr/share/ubuntu/settings/system/qml-plugins/bluetooth/PageComponent.qml:255:17:
 QML Label: Possible anchor loop detected on horizontal anchor.
  2016-11-01 13:23:59,559 - WARNING - 
file:///usr/share/ubuntu/settings/system/qml-plugins/bluetooth/PageComponent.qml:255:17:
 QML Label: Possible anchor loop detected on horizontal anchor.
  2016-11-01 13:23:59,619 - WARNING - 
file:///usr/share/ubuntu/settings/system/qml-plugins/bluetooth/PageComponent.qml:296:25:
 QML ActivityIndicator: 
file:///usr/lib/arm-linux-gnueabihf/qt5/qml/Ubuntu/Components/Themes/Ambiance/1.3/ActivityIndicatorStyle.qml:24
 Invalid property assignment: "implicitHeight" is a read-only property

  application-legacy-ubuntu-system-settings-.log.1.gz:
  2016-11-01 13:23:59,633 - WARNING - 
file:///usr/share/ubuntu/settings/system/qml-plugins/bluetooth/PageComponent.qml:251:
 TypeError: Property 'adapterName' of object Bluetooth(0x16171b0) is not a 
function
  2016-11-01 13:23:59,821 - WARNING - Last frame took 44 ms to render.

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

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


[Touch-packages] [Bug 1652303] Re: Ubuntu Touch Bluetooth Lag

2018-11-12 Thread Daniel van Vugt
Ubuntu Touch is no longer supported.

** Changed in: bluez (Ubuntu)
   Status: New => Won't Fix

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

Title:
  Ubuntu Touch Bluetooth Lag

Status in bluez package in Ubuntu:
  Won't Fix

Bug description:
  I am running Meizu Pro 5 rc-proposed Version 249. When running the
  phone in Desktop Mode (connecting to a Microsoft Wireless Display
  Adapter v2) and using a bluetooth keyboard and mouse, there are
  frequent lags of 3-4 seconds between moving the mouse pointer or
  typing and what appears on the connected monitor screen.

  After researching this, I discovered this old bug "Bluetooth does not
  coexist with WiFi" :

  https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/219057

  Simply adding "options iwlwifi bt_coex_active=0" at the bottom of
  iwlwifi.conf in /etc/modprobe.d/ and rebooting, seems to have all but
  solved the lag problem.

  Suggest the iwlwifi.conf might be updated in future builds?

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

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


[Touch-packages] [Bug 1447329] Re: Music plays shorty after disconnecting bluetooth audio sink

2018-11-12 Thread Daniel van Vugt
Ubuntu Touch is no longer supported.

** Changed in: pulseaudio (Ubuntu)
   Status: New => Won't Fix

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

Title:
  Music plays shorty after disconnecting bluetooth audio sink

Status in Ubuntu Music App:
  Invalid
Status in pulseaudio package in Ubuntu:
  Won't Fix

Bug description:
  Expected behaviour:
  After disconnecting or powering off an bluetooth audio sink, music should 
stop playing.

  What music does:
  Shorty after the phone looses the BT connection, the last sond is played on 
the phone for about half a second.

  Test case:
  - connect you phone to a bluetooth sink capable of A2DP
  - start listening
  - power down the BT sink
  -> audio is played using the phone speaker for a short time

  I tested this with two different audio sinks: a car handset and a
  Jawbone Jambox.

  I consider this a very unconvenient bug. It's simply annoying.

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

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


[Touch-packages] [Bug 1421598] Re: DisplayPasskey() "entered" number wrong on some devices

2018-11-12 Thread Daniel van Vugt
Ubuntu Touch is no longer supported.

** Changed in: bluez (Ubuntu)
   Status: New => Won't Fix

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

Title:
  DisplayPasskey() "entered" number wrong on some devices

Status in bluez package in Ubuntu:
  Won't Fix

Bug description:
  Using vivid on the n7, the number of "entered" digit is random/wrong,
  it should start at 0 and increase to 6 as you type, but on that device
  it returns random value (i.e 75, 92, etc)

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

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


[Touch-packages] [Bug 1649144] Re: Bluetooth audio quality bad

2018-11-12 Thread Daniel van Vugt
Ubuntu Touch is no longer supported.

** Changed in: bluez (Ubuntu)
   Status: New => Won't Fix

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

Title:
  Bluetooth audio quality bad

Status in bluez package in Ubuntu:
  Won't Fix

Bug description:
  Listening to music using a2dp compatible bt headphones, the audio is
  bad. Let me explain. If I plug in a pare of headphones with a 3.5 mm
  stereo plug and compare it to the bluetooth audio, I cannot tell the
  difference in most devices. I know that a2dp is done with lossy
  compression, so in theory the audio quality suffers. However, the
  difference is minimal, something that you can either barely notice, or
  at times other links in the audio-to-ear chain are way worse masking
  the quality difference from compression. I have tested this on
  Android, Debian, Ubuntu etc. and I have to admit that most of the time
  there appears to be no difference to me.

  However, on Ubuntu touch (arale OTA-14) there is a difference that any
  one can notice immediately. The bluetooth audio is really poor, sounds
  as if it were distoreted and compressed or sample rate lowered or
  something. Not poor enough to make it unusable but poor enough that
  you notice it right away.

  I have no idea what package is causing this, but I suspect that it has
  something to do with either audio mixer or bluetooth. But everything
  seems to be OK. AFAIK the audio settings are as I would expect.

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

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


[Touch-packages] [Bug 1544254] Re: connected bt mouse/kybd get disconnected/not in "connect when active" list

2018-11-12 Thread Daniel van Vugt
Ubuntu Touch is no longer supported.

** Changed in: bluez (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  connected bt mouse/kybd get disconnected/not in "connect when active"
  list

Status in Canonical System Image:
  Incomplete
Status in Canonical Pocket Desktop:
  New
Status in bluez package in Ubuntu:
  Won't Fix

Bug description:
  So I've been running ubuntu-pd on Nexus4 over a few days and began
  noticing this.

  1. connect bt mouse and keyboard
  2. connect to external monitor
  3. use device for extended period of time

  sometimes the devices will appear to disconnect, as well as be forgotten.
  I can't tell if this is in conjunction with the screen blanking or not

  I've even run into the kybd being forgotten, while the mouse was
  remembered.

  here's my devices info
  [bluetooth]# paired-devices
  Device 34:88:5D:24:05:61 Logitech Keyboard K480
  Device F0:65:DD:AA:04:8B HP Bluetooth Mouse X4000b
  [bluetooth]# info 34:88:5D:24:05:61
  Device 34:88:5D:24:05:61
   Name: Logitech Keyboard K480
   Alias: Logitech Keyboard K480
   Class: 0x002540
   Icon: input-keyboard
   Paired: yes
   Trusted: yes
   Blocked: no
   Connected: yes
   LegacyPairing: yes
   UUID: Service Discovery Serve.. (1000--1000-8000-00805f9b34fb)
   UUID: Human Interface Device... (1124--1000-8000-00805f9b34fb)
   UUID: PnP Information   (1200--1000-8000-00805f9b34fb)
   Modalias: usb:v046DpB330d2800
  [bluetooth]# info F0:65:DD:AA:04:8B
  Device F0:65:DD:AA:04:8B
   Name: HP Bluetooth Mouse X4000b
   Alias: HP Bluetooth Mouse X4000b
   Class: 0x002580
   Icon: input-mouse
   Paired: yes
   Trusted: yes
   Blocked: no
   Connected: yes
   LegacyPairing: no
   UUID: Service Discovery Serve.. (1000--1000-8000-00805f9b34fb)
   UUID: Human Interface Device... (1124--1000-8000-00805f9b34fb)
   UUID: PnP Information   (1200--1000-8000-00805f9b34fb)
   Modalias: usb:v03F0p024Cd0103
  [bluetooth]#

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

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


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

2018-11-12 Thread Daniel van Vugt
Ubuntu Touch is no longer supported.

** Changed in: bluez (Ubuntu)
   Status: Confirmed => Won't Fix

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

** Changed in: ofono (Ubuntu)
   Status: Confirmed => Won't Fix

** Changed in: pulseaudio (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  Call audio is not routed to headset with HFP

Status in Canonical System Image:
  Won't Fix
Status in bluez package in Ubuntu:
  Won't Fix
Status in media-hub package in Ubuntu:
  Invalid
Status in ofono package in Ubuntu:
  Won't Fix
Status in pulseaudio package in Ubuntu:
  Won't Fix

Bug description:
  With bluez 5.33 on Nexus 4 and silo 43 installed:

  * pair and connect a headset over HFP
  * Establish an outgoing call or accept an incoming one
  * Once the call is established the call audio isn't routed through the 
handsfree device

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

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


  1   2   3   >