Bluetooth mouse stops responding after 24-48 hours of connectivity

Bug #1812446 reported by Juan Martinez
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
bluez (Ubuntu)
Incomplete
Undecided
Unassigned

Bug Description

Tested on Dell XPS 9370, Ubuntu 18.04 Dell OEM ISO (for this model)

-Bluetooth mouse (Tested with a HP x4000b BT Laser Mouse) stops responding after 1-2 days of being connected whereas the expectation is that the mouse would continue working normally

-Bluetooth settings window will initially report Bluetooth is on when opened.

-Switching away and back to the Bluetooth settings GUI will now show Bluetooth as disabled, and Settings GUI will lock up until system is restarted.
       o Settings window can be force closed and re-opened, but it will still be locked up on the Bluetooth tab

-When moving the mouse or clicking any buttons in this state, the Bluetooth icon in the top right GNOME menu bar will briefly flash the Bluetooth icon but there is no actual mouse activity.

-dmesg log shows an extremely large number of events “Bluetooth: hci0: last event is not cmd complete (0x0f)”

Revision history for this message
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 1812446

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.

tags: added: bionic
affects: gnome-shell (Ubuntu) → ubuntu
Changed in ubuntu:
status: New → Incomplete
affects: ubuntu → bluez (Ubuntu)
Revision history for this message
Steven Meisner (smeisnerd) wrote : apport information

ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2019-01-03 (20 days ago)
InstallationMedia: Ubuntu 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 002: ID 0bda:58f4 Realtek Semiconductor Corp.
 Bus 001 Device 004: ID 0930:6545 Toshiba Corp. Kingston DataTraveler 102/2.0 / HEMA Flash Drive 2 GB / PNY Attache 4GB Stick
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. XPS 13 9370
Package: bluez 5.48-0ubuntu3.1
PackageArchitecture: amd64
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=767c0b00-e72c-44a2-bac1-9527767a7bb4 ro quiet splash vt.handoff=1
ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
Tags: bionic
Uname: Linux 4.15.0-43-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 11/04/2018
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.6.3
dmi.board.name: 0W970W
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvr1.6.3:bd11/04/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0W970W:rvrA01:cvnDellInc.:ct10:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 13 9370
dmi.sys.vendor: Dell Inc.
hciconfig:

rfkill:
 1: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no

tags: added: apport-collected
Revision history for this message
Steven Meisner (smeisnerd) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Steven Meisner (smeisnerd) wrote : Dependencies.txt

apport information

Revision history for this message
Steven Meisner (smeisnerd) wrote : Lspci.txt

apport information

Revision history for this message
Steven Meisner (smeisnerd) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Steven Meisner (smeisnerd) wrote : ProcCpuinfoMinimal.txt

apport information

Revision history for this message
Steven Meisner (smeisnerd) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Steven Meisner (smeisnerd) wrote : ProcModules.txt

apport information

Revision history for this message
Steven Meisner (smeisnerd) wrote : UdevDb.txt

apport information

Revision history for this message
Steven Meisner (smeisnerd) wrote : getfacl.txt

apport information

Revision history for this message
Steven Meisner (smeisnerd) wrote : syslog.txt

apport information

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Steven,

Please click Hide on all the above comments. Only the original reporter (Juan) should run apport-collect here.

Please then report your own bug by running:

  ubuntu-bug bluez

Revision history for this message
Jill Manfield (jlmanfield) wrote :

1813208 is a duplicate of this bug.

Revision history for this message
Jill Manfield (jlmanfield) wrote :

Daniel, my name is Jill and I have the customer's capture so I have to run the apport-collect from the customer's system. Juan is our back line engineer that opened the case with you so we could have Canonical and Dell collaborate. If this is not correct. How can I get you the data?

Revision history for this message
Jill Manfield (jlmanfield) wrote :

running ubuntu-bug bluez; I received a new bug id 1814925. These bugs are all related.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.