[Touch-packages] [Bug 1711605] Re: [xenial] A2DP profile still alive even though disconnected
Hi Daniel, Sorry for late response. This issue has been resolved since pulseaudio-8.0-0ubuntu3.4 version. Thanks for fixing the issue. pulseaudio (1:8.0-0ubuntu3.4) xenial; urgency=medium * debian/control: Update Vcs fields to launchpad git. * Cherrypick fixes for common crashes from upstream: - cb78d6f5: SIGABRT in device_start_waiting_for_profiles (LP: #1690028, LP: #1672171) - d985276c: SIGABRT in pa_alsa_path_set_volume (LP: #1539209, LP: #1562817) -- Daniel van Vugt Fri, 11 Aug 2017 15:16:57 +0800 ** Changed in: pulseaudio (Ubuntu) Status: New => Fix Released -- 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/1711605 Title: [xenial] A2DP profile still alive even though disconnected Status in pulseaudio package in Ubuntu: Fix Released Bug description: During connect/disconnect with BT headset repeatedly, the bluetooth connection(check using hcitool) is still alive even thoush the connection has been disconnected by bluetoothctl. The hsp profile is still connected on pulseaudio. --- Since the pulseaudio of Xenial has been updated from 8.0-0ubuntu3.2 to 8.0-0ubuntu3.3 at last May, I failed my TestCase The test case is just repeating connect/disconnect with BT headset through bluetoothctl. The change[1] can be retrieved from Xenial's pulseaudio source but I can't ensure which patch causes the problem. You can see the error log[2] when the error has been occurred. [1] pulseaudio (1:8.0-0ubuntu3.3) xenial; urgency=medium [Luke Yelavich, Konrad Zapałowicz] * Fixed multiple interrelated problems with using Bluetooth audio (A2DP), where users would experience some combination of: - Bluetooth headset/speakers listed but not selectable in Sound settings (LP: #1283003) - [regression] Bluetooth audio no longer supports A2DP (stuck in HSP/HFP mode) (LP: #1438510) - [xenial] Bluetooth device doesn't play any sound in A2DP mode unless set to HSP/HFP first (LP: #1582213) * Specific patches from upstream used to address the above problems: - 0103-bluetooth-Add-support-for-automatic-switch-between-h.patch - 0104-bluetooth-Add-support-for-automatic-switch-bluez5.patch - 0106-bluetooth-Add-optional-heuristic-for-switching-betwe.patch . Backport from upstream to fix a bug in Xenial where an incorrect audio profile is applied for a headset connected over Bluetooth making using it impossible. - 0105-bluetooth-policy-do-A2DP-profile-restoring-a-bit-lat.patch . Fix a crash that happens if the BT headset is the only non-monitor source in the system and the last "phone" stream dies. - 0700-pulsecore-add-new-card-profile-hook.patch . Backport from upstream (commit 7b6260140149) to allow for correct profile selection. - 0701-bluetooth-bluez5-wait-for-all-profiles-to-connect.patch . Backport from upstream waiting for all profiles to connect before creating a card. -- Daniel van Vugt Tue, 23 May 2017 16:24:14 +0800 [2] Error log D: [pulseaudio] backend-native.c: dbus: path=/Profile/HSPAGProfile, interface=org.bluez.Profile1, member=NewConnection D: [pulseaudio] backend-native.c: dbus: NewConnection path=/org/bluez/hci0/dev_00_18_09_2C_1F_41, fd=18 D: [pulseaudio] bluez5-util.c: Transport /org/bluez/hci0/dev_00_18_09_2C_1F_41/fd18 state changed from disconnected to idle D: [pulseaudio] backend-native.c: Transport /org/bluez/hci0/dev_00_18_09_2C_1F_41/fd18 available for profile headset_head_unit D: [pulseaudio] backend-native.c: RFCOMM << AT+VGS=07 D: [pulseaudio] backend-native.c: RFCOMM >> OK D: [pulseaudio] bluez5-util.c: d
[Touch-packages] [Bug 1751011] Re: bash crashes in qemu-user environments (bionic)
I'd like to know any progress from the qemu community. I feel like it would be long journey to address this problem. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1751011 Title: bash crashes in qemu-user environments (bionic) Status in bash package in Ubuntu: Triaged Status in bash package in Debian: Fix Released Bug description: Attempts to launch bash in an arm64 qemu-user environment in bionic results in the following error message: bash: xmalloc: .././shell.c:1709: cannot allocate 10 bytes (0 bytes allocated) This causes any qemu/chroot based bootstrapping to fail as many packages invoke bash during postinst. Version: bash_4.4.18-1ubuntu1_arm64 Release: 18.04 pre-release QEMU: 2.8.0 This appears to have been reported and fixed in the corresponding Debian package (https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=889869) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1751011/+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 1759961] Re: Update to bluez 5.50
Hi all, I've encountered Heart rate profile connection error of bluez-5.48 in Bionic. It can be resolved in bluez 5.49 version from below commit. - Fix issue with Connect and ConnectProfile returning in progress. Do you have a plan to upgrade the bluez version to 5.50 for Bionic as well? If not, could you pick the patch for Ubuntu bionic's bluez version. If you want to create a ticket for this release, I can make it. -- 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/1759961 Title: Update to bluez 5.50 Status in bluez package in Ubuntu: Fix Released Bug description: From upstream: http://www.bluez.org/release-of-bluez-5-49/ Release of BlueZ 5.49 This is mostly a bug fix release, with fixes to features such as AVCTP, OBEX, GATT and Mesh. There are however some notable new features also, such as improved heartbeat management support in meshctl as well as a new experimental ConnectDevice D-Bus method on the Adapter interface, which can be used for quick device object creation for testing purpose or when information about the device has been received over some Out-of-Band channel. Upstream changelog: https://git.kernel.org/pub/scm/bluetooth/bluez.git/tree/ChangeLog ver 5.49: Fix issue with configuring discoverable advertising flag. Fix issue with bearer selection and single mode controllers. Fix issue with Connect and ConnectProfile returning in progress. Fix issue with missing Paired property change when not bonded. Fix issue with storage for controllers without public address. Fix issue with handling AVCTP disconnecting the channel queue. Fix issue with not clearing connectable setting on power off. Fix issue with creating multiple mgmt socket instances. Fix issue with GATT server and BR/EDR only devices. Fix issue with InterfaceAdded event ordering. Add support for generic ConnectDevice method call. Add support for Mesh heartbeat client functionality. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1759961/+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 1732997] Re: bionic bash 4.4-5 failed to unpack
Hi, I have same error when I tried to run debootstrap --second-stage. Anyone who have the solution? Here is my test sequence. 1. Environment $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 16.04.3 LTS Release:16.04 Codename: xenial $ $ uname -a Linux cometzero-ubuntu 4.4.0-104-generic #127-Ubuntu SMP Mon Dec 11 12:16:42 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux 2. debootstrap stage1 $ sudo debootstrap --verbose --foreign --arch armhf bionic ./ubuntu http://ports.ubuntu.com 3. debootstrap stage2 $ sudo mount --bind /proc ubuntu/proc $ sudo mount --bind /dev ubuntu/dev $ sudo mount --bind /sys ubuntu/sys $ sudo cp /usr/bin/qemu-arm-static ubuntu/usr/bin $ sudo chroot ubuntu (inside chroot) $ /debootstrap/debootstrap --second-stage I: Keyring file not available at /usr/share/keyrings/ubuntu-archive-keyring.gpg; switching to https mirror https://mirrors.kernel.org/debian I: Installing core packages... I: Unpacking required packages... snip.. W: Failure while unpacking required packages. This will be attempted up to five times. W: See //debootstrap/debootstrap.log for details (possibly the package /var/cache/apt/archives/bash_4.4-5ubuntu1_armhf.deb is at fault) >From /debootstrap/debootstrap.log) dpkg: warning: ignoring pre-dependency problem! Preparing to unpack .../bash_4.4-5ubuntu1_armhf.deb ... preinst: ../sysdeps/unix/sysv/linux/spawni.c:368: __spawnix: Assertion `ec >= 0' failed. qemu: uncaught target signal 6 (Aborted) - core dumped dpkg: error processing archive /var/cache/apt/archives/bash_4.4-5ubuntu1_armhf.deb (--unpack): new bash package pre-installation script subprocess was killed by signal (Aborted), core dumped -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1732997 Title: bionic bash 4.4-5 failed to unpack Status in bash package in Ubuntu: New Bug description: Failure while unpacking required packages In debootstrap bash_4.4-5ubuntu1_armhf.deb is at fault. my question is can i get an eta on when the file will be updated/fixed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1732997/+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 1621824] Re: MFG:Garrison - Ubuntu 16.04.1 dmesg error "systemd[1]: Failed to start Set console keymap."
Hi, I've same error on my arm64 board with xenial. Could you also apply this for arm64 architecture? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kbd in Ubuntu. https://bugs.launchpad.net/bugs/1621824 Title: MFG:Garrison - Ubuntu 16.04.1 dmesg error "systemd[1]: Failed to start Set console keymap." Status in kbd package in Ubuntu: Fix Released Status in kbd source package in Xenial: Fix Released Status in kbd source package in Yakkety: Fix Released Bug description: [SRU Justification] On ppc64el, console keyboard maps will not be set at boot time because of a bug in detecting which VT is "safe" to use for setting the map. This problem does not affect amd64 purely by chance, or because of which toolchain version or toolchain options were used to build the binary on each architecture; a rebuild of the kbd package could also introduce the problem on amd64. [Test case] 1. On ppc64el, run 'sudo loadkeys /etc/console-setup/cached.kmap.gz' 2. Confirm that you are shown an error, "Couldn't get a file descriptor referring to the console". 3. Install the kbd package from xenial-proposed. 4. Run 'sudo loadkeys /etc/console-setup/cached.kmap.gz' again. 5. Confirm that no error message is shown and the command exits with staus 0. 6. Repeat steps 3-6 on amd64. [Regression potential] Since keymap settings are currently not being applied on ppc64el, it's possible that someone who has configured a non-default keymap on a ppc64el system will be surprised after upgrade that their keymap has changed. == Comment: #1 - Application Cdeadmin <> - 2016-08-23 15:05:14 == State: Open by: knodelk on 23 August 2016 14:00:43 Seeing the following error message in the Ubuntu dmesg log following IPL to Ubuntu on system with Ubuntu 16.04.1 installed: # dmesg -T --level=alert,crit,err [Tue Aug 23 09:20:12 2016] systemd[1]: Failed to start Set console keymap. This appears to be something that can be ignored so manufacturing will be ignoring this message until directed otherwise. ==> all systemd related messages: # dmesg -T | grep systemd [Tue Aug 23 09:20:12 2016] systemd[1]: systemd 229 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN) [Tue Aug 23 09:20:12 2016] systemd[1]: Detected architecture ppc64-le. [Tue Aug 23 09:20:12 2016] systemd[1]: Set hostname to . [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on Device-mapper event daemon FIFOs. [Tue Aug 23 09:20:12 2016] systemd[1]: Started Forward Password Requests to Wall Directory Watch. [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on /dev/initctl Compatibility Named Pipe. [Tue Aug 23 09:20:12 2016] systemd[1]: Reached target Encrypted Volumes. [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on Syslog Socket. [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on Journal Socket. [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on Journal Socket (/dev/log). [Tue Aug 23 09:20:12 2016] systemd[1]: Reached target User and Group Name Lookups. [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on fsck to fsckd communication Socket. [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on udev Control Socket. [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on LVM2 metadata daemon socket. [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on LVM2 poll daemon socket. [Tue Aug 23 09:20:12 2016] systemd[1]: Created slice User and Session Slice. [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on udev Kernel Socket. [Tue Aug 23 09:20:12 2016] systemd[1]: Created slice System Slice. [Tue Aug 23 09:20:12 2016] systemd[1]: Mounting POSIX Message Queue File System... [Tue Aug 23 09:20:12 2016] systemd[1]: Reached target Slices. [Tue Aug 23 09:20:12 2016] systemd[1]: Starting Create list of required static device nodes for the current kernel... [Tue Aug 23 09:20:12 2016] systemd[1]: Starting Nameserver information manager... [Tue Aug 23 09:20:12 2016] systemd[1]: Starting Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling... [Tue Aug 23 09:20:12 2016] systemd[1]: Mounting RPC Pipe File System... [Tue Aug 23 09:20:12 2016] systemd[1]: Created slice system-serial\x2dgetty.slice. [Tue Aug 23 09:20:12 2016] systemd[1]: Started Read required files in advance. [Tue Aug 23 09:20:12 2016] systemd[1]: Starting Load Kernel Modules... [Tue Aug 23 09:20:12 2016] systemd[1]: Mounting Debug File System... [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on Journal Audit Socket. [Tue Aug 23 09:20:12 2016] systemd[1]: Starting Journal Service... [Tue Aug 23 09:20:12 2016] systemd[1]: Mounting Huge Pages File System... [Tue Aug 23 09:20:12 2016] systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point. [Tue Aug 23 0
[Touch-packages] [Bug 1709881] [NEW] [xenial] QT5 gles support for arm64 architecture
Public bug reported: According to the Xenial's build log, it did not build as gles for the arm64 even though it should be built with -opengl es2 option. > debian/rules gles2_architectures := armel armhf arm64 ifeq ($(DEB_HOST_ARCH),$(findstring $(DEB_HOST_ARCH), $(gles2_architectures))) extra_configure_opts += -opengl es2 else extra_configure_opts += -opengl desktop endif Here is the xenial's build log and it shows OpenGL as Desktop version. - Xenial build log: https://launchpadlibrarian.net/319422529/buildlog_ubuntu-xenial-arm64.qtbase-opensource-src_5.5.1+dfsg-16ubuntu7.5_BUILDING.txt.gz OpenGL / OpenVG: EGL .. yes OpenGL ... desktop However, the zesty's build log shows OpenGL as ES2. - Zesty build log: https://launchpadlibrarian.net/328680692/buildlog_ubuntu-zesty-arm64.qtbase-opensource-src_5.7.1+dfsg-2ubuntu4~1.17.04.1_BUILDING.txt.gz OpenGL / OpenVG: EGL .. yes OpenGL ... yes (OpenGL ES 2.0+) ** Affects: qtbase-opensource-src (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1709881 Title: [xenial] QT5 gles support for arm64 architecture Status in qtbase-opensource-src package in Ubuntu: New Bug description: According to the Xenial's build log, it did not build as gles for the arm64 even though it should be built with -opengl es2 option. > debian/rules gles2_architectures := armel armhf arm64 ifeq ($(DEB_HOST_ARCH),$(findstring $(DEB_HOST_ARCH), $(gles2_architectures))) extra_configure_opts += -opengl es2 else extra_configure_opts += -opengl desktop endif Here is the xenial's build log and it shows OpenGL as Desktop version. - Xenial build log: https://launchpadlibrarian.net/319422529/buildlog_ubuntu-xenial-arm64.qtbase-opensource-src_5.5.1+dfsg-16ubuntu7.5_BUILDING.txt.gz OpenGL / OpenVG: EGL .. yes OpenGL ... desktop However, the zesty's build log shows OpenGL as ES2. - Zesty build log: https://launchpadlibrarian.net/328680692/buildlog_ubuntu-zesty-arm64.qtbase-opensource-src_5.7.1+dfsg-2ubuntu4~1.17.04.1_BUILDING.txt.gz OpenGL / OpenVG: EGL .. yes OpenGL ... yes (OpenGL ES 2.0+) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1709881/+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 1709881] Re: [xenial] QT5 gles support for arm64 architecture
Gently ping about this issue :) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1709881 Title: [xenial] QT5 gles support for arm64 architecture Status in qtbase-opensource-src package in Ubuntu: New Bug description: According to the Xenial's build log, it did not build as gles for the arm64 even though it should be built with -opengl es2 option. > debian/rules gles2_architectures := armel armhf arm64 ifeq ($(DEB_HOST_ARCH),$(findstring $(DEB_HOST_ARCH), $(gles2_architectures))) extra_configure_opts += -opengl es2 else extra_configure_opts += -opengl desktop endif Here is the xenial's build log and it shows OpenGL as Desktop version. - Xenial build log: https://launchpadlibrarian.net/319422529/buildlog_ubuntu-xenial-arm64.qtbase-opensource-src_5.5.1+dfsg-16ubuntu7.5_BUILDING.txt.gz OpenGL / OpenVG: EGL .. yes OpenGL ... desktop However, the zesty's build log shows OpenGL as ES2. - Zesty build log: https://launchpadlibrarian.net/328680692/buildlog_ubuntu-zesty-arm64.qtbase-opensource-src_5.7.1+dfsg-2ubuntu4~1.17.04.1_BUILDING.txt.gz OpenGL / OpenVG: EGL .. yes OpenGL ... yes (OpenGL ES 2.0+) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1709881/+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 1709881] Re: [xenial] QT5 gles support for arm64 architecture
Hi Dmitry, Thanks for the information about version difference. Is there no possibility to update the Xenial's qt5 build as yakkety because the Xenial is LTS version and I need the feature for the arm64. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1709881 Title: [xenial] QT5 gles support for arm64 architecture Status in qtbase-opensource-src package in Ubuntu: Invalid Bug description: According to the Xenial's build log, it did not build as gles for the arm64 even though it should be built with -opengl es2 option. > debian/rules gles2_architectures := armel armhf arm64 ifeq ($(DEB_HOST_ARCH),$(findstring $(DEB_HOST_ARCH), $(gles2_architectures))) extra_configure_opts += -opengl es2 else extra_configure_opts += -opengl desktop endif Here is the xenial's build log and it shows OpenGL as Desktop version. - Xenial build log: https://launchpadlibrarian.net/319422529/buildlog_ubuntu-xenial-arm64.qtbase-opensource-src_5.5.1+dfsg-16ubuntu7.5_BUILDING.txt.gz OpenGL / OpenVG: EGL .. yes OpenGL ... desktop However, the zesty's build log shows OpenGL as ES2. - Zesty build log: https://launchpadlibrarian.net/328680692/buildlog_ubuntu-zesty-arm64.qtbase-opensource-src_5.7.1+dfsg-2ubuntu4~1.17.04.1_BUILDING.txt.gz OpenGL / OpenVG: EGL .. yes OpenGL ... yes (OpenGL ES 2.0+) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1709881/+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 1711605] [NEW] a2dp profile still alive even though disconnected
Public bug reported: Since the pulseaudio of Xenial has been updated from 8.0-0ubuntu3.2 to 8.0-0ubuntu3.3 at last May, I failed my TestCase The test case is just repeating connect/disconnect with BT headset through bluetoothctl. The change[1] can be retrieved from Xenial's pulseaudio source but I can't ensure which patch causes the problem. You can see the error log[2] when the error has been occurred. [1] pulseaudio (1:8.0-0ubuntu3.3) xenial; urgency=medium [Luke Yelavich, Konrad Zapałowicz] * Fixed multiple interrelated problems with using Bluetooth audio (A2DP), where users would experience some combination of: - Bluetooth headset/speakers listed but not selectable in Sound settings (LP: #1283003) - [regression] Bluetooth audio no longer supports A2DP (stuck in HSP/HFP mode) (LP: #1438510) - [xenial] Bluetooth device doesn't play any sound in A2DP mode unless set to HSP/HFP first (LP: #1582213) * Specific patches from upstream used to address the above problems: - 0103-bluetooth-Add-support-for-automatic-switch-between-h.patch - 0104-bluetooth-Add-support-for-automatic-switch-bluez5.patch - 0106-bluetooth-Add-optional-heuristic-for-switching-betwe.patch . Backport from upstream to fix a bug in Xenial where an incorrect audio profile is applied for a headset connected over Bluetooth making using it impossible. - 0105-bluetooth-policy-do-A2DP-profile-restoring-a-bit-lat.patch . Fix a crash that happens if the BT headset is the only non-monitor source in the system and the last "phone" stream dies. - 0700-pulsecore-add-new-card-profile-hook.patch . Backport from upstream (commit 7b6260140149) to allow for correct profile selection. - 0701-bluetooth-bluez5-wait-for-all-profiles-to-connect.patch . Backport from upstream waiting for all profiles to connect before creating a card. -- Daniel van Vugt Tue, 23 May 2017 16:24:14 +0800 [2] Error log D: [pulseaudio] backend-native.c: dbus: path=/Profile/HSPAGProfile, interface=org.bluez.Profile1, member=NewConnection D: [pulseaudio] backend-native.c: dbus: NewConnection path=/org/bluez/hci0/dev_00_18_09_2C_1F_41, fd=18 D: [pulseaudio] bluez5-util.c: Transport /org/bluez/hci0/dev_00_18_09_2C_1F_41/fd18 state changed from disconnected to idle D: [pulseaudio] backend-native.c: Transport /org/bluez/hci0/dev_00_18_09_2C_1F_41/fd18 available for profile headset_head_unit D: [pulseaudio] backend-native.c: RFCOMM << AT+VGS=07 D: [pulseaudio] backend-native.c: RFCOMM >> OK D: [pulseaudio] bluez5-util.c: dbus: path=/MediaEndpoint/A2DPSource, interface=org.bluez.MediaEndpoint1, member=SelectConfiguration D: [pulseaudio] bluez5-util.c: Unknown interface org.freedesktop.DBus.Introspectable found, skipping D: [pulseaudio] bluez5-util.c: Unknown interface org.bluez.MediaTransport1 found, skipping D: [pulseaudio] bluez5-util.c: Unknown interface org.freedesktop.DBus.Properties found, skipping D: [pulseaudio] bluez5-util.c: dbus: path=/MediaEndpoint/A2DPSource, interface=org.bluez.MediaEndpoint1, member=SetConfiguration D: [pulseaudio] bluez5-util.c: Transport /org/bluez/hci0/dev_00_18_09_2C_1F_41/fd6 state changed from disconnected to idle D: [pulseaudio] bluez5-util.c: Transport /org/bluez/hci0/dev_00_18_09_2C_1F_41/fd6 available for profile a2dp_sink D: [pulseaudio] bluez5-util.c: Properties changed in device /org/bluez/hci0/dev_00_18_09_2C_1F_41 D: [pulseaudio] backend-native.c: dbus: path=/Profile/HSPAGProfile, interface=org.bluez.Profile1, member=RequestDisconnection D: [pulseaudio] bluez5-util.c: dbus: path=/MediaEndpoint/A2DPSource, interface=org.bluez.MediaEndpoint1, member=ClearConfiguration D: [pulseaudio] bluez5-util.c: Clearing transport /org/bluez/hci0/dev_00_18_09_2C_1F_41/fd6 profile a2dp_sink D: [pulseaudio] bluez5-util.c: Transport /org/bluez/hci0/dev_00_18_09_2C_1F_41/fd6 state changed from idle to disconnected D: [pulseaudio] bluez5-util.c: Unknown interface org.freedesktop.DBus.Introspectable found, skipping D: [pulseaudio] bluez5-util.c: Unknown interface org.bluez.MediaTransport1 found, skipping D: [pulseau
[Touch-packages] [Bug 1711605] Re: a2dp profile still alive even though disconnected
Okay. I can summarize what the problem is. During connect/disconnect with BT headset repeatedly, the bluetooth connection(check using hcitool) is still alive even thoush the connection has been disconnected by bluetoothctl. The hsp profile is still connected on pulseaudio. -- 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/1711605 Title: a2dp profile still alive even though disconnected Status in pulseaudio package in Ubuntu: Incomplete Bug description: Since the pulseaudio of Xenial has been updated from 8.0-0ubuntu3.2 to 8.0-0ubuntu3.3 at last May, I failed my TestCase The test case is just repeating connect/disconnect with BT headset through bluetoothctl. The change[1] can be retrieved from Xenial's pulseaudio source but I can't ensure which patch causes the problem. You can see the error log[2] when the error has been occurred. [1] pulseaudio (1:8.0-0ubuntu3.3) xenial; urgency=medium [Luke Yelavich, Konrad Zapałowicz] * Fixed multiple interrelated problems with using Bluetooth audio (A2DP), where users would experience some combination of: - Bluetooth headset/speakers listed but not selectable in Sound settings (LP: #1283003) - [regression] Bluetooth audio no longer supports A2DP (stuck in HSP/HFP mode) (LP: #1438510) - [xenial] Bluetooth device doesn't play any sound in A2DP mode unless set to HSP/HFP first (LP: #1582213) * Specific patches from upstream used to address the above problems: - 0103-bluetooth-Add-support-for-automatic-switch-between-h.patch - 0104-bluetooth-Add-support-for-automatic-switch-bluez5.patch - 0106-bluetooth-Add-optional-heuristic-for-switching-betwe.patch . Backport from upstream to fix a bug in Xenial where an incorrect audio profile is applied for a headset connected over Bluetooth making using it impossible. - 0105-bluetooth-policy-do-A2DP-profile-restoring-a-bit-lat.patch . Fix a crash that happens if the BT headset is the only non-monitor source in the system and the last "phone" stream dies. - 0700-pulsecore-add-new-card-profile-hook.patch . Backport from upstream (commit 7b6260140149) to allow for correct profile selection. - 0701-bluetooth-bluez5-wait-for-all-profiles-to-connect.patch . Backport from upstream waiting for all profiles to connect before creating a card. -- Daniel van Vugt Tue, 23 May 2017 16:24:14 +0800 [2] Error log D: [pulseaudio] backend-native.c: dbus: path=/Profile/HSPAGProfile, interface=org.bluez.Profile1, member=NewConnection D: [pulseaudio] backend-native.c: dbus: NewConnection path=/org/bluez/hci0/dev_00_18_09_2C_1F_41, fd=18 D: [pulseaudio] bluez5-util.c: Transport /org/bluez/hci0/dev_00_18_09_2C_1F_41/fd18 state changed from disconnected to idle D: [pulseaudio] backend-native.c: Transport /org/bluez/hci0/dev_00_18_09_2C_1F_41/fd18 available for profile headset_head_unit D: [pulseaudio] backend-native.c: RFCOMM << AT+VGS=07 D: [pulseaudio] backend-native.c: RFCOMM >> OK D: [pulseaudio] bluez5-util.c: dbus: path=/MediaEndpoint/A2DPSource, interface=org.bluez.MediaEndpoint1, member=SelectConfiguration D: [pulseaudio] bluez5-util.c: Unknown interface org.freedesktop.DBus.Introspectable found, skipping D: [pulseaudio] bluez5-util.c: Unknown interface org.bluez.MediaTransport1 found, skipping D: [pulseaudio] bluez5-util.c: Unknown interface org.freedesktop.DBus.Properties found, skipping D: [pulseaudio] bluez5-util.c: dbus: path=/MediaEndpoint/A2DPSource, interface=org.bluez.MediaEndpoint1, member=SetConfiguration D: [pulseaudio] bluez5-util.c: Transport /org/bluez/hci0/dev_00_18_09_2C_1F_41/fd6 state changed from disconnected to idle D: [pulseaudio] bluez5-util.c: Transport /org/bluez/hci0/dev_00_18_09_2C_1F_41/fd6 available for profile a2dp_sink D: [pulseaudio] bluez5-util.c: Properties changed in device /org/bluez/hci0/dev_00_18_09_2C_1F_41 D: [pulseaudio] backend-native.c: dbus: path=/Profile/HSPAGProfile, interface=org.bluez.Profile1, member=RequestDisconnection D: [pulseaudio] bluez5-util.c: dbus: path=/MediaEndpoint/A2DPSource, interface=org.bluez.
[Touch-packages] [Bug 1711605] Re: a2dp profile still alive even though disconnected
Hi, The "0701-bluetooth-bluez5-wait-for-all-profiles-to-connect.patch" which you picked from the upstream has a bug and it has been already fixed at mainline by the same author. Please pick below patch to address this problem. https://cgit.freedesktop.org/pulseaudio/pulseaudio/commit/?id=cb78d6f57c00f3694dae9110f7a7d6f80e3344ac https://bugs.freedesktop.org/show_bug.cgi?id=100237 ** Bug watch added: freedesktop.org Bugzilla #100237 https://bugs.freedesktop.org/show_bug.cgi?id=100237 -- 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/1711605 Title: a2dp profile still alive even though disconnected Status in pulseaudio package in Ubuntu: New Bug description: During connect/disconnect with BT headset repeatedly, the bluetooth connection(check using hcitool) is still alive even thoush the connection has been disconnected by bluetoothctl. The hsp profile is still connected on pulseaudio. --- Since the pulseaudio of Xenial has been updated from 8.0-0ubuntu3.2 to 8.0-0ubuntu3.3 at last May, I failed my TestCase The test case is just repeating connect/disconnect with BT headset through bluetoothctl. The change[1] can be retrieved from Xenial's pulseaudio source but I can't ensure which patch causes the problem. You can see the error log[2] when the error has been occurred. [1] pulseaudio (1:8.0-0ubuntu3.3) xenial; urgency=medium [Luke Yelavich, Konrad Zapałowicz] * Fixed multiple interrelated problems with using Bluetooth audio (A2DP), where users would experience some combination of: - Bluetooth headset/speakers listed but not selectable in Sound settings (LP: #1283003) - [regression] Bluetooth audio no longer supports A2DP (stuck in HSP/HFP mode) (LP: #1438510) - [xenial] Bluetooth device doesn't play any sound in A2DP mode unless set to HSP/HFP first (LP: #1582213) * Specific patches from upstream used to address the above problems: - 0103-bluetooth-Add-support-for-automatic-switch-between-h.patch - 0104-bluetooth-Add-support-for-automatic-switch-bluez5.patch - 0106-bluetooth-Add-optional-heuristic-for-switching-betwe.patch . Backport from upstream to fix a bug in Xenial where an incorrect audio profile is applied for a headset connected over Bluetooth making using it impossible. - 0105-bluetooth-policy-do-A2DP-profile-restoring-a-bit-lat.patch . Fix a crash that happens if the BT headset is the only non-monitor source in the system and the last "phone" stream dies. - 0700-pulsecore-add-new-card-profile-hook.patch . Backport from upstream (commit 7b6260140149) to allow for correct profile selection. - 0701-bluetooth-bluez5-wait-for-all-profiles-to-connect.patch . Backport from upstream waiting for all profiles to connect before creating a card. -- Daniel van Vugt Tue, 23 May 2017 16:24:14 +0800 [2] Error log D: [pulseaudio] backend-native.c: dbus: path=/Profile/HSPAGProfile, interface=org.bluez.Profile1, member=NewConnection D: [pulseaudio] backend-native.c: dbus: NewConnection path=/org/bluez/hci0/dev_00_18_09_2C_1F_41, fd=18 D: [pulseaudio] bluez5-util.c: Transport /org/bluez/hci0/dev_00_18_09_2C_1F_41/fd18 state changed from disconnected to idle D: [pulseaudio] backend-native.c: Transport /org/bluez/hci0/dev_00_18_09_2C_1F_41/fd18 available for profile headset_head_unit D: [pulseaudio] backend-native.c: RFCOMM << AT+VGS=07 D: [pulseaudio] backend-native.c: RFCOMM >> OK D: [pulseaudio] bluez5-util.c: dbus: path=/MediaEndpoint/A2DPSource, interface=org.bluez.MediaEndpoint1, member=SelectConfiguration D: [pulseaudio] bluez5-util.c: Unknown interface org.freedesktop.DBus.Introspectable found, skipping D: [pulseaudio] bluez5-util.c: Unknown interface org.bluez.MediaTransport1 found, skipping D: [pulseaudio] bluez5-util.c: Unknown interface org.freedesktop.DBus.Properties found, skipping D: [pulseaudio] bluez5-util.c: dbus: path=/MediaEndpoint/A2DPSource, interface=org.bluez.MediaEndpoint1, member=SetConfiguration D: [pulseaudio] bluez5-util.c: Transport /org/bluez/hci0/dev_00_18_09_2C_1F_41/fd6 state changed from disconnected to idle D: [pulseaudio] bluez5-util.c: Transport /org/bluez/hci0/dev_00_18_09_2C_1F_41/fd6 available for profile a2dp_sink D: [pulseaudio] bluez5-util.c: Properties changed in device /org/bluez/hci0/dev_00_18_09_2C_1F_41 D: [pulseaudio] backend-native.c: dbus: path=/Profile/HSPAGProfile, interface=org.bluez.Profile1, member=RequestDisconnection D: [pulseaudio] bluez5-util.c: dbus: path=/MediaEndpoint/A2DPSource, interface=org.bluez.MediaEndpoint1, member=ClearConfiguration D: [pulseaudio] bluez5-util.c: Clearing transport /org/bluez/hci0/dev_00_18_09_2C_1F_41/fd6 profile a2dp_sink D: [pulseaud
[Touch-packages] [Bug 1711605] Re: a2dp profile still alive even though disconnected
Hi, You picked wrong patch for "bluetooth: Add optional heuristic for switching between hsp and a2dp profiles"[1] Originally, it was written without "bluetooth-policy: do A2DP profile restoring a bit later"[2] and it was overwritten the [2] code. Please see the patch order and patch result. -/* If there are still some source outputs do nothing. */ -if (source_output_count(c) > 0) +/* If there are still some source outputs do nothing (count is with *this* source_output, so +1) */ +if (source_output_count(c, userdata) > 1) [1]: https://cgit.freedesktop.org/pulseaudio/pulseaudio/commit/?id=3397127f0045d3c130b59e59b4ce6b3601b239b9 [2]: https://cgit.freedesktop.org/pulseaudio/pulseaudio/commit/?id=2250dbfd6968bd9ce295fc7bef8595b2c6ef6a44 -- 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/1711605 Title: a2dp profile still alive even though disconnected Status in pulseaudio package in Ubuntu: New Bug description: During connect/disconnect with BT headset repeatedly, the bluetooth connection(check using hcitool) is still alive even thoush the connection has been disconnected by bluetoothctl. The hsp profile is still connected on pulseaudio. --- Since the pulseaudio of Xenial has been updated from 8.0-0ubuntu3.2 to 8.0-0ubuntu3.3 at last May, I failed my TestCase The test case is just repeating connect/disconnect with BT headset through bluetoothctl. The change[1] can be retrieved from Xenial's pulseaudio source but I can't ensure which patch causes the problem. You can see the error log[2] when the error has been occurred. [1] pulseaudio (1:8.0-0ubuntu3.3) xenial; urgency=medium [Luke Yelavich, Konrad Zapałowicz] * Fixed multiple interrelated problems with using Bluetooth audio (A2DP), where users would experience some combination of: - Bluetooth headset/speakers listed but not selectable in Sound settings (LP: #1283003) - [regression] Bluetooth audio no longer supports A2DP (stuck in HSP/HFP mode) (LP: #1438510) - [xenial] Bluetooth device doesn't play any sound in A2DP mode unless set to HSP/HFP first (LP: #1582213) * Specific patches from upstream used to address the above problems: - 0103-bluetooth-Add-support-for-automatic-switch-between-h.patch - 0104-bluetooth-Add-support-for-automatic-switch-bluez5.patch - 0106-bluetooth-Add-optional-heuristic-for-switching-betwe.patch . Backport from upstream to fix a bug in Xenial where an incorrect audio profile is applied for a headset connected over Bluetooth making using it impossible. - 0105-bluetooth-policy-do-A2DP-profile-restoring-a-bit-lat.patch . Fix a crash that happens if the BT headset is the only non-monitor source in the system and the last "phone" stream dies. - 0700-pulsecore-add-new-card-profile-hook.patch . Backport from upstream (commit 7b6260140149) to allow for correct profile selection. - 0701-bluetooth-bluez5-wait-for-all-profiles-to-connect.patch . Backport from upstream waiting for all profiles to connect before creating a card. -- Daniel van Vugt Tue, 23 May 2017 16:24:14 +0800 [2] Error log D: [pulseaudio] backend-native.c: dbus: path=/Profile/HSPAGProfile, interface=org.bluez.Profile1, member=NewConnection D: [pulseaudio] backend-native.c: dbus: NewConnection path=/org/bluez/hci0/dev_00_18_09_2C_1F_41, fd=18 D: [pulseaudio] bluez5-util.c: Transport /org/bluez/hci0/dev_00_18_09_2C_1F_41/fd18 state changed from disconnected to idle D: [pulseaudio] backend-native.c: Transport /org/bluez/hci0/dev_00_18_09_2C_1F_41/fd18 available for profile headset_head_unit D: [pulseaudio] backend-native.c: RFCOMM << AT+VGS=07 D: [pulseaudio] backend-native.c: RFCOMM >> OK D: [pulseaudio] bluez5-util.c: dbus: path=/MediaEndpoint/A2DPSource, interface=org.bluez.MediaEndpoint1, member=SelectConfiguration D: [pulseaudio] bluez5-util.c: Unknown interface org.freedesktop.DBus.Introspectable found, skipping D: [pulseaudio] bluez5-util.c: Unknown interface org.bluez.MediaTransport1 found, skipping D: [pulseaudio] bluez5-util.c: Unknown interface org.freedesktop.DBus.Properties found, skipping D: [pulseaudio] bluez5-util.c: dbus: path=/MediaEndpoint/A2DPSource, interface=org.bluez.MediaEndpoint1, member=SetConfiguration D: [pulseaudio] bluez5-util.c: Transport /org/bluez/hci0/dev_00_18_09_2C_1F_41/fd6 state changed from disconnected to idle D: [pulseaudio] bluez5-util.c: Transport /
