[Bug 1845689] Re: Bluetooth loops when pairing Connecting MPOW T5 headset
My only backup image was from 17.10, running kernel Kernel 4.13.0-46-generic. I stand corrected on the earbud model. It was an MPOW Flame that time, and not an MPOW T5/M5 model Nonetheless, even in the 17.10 backup image, bluetooth restarts. However, unlike in Disco, my earbuds actually manage to connect. The connection does drop after a couple of seconds, however. Also, I did find something that may be of relevance. I have an old USB Bluetooth dongle. And I plugged that in, and then used Blueman-manager to switch to that adapter and pair my earbuds -- and it works. Does this help further debugging? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845689 Title: Bluetooth loops when pairing Connecting MPOW T5 headset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845689/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845689] Re: Bluetooth loops when pairing Connecting MPOW T5 headset
Okay, will dig out my old backup images and see. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845689 Title: Bluetooth loops when pairing Connecting MPOW T5 headset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845689/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845689] Re: Bluetooth loops when pairing Connecting MPOW T5 headset
Hi, the same problem occurs, even using a different MPOW model and an Anker brand. I've attached the syslog output in another file -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845689 Title: Bluetooth loops when pairing Connecting MPOW T5 headset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845689/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845689] Re: Bluetooth loops when pairing Connecting MPOW T5 headset
** Attachment added: "focal.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845689/+attachment/5325305/+files/focal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845689 Title: Bluetooth loops when pairing Connecting MPOW T5 headset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845689/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860935] Re: Unable to pair to Bluetooth earbuds on Eoan (MPOW M5)
Additional. I got my hands on a different brand of headphones (Anker) to see if the manufacturer was the issue. I still have the same problem. TL;DR: Clean install of Eoan, bluetooth pairs then bluetooth restarts, over and over. Sometimes, I'm lucky and it will stay connected. Most of the time it restarts. Same machine and headphones work fine under Windows 8.1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860935 Title: Unable to pair to Bluetooth earbuds on Eoan (MPOW M5) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1860935/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860935] [NEW] Unable to pair to Bluetooth earbuds on Eoan (MPOW M5)
Public bug reported: This is a clean install of Eoan (although I have copied the home directory files from my previous installation, though I don't think that should affect this problem) A fresh pairing attempt gives this in the syslog: ``` Jan 26 20:46:37 johnny-W35xSS-370SS bluetoothd[887]: connect error: Connection refused (111) Jan 26 20:46:37 johnny-W35xSS-370SS bluetoothd[887]: a2dp-source profile connect failed for 9A:25:5B:01:32:A8: Device or resource busy Jan 26 20:46:37 johnny-W35xSS-370SS bluetoothd[887]: connect error: Connection refused (111) Jan 26 20:46:37 johnny-W35xSS-370SS bluetoothd[887]: a2dp-source profile connect failed for 9A:25:5B:01:32:A8: Device or resource busy Jan 26 20:46:38 johnny-W35xSS-370SS bluetoothd[887]: connect error: Connection refused (111) Jan 26 20:46:38 johnny-W35xSS-370SS bluetoothd[887]: a2dp-source profile connect failed for 9A:25:5B:01:32:A8: Device or resource busy Jan 26 20:46:38 johnny-W35xSS-370SS bluetoothd[887]: connect error: Connection refused (111) Jan 26 20:46:38 johnny-W35xSS-370SS bluetoothd[887]: a2dp-source profile connect failed for 9A:25:5B:01:32:A8: Device or resource busy Jan 26 20:46:39 johnny-W35xSS-370SS bluetoothd[887]: connect error: Connection refused (111) Jan 26 20:46:39 johnny-W35xSS-370SS bluetoothd[887]: a2dp-source profile connect failed for 9A:25:5B:01:32:A8: Device or resource busy Jan 26 20:46:40 johnny-W35xSS-370SS bluetoothd[887]: connect error: Connection refused (111) Jan 26 20:46:40 johnny-W35xSS-370SS bluetoothd[887]: a2dp-source profile connect failed for 9A:25:5B:01:32:A8: Device or resource busy ``` ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: johnny 1571 F pulseaudio /dev/snd/controlC1: johnny 1571 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Jan 26 20:47:40 2020 InstallationDate: Installed on 2020-01-25 (1 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: Bluetooth sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/08/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W35xSS_370SS dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/08/2014:svnNotebook:pnW35xSS_370SS:pvrNotApplicable:rvnNotebook:rnW35xSS_370SS:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W35xSS_370SS dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860935 Title: Unable to pair to Bluetooth earbuds on Eoan (MPOW M5) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1860935/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845689] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1845689/+attachment/5314077/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845689 Title: Bluetooth loops when pairing Connecting MPOW T5 headset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845689/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845689] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1845689/+attachment/5314074/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845689 Title: Bluetooth loops when pairing Connecting MPOW T5 headset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845689/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845689] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1845689/+attachment/5314080/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845689 Title: Bluetooth loops when pairing Connecting MPOW T5 headset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845689/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845689] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1845689/+attachment/5314076/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845689 Title: Bluetooth loops when pairing Connecting MPOW T5 headset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845689/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845689] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1845689/+attachment/5314079/+files/RfKill.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845689 Title: Bluetooth loops when pairing Connecting MPOW T5 headset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845689/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845689] Re: Bluetooth loops when pairing Connecting MPOW T5 headset
apport information ** Tags added: apport-collected ** Description changed: I am running ubuntu Disco, recently upgraded from Beaver. Now when I pair my MPOW T5 bluetooth earbuds, they will pair, connect, then Bluetooth on the machine will restart. This is visible by the Bluetooth applet showing Bluetooth being switched off then on again. This will happen a few times, then bluetooth will lock up, rendering it and the settings applet frozen. Requiring a restart to fix. It is like something in Bluetooth subsystem is crashing out when pairing with the T5 I used to use this MPOW T5 with ubuntu Beaver without issue and am tempted just to roll back to my image from then But here's hoping someone can help identify why this is happening. I am also using this on my Disco installation on my Pixelbook (which was a clean install, not an upgrade), so maybe that's something worth noting. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-29.31-generic 5.0.21 Uname: Linux 5.0.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: johnny 2201 F pulseaudio /dev/snd/controlC0: johnny 2201 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Sep 27 17:34:49 2019 InstallationDate: Installed on 2018-12-31 (269 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: Bluetooth sound card not detected UpgradeStatus: Upgraded to disco on 2019-09-21 (6 days ago) dmi.bios.date: 04/08/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W35xSS_370SS dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/08/2014:svnNotebook:pnW35xSS_370SS:pvrNotApplicable:rvnNotebook:rnW35xSS_370SS:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W35xSS_370SS dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook + --- + ProblemType: Bug + ApportVersion: 2.20.10-0ubuntu27.3 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC1: johnny 2878 F pulseaudio + /dev/snd/controlC0: johnny 2878 F pulseaudio + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 19.04 + InstallationDate: Installed on 2018-12-31 (352 days ago) + InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) + MachineType: Notebook W35xSS_370SS + NonfreeKernelModules: nvidia_modeset nvidia + Package: linux (not installed) + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-37-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 + ProcVersionSignature: Ubuntu 5.0.0-37.40-generic 5.0.21 + RelatedPackageVersions: + linux-restricted-modules-5.0.0-37-generic N/A + linux-backports-modules-5.0.0-37-generic N/A + linux-firmware1.178.6 + Tags: disco + Uname: Linux 5.0.0-37-generic x86_64 + UpgradeStatus: Upgraded to disco on 2019-09-21 (89 days ago) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 04/08/2014 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: 4.6.5 + dmi.board.asset.tag: Tag 12345 + dmi.board.name: W35xSS_370SS + dmi.board.vendor: Notebook + dmi.board.version: Not Applicable + dmi.chassis.asset.tag: No Asset Tag + dmi.chassis.type: 9 + dmi.chassis.vendor: Notebook + dmi.chassis.version: N/A + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/08/2014:svnNotebook:pnW35xSS_370SS:pvrNotApplicable:rvnNotebook:rnW35xSS_370SS:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: + dmi.product.family: Not Applicable + dmi.product.name: W35xSS_370SS + dmi.product.sku: Not Applicable + dmi.product.version: Not Applicable + dmi.sys.vendor: Notebook ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1845689/+attachment/5314067/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845689 Title: Bluetooth loops when pairing Connecting MPOW T5 headset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845689/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845689] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1845689/+attachment/5314071/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845689 Title: Bluetooth loops when pairing Connecting MPOW T5 headset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845689/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845689] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1845689/+attachment/5314078/+files/PulseList.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845689 Title: Bluetooth loops when pairing Connecting MPOW T5 headset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845689/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845689] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1845689/+attachment/5314081/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845689 Title: Bluetooth loops when pairing Connecting MPOW T5 headset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845689/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845689] Re: Bluetooth loops when pairing Connecting MPOW T5 headset
Marking as confirmed as instructed ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845689 Title: Bluetooth loops when pairing Connecting MPOW T5 headset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845689/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845689] Re: Bluetooth loops when pairing Connecting MPOW T5 headset
@seb128 re the bluetooth log, how do I obtain that? I've done the apport stuff, does that include the bluetooth log? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845689 Title: Bluetooth loops when pairing Connecting MPOW T5 headset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845689/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845689] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1845689/+attachment/5314068/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845689 Title: Bluetooth loops when pairing Connecting MPOW T5 headset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845689/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845689] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1845689/+attachment/5314073/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845689 Title: Bluetooth loops when pairing Connecting MPOW T5 headset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845689/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845689] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1845689/+attachment/5314075/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845689 Title: Bluetooth loops when pairing Connecting MPOW T5 headset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845689/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845689] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1845689/+attachment/5314072/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845689 Title: Bluetooth loops when pairing Connecting MPOW T5 headset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845689/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845689] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1845689/+attachment/5314069/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845689 Title: Bluetooth loops when pairing Connecting MPOW T5 headset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845689/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845689] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1845689/+attachment/5314070/+files/IwConfig.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845689 Title: Bluetooth loops when pairing Connecting MPOW T5 headset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845689/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845689] Re: Bluetooth loops when pairing Connecting MPOW T5 headset
More details that might help debugging. Found this in the syslog: Dec 18 18:58:21 johnny-W35xSS-370SS systemd[1]: systemd-rfkill.service: Succeeded. Dec 18 18:58:24 johnny-W35xSS-370SS kernel: [ 336.791201] input: 00:20:5B:12:1F:B6 as /devices/virtual/input/input34 Dec 18 18:58:24 johnny-W35xSS-370SS /usr/lib/gdm3/gdm-x-session[1858]: (II) config/udev: Adding input device 00:20:5B:12:1F:B6 (/dev/input/event20) Dec 18 18:58:24 johnny-W35xSS-370SS /usr/lib/gdm3/gdm-x-session[1858]: (**) 00:20:5B:12:1F:B6: Applying InputClass "libinput keyboard catchall" Dec 18 18:58:24 johnny-W35xSS-370SS /usr/lib/gdm3/gdm-x-session[1858]: (II) Using input driver 'libinput' for '00:20:5B:12:1F:B6' Dec 18 18:58:24 johnny-W35xSS-370SS /usr/lib/gdm3/gdm-x-session[1858]: (II) systemd-logind: got fd for /dev/input/event20 13:84 fd 70 paused 0 Dec 18 18:58:24 johnny-W35xSS-370SS /usr/lib/gdm3/gdm-x-session[1858]: (**) 00:20:5B:12:1F:B6: always reports core events Dec 18 18:58:24 johnny-W35xSS-370SS /usr/lib/gdm3/gdm-x-session[1858]: (**) Option "Device" "/dev/input/event20" Dec 18 18:58:24 johnny-W35xSS-370SS /usr/lib/gdm3/gdm-x-session[1858]: (**) Option "_source" "server/udev" Dec 18 18:58:24 johnny-W35xSS-370SS /usr/lib/gdm3/gdm-x-session[1858]: (II) event20 - 00:20:5B:12:1F:B6: is tagged by udev as: Keyboard Dec 18 18:58:24 johnny-W35xSS-370SS /usr/lib/gdm3/gdm-x-session[1858]: (II) event20 - 00:20:5B:12:1F:B6: device is a keyboard Dec 18 18:58:24 johnny-W35xSS-370SS /usr/lib/gdm3/gdm-x-session[1858]: (II) event20 - 00:20:5B:12:1F:B6: device removed Dec 18 18:58:24 johnny-W35xSS-370SS /usr/lib/gdm3/gdm-x-session[1858]: (**) Option "config_info" "udev:/sys/devices/virtual/input/input34/event20" Dec 18 18:58:24 johnny-W35xSS-370SS /usr/lib/gdm3/gdm-x-session[1858]: (II) XINPUT: Adding extended input device "00:20:5B:12:1F:B6" (type: KEYBOARD, id 18) Dec 18 18:58:24 johnny-W35xSS-370SS /usr/lib/gdm3/gdm-x-session[1858]: (**) Option "xkb_model" "pc105" Dec 18 18:58:24 johnny-W35xSS-370SS /usr/lib/gdm3/gdm-x-session[1858]: (**) Option "xkb_layout" "gb" Dec 18 18:58:24 johnny-W35xSS-370SS /usr/lib/gdm3/gdm-x-session[1858]: (**) Option "xkb_variant" "extd" Dec 18 18:58:24 johnny-W35xSS-370SS /usr/lib/gdm3/gdm-x-session[1858]: (WW) Option "xkb_options" requires a string value Dec 18 18:58:24 johnny-W35xSS-370SS /usr/lib/gdm3/gdm-x-session[1858]: (II) event20 - 00:20:5B:12:1F:B6: is tagged by udev as: Keyboard Dec 18 18:58:24 johnny-W35xSS-370SS /usr/lib/gdm3/gdm-x-session[1858]: (II) event20 - 00:20:5B:12:1F:B6: device is a keyboard Dec 18 18:58:24 johnny-W35xSS-370SS org.gnome.Shell.desktop[2085]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). Dec 18 18:58:24 johnny-W35xSS-370SS org.gnome.Shell.desktop[2085]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). Dec 18 18:58:24 johnny-W35xSS-370SS org.gnome.Shell.desktop[2085]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12). Dec 18 18:58:24 johnny-W35xSS-370SS org.gnome.Shell.desktop[2085]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d). Dec 18 18:58:24 johnny-W35xSS-370SS org.gnome.Shell.desktop[2085]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). Dec 18 18:58:24 johnny-W35xSS-370SS org.gnome.Shell.desktop[2085]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). Dec 18 18:58:24 johnny-W35xSS-370SS org.gnome.Shell.desktop[2085]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a). Dec 18 18:58:24 johnny-W35xSS-370SS org.gnome.Shell.desktop[2085]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11). Dec 18 18:58:24 johnny-W35xSS-370SS org.gnome.Shell.desktop[2085]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b). Dec 18 18:58:29 johnny-W35xSS-370SS bluetoothd[1134]: /org/bluez/hci0/dev_00_20_5B_12_1F_B6/fd7: fd(37) ready Dec 18 18:58:29 johnny-W35xSS-370SS rtkit-daemon[1517]: Supervising 3 threads of 1 processes of 1 users. Dec 18 18:58:29 johnny-W35xSS-370SS rtkit-daemon[1517]: Successfully made thread 6460 of process 2154 owned by '1000' RT at priority 5. Dec 18 18:58:29 johnny-W35xSS-370SS rtkit-daemon[1517]: Supervising 4 threads of 1 processes of 1 users. -- At this point the headset is connected. After a few seconds, bluetooth then restarts: Dec 18 18:58:40 johnny-W35xSS-370SS kernel: [ 353.504506] usb 3-7: Failed to suspend device, error -71 Dec 18 18:58:40 johnny-W35xSS-370SS kernel: [ 353.504570] usb 3-7: USB disconnect, device number 12 Dec 18 18:58:40 johnny-W35xSS-370SS acpid: input device has been disconnected, fd 24 Dec 18 18:58:40 johnny-W35xSS-370SS /usr/lib/gdm3/gdm-x-session[1858]: (II) config/udev: removing device 00:20:
[Bug 1845689] Re: Bluetooth loops when pairing Connecting MPOW T5 headset
Oh, and it pairs okay under Windows on the same laptop (I dual boot Windows 8 and Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845689 Title: Bluetooth loops when pairing Connecting MPOW T5 headset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1845689/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845689] Re: Bluetooth loops when pairing Connecting MPOW T5 headset
As an experiment took the 19.04 Ubuntu live disk, booted up from that and paired mt MPOW T5. Bluetooth crash looped as well. This eliminates anything I've installed as cause. I suspect something in the driver is not liking the bluetooth device on my machine, since it paired with 19.04 on my Pixelbook okay without crash looping. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845689 Title: Bluetooth loops when pairing Connecting MPOW T5 headset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1845689/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845689] [NEW] Bluetooth loops when pairing Connecting MPOW T5 headset
Public bug reported: I am running ubuntu Disco, recently upgraded from Beaver. Now when I pair my MPOW T5 bluetooth earbuds, they will pair, connect, then Bluetooth on the machine will restart. This is visible by the Bluetooth applet showing Bluetooth being switched off then on again. This will happen a few times, then bluetooth will lock up, rendering it and the settings applet frozen. Requiring a restart to fix. It is like something in Bluetooth subsystem is crashing out when pairing with the T5 I used to use this MPOW T5 with ubuntu Beaver without issue and am tempted just to roll back to my image from then But here's hoping someone can help identify why this is happening. I am also using this on my Disco installation on my Pixelbook (which was a clean install, not an upgrade), so maybe that's something worth noting. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-29.31-generic 5.0.21 Uname: Linux 5.0.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: johnny 2201 F pulseaudio /dev/snd/controlC0: johnny 2201 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Sep 27 17:34:49 2019 InstallationDate: Installed on 2018-12-31 (269 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: Bluetooth sound card not detected UpgradeStatus: Upgraded to disco on 2019-09-21 (6 days ago) dmi.bios.date: 04/08/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W35xSS_370SS dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/08/2014:svnNotebook:pnW35xSS_370SS:pvrNotApplicable:rvnNotebook:rnW35xSS_370SS:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W35xSS_370SS dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845689 Title: Bluetooth loops when pairing Connecting MPOW T5 headset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1845689/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768212] [NEW] Package docker.io cannot be purged
Public bug reported: After installing docker.io in Artful, then attempting to purge it, it asks for confirmation, then complains it cannot nuke /var/lib/docker. An almost identical error to this Debian bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856149 /var/lib/docker/nuke-graph-directory.sh: 64: /var/lib/docker/nuke-graph- directory.sh: shopt: not found Running rm -rf /var/lib/docker then trying to purge docker.io again worked and then gave me a warning about /etc/docker not being empty. So rm -rf /etc/docker and purge again then worked. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: docker.io (not installed) ProcVersionSignature: Ubuntu 4.13.0-39.44-generic 4.13.16 Uname: Linux 4.13.0-39-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue May 1 10:16:19 2018 InstallationDate: Installed on 2018-04-15 (15 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) SourcePackage: docker.io UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: docker.io (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768212 Title: Package docker.io cannot be purged To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1768212/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1531087] [NEW] Pidgin system tray icon randomly disappears/corrupts
Public bug reported: When loading Pidgin under Cinnamon, the system tray icon will randomly either: 1. Not appear (blank space appears where the system tray should be) 2. Appear, but then later corrupt (see screenshot) 3. Appear and stay normal I haven't been able to replicate reliably, but it tends to most often happen on first startup after boot. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: pidgin 1:2.10.9-0ubuntu8 ProcVersionSignature: Ubuntu 3.19.0-42.48-generic 3.19.8-ckt10 Uname: Linux 3.19.0-42-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.8 Architecture: amd64 CurrentDesktop: X-Cinnamon Date: Tue Jan 5 07:41:35 2016 InstallationDate: Installed on 2015-03-16 (294 days ago) InstallationMedia: Lubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) SourcePackage: pidgin UpgradeStatus: Upgraded to vivid on 2015-05-08 (241 days ago) ** Affects: pidgin (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid ** Attachment added: "Corrupted system tray icon (scenario 2 above)" https://bugs.launchpad.net/bugs/1531087/+attachment/4544228/+files/postload.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1531087 Title: Pidgin system tray icon randomly disappears/corrupts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/1531087/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1511490] [NEW] Display corrupts after a while
Public bug reported: This has been detected on Utopic, Vivid and Wily and on two different machines. Basically, you can login fine, with a background screen and everything correct. But, after a while (and there is no consistency behind what/when/why), the background will reset to the default Ubuntu background, and the desktop icons will suddenly randomly start overlapping. Rebooting fixes this temporarily. Functionality, everything works fine, other than this graphical error. Example of the overlap attached. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: cinnamon 2.6.13-1ubuntu2 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 CurrentDesktop: X-Cinnamon Date: Thu Oct 29 18:21:06 2015 InstallationDate: Installed on 2015-10-18 (11 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151017) SourcePackage: cinnamon UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: cinnamon (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug wily ** Attachment added: "Screenshot from 2015-10-29 18-27-00.png" https://bugs.launchpad.net/bugs/1511490/+attachment/4508669/+files/Screenshot%20from%202015-10-29%2018-27-00.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1511490 Title: Display corrupts after a while To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cinnamon/+bug/1511490/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1506845] Re: Suspected Race Condition on boot
No, because Citrix Netscaler Gateway is not installed on my box now (Wily). Under Vivid, where I did have a race condition, and had it installed successfully, it happened even before I installed it. Even on Fedora, which Netscaler doesn't work, it had a race condition. So, my correlation is that CNG doesn't have an impact on the race condition, BUT Wily is causing it to be uninstallable due to renaming of some of the packages it depends on (e.g. libproxy1 -> libproxy1v5). Since this ticket is regarding the race condition and we have rectified that by using the daily live cd to install Wily, I would consider it fixed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1506845 Title: Suspected Race Condition on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1506845/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1506845] Re: Suspected Race Condition on boot
Regarding the software issues, yes. Certain programs, such Citrix netscaler gateway, which is used by my corporate workplace for VPN depends on libproxy1, but the version available as of 15.10 is libproxy1v5, and if I force install libproxy1, it forces other software to be removed through dependency on libproxy1v5. But, that is a separate issue, and Citrix should address that dependency problem, and it is not a fault of Ubuntu. So for now, I'm running a VirtualBox version of Ubuntu 14 which have this problem, as it uses libproxy1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1506845 Title: Suspected Race Condition on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1506845/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1506845] Re: Suspected Race Condition on boot
I'll have to image my laptop before I try that. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1506845 Title: Suspected Race Condition on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1506845/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1506845] Re: Suspected Race Condition on boot
Upgrade. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1506845 Title: Suspected Race Condition on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1506845/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1506845] Re: Suspected Race Condition on boot
Okay, the good news is that Wily has worked and it boots pretty reliably -- only had a few occasions where I had to hard reboot. Problem though, and I'm guess its because of the current status of Wily is that a lot of the packages I am trying to use are now broken and refuse to either install or work because of broken dependencies. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1506845 Title: Suspected Race Condition on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1506845/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1506845] Re: Suspected Race Condition on boot
Only slightly. I would be able to login, but would have to install any new packages all over again. Nonetheless, I shall give the live cd a go. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1506845 Title: Suspected Race Condition on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1506845/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1506845] Re: Suspected Race Condition on boot
It seems like a recent update has changed something and now it don't get to the graphical login. I login by using recovery mode then resuming the boot (which bypasses drivers I believe) and this lets me get into Cinnamon, although with software rendering. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1506845 Title: Suspected Race Condition on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1506845/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1506845] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1506845/+attachment/4497890/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1506845 Title: Suspected Race Condition on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1506845/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1506845] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1506845/+attachment/4497887/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1506845 Title: Suspected Race Condition on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1506845/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1506845] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1506845/+attachment/4497881/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1506845 Title: Suspected Race Condition on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1506845/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1506845] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1506845/+attachment/4497892/+files/RfKill.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1506845 Title: Suspected Race Condition on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1506845/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1506845] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1506845/+attachment/4497884/+files/JournalErrors.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1506845 Title: Suspected Race Condition on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1506845/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1506845] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1506845/+attachment/4497893/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1506845 Title: Suspected Race Condition on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1506845/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1506845] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1506845/+attachment/4497894/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1506845 Title: Suspected Race Condition on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1506845/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1506845] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1506845/+attachment/4497885/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1506845 Title: Suspected Race Condition on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1506845/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1506845] Re: Suspected Race Condition on boot
apport information ** Tags added: apport-collected vivid ** Description changed: Ubuntu Vivid using stock install, no additional configs, on a dual boot (Ubuntu + Win7) When booting, my laptop will sometimes boot successfully, sometimes not, and sometimes, will reboot. Using CTRL+ALT+F1 to get to terminal shows me a console flood for Nouveau (sometimes) and sometimes not. Sometimes I see messages about firmware not being used/installed. I cannot reliably replicate this problem, but I have had similar problems running Fedora on this machine with similar console floods, which points further up to the upstream kernel. I suspect it is a race condition, as if I can see the console flood, the laptop often boots successfully, but if I don't I either get a kernel panic or a self-reboot. - Can provide more information/HW details if needed (but not at the - machine right now) + Can provide more information/HW details if needed (but not at the machine right now) + --- + ApportVersion: 2.17.2-0ubuntu1.5 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/pcmC1D0p: johnny 1685 F...m pulseaudio + /dev/snd/controlC1: johnny 1685 F pulseaudio + CurrentDesktop: X-Cinnamon + DistroRelease: Ubuntu 15.04 + HibernationDevice: RESUME=UUID=05d5c6ab-b18c-44c9-ba05-7eff0f8d62b5 + InstallationDate: Installed on 2015-10-12 (5 days ago) + InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) + MachineType: Notebook W35xSS_370SS + Package: linux (not installed) + ProcFB: + + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-30-generic root=UUID=f8a017f7-c589-4cbb-a001-08c7e3c2a815 ro recovery nomodeset priority=low + ProcVersionSignature: Ubuntu 3.19.0-30.34-generic 3.19.8-ckt6 + RelatedPackageVersions: + linux-restricted-modules-3.19.0-30-generic N/A + linux-backports-modules-3.19.0-30-generic N/A + linux-firmware 1.143.3 + Tags: vivid + UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' + Uname: Linux 3.19.0-30-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 04/08/2014 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: 4.6.5 + dmi.board.asset.tag: Tag 12345 + dmi.board.name: W35xSS_370SS + dmi.board.vendor: Notebook + dmi.board.version: Not Applicable + dmi.chassis.asset.tag: No Asset Tag + dmi.chassis.type: 9 + dmi.chassis.vendor: Notebook + dmi.chassis.version: N/A + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/08/2014:svnNotebook:pnW35xSS_370SS:pvrNotApplicable:rvnNotebook:rnW35xSS_370SS:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: + dmi.product.name: W35xSS_370SS + dmi.product.version: Not Applicable + dmi.sys.vendor: Notebook ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1506845/+attachment/4497880/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1506845 Title: Suspected Race Condition on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1506845/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1506845] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1506845/+attachment/4497889/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1506845 Title: Suspected Race Condition on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1506845/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1506845] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1506845/+attachment/4497891/+files/PulseList.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1506845 Title: Suspected Race Condition on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1506845/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1506845] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1506845/+attachment/4497886/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1506845 Title: Suspected Race Condition on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1506845/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1506845] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1506845/+attachment/4497882/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1506845 Title: Suspected Race Condition on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1506845/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1506845] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1506845/+attachment/4497883/+files/IwConfig.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1506845 Title: Suspected Race Condition on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1506845/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1506845] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1506845/+attachment/4497888/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1506845 Title: Suspected Race Condition on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1506845/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1506845] Re: Suspected Race Condition on boot
** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1506845 Title: Suspected Race Condition on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1506845/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1506845] [NEW] Suspected Race Condition on boot
Public bug reported: Ubuntu Vivid using stock install, no additional configs, on a dual boot (Ubuntu + Win7) When booting, my laptop will sometimes boot successfully, sometimes not, and sometimes, will reboot. Using CTRL+ALT+F1 to get to terminal shows me a console flood for Nouveau (sometimes) and sometimes not. Sometimes I see messages about firmware not being used/installed. I cannot reliably replicate this problem, but I have had similar problems running Fedora on this machine with similar console floods, which points further up to the upstream kernel. I suspect it is a race condition, as if I can see the console flood, the laptop often boots successfully, but if I don't I either get a kernel panic or a self-reboot. Can provide more information/HW details if needed (but not at the machine right now) ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1506845 Title: Suspected Race Condition on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1506845/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1309917] [NEW] Unable to switch login at xscreensaver lock screen
Public bug reported: When xscreensaver locks the session and a user attempts to start a new session via the "New Login" button, the message "Could not execute 'gdmflexiserver'" is displayed. This has only started to occur since upgrade from Saucy to Trusty and has occurred on two machines. The one on which I'm reporting this error on (a laptop running Ubuntu Studio upgraded from Saucy to Trusty) and a second (a desktop running Lubuntu, also upgraded from Saucy to Trusty) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xscreensaver 5.15-3ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-lowlatency 3.13.9 Uname: Linux 3.13.0-24-lowlatency i686 ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 CurrentDesktop: XFCE Date: Sat Apr 19 11:39:29 2014 InstallationDate: Installed on 2014-02-15 (62 days ago) InstallationMedia: Ubuntu-Studio 13.10 "Saucy Salamander" - Release i386 (20131016.1) SourcePackage: xscreensaver UpgradeStatus: Upgraded to trusty on 2014-04-18 (0 days ago) ** Affects: xscreensaver (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1309917 Title: Unable to switch login at xscreensaver lock screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xscreensaver/+bug/1309917/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1092792] Re: "Unexpected output" when cleaning LVM swap partition
I copied that file over the existing one and ran bleachbit. It now berhaves correctly, with no errors when wiping the swap. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1092792 Title: "Unexpected output" when cleaning LVM swap partition To manage notifications about this bug go to: https://bugs.launchpad.net/bleachbit/+bug/1092792/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1092792] Re: "Unexpected output" when cleaning LVM swap partition
Sure: $ sudo blkid /dev/mapper/lubuntu-swap_1 /dev/mapper/lubuntu-swap_1: UUID="015c1a05-8877-45c1-bad5-520c25b9306c" TYPE="swap" $ sudo size /dev/mapper/lubuntu-swap_1 size: Warning: '/dev/mapper/lubuntu-swap_1' is not an ordinary file $ sudo fdisk -s /dev/mapper/lubuntu-swap_1 6283264 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1092792 Title: "Unexpected output" when cleaning LVM swap partition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bleachbit/+bug/1092792/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1092792] Re: "Unexpected output" when cleaning LVM swap partition
LVM can be a real bum to manage, I agree. And yes, dm-1 is the same as lubuntu_swap_1: $ ls -l /dev/mapper total 0 crw--- 1 root root 10, 236 Dec 22 10:59 control lrwxrwxrwx 1 root root 7 Dec 22 10:59 lubuntu-root -> ../dm-0 lrwxrwxrwx 1 root root 7 Dec 22 10:59 lubuntu-swap_1 -> ../dm-1 $ ls -l /dev/dm* brw-rw 1 root disk 252, 0 Dec 22 10:59 /dev/dm-0 brw-rw 1 root disk 252, 1 Dec 22 10:59 /dev/dm-1 $ swapon -s FilenameTypeSizeUsedPriority /dev/mapper/lubuntu-swap_1 partition 6283260 200732 -1 So I guess you could use the output from swapon to determine the size (third column) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1092792 Title: "Unexpected output" when cleaning LVM swap partition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bleachbit/+bug/1092792/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1092792] Re: "Unexpected output" when cleaning LVM swap partition
I have applied that fix, and whilst I no longer get the same error, it still does not complete successfully: >> debug: disabling swap debug: running cmd ['swapoff', '-a', '-v'] debug: detected swap devices: ['/dev/mapper/lubuntu-swap_1'] info: wiping swap device '/dev/mapper/lubuntu-swap_1' Traceback (most recent call last): File "/usr/share/bleachbit/bleachbit/Worker.py", line 88, in execute for ret in cmd.execute(self.really_delete): File "/usr/share/bleachbit/bleachbit/Command.py", line 131, in execute for func_ret in self.func(): File "/usr/share/bleachbit/bleachbit/Memory.py", line 250, in wipe_memory wipe_swap_linux(devices, proc_swaps) File "/usr/share/bleachbit/bleachbit/Memory.py", line 227, in wipe_swap_linux if get_swap_size_linux(device, proc_swaps) > 8*1024**3: File "/usr/share/bleachbit/bleachbit/Memory.py", line 140, in get_swap_size_linux (device, proc_swaps)) RuntimeError: error: cannot find size of swap device '/dev/mapper/lubuntu-swap_1' FilenameTypeSizeUsedPriority /dev/dm-1 partition 6283260 19292 -1 error: cannot find size of swap device '/dev/mapper/lubuntu-swap_1' FilenameTypeSizeUsedPriority /dev/dm-1 partition 6283260 19292 -1 Disk space recovered: 16.4kB Files deleted: 4 Special operations: 14 Errors: 2 << -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1092792 Title: "Unexpected output" when cleaning LVM swap partition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bleachbit/+bug/1092792/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1092792] [NEW] "Unexpected output" when cleaning LVM swap partition
Public bug reported:
Console output:
>>
debug: disabling swap
debug: running cmd ['swapoff', '-a', '-v']
Traceback (most recent call last):
File "/usr/share/bleachbit/bleachbit/Worker.py", line 88, in execute
for ret in cmd.execute(self.really_delete):
File "/usr/share/bleachbit/bleachbit/Command.py", line 131, in execute
for func_ret in self.func():
File "/usr/share/bleachbit/bleachbit/Memory.py", line 246, in wipe_memory
devices = disable_swap_linux()
File "/usr/share/bleachbit/bleachbit/Memory.py", line 70, in
disable_swap_linux
% { 'args' : str(args), 'stdout' : stdout, 'stderr' : stderr } )
RuntimeError: Unexpected output:
args='['swapoff', '-a', '-v']'
stdout='swapoff on /dev/mapper/lubuntu-swap_1
'
stderr=''
Unexpected output:
args='['swapoff', '-a', '-v']'
stdout='swapoff on /dev/mapper/lubuntu-swap_1
'
stderr=''
<<
This only occurs when attempting to clean the swap on a system where LVM
is used. A consequence of this problem is that the swap area is left
off, and must be enabled again, manually.
This problem does not occur when running the same operation under a
system where LVM is not used.
Checked on various systems running Natty, Oneiric, Precise, Quantal and
Ringtail
ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: bleachbit 0.9.3-1
ProcVersionSignature: Ubuntu 3.7.0-7.15-generic 3.7.0
Uname: Linux 3.7.0-7-generic i686
ApportVersion: 2.7-0ubuntu2
Architecture: i386
Date: Fri Dec 21 05:18:05 2012
InstallationDate: Installed on 2012-12-14 (6 days ago)
InstallationMedia: Lubuntu 13.04 "Raring Ringtail" - Alpha i386 (20121214)
MarkForUpload: True
PackageArchitecture: all
SourcePackage: bleachbit
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: bleachbit (Ubuntu)
Importance: Undecided
Status: New
** Tags: apport-bug i386 raring
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1092792
Title:
"Unexpected output" when cleaning LVM swap partition
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bleachbit/+bug/1092792/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
