[Kernel-packages] [Bug 1998194] Re: Please add support for Qualcomm IPC Router in 5.4 focal kernel
** Description changed: The modemmanager debian package in focal was recently upgraded to 1.18 - (apparently the jammy version was backported). This version has broken - some Qualcomm modems as it start to require the Qualcomm IPC Router for - them, which drivers are not enabled in Ubuntu kernel 5.4. To fix this we - need these options enabled in the focal kernel: + (the jammy version was backported - see LP: #1965901). This version has + broken some Qualcomm modems as it start to require the Qualcomm IPC + Router for them, which drivers are not enabled in Ubuntu kernel 5.4. To + fix this we need these options enabled in the focal kernel: CONFIG_QRTR=m CONFIG_QRTR_SMD=m CONFIG_QRTR_TUN=m CONFIG_QRTR_MHI=m The options are already enabled in more modern Ubuntu kernel, i.e. 5.17. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1998194 Title: Please add support for Qualcomm IPC Router in 5.4 focal kernel Status in linux package in Ubuntu: Confirmed Bug description: The modemmanager debian package in focal was recently upgraded to 1.18 (the jammy version was backported - see LP: #1965901). This version has broken some Qualcomm modems as it start to require the Qualcomm IPC Router for them, which drivers are not enabled in Ubuntu kernel 5.4. To fix this we need these options enabled in the focal kernel: CONFIG_QRTR=m CONFIG_QRTR_SMD=m CONFIG_QRTR_TUN=m CONFIG_QRTR_MHI=m The options are already enabled in more modern Ubuntu kernel, i.e. 5.17. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998194/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998194] Re: Please add support for Qualcomm IPC Router in 5.4 focal kernel
Changing to confirmed as I cannot run the apport command in the system where this was found. ** Changed in: linux (Ubuntu) Status: Incomplete => New ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1998194 Title: Please add support for Qualcomm IPC Router in 5.4 focal kernel Status in linux package in Ubuntu: Confirmed Bug description: The modemmanager debian package in focal was recently upgraded to 1.18 (apparently the jammy version was backported). This version has broken some Qualcomm modems as it start to require the Qualcomm IPC Router for them, which drivers are not enabled in Ubuntu kernel 5.4. To fix this we need these options enabled in the focal kernel: CONFIG_QRTR=m CONFIG_QRTR_SMD=m CONFIG_QRTR_TUN=m CONFIG_QRTR_MHI=m The options are already enabled in more modern Ubuntu kernel, i.e. 5.17. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998194/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998194] [NEW] Please add support for Qualcomm IPC Router in 5.4 focal kernel
Public bug reported: The modemmanager debian package in focal was recently upgraded to 1.18 (apparently the jammy version was backported). This version has broken some Qualcomm modems as it start to require the Qualcomm IPC Router for them, which drivers are not enabled in Ubuntu kernel 5.4. To fix this we need these options enabled in the focal kernel: CONFIG_QRTR=m CONFIG_QRTR_SMD=m CONFIG_QRTR_TUN=m CONFIG_QRTR_MHI=m The options are already enabled in more modern Ubuntu kernel, i.e. 5.17. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1998194 Title: Please add support for Qualcomm IPC Router in 5.4 focal kernel Status in linux package in Ubuntu: New Bug description: The modemmanager debian package in focal was recently upgraded to 1.18 (apparently the jammy version was backported). This version has broken some Qualcomm modems as it start to require the Qualcomm IPC Router for them, which drivers are not enabled in Ubuntu kernel 5.4. To fix this we need these options enabled in the focal kernel: CONFIG_QRTR=m CONFIG_QRTR_SMD=m CONFIG_QRTR_TUN=m CONFIG_QRTR_MHI=m The options are already enabled in more modern Ubuntu kernel, i.e. 5.17. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998194/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1938530] Re: arm64: virtio_blk is not included in the initramfs
** Changed in: linux-meta (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1938530 Title: arm64: virtio_blk is not included in the initramfs Status in linux-meta package in Ubuntu: Won't Fix Bug description: The virtio_blk module is not included by default in the initramfs for arm64, so UC20 cannot boot as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1938530/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1973835] Re: Ubuntu 22.04, Bluetooth issues
** Also affects: bluez (Ubuntu) Importance: Undecided Status: New ** No longer affects: snappy-hwe-snaps -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1973835 Title: Ubuntu 22.04, Bluetooth issues Status in bluez package in Ubuntu: New Bug description: 0 I installed Ubuntu 22.04 and the Bluetooth was working fine. I turned off the bluetooth and could not turn it back on. I did some research and found some calls to turn it back on: sudo rfkill unblock all sudo hciconfig hci0 down sudo rmmod btusb sudo modprobe btusb sudo hciconfig hci0 up Now, I can turn it on and off as I please but It is now not connecting to any device. It would connect for a brief second and then disconnect. Can't find anything from research. Anyone can help with this ? Also, Whenever I boot up windows, the bluetooth works perfectly fine on windows. So it's not an hardware issue. I ran the command: bluetoothctl and the bluetooth is cycling through connecting to the device and disconnecting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1973835/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1975688] [NEW] Accessing squashfs with lzma compression is ~16% slower in 5.15 when compared to 5.4, on an RPi3 B+
Public bug reported:
On the server image on an RPi3 B+, I run this script:
```
#!/bin/bash -eu
mount_and_read()
{
local snap=$1
local mnt_d=$2
mount "$snap" "$mnt_d"
# We should not use /dev/null here, see
#
https://unix.stackexchange.com/questions/512362/why-does-tar-appear-to-skip-file-contents-when-output-file-is-dev-null
tar -cO "$mnt_d"/ > /dev/zeros
}
snap_d=$(mktemp -d)
for i in {1..3}; do
sync && echo 3 > /proc/sys/vm/drop_caches
time mount_and_read "$1" "$snap_d"
umount "$snap_d"
done
rmdir "$snap_d"
```
With these commands:
$ sudo mount -t tmpfs -o size=400M tmpfs tmpfs/
$ cd tmpfs
$ snap download core22
$ sudo ../measure-snap-mnt.sh core22_169.snap
I get these results on 20.04:
real0m21.667s
user0m0.302s
sys 0m20.299s
real0m21.650s
user0m0.351s
sys 0m20.417s
real0m21.718s
user0m0.285s
sys 0m20.528s
On 22.04 server image:
real0m25.084s
user0m0.407s
sys 0m23.778s
real0m25.064s
user0m0.397s
sys 0m23.768s
real0m25.051s
user0m0.369s
sys 0m23.803s
Which is a considerable difference. This affects snaps compressed with
xz, and although these measurements are for server the bigger impact is
on UC images, where the boot time increases considerably because of
this.
** Affects: linux-raspi (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- Accessing squashfs with lzma compression is ~16% slower in 5.15 when compared
to 5.4
+ Accessing squashfs with lzma compression is ~16% slower in 5.15 when compared
to 5.4, on an RPi3 B+
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi in Ubuntu.
https://bugs.launchpad.net/bugs/1975688
Title:
Accessing squashfs with lzma compression is ~16% slower in 5.15 when
compared to 5.4, on an RPi3 B+
Status in linux-raspi package in Ubuntu:
New
Bug description:
On the server image on an RPi3 B+, I run this script:
```
#!/bin/bash -eu
mount_and_read()
{
local snap=$1
local mnt_d=$2
mount "$snap" "$mnt_d"
# We should not use /dev/null here, see
#
https://unix.stackexchange.com/questions/512362/why-does-tar-appear-to-skip-file-contents-when-output-file-is-dev-null
tar -cO "$mnt_d"/ > /dev/zeros
}
snap_d=$(mktemp -d)
for i in {1..3}; do
sync && echo 3 > /proc/sys/vm/drop_caches
time mount_and_read "$1" "$snap_d"
umount "$snap_d"
done
rmdir "$snap_d"
```
With these commands:
$ sudo mount -t tmpfs -o size=400M tmpfs tmpfs/
$ cd tmpfs
$ snap download core22
$ sudo ../measure-snap-mnt.sh core22_169.snap
I get these results on 20.04:
real 0m21.667s
user 0m0.302s
sys 0m20.299s
real 0m21.650s
user 0m0.351s
sys 0m20.417s
real 0m21.718s
user 0m0.285s
sys 0m20.528s
On 22.04 server image:
real 0m25.084s
user 0m0.407s
sys 0m23.778s
real 0m25.064s
user 0m0.397s
sys 0m23.768s
real 0m25.051s
user 0m0.369s
sys 0m23.803s
Which is a considerable difference. This affects snaps compressed with
xz, and although these measurements are for server the bigger impact
is on UC images, where the boot time increases considerably because of
this.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1975688/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1968111] Re: uc22 rpi3 ethernet getting renamed on every boot
** Also affects: linux-raspi (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1968111 Title: uc22 rpi3 ethernet getting renamed on every boot Status in snapd: New Status in linux-raspi package in Ubuntu: New Bug description: On rpi3 with uc22 (just confirmed on the latest image from 20220406.1), the built-in ethernet interface should use generic names (i.e. eth0). On rpi4 this works as it should, and it uses eth0. On the rpi3b+ I'm testing on, I saw it get enxea1a4588e236 on the first boot. On the second boot though, it got renamed to enx3a583dc734b6 The result of this, is that on rpi3 with uc22, if you only configure ethernet, then it will no longer work after you reboot. Since console-conf only runs on first boot, it will be stuck thinking it was unable to get an address. The netplan config file that is generated by console-conf references the device name, so it will still be looking for that original name: network: ethernets: enxea1a4588e236: dhcp4: true version: 2 ... Fortunately, the wifi interface gets named wlan0 and does not get renamed every boot. So I was able to configure that interface and still get in to gather some information about this. However, unless you use wifi, rpi3 devices will be useless after the first boot To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1968111/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960300] [NEW] llvm-objcopy cannot generate EFI images valid for Ubuntu Core
Public bug reported: llvm-objcopy cannot generate EFI images valid for Ubuntu Core, due to some bugs already fixed in upstream: https://llvm.org/PR51243 https://llvm.org/PR51244 Patches fixing the issues: https://github.com/llvm/llvm-project/commit/cdd407286a9652ec62b33f437a298754fe3ba7ab https://github.com/llvm/llvm-project/commit/b25ab4f313f38d3dee9674789cf56b9143515034 https://github.com/llvm/llvm-project/commit/b33fd3177229c67fe44b65fff8666a7746595daa ** Affects: llvm-toolchain-13 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to llvm-toolchain-13 in Ubuntu. https://bugs.launchpad.net/bugs/1960300 Title: llvm-objcopy cannot generate EFI images valid for Ubuntu Core Status in llvm-toolchain-13 package in Ubuntu: New Bug description: llvm-objcopy cannot generate EFI images valid for Ubuntu Core, due to some bugs already fixed in upstream: https://llvm.org/PR51243 https://llvm.org/PR51244 Patches fixing the issues: https://github.com/llvm/llvm-project/commit/cdd407286a9652ec62b33f437a298754fe3ba7ab https://github.com/llvm/llvm-project/commit/b25ab4f313f38d3dee9674789cf56b9143515034 https://github.com/llvm/llvm-project/commit/b33fd3177229c67fe44b65fff8666a7746595daa To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-13/+bug/1960300/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1948807] [NEW] Boot time from snap in 20/stable increses boot time on 3.5 seconds
Public bug reported: I am seeing what looks as a regression in pi-kernel snap for UC20: there are around 3.5 additional seconds spent in boot time. In the image from cdimage (2021-06-30), I see: [1.856540] random: crng init done [1.871798] loop: module loaded (see https://paste.ubuntu.com/p/CkfWXY5Vgf/) while if I build an image from latest snaps in the 20/stable channel, I get: [1.855481] random: crng init done [5.349491] loop: module loaded (see https://paste.ubuntu.com/p/CNt42gdDcZ/) The pi-kernel snap revision is 353. ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1948807 Title: Boot time from snap in 20/stable increses boot time on 3.5 seconds Status in linux-raspi package in Ubuntu: New Bug description: I am seeing what looks as a regression in pi-kernel snap for UC20: there are around 3.5 additional seconds spent in boot time. In the image from cdimage (2021-06-30), I see: [1.856540] random: crng init done [1.871798] loop: module loaded (see https://paste.ubuntu.com/p/CkfWXY5Vgf/) while if I build an image from latest snaps in the 20/stable channel, I get: [1.855481] random: crng init done [5.349491] loop: module loaded (see https://paste.ubuntu.com/p/CNt42gdDcZ/) The pi-kernel snap revision is 353. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1948807/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1938530] Re: arm64: virtio_blk is not included in the initramfs
I'm trying to boot UC20 on qemu. Note that the module is present in the x86 initramfs, and we can use UC20 on qemu/x86. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1938530 Title: arm64: virtio_blk is not included in the initramfs Status in linux-meta package in Ubuntu: New Bug description: The virtio_blk module is not included by default in the initramfs for arm64, so UC20 cannot boot as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1938530/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1938530] [NEW] arm64: virtio_blk is not included in the initramfs
Public bug reported: The virtio_blk module is not included by default in the initramfs for arm64, so UC20 cannot boot as expected. ** Affects: linux-meta (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1938530 Title: arm64: virtio_blk is not included in the initramfs Status in linux-meta package in Ubuntu: New Bug description: The virtio_blk module is not included by default in the initramfs for arm64, so UC20 cannot boot as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1938530/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1932035] Re: Enable features for supporting PXE installer
I have successfully finished an installation with this kernel, changing to verified. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1932035 Title: Enable features for supporting PXE installer Status in linux-bluefield package in Ubuntu: In Progress Status in linux-bluefield source package in Focal: Fix Committed Bug description: == Impact == The PXE installer requires some features available in order to run. == Fix == * CONFIG_ISO9660_FS=m * CONFIG_BCACHE=m * enable zfs == Risk of Regression == Low. These features are also enabled in the generic kernel for arm64, and has been tested on the target platform. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1932035/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1587366] Re: On cooler devices, BT sometimes cannot be enabled
I have been trying to reproduce this by switching on/off bluetooth from the indicator and from system setting several times, but no luck yet. While doing this I tried to connect a BT headset after each few tries, successfully. I also left the tablet aside for a few minutes without BT, then was able to turn it on successfully too. Were there any files in /var/crash/ when this happened? Could somebody attach syslog after reproducing this? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1587366 Title: On cooler devices, BT sometimes cannot be enabled Status in The Avila project: New Status in Canonical System Image: New Status in cooler: New Status in bluez package in Ubuntu: New Bug description: Using ths DUT at least 20 minutes, then trying to turn on the BT. DUT cannot turning on by itself, user need to reboot the DUT to be able to connect any BT device. Fw: Ubuntu 15.04 (r10) Tested on a cooler (M10 HD) Expected behavior: Bluetooth slider is moved to on Bluetooth activates Available devices appear in the list Experienced behavior: Bluetooth slider is moved to on Activity spinners appear Bluetooth slider moves to off. To manage notifications about this bug go to: https://bugs.launchpad.net/avila/+bug/1587366/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1493386] Re: IN CAR: SIM2 calls cann not be routed via car audio
Please recheck after OTA-11 is released. Not sure if all use cases you mention will be solved, but as a minimum you will be able to start calls from SIM2 from the car if SIM2 is the preferred slot. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1493386 Title: IN CAR: SIM2 calls cann not be routed via car audio Status in bluez package in Ubuntu: Invalid Status in ofono package in Ubuntu: In Progress Bug description: STEPS: Requirements: Aquaris E4.5 with 2 SIMs, 2nd phone, a car with blue tooth phone support (Seat Alhambra 2012 in my case) 1. Connect the Aquaris to the car (with two SIM cards, car kid shows the provider of the 2nd SIM card in the display) 2. From the second device call the number of SIM1 3. Phone & car sound rings and call can be taken 4. From the second device call the number of SIM2 5. Phone does ring but car kit not. 6. Call 2nd phone from Aquaris connected to the car with SIM1 (via the phone directly or using the car kit) 7. Normal behaviour with in car phone & audio system 8. Call 2nd phone from Aquaris connected to car with SIM2 (only possible dialling from the phone) 9. No sound on the phone, no microphone support EXPECTED: I expect that calls from SIM2 can be taken and performed as from SIM1 ACTUAL: SIM2 seems not to work when phone is connected to blue tooth of car whereby SIM1 works flawlessly VERSIONS: OS-Build-Number: 25 Ubuntu-Image: 20150825.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1493386/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1418040] Re: Calling from car using bluetooth, call is placed on ril_0, even though ril_1 is default
** Changed in: ofono (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1418040 Title: Calling from car using bluetooth, call is placed on ril_0, even though ril_1 is default Status in Canonical System Image: In Progress Status in bluez package in Ubuntu: Invalid Status in ofono package in Ubuntu: Fix Released Status in telephony-service package in Ubuntu: Triaged Status in ubuntu-system-settings package in Ubuntu: In Progress Bug description: What happened Placed call from car over bluetooth Call was placed on my first SIM card, even though I selected my second SIM as default for calls What should have happened The call should have been placed on my second SIM ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: telephony-service 0.1+15.04.20150124-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.15.1-0ubuntu4 Architecture: armhf Date: Wed Feb 4 14:25:44 2015 InstallationDate: Installed on 2015-02-02 (2 days ago) InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf (20150202-020204) SourcePackage: telephony-service UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1418040/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1551131] Re: Cannot pair Jabra Classic headset
Some more information: In some cases I am able to pair the device, but it does not connect using HFP, and does not connect to ofono. It is just an A2DP sink and I can use it to hear music but not for calls. See http://paste.ubuntu.com/15241647/ http://paste.ubuntu.com/15241661/ This device has also and odd behaviour on desktop/wily. When I connect it, initially it is shown only as an audio sink. If I disconnect the device, then connect again from the indicator, it uses HFP and I see both MIC and audio sink for the device. But this reconnect trick does not work for Touch unfortunately. It seems that some race condition is happening and it does not select HFP as the first option. -- You received this bug notification because you are a member of Kernel 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: New 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/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1551131] [NEW] Cannot pair Jabra Classic headset
Public bug reported: 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) ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Attachment added: "syslog" https://bugs.launchpad.net/bugs/1551131/+attachment/4584137/+files/syslog -- You received this bug notification because you are a member of Kernel 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: New 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/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1418040] Re: Calling from car using bluetooth, call is placed on ril_0, even though ril_1 is default
** Also affects: ubuntu-system-settings (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1418040 Title: Calling from car using bluetooth, call is placed on ril_0, even though ril_1 is default Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Triaged Status in ofono package in Ubuntu: Triaged Status in telephony-service package in Ubuntu: Triaged Status in ubuntu-system-settings package in Ubuntu: New Status in telephony-service package in Ubuntu RTM: Triaged Bug description: What happened Placed call from car over bluetooth Call was placed on my first SIM card, even though I selected my second SIM as default for calls What should have happened The call should have been placed on my second SIM ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: telephony-service 0.1+15.04.20150124-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.15.1-0ubuntu4 Architecture: armhf Date: Wed Feb 4 14:25:44 2015 InstallationDate: Installed on 2015-02-02 (2 days ago) InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf (20150202-020204) SourcePackage: telephony-service UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1418040/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1418040] Re: Calling from car using bluetooth, call is placed on ril_0, even though ril_1 is default
As a matter of fact I will also add that the slot chosen to start a call is kind of random and can change after a reboot. It would be possible to fix it in the code as a quick work around to have as a minimum a deterministic behaviour. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1418040 Title: Calling from car using bluetooth, call is placed on ril_0, even though ril_1 is default Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Confirmed Status in ofono package in Ubuntu: Confirmed Status in telephony-service package in Ubuntu: Confirmed Status in telephony-service package in Ubuntu RTM: Confirmed Bug description: What happened Placed call from car over bluetooth Call was placed on my first SIM card, even though I selected my second SIM as default for calls What should have happened The call should have been placed on my second SIM ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: telephony-service 0.1+15.04.20150124-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.15.1-0ubuntu4 Architecture: armhf Date: Wed Feb 4 14:25:44 2015 InstallationDate: Installed on 2015-02-02 (2 days ago) InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf (20150202-020204) SourcePackage: telephony-service UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1418040/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1418040] Re: Calling from car using bluetooth, call is placed on ril_0, even though ril_1 is default
Some research shows that audio/telephony-ofono.c in BlueZ 4 source tree only accounts for one modem in the system. Currently there is no way to specify a preferred modem. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1418040 Title: Calling from car using bluetooth, call is placed on ril_0, even though ril_1 is default Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Confirmed Status in ofono package in Ubuntu: Confirmed Status in telephony-service package in Ubuntu: Confirmed Status in telephony-service package in Ubuntu RTM: Confirmed Bug description: What happened Placed call from car over bluetooth Call was placed on my first SIM card, even though I selected my second SIM as default for calls What should have happened The call should have been placed on my second SIM ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: telephony-service 0.1+15.04.20150124-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.15.1-0ubuntu4 Architecture: armhf Date: Wed Feb 4 14:25:44 2015 InstallationDate: Installed on 2015-02-02 (2 days ago) InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf (20150202-020204) SourcePackage: telephony-service UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1418040/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1418040] Re: Calling from car using bluetooth, call is placed on ril_0, even though ril_1 is default
Actually, the call is started by a Dial DBus call to an ofono modem started from bluetoothd. Currently we are not using ofono's HFP implementation, but the BlueZ one. This will change when we move from BlueZ 4 to BlueZ 5. But for the moment the one which chooses the modem to use is BlueZ. ** Also affects: bluez (Ubuntu) Importance: Undecided Status: New ** Changed in: bluez (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1418040 Title: Calling from car using bluetooth, call is placed on ril_0, even though ril_1 is default Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Confirmed Status in ofono package in Ubuntu: Confirmed Status in telephony-service package in Ubuntu: Confirmed Status in telephony-service package in Ubuntu RTM: Confirmed Bug description: What happened Placed call from car over bluetooth Call was placed on my first SIM card, even though I selected my second SIM as default for calls What should have happened The call should have been placed on my second SIM ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: telephony-service 0.1+15.04.20150124-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.15.1-0ubuntu4 Architecture: armhf Date: Wed Feb 4 14:25:44 2015 InstallationDate: Installed on 2015-02-02 (2 days ago) InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf (20150202-020204) SourcePackage: telephony-service UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1418040/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
