[Touch-packages] [Bug 1978746] [NEW] Had to restart Modem Manager to establish Mobile broadband connection from hotswap
Public bug reported: [Description] After hot-swapping sim 1 and sim 2, modem manager restart is needed to be able to establish cellular connection. [Expected result] After hot-swapping sim 1 and sim 2, cellular connection could be established after selecting the appropriate APN profile. [Actual result] After hot-swapping sim 1 and sim 2, cellular connection cannot be established after selecting the appropriate APN profile [Steps to reproduce] 1. Assuming that cellular connection was already established using sim 1, remove sim 1 from the sim card slot while the system is still booted on. 2. Insert sim 2 in the sim card slot. 3. Check that the sim card is already recognize by running "mmcli -m " to check if the sim card information is reflected. 4. From the mobile broadband GUI, select the appropriate APN profile for sim 2. Notice that cellular connection cannot be established ==> PROBLEM [Workaround] 1. Run "sudo systemctl restart ModemManager" to restart Modem Manager 2. Select the appropriate APN profile to establish cellular connection Ubuntu release version: Ubuntu 20.04.4 LTS Kernel version: 5.15.0-33-generic (hwe-kernel) ** Affects: modemmanager (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1978746 Title: Had to restart Modem Manager to establish Mobile broadband connection from hotswap Status in modemmanager package in Ubuntu: New Bug description: [Description] After hot-swapping sim 1 and sim 2, modem manager restart is needed to be able to establish cellular connection. [Expected result] After hot-swapping sim 1 and sim 2, cellular connection could be established after selecting the appropriate APN profile. [Actual result] After hot-swapping sim 1 and sim 2, cellular connection cannot be established after selecting the appropriate APN profile [Steps to reproduce] 1. Assuming that cellular connection was already established using sim 1, remove sim 1 from the sim card slot while the system is still booted on. 2. Insert sim 2 in the sim card slot. 3. Check that the sim card is already recognize by running "mmcli -m " to check if the sim card information is reflected. 4. From the mobile broadband GUI, select the appropriate APN profile for sim 2. Notice that cellular connection cannot be established ==> PROBLEM [Workaround] 1. Run "sudo systemctl restart ModemManager" to restart Modem Manager 2. Select the appropriate APN profile to establish cellular connection Ubuntu release version: Ubuntu 20.04.4 LTS Kernel version: 5.15.0-33-generic (hwe-kernel) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1978746/+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 1888164] Re: Cannot re-pair Bluetooth Keyboard when wrong pairing code is entered
I'm attaching the captured btsnoop logs ** Description changed: Expected behavior: 1.Pressing the “Cancel” button during device pairing should close the pairing code prompt 2.Re-pairing BT keyboard after cancelling initial pairing should re-open the pairing code prompt Problem: 1.Pressing the “Cancel” button during device pairing does not close the pairing code prompt 2.Re-pairing BT keyboard after cancelling initial pairing does not show the pairing code prompt. Steps: 1.Turn on the system’s Bluetooth (usually turned on by default on boot) 2.Try to pair the system with the BT Keyboard via the Bluetooth Settings UI 3.When the pairing code prompt appears, input the wrong code and press enter. This should generate a new code 4.Press “Cancel” on the pairing code prompt. Notice that the cancel button is not working. 5.Press the Esc button on the system’s keyboard. This should close the pairing code prompt. 6.Try re-pairing the system with the BT Keyboard via the Bluetooth Settings UI. 7.Notice that the connection is loading but the pairing code prompt does not reappear. The system and the BT keyboard cannot be re-paired. Workaround: 1.When a new code is generated in Step 3, input the correct code. This would successfully pair the system and the BT keyboard. 2.Try rebooting the system after Step 7 to recover the connection. Notes: - Keyboards tested: - > ThinkPad Compact Bluetooth Keyboard - > Microsoft Designer Keyboard + > ThinkPad Compact Bluetooth Keyboard + > Microsoft Designer Keyboard - Issue does not happen in Windows OS + - I have reported this issue to Intel and they didn't see any error from the connection logs. We are suspecting that this has to do with the Bluetooth UI instead. ** Package changed: bluez (Ubuntu) => gnome-bluetooth (Ubuntu) ** Attachment added: "btsnoop logs" https://bugs.launchpad.net/ubuntu/+source/gnome-bluetooth/+bug/1888164/+attachment/5394187/+files/new_ubuntu_btsnoop.log -- 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/1888164 Title: Cannot re-pair Bluetooth Keyboard when wrong pairing code is entered Status in gnome-bluetooth package in Ubuntu: New Bug description: Expected behavior: 1.Pressing the “Cancel” button during device pairing should close the pairing code prompt 2.Re-pairing BT keyboard after cancelling initial pairing should re-open the pairing code prompt Problem: 1.Pressing the “Cancel” button during device pairing does not close the pairing code prompt 2.Re-pairing BT keyboard after cancelling initial pairing does not show the pairing code prompt. Steps: 1.Turn on the system’s Bluetooth (usually turned on by default on boot) 2.Try to pair the system with the BT Keyboard via the Bluetooth Settings UI 3.When the pairing code prompt appears, input the wrong code and press enter. This should generate a new code 4.Press “Cancel” on the pairing code prompt. Notice that the cancel button is not working. 5.Press the Esc button on the system’s keyboard. This should close the pairing code prompt. 6.Try re-pairing the system with the BT Keyboard via the Bluetooth Settings UI. 7.Notice that the connection is loading but the pairing code prompt does not reappear. The system and the BT keyboard cannot be re-paired. Workaround: 1.When a new code is generated in Step 3, input the correct code. This would successfully pair the system and the BT keyboard. 2.Try rebooting the system after Step 7 to recover the connection. Notes: - Keyboards tested: > ThinkPad Compact Bluetooth Keyboard > Microsoft Designer Keyboard - Issue does not happen in Windows OS - I have reported this issue to Intel and they didn't see any error from the connection logs. We are suspecting that this has to do with the Bluetooth UI instead. - Bluez version: 5.53 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-bluetooth/+bug/1888164/+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 1888164] [NEW] Cannot re-pair Bluetooth Keyboard when wrong pairing code is entered
Public bug reported: Expected behavior: 1. Pressing the “Cancel” button during device pairing should close the pairing code prompt 2. Re-pairing BT keyboard after cancelling initial pairing should re-open the pairing code prompt Problem: 1. Pressing the “Cancel” button during device pairing does not close the pairing code prompt 2. Re-pairing BT keyboard after cancelling initial pairing does not show the pairing code prompt. Steps: 1. Turn on the system’s Bluetooth (usually turned on by default on boot) 2. Try to pair the system with the BT Keyboard via the Bluetooth Settings UI 3. When the pairing code prompt appears, input the wrong code and press enter. This should generate a new code 4. Press “Cancel” on the pairing code prompt. Notice that the cancel button is not working. 5. Press the Esc button on the system’s keyboard. This should close the pairing code prompt. 6. Try re-pairing the system with the BT Keyboard via the Bluetooth Settings UI. 7. Notice that the connection is loading but the pairing code prompt does not reappear. The system and the BT keyboard cannot be re-paired. Workaround: 1. When a new code is generated in Step 3, input the correct code. This would successfully pair the system and the BT keyboard. 2. Try rebooting the system after Step 7 to recover the connection. Notes: - Keyboards tested: > ThinkPad Compact Bluetooth Keyboard > Microsoft Designer Keyboard - Issue does not happen in Windows OS ** Affects: bluez (Ubuntu) Importance: Undecided Status: New -- 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/1888164 Title: Cannot re-pair Bluetooth Keyboard when wrong pairing code is entered Status in bluez package in Ubuntu: New Bug description: Expected behavior: 1.Pressing the “Cancel” button during device pairing should close the pairing code prompt 2.Re-pairing BT keyboard after cancelling initial pairing should re-open the pairing code prompt Problem: 1.Pressing the “Cancel” button during device pairing does not close the pairing code prompt 2.Re-pairing BT keyboard after cancelling initial pairing does not show the pairing code prompt. Steps: 1.Turn on the system’s Bluetooth (usually turned on by default on boot) 2.Try to pair the system with the BT Keyboard via the Bluetooth Settings UI 3.When the pairing code prompt appears, input the wrong code and press enter. This should generate a new code 4.Press “Cancel” on the pairing code prompt. Notice that the cancel button is not working. 5.Press the Esc button on the system’s keyboard. This should close the pairing code prompt. 6.Try re-pairing the system with the BT Keyboard via the Bluetooth Settings UI. 7.Notice that the connection is loading but the pairing code prompt does not reappear. The system and the BT keyboard cannot be re-paired. Workaround: 1.When a new code is generated in Step 3, input the correct code. This would successfully pair the system and the BT keyboard. 2.Try rebooting the system after Step 7 to recover the connection. Notes: - Keyboards tested: > ThinkPad Compact Bluetooth Keyboard > Microsoft Designer Keyboard - Issue does not happen in Windows OS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1888164/+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 1879438] Re: bluetooth file transfer via bluetooth UI is too slow
Hi @Sebastien, sorry for the late reply. I have reported the bug on bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=208227 ** Bug watch added: Linux Kernel Bug Tracker #208227 https://bugzilla.kernel.org/show_bug.cgi?id=208227 -- 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/1879438 Title: bluetooth file transfer via bluetooth UI is too slow Status in bluez package in Ubuntu: New Bug description: OS: Ubuntu 20.04 Kernel: 5.4.0-31-generic When using the UI to connect and transfer the file form one machine to another machine, BASIC mode is getting selected in the L2CAP configuration and continuous scan is not going on in both sides. the L2CAP MTU size is also in 672, which is very small. Even with the patch applied by Intel, it does not increase the TPT because the UI always selects BASIC mode. Sample File transfer duration: sending - (8MB) 5min 18s sending - (12MB) 7min36s receiving - (8MB) 4min 8s receiving - (12MB) 5min 48s **This issue was also observed in Ubuntu 18.04 OS ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 19 14:46:11 2020 InstallationDate: Installed on 2020-05-19 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20U9SITR39 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic root=UUID=6716936f-20b8-4840-8a75-00f4279d9062 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/12/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2WET11C (1.01C ) dmi.board.asset.tag: Not Available dmi.board.name: 20U9SITR39 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2WET11C(1.01C):bd02/12/2020:svnLENOVO:pn20U9SITR39:pvrThinkPadX1CarbonGen8:rvnLENOVO:rn20U9SITR39:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon Gen 8 dmi.product.name: 20U9SITR39 dmi.product.sku: LENOVO_MT_20U9_BU_Think_FM_ThinkPad X1 Carbon Gen 8 dmi.product.version: ThinkPad X1 Carbon Gen 8 dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: D8:3B:BF:7A:E4:22 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:22494299 acl:63654 sco:0 events:77112 errors:0 TX bytes:45158198 acl:65574 sco:0 commands:7661 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1879438/+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 1879438] Re: bluetooth file transfer via bluetooth UI is too slow
** Attachment added: "logs for file transfer (receiving)" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1879438/+attachment/5373902/+files/btsnoop_receive.log -- 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/1879438 Title: bluetooth file transfer via bluetooth UI is too slow Status in bluez package in Ubuntu: New Bug description: OS: Ubuntu 20.04 Kernel: 5.4.0-31-generic When using the UI to connect and transfer the file form one machine to another machine, BASIC mode is getting selected in the L2CAP configuration and continuous scan is not going on in both sides. the L2CAP MTU size is also in 672, which is very small. Even with the patch applied by Intel, it does not increase the TPT because the UI always selects BASIC mode. Sample File transfer duration: sending - (8MB) 5min 18s sending - (12MB) 7min36s receiving - (8MB) 4min 8s receiving - (12MB) 5min 48s **This issue was also observed in Ubuntu 18.04 OS ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 19 14:46:11 2020 InstallationDate: Installed on 2020-05-19 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20U9SITR39 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic root=UUID=6716936f-20b8-4840-8a75-00f4279d9062 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/12/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2WET11C (1.01C ) dmi.board.asset.tag: Not Available dmi.board.name: 20U9SITR39 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2WET11C(1.01C):bd02/12/2020:svnLENOVO:pn20U9SITR39:pvrThinkPadX1CarbonGen8:rvnLENOVO:rn20U9SITR39:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon Gen 8 dmi.product.name: 20U9SITR39 dmi.product.sku: LENOVO_MT_20U9_BU_Think_FM_ThinkPad X1 Carbon Gen 8 dmi.product.version: ThinkPad X1 Carbon Gen 8 dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: D8:3B:BF:7A:E4:22 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:22494299 acl:63654 sco:0 events:77112 errors:0 TX bytes:45158198 acl:65574 sco:0 commands:7661 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1879438/+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 1879438] [NEW] bluetooth file transfer via bluetooth UI is too slow
Public bug reported: OS: Ubuntu 20.04 Kernel: 5.4.0-31-generic When using the UI to connect and transfer the file form one machine to another machine, BASIC mode is getting selected in the L2CAP configuration and continuous scan is not going on in both sides. the L2CAP MTU size is also in 672, which is very small. Even with the patch applied by Intel, it does not increase the TPT because the UI always selects BASIC mode. Sample File transfer duration: sending - (8MB) 5min 18s sending - (12MB) 7min36s receiving - (8MB) 4min 8s receiving - (12MB) 5min 48s **This issue was also observed in Ubuntu 18.04 OS ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 19 14:46:11 2020 InstallationDate: Installed on 2020-05-19 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20U9SITR39 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic root=UUID=6716936f-20b8-4840-8a75-00f4279d9062 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/12/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2WET11C (1.01C ) dmi.board.asset.tag: Not Available dmi.board.name: 20U9SITR39 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2WET11C(1.01C):bd02/12/2020:svnLENOVO:pn20U9SITR39:pvrThinkPadX1CarbonGen8:rvnLENOVO:rn20U9SITR39:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon Gen 8 dmi.product.name: 20U9SITR39 dmi.product.sku: LENOVO_MT_20U9_BU_Think_FM_ThinkPad X1 Carbon Gen 8 dmi.product.version: ThinkPad X1 Carbon Gen 8 dmi.sys.vendor: LENOVO hciconfig: hci0: Type: Primary Bus: USB BD Address: D8:3B:BF:7A:E4:22 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:22494299 acl:63654 sco:0 events:77112 errors:0 TX bytes:45158198 acl:65574 sco:0 commands:7661 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- 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/1879438 Title: bluetooth file transfer via bluetooth UI is too slow Status in bluez package in Ubuntu: New Bug description: OS: Ubuntu 20.04 Kernel: 5.4.0-31-generic When using the UI to connect and transfer the file form one machine to another machine, BASIC mode is getting selected in the L2CAP configuration and continuous scan is not going on in both sides. the L2CAP MTU size is also in 672, which is very small. Even with the patch applied by Intel, it does not increase the TPT because the UI always selects BASIC mode. Sample File transfer duration: sending - (8MB) 5min 18s sending - (12MB) 7min36s receiving - (8MB) 4min 8s receiving - (12MB) 5min 48s **This issue was also observed in Ubuntu 18.04 OS ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 19 14:46:11 2020 InstallationDate: Installed on 2020-05-19 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20U9SITR39 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic root=UUID=6716936f-20b8-4840-8a75-00f4279d9062 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/12/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2WET11C (1.01C ) dmi.board.asset.tag: Not Available dmi.board.name: 20U9SITR39 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2WET11C(1.01C):bd02/12/2020:svnLENOVO:pn20U9SITR39:pvrThinkPadX1CarbonGen8:rvnLENOVO:rn20U9SITR39:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon Gen 8 dmi.product.name: 20U9SITR39 dmi.product.sku: LENOVO_MT_20U9_BU_Think_FM_ThinkPad X1 Carbon Gen 8 dmi.product.version: ThinkPad X1 Carbon Gen 8 dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: D8:3B:BF:7A:E4:22 ACL MTU: 1021:4 SCO MTU:
[Touch-packages] [Bug 1879438] Re: bluetooth file transfer via bluetooth UI is too slow
** Attachment added: "logs for file transfer (sending)" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1879438/+attachment/5373901/+files/btsnoop.log -- 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/1879438 Title: bluetooth file transfer via bluetooth UI is too slow Status in bluez package in Ubuntu: New Bug description: OS: Ubuntu 20.04 Kernel: 5.4.0-31-generic When using the UI to connect and transfer the file form one machine to another machine, BASIC mode is getting selected in the L2CAP configuration and continuous scan is not going on in both sides. the L2CAP MTU size is also in 672, which is very small. Even with the patch applied by Intel, it does not increase the TPT because the UI always selects BASIC mode. Sample File transfer duration: sending - (8MB) 5min 18s sending - (12MB) 7min36s receiving - (8MB) 4min 8s receiving - (12MB) 5min 48s **This issue was also observed in Ubuntu 18.04 OS ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 19 14:46:11 2020 InstallationDate: Installed on 2020-05-19 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20U9SITR39 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic root=UUID=6716936f-20b8-4840-8a75-00f4279d9062 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/12/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2WET11C (1.01C ) dmi.board.asset.tag: Not Available dmi.board.name: 20U9SITR39 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2WET11C(1.01C):bd02/12/2020:svnLENOVO:pn20U9SITR39:pvrThinkPadX1CarbonGen8:rvnLENOVO:rn20U9SITR39:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon Gen 8 dmi.product.name: 20U9SITR39 dmi.product.sku: LENOVO_MT_20U9_BU_Think_FM_ThinkPad X1 Carbon Gen 8 dmi.product.version: ThinkPad X1 Carbon Gen 8 dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: D8:3B:BF:7A:E4:22 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:22494299 acl:63654 sco:0 events:77112 errors:0 TX bytes:45158198 acl:65574 sco:0 commands:7661 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1879438/+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
