[Bug 1759961] Re: Update to bluez 5.50

2018-10-10 Thread Chanho Park
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1759961

Title:
  Update to bluez 5.50

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1766513] Re: RM: pkg-create-dbgsym: obsolete, debhelper conflicts

2018-04-30 Thread Chanho Park
Hi,
Since this change, I cannot make a bionic chroot image on top of the ubuntu 
16.04 version.

This is my Host PC.
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 16.04.3 LTS
Release:16.04
Codename:   xenial

When I tried to generate a bionic chroot image using mk-sbuild tool, I
failed to make it due to lack of the pkg-create-dbgsym.

$ mk-sbuild --arch armhf bionic
< --- Snip --->

Package pkg-create-dbgsym is not available, but is referred to by another 
package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
However the following packages replace it:
  debhelper

W: --force-yes is deprecated, use one of the options starting with --allow 
instead.
E: Package 'pkg-create-dbgsym' has no installation candidate

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1766513

Title:
  RM: pkg-create-dbgsym: obsolete, debhelper conflicts

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pkg-create-dbgsym/+bug/1766513/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1751011] Re: bash crashes in qemu-user environments (bionic)

2018-03-14 Thread Chanho Park
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1751011

Title:
  bash crashes in qemu-user environments (bionic)

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1732997] Re: bionic bash 4.4-5 failed to unpack

2018-01-30 Thread Chanho Park
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1732997

Title:
  bionic bash 4.4-5 failed to unpack

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1711605] Re: [xenial] A2DP profile still alive even though disconnected

2018-01-07 Thread Chanho Park
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1711605

Title:
  [xenial] A2DP profile still alive even though disconnected

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1711605] Re: a2dp profile still alive even though disconnected

2017-08-21 Thread Chanho Park
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1711605

Title:
  a2dp profile still alive even though disconnected

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1711605] Re: a2dp profile still alive even though disconnected

2017-08-21 Thread Chanho Park
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1711605

Title:
  a2dp profile still alive even though disconnected

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1711605] Re: a2dp profile still alive even though disconnected

2017-08-20 Thread Chanho Park
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1711605

Title:
  a2dp profile still alive even though disconnected

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1711605] [NEW] a2dp profile still alive even though disconnected

2017-08-18 Thread Chanho Park
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

[Bug 1709881] Re: [xenial] QT5 gles support for arm64 architecture

2017-08-18 Thread Chanho Park
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1709881

Title:
  [xenial] QT5 gles support for arm64 architecture

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1709881/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1709881] Re: [xenial] QT5 gles support for arm64 architecture

2017-08-18 Thread Chanho Park
Gently ping about this issue :)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1709881

Title:
  [xenial] QT5 gles support for arm64 architecture

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1709881/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1709881] [NEW] [xenial] QT5 gles support for arm64 architecture

2017-08-10 Thread Chanho Park
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1709881

Title:
  [xenial] QT5 gles support for arm64 architecture

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1709881/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1621824] Re: MFG:Garrison - Ubuntu 16.04.1 dmesg error "systemd[1]: Failed to start Set console keymap."

2017-02-01 Thread Chanho Park
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1621824

Title:
  MFG:Garrison - Ubuntu 16.04.1 dmesg error "systemd[1]: Failed to start
  Set console keymap."

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs