[Touch-packages] [Bug 2000798] Re: cannot connect to K380 bluetooth keyboard
Any other ideas, anything I can do to help diagnostics? -- 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/2000798 Title: cannot connect to K380 bluetooth keyboard Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: Had trouble connecting my K380 keyboard with the laptop (previously used it without issues), unpaired and now I can no longer pair it. Other bluetooth devices work with this particular laptop (mouse, earbuds), the keyboard works flawlessly with a different laptop (running the same Ubuntu 20.04 OS) and an Android phone. Used bluetoothctl to peek under the hood and got nowhere after turning scan on on the controller and activating the keyboard: [NEW] Device [...mac address of the keyboard...] Keyboard K380 [CHG] Device [...mac address of the keyboard...] Connected: no [DEL] Device [...mac address of the keyboard...] Keyboard K380 After this action, I get: # connect [...mac address of the keyboard...] Device [...mac address of the keyboard...] not available When I activate the keyboard (by pressing any key on it while it's turned on), in the bluetooth settings GUI tool I see the keyboard appear for a fraction of a second in the list of unpaired devices and then it disappears. Help? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3.6 ProcVersionSignature: Ubuntu 5.15.0-56.62~20.04.1-generic 5.15.64 Uname: Linux 5.15.0-56-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Dec 30 19:41:41 2022 InstallationDate: Installed on 2022-11-03 (57 days ago) InstallationMedia: Ubuntu 20.04.5 LTS "Focal Fossa" - Release amd64 (20220831) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Intel(R) Client Systems LAPKC71E ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-56-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/12/2021 dmi.bios.release: 5.19 dmi.bios.vendor: Intel Corp. dmi.bios.version: KCTGL357.0037.2021.0712.0948 dmi.board.name: LAPKC71E dmi.board.vendor: Intel Corporation dmi.board.version: M1-402 dmi.chassis.type: 10 dmi.chassis.vendor: Intel(R) Corporation dmi.chassis.version: 2.0 dmi.ec.firmware.release: 1.5 dmi.modalias: dmi:bvnIntelCorp.:bvrKCTGL357.0037.2021.0712.0948:bd07/12/2021:br5.19:efr1.5:svnIntel(R)ClientSystems:pnLAPKC71E:pvrM38559-402:rvnIntelCorporation:rnLAPKC71E:rvrM1-402:cvnIntel(R)Corporation:ct10:cvr2.0:skuBKC71EBFB6000: dmi.product.family: KC dmi.product.name: LAPKC71E dmi.product.sku: BKC71EBFB6000 dmi.product.version: M38559-402 dmi.sys.vendor: Intel(R) Client Systems hciconfig: hci0:Type: Primary Bus: USB BD Address: 20:1E:88:3C:4C:FD ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:221779 acl:5063 sco:0 events:6018 errors:0 TX bytes:785416 acl:104 sco:0 commands:4168 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2000798/+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 2000798] Re: cannot connect to K380 bluetooth keyboard
That's generally possible, but unlikely, given that everything worked well for a couple of months and then suddenly stopped working altogether (rather than occasionally). -- 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/2000798 Title: cannot connect to K380 bluetooth keyboard Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: New Bug description: Had trouble connecting my K380 keyboard with the laptop (previously used it without issues), unpaired and now I can no longer pair it. Other bluetooth devices work with this particular laptop (mouse, earbuds), the keyboard works flawlessly with a different laptop (running the same Ubuntu 20.04 OS) and an Android phone. Used bluetoothctl to peek under the hood and got nowhere after turning scan on on the controller and activating the keyboard: [NEW] Device [...mac address of the keyboard...] Keyboard K380 [CHG] Device [...mac address of the keyboard...] Connected: no [DEL] Device [...mac address of the keyboard...] Keyboard K380 After this action, I get: # connect [...mac address of the keyboard...] Device [...mac address of the keyboard...] not available When I activate the keyboard (by pressing any key on it while it's turned on), in the bluetooth settings GUI tool I see the keyboard appear for a fraction of a second in the list of unpaired devices and then it disappears. Help? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3.6 ProcVersionSignature: Ubuntu 5.15.0-56.62~20.04.1-generic 5.15.64 Uname: Linux 5.15.0-56-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Dec 30 19:41:41 2022 InstallationDate: Installed on 2022-11-03 (57 days ago) InstallationMedia: Ubuntu 20.04.5 LTS "Focal Fossa" - Release amd64 (20220831) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Intel(R) Client Systems LAPKC71E ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-56-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/12/2021 dmi.bios.release: 5.19 dmi.bios.vendor: Intel Corp. dmi.bios.version: KCTGL357.0037.2021.0712.0948 dmi.board.name: LAPKC71E dmi.board.vendor: Intel Corporation dmi.board.version: M1-402 dmi.chassis.type: 10 dmi.chassis.vendor: Intel(R) Corporation dmi.chassis.version: 2.0 dmi.ec.firmware.release: 1.5 dmi.modalias: dmi:bvnIntelCorp.:bvrKCTGL357.0037.2021.0712.0948:bd07/12/2021:br5.19:efr1.5:svnIntel(R)ClientSystems:pnLAPKC71E:pvrM38559-402:rvnIntelCorporation:rnLAPKC71E:rvrM1-402:cvnIntel(R)Corporation:ct10:cvr2.0:skuBKC71EBFB6000: dmi.product.family: KC dmi.product.name: LAPKC71E dmi.product.sku: BKC71EBFB6000 dmi.product.version: M38559-402 dmi.sys.vendor: Intel(R) Client Systems hciconfig: hci0:Type: Primary Bus: USB BD Address: 20:1E:88:3C:4C:FD ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:221779 acl:5063 sco:0 events:6018 errors:0 TX bytes:785416 acl:104 sco:0 commands:4168 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2000798/+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 2000798] Re: cannot connect to K380 bluetooth keyboard
Thanks for responding, Daniel. If it was the driver, I don't know how the keyboard would have worked until a week ago. If it was the hardware, I imagine other BT devices wouldn't connect either, but they do (mouse, earbuds). I might be wrong, of course. -- 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/2000798 Title: cannot connect to K380 bluetooth keyboard Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: New Bug description: Had trouble connecting my K380 keyboard with the laptop (previously used it without issues), unpaired and now I can no longer pair it. Other bluetooth devices work with this particular laptop (mouse, earbuds), the keyboard works flawlessly with a different laptop (running the same Ubuntu 20.04 OS) and an Android phone. Used bluetoothctl to peek under the hood and got nowhere after turning scan on on the controller and activating the keyboard: [NEW] Device [...mac address of the keyboard...] Keyboard K380 [CHG] Device [...mac address of the keyboard...] Connected: no [DEL] Device [...mac address of the keyboard...] Keyboard K380 After this action, I get: # connect [...mac address of the keyboard...] Device [...mac address of the keyboard...] not available When I activate the keyboard (by pressing any key on it while it's turned on), in the bluetooth settings GUI tool I see the keyboard appear for a fraction of a second in the list of unpaired devices and then it disappears. Help? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3.6 ProcVersionSignature: Ubuntu 5.15.0-56.62~20.04.1-generic 5.15.64 Uname: Linux 5.15.0-56-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Dec 30 19:41:41 2022 InstallationDate: Installed on 2022-11-03 (57 days ago) InstallationMedia: Ubuntu 20.04.5 LTS "Focal Fossa" - Release amd64 (20220831) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Intel(R) Client Systems LAPKC71E ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-56-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/12/2021 dmi.bios.release: 5.19 dmi.bios.vendor: Intel Corp. dmi.bios.version: KCTGL357.0037.2021.0712.0948 dmi.board.name: LAPKC71E dmi.board.vendor: Intel Corporation dmi.board.version: M1-402 dmi.chassis.type: 10 dmi.chassis.vendor: Intel(R) Corporation dmi.chassis.version: 2.0 dmi.ec.firmware.release: 1.5 dmi.modalias: dmi:bvnIntelCorp.:bvrKCTGL357.0037.2021.0712.0948:bd07/12/2021:br5.19:efr1.5:svnIntel(R)ClientSystems:pnLAPKC71E:pvrM38559-402:rvnIntelCorporation:rnLAPKC71E:rvrM1-402:cvnIntel(R)Corporation:ct10:cvr2.0:skuBKC71EBFB6000: dmi.product.family: KC dmi.product.name: LAPKC71E dmi.product.sku: BKC71EBFB6000 dmi.product.version: M38559-402 dmi.sys.vendor: Intel(R) Client Systems hciconfig: hci0:Type: Primary Bus: USB BD Address: 20:1E:88:3C:4C:FD ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:221779 acl:5063 sco:0 events:6018 errors:0 TX bytes:785416 acl:104 sco:0 commands:4168 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2000798/+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 2000798] Re: cannot connect to K380 bluetooth keyboard
Forgot to mention: I use this utility to invert Fn key behaviour: https://github.com/jergusg/k380-function-keys-conf ...and it's set up to start on boot using a variant of the procedure described here: https://github.com/embuc/k480_conf My /etc/udev/rules.d/80-k380.rules looks as follows: ACTION=="add", KERNEL=="hidraw[0-9]*", RUN+="/usr/local/bin/fn_on.sh /dev/%k" Tried temporarily removing the udev rule (without a reboot, though), but nothing changed. -- 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/2000798 Title: cannot connect to K380 bluetooth keyboard Status in bluez package in Ubuntu: New Bug description: Had trouble connecting my K380 keyboard with the laptop (previously used it without issues), unpaired and now I can no longer pair it. Other bluetooth devices work with this particular laptop (mouse, earbuds), the keyboard works flawlessly with a different laptop (running the same Ubuntu 20.04 OS) and an Android phone. Used bluetoothctl to peek under the hood and got nowhere after turning scan on on the controller and activating the keyboard: [NEW] Device [...mac address of the keyboard...] Keyboard K380 [CHG] Device [...mac address of the keyboard...] Connected: no [DEL] Device [...mac address of the keyboard...] Keyboard K380 After this action, I get: # connect [...mac address of the keyboard...] Device [...mac address of the keyboard...] not available When I activate the keyboard (by pressing any key on it while it's turned on), in the bluetooth settings GUI tool I see the keyboard appear for a fraction of a second in the list of unpaired devices and then it disappears. Help? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3.6 ProcVersionSignature: Ubuntu 5.15.0-56.62~20.04.1-generic 5.15.64 Uname: Linux 5.15.0-56-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Dec 30 19:41:41 2022 InstallationDate: Installed on 2022-11-03 (57 days ago) InstallationMedia: Ubuntu 20.04.5 LTS "Focal Fossa" - Release amd64 (20220831) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Intel(R) Client Systems LAPKC71E ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-56-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/12/2021 dmi.bios.release: 5.19 dmi.bios.vendor: Intel Corp. dmi.bios.version: KCTGL357.0037.2021.0712.0948 dmi.board.name: LAPKC71E dmi.board.vendor: Intel Corporation dmi.board.version: M1-402 dmi.chassis.type: 10 dmi.chassis.vendor: Intel(R) Corporation dmi.chassis.version: 2.0 dmi.ec.firmware.release: 1.5 dmi.modalias: dmi:bvnIntelCorp.:bvrKCTGL357.0037.2021.0712.0948:bd07/12/2021:br5.19:efr1.5:svnIntel(R)ClientSystems:pnLAPKC71E:pvrM38559-402:rvnIntelCorporation:rnLAPKC71E:rvrM1-402:cvnIntel(R)Corporation:ct10:cvr2.0:skuBKC71EBFB6000: dmi.product.family: KC dmi.product.name: LAPKC71E dmi.product.sku: BKC71EBFB6000 dmi.product.version: M38559-402 dmi.sys.vendor: Intel(R) Client Systems hciconfig: hci0:Type: Primary Bus: USB BD Address: 20:1E:88:3C:4C:FD ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:221779 acl:5063 sco:0 events:6018 errors:0 TX bytes:785416 acl:104 sco:0 commands:4168 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2000798/+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 2000798] [NEW] cannot connect to K380 bluetooth keyboard
Public bug reported: Had trouble connecting my K380 keyboard with the laptop (previously used it without issues), unpaired and now I can no longer pair it. Other bluetooth devices work with this particular laptop (mouse, earbuds), the keyboard works flawlessly with a different laptop (running the same Ubuntu 20.04 OS) and an Android phone. Used bluetoothctl to peek under the hood and got nowhere after turning scan on on the controller and activating the keyboard: [NEW] Device [...mac address of the keyboard...] Keyboard K380 [CHG] Device [...mac address of the keyboard...] Connected: no [DEL] Device [...mac address of the keyboard...] Keyboard K380 After this action, I get: # connect [...mac address of the keyboard...] Device [...mac address of the keyboard...] not available When I activate the keyboard (by pressing any key on it while it's turned on), in the bluetooth settings GUI tool I see the keyboard appear for a fraction of a second in the list of unpaired devices and then it disappears. Help? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3.6 ProcVersionSignature: Ubuntu 5.15.0-56.62~20.04.1-generic 5.15.64 Uname: Linux 5.15.0-56-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Dec 30 19:41:41 2022 InstallationDate: Installed on 2022-11-03 (57 days ago) InstallationMedia: Ubuntu 20.04.5 LTS "Focal Fossa" - Release amd64 (20220831) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Intel(R) Client Systems LAPKC71E ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-56-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/12/2021 dmi.bios.release: 5.19 dmi.bios.vendor: Intel Corp. dmi.bios.version: KCTGL357.0037.2021.0712.0948 dmi.board.name: LAPKC71E dmi.board.vendor: Intel Corporation dmi.board.version: M1-402 dmi.chassis.type: 10 dmi.chassis.vendor: Intel(R) Corporation dmi.chassis.version: 2.0 dmi.ec.firmware.release: 1.5 dmi.modalias: dmi:bvnIntelCorp.:bvrKCTGL357.0037.2021.0712.0948:bd07/12/2021:br5.19:efr1.5:svnIntel(R)ClientSystems:pnLAPKC71E:pvrM38559-402:rvnIntelCorporation:rnLAPKC71E:rvrM1-402:cvnIntel(R)Corporation:ct10:cvr2.0:skuBKC71EBFB6000: dmi.product.family: KC dmi.product.name: LAPKC71E dmi.product.sku: BKC71EBFB6000 dmi.product.version: M38559-402 dmi.sys.vendor: Intel(R) Client Systems hciconfig: hci0: Type: Primary Bus: USB BD Address: 20:1E:88:3C:4C:FD ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:221779 acl:5063 sco:0 events:6018 errors:0 TX bytes:785416 acl:104 sco:0 commands:4168 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/2000798 Title: cannot connect to K380 bluetooth keyboard Status in bluez package in Ubuntu: New Bug description: Had trouble connecting my K380 keyboard with the laptop (previously used it without issues), unpaired and now I can no longer pair it. Other bluetooth devices work with this particular laptop (mouse, earbuds), the keyboard works flawlessly with a different laptop (running the same Ubuntu 20.04 OS) and an Android phone. Used bluetoothctl to peek under the hood and got nowhere after turning scan on on the controller and activating the keyboard: [NEW] Device [...mac address of the keyboard...] Keyboard K380 [CHG] Device [...mac address of the keyboard...] Connected: no [DEL] Device [...mac address of the keyboard...] Keyboard K380 After this action, I get: # connect [...mac address of the keyboard...] Device [...mac address of the keyboard...] not available When I activate the keyboard (by pressing any key on it while it's turned on), in the bluetooth settings GUI tool I see the keyboard appear for a fraction of a second in the list of unpaired devices and then it disappears. Help? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3.6 ProcVersionSignature: Ubuntu 5.15.0-56.62~20.04.1-generic 5.15.64 Uname: Linux 5.15.0-56-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Dec 30 19:41:41 2022 InstallationDate: Installed on 2022-11-03 (57 days ago) InstallationMedia: Ubuntu 20.04.5 LTS "Focal Fossa" - Release amd64 (20220831) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Intel(R) Client Systems LAPKC71E ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-56-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
[Touch-packages] [Bug 1993516] [NEW] bluetooth input freezes for a few second after brief inactivity
Public bug reported: I have a Logitech bluetooth mouse (M650) and keyboard (K380, details in the attached log). I almost never power down the laptop: I suspend and resume it. Sometimes when I resume from suspend everything works flawlessly. Other times, there's a 2-3s "freeze" after just several seconds of input inactivity, during which moving the mouse or pressing keyboard keys gives no response. After 2-3s, all the keys pressed during the freeze suddenly appear on screen. Restarting the bluetooth service, going to airplane mode and back or turning the mouse and keyboard on and off does not help at all. The delay makes using these input devices barely usable. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3.6 ProcVersionSignature: Ubuntu 5.4.0-126.142-generic 5.4.203 Uname: Linux 5.4.0-126-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Oct 19 11:25:13 2022 InstallationDate: Installed on 2017-02-18 (2068 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. Latitude E5570 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-126-generic root=UUID=2b559de5-44d4-4f98-a211-a39edbb31bc8 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to focal on 2022-08-02 (77 days ago) dmi.bios.date: 10/02/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.21.6 dmi.board.name: 03MCRF dmi.board.vendor: Dell Inc. dmi.board.version: A09 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.21.6:bd10/02/2019:svnDellInc.:pnLatitudeE5570:pvr:rvnDellInc.:rn03MCRF:rvrA09:cvnDellInc.:ct9:cvr: dmi.product.family: Latitude dmi.product.name: Latitude E5570 dmi.product.sku: 06DF dmi.sys.vendor: Dell Inc. hciconfig: hci0: Type: Primary Bus: USB BD Address: B8:8A:60:C5:C9:BF ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:34304 acl:977 sco:0 events:2580 errors:0 TX bytes:603917 acl:73 sco:0 commands:2473 errors:0 mtime.conffile..etc.bluetooth.main.conf: 2022-10-19T11:24:40.907104 ** 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/1993516 Title: bluetooth input freezes for a few second after brief inactivity Status in bluez package in Ubuntu: New Bug description: I have a Logitech bluetooth mouse (M650) and keyboard (K380, details in the attached log). I almost never power down the laptop: I suspend and resume it. Sometimes when I resume from suspend everything works flawlessly. Other times, there's a 2-3s "freeze" after just several seconds of input inactivity, during which moving the mouse or pressing keyboard keys gives no response. After 2-3s, all the keys pressed during the freeze suddenly appear on screen. Restarting the bluetooth service, going to airplane mode and back or turning the mouse and keyboard on and off does not help at all. The delay makes using these input devices barely usable. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3.6 ProcVersionSignature: Ubuntu 5.4.0-126.142-generic 5.4.203 Uname: Linux 5.4.0-126-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Oct 19 11:25:13 2022 InstallationDate: Installed on 2017-02-18 (2068 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. Latitude E5570 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-126-generic root=UUID=2b559de5-44d4-4f98-a211-a39edbb31bc8 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to focal on 2022-08-02 (77 days ago) dmi.bios.date: 10/02/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.21.6 dmi.board.name: 03MCRF dmi.board.vendor: Dell Inc. dmi.board.version: A09 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.21.6:bd10/02/2019:svnDellInc.:pnLatitudeE5570:pvr:rvnDellInc.:rn03MCRF:rvrA09:cvnDellInc.:ct9:cvr: dmi.product.family: Latitude dmi.product.name: Latitude E5570 dmi.product.sku: 06DF dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: B8:8A:60:C5:C9:BF ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:34304 acl:977 sco:0 events:2580 errors:0 TX bytes:603917 acl:73 sco:0 commands:2473 errors:0 mtime.conffile..etc.bluetooth.main.conf: 2022-10-19T11:24:40.907104 To manage notifications about this bug go to:
[Touch-packages] [Bug 1910768] Re: apport-collect hangs and makes computer hang
I see a similar (same?) issue: if I say a bug is display-related, apport collecting problem information hangs ~20% through the process and neither "Cancel" nor (x) can stop the process. Cancel in the parent window helps. This is on 20.04. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1910768 Title: apport-collect hangs and makes computer hang Status in apport package in Ubuntu: Confirmed Bug description: This bug is related to bug 1723558 (https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1723558) but I could not transfer the generated information. After a crash of bluetoothd (see bug 1910405) I tried to run apport- collect with the bug ID, but the process hangs. After clicking cancel, it makes the computer hang totally, except running teams calls that keep streaming but without interaction possible. All is released when apport is killed manually. The problem also occurs when a crash of the Brave browser causes a call to apport. This bug is generated through ubuntu-bug -w after clicking on the apport-collect window. This second apport process doesn't hang. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: apport-gtk 2.20.9-0ubuntu7.21 ProcVersionSignature: Ubuntu 5.4.0-58.64~18.04.1-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jan 8 15:29:04 2021 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92 ExecutablePath: /usr/share/apport/apport-gtk InstallationDate: Installed on 2019-11-22 (412 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 InterpreterPath: /usr/bin/python3.6 PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.15~rc1-1 SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1910768/+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 1887161] [NEW] sound does not switch to bluetooth speakers automatically after connecting
Public bug reported: I connect to a bluetooth speaker. Observed behaviour: connection established, but sound still continues to come from the built-in speakers and when looking at available sound outputs in the gnome-control-center, there are no new outputs. Expected behaviour: connection established, sound output switches to BT speaker automatically, new sound output device visible in sound settings Workaround: disconnect and reconnect a few times, after which everything seems to work The BT speaker is a actually the F900 2 Channel Amp Bluetooth Amplifier feeding regular wired speakers behind it. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-108.109-generic 4.15.18 Uname: Linux 4.15.0-108-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tnalfir2036 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Jul 10 13:33:04 2020 InstallationDate: Installed on 2017-02-18 (1237 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: Bluetooth sound card not detected UpgradeStatus: Upgraded to bionic on 2020-05-10 (60 days ago) dmi.bios.date: 06/15/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.3 dmi.board.asset.tag: 201710275 dmi.board.name: 0R3VX4 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.asset.tag: 201710275 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.3:bd06/15/2016:svnDellInc.:pnLatitudeE5570:pvr:rvnDellInc.:rn0R3VX4:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5570 dmi.sys.vendor: Dell Inc. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1887161 Title: sound does not switch to bluetooth speakers automatically after connecting Status in alsa-driver package in Ubuntu: New Bug description: I connect to a bluetooth speaker. Observed behaviour: connection established, but sound still continues to come from the built-in speakers and when looking at available sound outputs in the gnome-control-center, there are no new outputs. Expected behaviour: connection established, sound output switches to BT speaker automatically, new sound output device visible in sound settings Workaround: disconnect and reconnect a few times, after which everything seems to work The BT speaker is a actually the F900 2 Channel Amp Bluetooth Amplifier feeding regular wired speakers behind it. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-108.109-generic 4.15.18 Uname: Linux 4.15.0-108-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tnalfir2036 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Jul 10 13:33:04 2020 InstallationDate: Installed on 2017-02-18 (1237 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: Bluetooth sound card not detected UpgradeStatus: Upgraded to bionic on 2020-05-10 (60 days ago) dmi.bios.date: 06/15/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.3 dmi.board.asset.tag: 201710275 dmi.board.name: 0R3VX4 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.asset.tag: 201710275 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.3:bd06/15/2016:svnDellInc.:pnLatitudeE5570:pvr:rvnDellInc.:rn0R3VX4:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5570 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1887161/+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 1873086] Re: sound stutters when playing on a bluetooth receiver
@Daniel Thank you, will see where I get with sudo modprobe ath10k_core btcoex_enable=1 bt_ant_diversity=1 as seems to have been suggested under the related bug. Will try 5GHz and disabling WiFi, but the latter can obviously only be a temporary diagnostics step. -- 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/1873086 Title: sound stutters when playing on a bluetooth receiver Status in pulseaudio package in Ubuntu: Incomplete Bug description: I can play via bluetooth from my laptop or my mobile phone. I have a set of bluetooth headphones and bluetooth speakers. Any combination of output with the smartphone as the player works, which is as it should be. Any combination of output with the laptop as the player is miserable: sound stutters, sometimes randomly, sometimes seemingly when I touch the laptop or come close to it...had similar or identical problems with a previous Ubuntu laptop. Bluetooth audio seems to be in very bad shape. $ lsb_release -rd Description: Ubuntu 18.04.4 LTS Release: 18.04 laptop Dell XPS 9370 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.4 ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tna2174 F pulseaudio /dev/snd/pcmC0D0p: tna2174 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Apr 15 22:55:05 2020 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 InstallationDate: Installed on 2018-05-10 (706 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to bionic on 2020-03-04 (42 days ago) dmi.bios.date: 12/11/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.1 dmi.board.name: 0W970W dmi.board.vendor: Dell Inc. dmi.board.version: A05 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.1:bd12/11/2019:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0W970W:rvrA05:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1873086/+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 1873086] Re: sound stutters when playing on a bluetooth receiver
** Attachment added: "lsusb.txt" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1873086/+attachment/5356583/+files/lsusb.txt -- 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/1873086 Title: sound stutters when playing on a bluetooth receiver Status in pulseaudio package in Ubuntu: Incomplete Bug description: I can play via bluetooth from my laptop or my mobile phone. I have a set of bluetooth headphones and bluetooth speakers. Any combination of output with the smartphone as the player works, which is as it should be. Any combination of output with the laptop as the player is miserable: sound stutters, sometimes randomly, sometimes seemingly when I touch the laptop or come close to it...had similar or identical problems with a previous Ubuntu laptop. Bluetooth audio seems to be in very bad shape. $ lsb_release -rd Description: Ubuntu 18.04.4 LTS Release: 18.04 laptop Dell XPS 9370 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.4 ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tna2174 F pulseaudio /dev/snd/pcmC0D0p: tna2174 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Apr 15 22:55:05 2020 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 InstallationDate: Installed on 2018-05-10 (706 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to bionic on 2020-03-04 (42 days ago) dmi.bios.date: 12/11/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.1 dmi.board.name: 0W970W dmi.board.vendor: Dell Inc. dmi.board.version: A05 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.1:bd12/11/2019:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0W970W:rvrA05:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1873086/+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 1873086] Re: sound stutters when playing on a bluetooth receiver
Adding lsusb output. ** Attachment added: "lspci.txt" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1873086/+attachment/5356582/+files/lspci.txt -- 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/1873086 Title: sound stutters when playing on a bluetooth receiver Status in pulseaudio package in Ubuntu: Incomplete Bug description: I can play via bluetooth from my laptop or my mobile phone. I have a set of bluetooth headphones and bluetooth speakers. Any combination of output with the smartphone as the player works, which is as it should be. Any combination of output with the laptop as the player is miserable: sound stutters, sometimes randomly, sometimes seemingly when I touch the laptop or come close to it...had similar or identical problems with a previous Ubuntu laptop. Bluetooth audio seems to be in very bad shape. $ lsb_release -rd Description: Ubuntu 18.04.4 LTS Release: 18.04 laptop Dell XPS 9370 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.4 ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tna2174 F pulseaudio /dev/snd/pcmC0D0p: tna2174 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Apr 15 22:55:05 2020 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 InstallationDate: Installed on 2018-05-10 (706 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to bionic on 2020-03-04 (42 days ago) dmi.bios.date: 12/11/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.1 dmi.board.name: 0W970W dmi.board.vendor: Dell Inc. dmi.board.version: A05 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.1:bd12/11/2019:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0W970W:rvrA05:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1873086/+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 1873086] [NEW] sound stutters when playing on a bluetooth receiver
Public bug reported: I can play via bluetooth from my laptop or my mobile phone. I have a set of bluetooth headphones and bluetooth speakers. Any combination of output with the smartphone as the player works, which is as it should be. Any combination of output with the laptop as the player is miserable: sound stutters, sometimes randomly, sometimes seemingly when I touch the laptop or come close to it...had similar or identical problems with a previous Ubuntu laptop. Bluetooth audio seems to be in very bad shape. $ lsb_release -rd Description:Ubuntu 18.04.4 LTS Release:18.04 laptop Dell XPS 9370 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.4 ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tna2174 F pulseaudio /dev/snd/pcmC0D0p: tna2174 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Apr 15 22:55:05 2020 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 InstallationDate: Installed on 2018-05-10 (706 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to bionic on 2020-03-04 (42 days ago) dmi.bios.date: 12/11/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.1 dmi.board.name: 0W970W dmi.board.vendor: Dell Inc. dmi.board.version: A05 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.1:bd12/11/2019:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0W970W:rvrA05:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- 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/1873086 Title: sound stutters when playing on a bluetooth receiver Status in pulseaudio package in Ubuntu: New Bug description: I can play via bluetooth from my laptop or my mobile phone. I have a set of bluetooth headphones and bluetooth speakers. Any combination of output with the smartphone as the player works, which is as it should be. Any combination of output with the laptop as the player is miserable: sound stutters, sometimes randomly, sometimes seemingly when I touch the laptop or come close to it...had similar or identical problems with a previous Ubuntu laptop. Bluetooth audio seems to be in very bad shape. $ lsb_release -rd Description: Ubuntu 18.04.4 LTS Release: 18.04 laptop Dell XPS 9370 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.4 ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tna2174 F pulseaudio /dev/snd/pcmC0D0p: tna2174 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Apr 15 22:55:05 2020 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 InstallationDate: Installed on 2018-05-10 (706 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to bionic on 2020-03-04 (42 days ago) dmi.bios.date: 12/11/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.1 dmi.board.name: 0W970W dmi.board.vendor: Dell Inc. dmi.board.version: A05 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.1:bd12/11/2019:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0W970W:rvrA05:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1873086/+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 1594939] Re: Sound over bluetooth is stuttering
#1594591 might be related. -- 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/1594939 Title: Sound over bluetooth is stuttering Status in bluez package in Ubuntu: Confirmed Bug description: I am using a Meizu Pro 5 device with Ubuntu 15.04 (r110). Problem description: When paired with a bluetooth receiver (tested with 'Bose Soundlink Colour' and 'Philips AEA2700') the sound is very laggy and stuttering a lot. Apart from the stuttering where there is no sound at all for short periods of time you can also hear, that the sound is stretched and squeezed sometimes (maybe to compensate the lags). The stuttering is a lot worse, when the system-settings-app is open and searching for bt-devices. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1594939/+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 1594591] Re: Bluetooth audio isn't working properly!
I encounter sound over bluetooth stuttering as well. Ubuntu 14.04, bluetooth in A2DP mode. I get the vague feeling that the stuttering gets worse when the system is active, but sometimes it's the CPU, sometimes the WiFi...sometimes no obvious reason. I'm 3m away from a receiver in line of sight, FWIW. Also, issue #1594939 sounds like it might be related. -- 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/1594591 Title: Bluetooth audio isn't working properly! Status in bluez package in Ubuntu: Confirmed Bug description: My bluetooth headset is connected fine but the sound keeps stuttering, then the sound completely disappears! I noticed that it only happens when wifi is enabled! I'm using Ubuntu 16.04 LTS | Broadcom driver ps: it works quite well with windows 10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1594591/+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 1661763] Re: screen turns off during standby, doesn't wake up on resume
What I see is similar, but not identical to Gábor's description:
Feb 24 14:51:10 tena kernel: [ 761.070735] CPU: 0 PID: 1132 Comm: Xorg
Tainted: GW 4.4.
0-64-generic #85~14.04.1-Ubuntu
Feb 24 14:51:10 tena kernel: [ 761.070736] Hardware name: Dell Inc. Latitude
E5570/0R3VX4, BIOS 1.7.3
06/15/2016
Feb 24 14:51:10 tena kernel: [ 761.070737] 880097f47928
813dc80c 88
0097f47970
Feb 24 14:51:10 tena kernel: [ 761.070738] c069e700 880097f47960
8107e9d6 88
0097156000
Feb 24 14:51:10 tena kernel: [ 761.070739] 880097308000 0004
880097cf8b78 88
0097f479ec
Feb 24 14:51:10 tena kernel: [ 761.070741] Call Trace:
Feb 24 14:51:10 tena kernel: [ 761.070742] []
dump_stack+0x63/0x87
Notice that in my case, it says "Xorg Tainted", where Gábor sees "Xorg Not
Tainted". Not sure if it's the same bug, but it sounds like it might be. I'm on
Ubuntu 14.04 ("4.4.0-64-generic #85~14.04.1-Ubuntu SMP Mon Feb 20 12:10:54 UTC
2017 x86_64 x86_64 x86_64 GNU/Linux"), on a Latitude E5570. Fresh install a few
days ago.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libdrm in Ubuntu.
https://bugs.launchpad.net/bugs/1661763
Title:
screen turns off during standby, doesn't wake up on resume
Status in libdrm package in Ubuntu:
Confirmed
Bug description:
screen turns off during standby, doesn't wake up on resume
had to reboot to recover
Feb 2 22:51:59 ubuntu8 kernel: [318555.548546] [ cut here
]
Feb 2 22:51:59 ubuntu8 kernel: [318555.548650] WARNING: CPU: 3 PID: 14496 at
/build/linux-RZGRu0/linux-4.8.0/drivers/gpu/drm/i915/intel_display.c:14328
skl_max_scale.part.120+0x75/0x80 [i915]
Feb 2 22:51:59 ubuntu8 kernel: [318555.548654] WARN_ON_ONCE(!crtc_clock ||
cdclk < crtc_clock)
Feb 2 22:51:59 ubuntu8 kernel: [318555.548657] Modules linked in: msr ccm
rfcomm bnep hid_multitouch i2c_designware_platform i2c_designware_core hp_wmi
sparse_keymap nls_iso8859_1 arc4 snd_soc_skl snd_soc_skl_ipc snd_soc_sst_ipc
snd_hda_codec_hdmi intel_rapl x86_pkg_temp_thermal coretemp
snd_hda_codec_conexant snd_hda_codec_generic snd_soc_sst_dsp snd_hda_ext_core
kvm_intel snd_soc_sst_match kvm iwlmvm snd_soc_core irqbypass crct10dif_pclmul
snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel snd_hda_codec
crc32_pclmul mac80211 snd_hda_core ghash_clmulni_intel snd_hwdep aesni_intel
snd_pcm aes_x86_64 lrw snd_seq_midi glue_helper snd_seq_midi_event ablk_helper
snd_rawmidi cryptd iwlwifi snd_seq snd_seq_device snd_timer input_leds cfg80211
joydev serio_raw rtsx_pci_ms memstick snd soundcore uvcvideo videobuf2_vmalloc
videobuf2_memops videobuf2_v4l2 shpchp videobuf2_core videodev media mei_me
idma64 mei virt_dma btusb btrtl intel_lpss_pci intel_pch_thermal
processor_thermal_device intel_soc_dts_iosf ucsi int3403_thermal hci_uart btbcm
btqca btintel bluetooth intel_lpss_acpi intel_lpss hp_accel lis3lv02d
input_polldev int3402_thermal int3406_thermal int340x_thermal_zone tpm_crb
mac_hid int3400_thermal acpi_thermal_rel acpi_pad dptf_power hp_wireless
parport_pc ppdev lp parport ip_tables x_tables autofs4 btrfs xor raid6_pq
rtsx_pci_sdmmc i915 i2c_algo_bit drm_kms_helper syscopyarea psmouse sysfillrect
nvme sysimgblt fb_sys_fops nvme_core drm ahci rtsx_pci libahci i2c_hid wmi hid
video fjes
Feb 2 22:51:59 ubuntu8 kernel: [318555.548904] CPU: 3 PID: 14496 Comm: Xorg
Not tainted 4.8.0-34-generic #36-Ubuntu
Feb 2 22:51:59 ubuntu8 kernel: [318555.548907] Hardware name: HP HP ENVY
Notebook/81D1, BIOS F.28 10/05/2016
Feb 2 22:51:59 ubuntu8 kernel: [318555.548911] 0286
8055b5e8 975531437930 8e430a22
Feb 2 22:51:59 ubuntu8 kernel: [318555.548924] 975531437980
975531437970 8e08319b
Feb 2 22:51:59 ubuntu8 kernel: [318555.548930] 37f88e1a9a80
975412ad86c0 97555c5b3c00 9755660a6000
Feb 2 22:51:59 ubuntu8 kernel: [318555.548936] Call Trace:
Feb 2 22:51:59 ubuntu8 kernel: [318555.548948] []
dump_stack+0x63/0x81
Feb 2 22:51:59 ubuntu8 kernel: [318555.548957] []
__warn+0xcb/0xf0
Feb 2 22:51:59 ubuntu8 kernel: [318555.548965] []
warn_slowpath_fmt+0x5f/0x80
Feb 2 22:51:59 ubuntu8 kernel: [318555.548998] [] ?
drm_atomic_helper_normalize_zpos+0x264/0x300 [drm_kms_helper]
Feb 2 22:51:59 ubuntu8 kernel: [318555.549068] []
skl_max_scale.part.120+0x75/0x80 [i915]
Feb 2 22:51:59 ubuntu8 kernel: [318555.549131] []
intel_check_primary_plane+0xc6/0xe0 [i915]
Feb 2 22:51:59 ubuntu8 kernel: [318555.549151] [] ?
drm_atomic_helper_normalize_zpos+0x264/0x300 [drm_kms_helper]
Feb 2 22:51:59 ubuntu8 kernel: [318555.549211] []
intel_plane_atomic_check+0x132/0x1f0 [i915]
Feb 2 22:51:59 ubuntu8 kernel: [318555.549230] []
drm_atomic_helper_check_planes+0x84/0x200 [drm_kms_helper]
Feb 2 22:51:59 ubuntu8
[Touch-packages] [Bug 1290217] Re: The overwriting error message was: Key file does not have group 'connectivity'
14.04, affected by the bug, manually starting NetworkManager helps, but I do get the error message: http://postimg.org/image/c9z0at29z/ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1290217 Title: The overwriting error message was: Key file does not have group 'connectivity' Status in network-manager package in Ubuntu: Confirmed Bug description: Looking at /var/log/upstart/network-manager.log, that error is written: (NetworkManager:969): GLib-WARNING **: GError set over the top of a previous GError or uninitialized memory. This indicates a bug in someone's code. You must ensure an error is NULL before it's set. The overwriting error message was: Key file does not have group 'connectivity' ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: network-manager 0.9.8.8-0ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5 Uname: Linux 3.13.0-16-generic i686 ApportVersion: 2.13.3-0ubuntu1 Architecture: i386 CurrentDesktop: GNOME Date: Mon Mar 10 07:02:37 2014 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-10-25 (135 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20131021.1) IpRoute: default via 192.168.1.1 dev eth0 proto static 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.3 metric 1 IwConfig: lono wireless extensions. eth0 no wireless extensions. eth1 no wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true RfKill: SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified] mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2013-12-25T13:58:11.169010 nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Wired connection 17cca4ae1-9b74-45ac-bc15-7b1757516613 802-3-ethernet1394431189 Mon 10 Mar 2014 06:59:49 CET yes no /org/freedesktop/NetworkManager/Settings/1 Connexion filaire 2 2f951ef2-14cf-4fb5-a89a-b83bdae4731d 802-3-ethernet1389770221 Wed 15 Jan 2014 08:17:01 CET yes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth1 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/1 eth0 802-3-ethernetconnected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.8connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1290217/+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 1072206] Re: [nvidia] Window content is black or transparent
Can some1 tell me when this fix will hit ubuntu 14.04 ? thx -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1072206 Title: [nvidia] Window content is black or transparent Status in Compiz: In Progress Status in Compiz 0.9.11 series: Triaged Status in NVIDIA Drivers Ubuntu: Invalid Status in Unity: Invalid Status in compiz package in Ubuntu: Fix Released Status in unity package in Ubuntu: Invalid Bug description: Ubuntu 12.10 64bit (updated from 12.04) / NVIDIA GeForce 8 proprietary driver. This bug happens to me from 12.04 from some update I think. It appears mostly when I open a new application and only ocassionally. As temporary solution creating some other event like opening Unity dash or opening some next window, etc. fix it. Then window content is refreshed and I can see all correctly. Same with stable and experimental nvidia drivers. Screenshot of this bug is attached. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: unity 6.8.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] je adresářem: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 304.48 Sun Sep 9 20:22:27 PDT 2012 GCC version: gcc version 4.7.2 (Ubuntu/Linaro 4.7.2-2ubuntu1) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. .tmp.unity.support.test.0: ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz Date: Sat Oct 27 23:00:14 2012 DistUpgraded: 2012-10-23 19:34:29,842 DEBUG enabling apt cron job DistroCodename: quantal DistroVariant: ubuntu DkmsStatus: nvidia-experimental-304, 304.48, 3.5.0-17-generic, x86_64: installed virtualbox, 4.1.18, 3.2.0-32-generic, x86_64: installed virtualbox, 4.1.18, 3.5.0-17-generic, x86_64: installed GraphicsCard: NVIDIA Corporation G92 [GeForce 8800 GT] [10de:0611] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Giga-byte Technology Device [1458:3468] InstallationDate: Installed on 2012-08-29 (59 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta amd64 (20120328) JockeyStatus: kmod:nvidia_experimental_304 - nvidia_experimental_304 (Proprietary, Enabled, Not in use) kmod:nvidia_173 - NVIDIA binary Xorg driver, kernel module and VDPAU library (Proprietary, Disabled, Not in use) kmod:nvidia_current - NVIDIA binary Xorg driver, kernel module and VDPAU library (Proprietary, Disabled, Not in use) kmod:nvidia_173_updates - NVIDIA binary Xorg driver, kernel module and VDPAU library (Proprietary, Disabled, Not in use) kmod:nvidia_current_updates - NVIDIA binary Xorg driver, kernel module and VDPAU library (Proprietary, Disabled, Not in use) MachineType: System manufacturer System Product Name MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=cs_CZ.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic root=UUID=3ae94b68-4a0c-4633-aec7-b4ed25a23003 ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to quantal on 2012-10-23 (4 days ago) XorgConf: Section Device Identifier Default Device Option NoLogoTrue EndSection dmi.bios.date: 05/26/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0208 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H61-M LX dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev x.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0208:bd05/26/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8H61-MLX:rvrRevx.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.8.4-0ubuntu3 version.ia32-libs: ia32-libs 20090808ubuntu36 version.libdrm2: libdrm2 2.4.39-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0-0ubuntu1
