[Touch-packages] [Bug 1910405] Re: bluetoothd hangs and cannot be killed

2021-02-03 Thread You-Sheng Yang
jan 11 11:59:05 omer kernel: Bluetooth: hci0: Received unexpected HCI Event jan 11 11:59:05 omer kernel: Bluetooth: hci0: Received unexpected HCI Event jan 11 11:59:05 omer kernel: Bluetooth: hci0: Received unexpected HCI Event jan 11 11:59:05 omer kernel: Bluetooth:

[Touch-packages] [Bug 1910405] Re: bluetoothd hangs and cannot be killed

2021-02-03 Thread Peter Dedecker
The problem is back. This time I let the restart process wait for several minutes. See this output. peddecke@omer:~$ sudo service bluetooth restart Job for bluetooth.service failed because the control process exited with error code. See "systemctl status bluetooth.service" and "journalctl -xe"

[Touch-packages] [Bug 1910405] Re: bluetoothd hangs and cannot be killed

2021-01-11 Thread Peter Dedecker
For some reason, killing the bluetoothd process just worked today unlike previous attempts in the past days. The problem of the headset loosing connection during a meeting, blocking the bluetooth process and settings interface, still occurs requiring a restart of the bluetooth service and the

[Touch-packages] [Bug 1910405] Re: bluetoothd hangs and cannot be killed

2021-01-11 Thread Peter Dedecker
apport information ** Tags added: apport-collected ** Description changed: Hi, When having a bluetooth headphone (JBL Live) connected using the A2DP pulseaudio sink, the output sound suddenly stops during a music streaming of videocall session. Sometimes just disconnecting and

[Touch-packages] [Bug 1910405] Re: bluetoothd hangs and cannot be killed

2021-01-08 Thread Peter Dedecker
I'm sorry, the apport-collect comment also results in a hanging process. See this bug: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1910768 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu.

[Touch-packages] [Bug 1910405] Re: bluetoothd hangs and cannot be killed

2021-01-06 Thread Daniel van Vugt
A process that cannot be killed usually means it's blocked in a kernel call. So this sounds like a bug in the kernel Bluetooth code... Please: 1. Run this command to gather more system info: apport-collect 1910405 2. Try a newer Ubuntu release or just a newer kernel from