bluetooth device disappears after several minutes of use

Bug #1771733 reported by Rob on 2018-05-17

This bug report will be marked for expiration in 28 days if no further activity occurs. (find out why)

6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ubuntu Budgie
Undecided
Unassigned
bluez (Ubuntu)
Undecided
Unassigned

Bug Description

I am using budgie-desktop 10.4 on ubuntu budgie 18.04, fully up-to-date.

When I open bluetooth settings, I am able to see many different bluetooth devices detected by my computer, and I can connect to my bluetooth mouse (Microsoft sculpt comfort mouse). However, after several minutes of use, I find that my mouse has disconnected, and I no longer have a bluetooth icon in the top right status indicator. Then, when I open bluetooth settings, the window reads "No bluetooth found: Plug in a dongle to use bluetooth." My laptop has bluetooth built in. It's an Asus UX305CA.

This is my first bug report so please let me know if I've left out any important details and I will provide them as soon as possible. Thanks for all your hard work with Ubuntu Budgie!
---
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: Budgie:GNOME
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2018-05-15 (3 days ago)
InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
InterestingModules: rfcomm bnep btusb bluetooth
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 8087:0a2a Intel Corp.
 Bus 001 Device 002: ID 064e:9700 Suyin Corp. Asus Integrated Webcam
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. UX305CA
Package: bluez 5.48-0ubuntu3
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=/dev/mapper/ubuntu--budgie--vg-root ro quiet splash vt.handoff=1
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Tags: bionic
Uname: Linux 4.15.0-20-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 06/08/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX305CA.300
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX305CA
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: ATN12345678901234567
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX305CA.300:bd06/08/2016:svnASUSTeKCOMPUTERINC.:pnUX305CA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX305CA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: UX
dmi.product.name: UX305CA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
hciconfig:
 hci0: Type: Primary Bus: USB
  BD Address: 4C:34:88:A3:4C:6E ACL MTU: 1021:5 SCO MTU: 96:6
  UP RUNNING PSCAN ISCAN
  RX bytes:1186983 acl:12228 sco:0 events:120531 errors:0
  TX bytes:99607321 acl:116734 sco:0 commands:1078 errors:0

Rob (subalpine) wrote :

Just a little more info to add. The bluetooth device remains unavailable until reboot, and upon reboot, I am able to reproduce the issue every time. Also, this happened when I upgraded from 17.10 to 18.04. I thought perhaps there was a strange issue with the upgrade, so I started from scratch with a fresh install of 18.04. The issue persists.

Check to see if this is a Bluetooth power management issue due to tlp being
a little over zealous.

Purge the tlp package

  sudo apt purge tlp

On Thu, 17 May 2018, 06:30 Rob, <email address hidden> wrote:

> Just a little more info to add. The bluetooth device remains unavailable
> until reboot, and upon reboot, I am able to reproduce the issue every
> time. Also, this happened when I upgraded from 17.10 to 18.04. I thought
> perhaps there was a strange issue with the upgrade, so I started from
> scratch with a fresh install of 18.04. The issue persists.
>
> --
> You received this bug notification because you are subscribed to Ubuntu
> Budgie.
> https://bugs.launchpad.net/bugs/1771733
>
> Title:
> bluetooth device disappears after several minutes of use
>
> Status in Ubuntu Budgie:
> New
>
> Bug description:
> I am using budgie-desktop 10.4 on ubuntu budgie 18.04, fully up-to-
> date.
>
> When I open bluetooth settings, I am able to see many different
> bluetooth devices detected by my computer, and I can connect to my
> bluetooth mouse (Microsoft sculpt comfort mouse). However, after
> several minutes of use, I find that my mouse has disconnected, and I
> no longer have a bluetooth icon in the top right status indicator.
> Then, when I open bluetooth settings, the window reads "No bluetooth
> found: Plug in a dongle to use bluetooth." My laptop has bluetooth
> built in. It's an Asus UX305CA.
>
> This is my first bug report so please let me know if I've left out any
> important details and I will provide them as soon as possible. Thanks
> for all your hard work with Ubuntu Budgie!
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntubudgie/+bug/1771733/+subscriptions
>

Rob (subalpine) wrote :

Ok, so I was incorrect in my previous statement when I said that I could reproduce this problem upon reboot. I was thinking of my experience with the live media since I tried it so many times.

On my permanent installation on the hard drive, after bluetooth stops working, I am not able to turn bluetooth back on even after reboot. Although my computer appears to recognize that there is in fact bluetooth hardware in my PC after reboot (ie. It does not prompt me to plug in a bluetooth dongle), the toggle switch to enable bluetooth does nothing.

So to recap, on a new installation of 18.04, I am able to see and use bluetooth devices for several minutes, but then the bluetooth hardware stops working and after reboot, I am still unable to use bluetooth.

Also, I did purge tlp and it had no effect.

Sorry for the confusion.

fossfreedom (fossfreedom) wrote :

Ok. So not a TLP issue. Subscribing to the bluez package. But may also be kernel related.

Daniel van Vugt (vanvugt) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal:

apport-collect 1771733

When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

Changed in bluez (Ubuntu):
status: New → Incomplete

apport information

tags: added: apport-collected bionic
description: updated

apport information

Rob (subalpine) wrote : Lspci.txt

apport information

apport information

apport information

apport information

apport information

apport information

Rob (subalpine) wrote : UdevDb.txt

apport information

Rob (subalpine) wrote : getfacl.txt

apport information

Rob (subalpine) wrote :

I have executed the command suggested by vanvugt for one week, but to complicate matters further, I have been able to use my mouse for about an hour now... I don't know how to troubleshoot this issue, but I will update if I have any complications from this point forward... I just replaced the batteries in my mouse, but that doesn't explain the loss of *ALL* bluetooth hardware functionality until several reboots later...right? Even with dead mouse batteries, surely my computer should not report that there is no bluetooth hardware available. Please note that bluetooth became available again *without* rebooting, I just hadn't touched anything for several hours.

Changed in bluez (Ubuntu):
status: Incomplete → New
Rob (subalpine) wrote :

Welp. My mouse has been working for a couple days now and has survived multiple reboots, but the problem is that I don't know what I did to get it working again. I just sat down, wiggled the mouse to wake it up out of habit, and it worked. Could be a hardware issue on my end. Close this bug I guess. Sorry for the mix up, I really have no idea what happened.

Changed in bluez (Ubuntu):
status: New → Incomplete
Changed in ubuntubudgie:
status: New → Incomplete
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers