[Touch-packages] [Bug 1835297] Re: Precision 7730 smart card reader does not work out of box

2019-07-18 Thread Jill Manfield
The link is not working.  Skip that.  I have the following commands in case it 
helps:
  *-usb
   description: Mass storage device
   product: DataTraveler 3.0
   vendor: Kingston
   physical id: 1
   bus info: usb@2:1
   logical name: scsi0
   version: 0.01
   serial: 0026186871D2F02178471906
   capabilities: usb-3.00 scsi emulated scsi-host
   configuration: driver=usb-storage maxpower=296mA speed=5000Mbit/s
 *-disk
  description: SCSI Disk
  product: DataTraveler 3.0
  vendor: Kingston
  physical id: 0.0.0
  bus info: scsi@0:0.0.0
  logical name: /dev/sda
  serial: 0
  size: 7377MiB (7736MB)
  capabilities: removable
  configuration: ansiversion=6 logicalsectorsize=512 sectorsize=512
*-medium
 physical id: 0
 logical name: /dev/sda
 size: 7377MiB (7736MB)
 capabilities: partitioned partitioned:dos
 configuration: signature=06593661
  *-storage
   description: Non-Volatile memory controller
   product: Toshiba America Info Systems
   vendor: Toshiba America Info Systems
   physical id: 0
   bus info: pci@:02:00.0
   version: 00
   width: 64 bits
   clock: 33MHz
   capabilities: storage pciexpress pm msi msix nvm_express bus_master 
cap_list
   configuration: driver=nvme latency=0
   resources: irq:16 memory:b050-b0503fff

Bus 002 Device 002: ID 0951:1666 Kingston Technology DataTraveler G4
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 8087:0025 Intel Corp. 
Bus 001 Device 003: ID 1bcf:2b96 Sunplus Innovation Technology Inc. 
Bus 001 Device 002: ID 0a5c:5832 Broadcom Corp. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

00:00.0 Host bridge: Intel Corporation Device 3ec4 (rev 07)
00:01.0 PCI bridge: Intel Corporation Skylake PCIe Controller (x16) (rev 07)
00:02.0 VGA compatible controller: Intel Corporation Device 3e94
00:04.0 Signal processing controller: Intel Corporation Skylake Processor 
Thermal Subsystem (rev 07)
00:08.0 System peripheral: Intel Corporation Skylake Gaussian Mixture Model
00:12.0 Signal processing controller: Intel Corporation Device a379 (rev 10)
00:14.0 USB controller: Intel Corporation Device a36d (rev 10)
00:14.2 RAM memory: Intel Corporation Device a36f (rev 10)
00:15.0 Serial bus controller [0c80]: Intel Corporation Device a368 (rev 10)
00:15.1 Serial bus controller [0c80]: Intel Corporation Device a369 (rev 10)
00:16.0 Communication controller: Intel Corporation Device a360 (rev 10)
00:1b.0 PCI bridge: Intel Corporation Device a32c (rev f0)
00:1c.0 PCI bridge: Intel Corporation Device a338 (rev f0)
00:1c.5 PCI bridge: Intel Corporation Device a33d (rev f0)
00:1c.6 PCI bridge: Intel Corporation Device a33e (rev f0)
00:1f.0 ISA bridge: Intel Corporation Device a30e (rev 10)
00:1f.3 Audio device: Intel Corporation Device a348 (rev 10)
00:1f.4 SMBus: Intel Corporation Device a323 (rev 10)
00:1f.5 Serial bus controller [0c80]: Intel Corporation Device a324 (rev 10)
00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (7) I219-LM 
(rev 10)
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Ellesmere [Polaris10]
01:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon 
RX 580]
02:00.0 Non-Volatile memory controller: Toshiba America Info Systems Device 0116
6e:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device 5260 
(rev 01)
6f:00.0 Network controller: Intel Corporation Device 2526 (rev 29)


Bus 002 Device 002: ID 0951:1666 Kingston Technology DataTraveler G4
Device Descriptor:
  bLength18
  bDescriptorType 1
  bcdUSB   3.00
  bDeviceClass0 (Defined at Interface level)
  bDeviceSubClass 0 
  bDeviceProtocol 0 
  bMaxPacketSize0 9
  idVendor   0x0951 Kingston Technology
  idProduct  0x1666 DataTraveler G4
  bcdDevice0.01
  iManufacturer   1 Kingston
  iProduct2 DataTraveler 3.0
  iSerial 3 0026186871D2F02178471906
  bNumConfigurations  1
  Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength   44
bNumInterfaces  1
bConfigurationValue 1
iConfiguration  0 
bmAttributes 0x80
  (Bus Powered)
MaxPower   74mA
Interface Descriptor:
  bLength 9
  bDescriptorType 4
  bInterfaceNumber0
  bAlternateSetting   0
  bNumEndpoints   2
  bInterfaceClass 8 Mass Storage
  bInterfaceSubClass  6 SCSI
  bInterfaceProtocol 80 Bulk-Only
  iInterface  0 
  Endpoint Descriptor:
bLength 7
bDescriptorType 5

[Touch-packages] [Bug 1835297] Re: Precision 7730 smart card reader does not work out of box

2019-07-18 Thread Jill Manfield
Following https://help.ubuntu.com/community/CommonAccessCard
Does not work to get the smartcard reader working.
pcsc_scan returns
'Waiting for first reader'

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu.
https://bugs.launchpad.net/bugs/1835297

Title:
  Precision 7730 smart card reader does not work out of box

Status in pcsc-lite package in Ubuntu:
  New

Bug description:
  The Canonical certified smart card reader will not function until the
  following commands are run:

  sudo mkdir /tmp/USH

  cd /tmp/USH

  sudo mkdir debs

  cd debs

  sudo wget https://http.kali.org/pool/main/p/pcsc-lite/libpcsclite-
  dev_1.8.24-1_amd64.deb

  sudo wget https://http.kali.org/pool/main/p/pcsc-
  lite/libpcsclite1_1.8.24-1_amd64.deb

  sudo wget https://http.kali.org/pool/main/p/pcsc-
  lite/pcscd_1.8.24-1_amd64.deb

  sudo wget https://http.kali.org/pool/main/p/pcsc-tools/pcsc-
  tools_1.5.4-1_amd64.deb

  cd ..

  sudo apt-get -f install -y

  sudo apt purge lib-pcsc* pcscd* -y

  sudo apt install ./debs/*.deb --install-recommends -y sudo apt-get
  install libusb-1.0-0-dev sudo wget https://alioth-
  archive.debian.org/releases/pcsclite/ccid/1.4.25/ccid-1.4.25.tar.bz2

  sudo tar xvfj ccid-*.tar.bz2

  cd ccid-1.4.25/

  ./configure

  sudo make

  sudo make install

  sudo cp src/92_pcscd_ccid.rules /etc/udev/rules.d/


  sudo systemctl restart pcscd

  sudo systemctl status pcscd

  sudo pcsc_scan


  Additionally, the following commands, which do the same thing as the
  above in a cleaner way, do NOT resolve the issue in both the OEM and
  public image:

  sudo apt install -y libpcsclite-dev libpcsclite1 pcscd pcsc-tools
  libusb-1.0-0 libusb-1.0-0-dev libccid libacsccid1

  sudo systemctl restart pcscd

  sudo systemctl status pcscd

  sudo pcsc_scan

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1835297/+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 1835297] Re: Precision 7730 smart card reader does not work out of box

2019-07-18 Thread Jill Manfield
The information Nick previously provided was how they got around the
issue using the Kali opensource drivers.  Would you like us to follow
https://pcsclite.alioth.debian.org/ccid.html#support to get you that
information.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu.
https://bugs.launchpad.net/bugs/1835297

Title:
  Precision 7730 smart card reader does not work out of box

Status in pcsc-lite package in Ubuntu:
  New

Bug description:
  The Canonical certified smart card reader will not function until the
  following commands are run:

  sudo mkdir /tmp/USH

  cd /tmp/USH

  sudo mkdir debs

  cd debs

  sudo wget https://http.kali.org/pool/main/p/pcsc-lite/libpcsclite-
  dev_1.8.24-1_amd64.deb

  sudo wget https://http.kali.org/pool/main/p/pcsc-
  lite/libpcsclite1_1.8.24-1_amd64.deb

  sudo wget https://http.kali.org/pool/main/p/pcsc-
  lite/pcscd_1.8.24-1_amd64.deb

  sudo wget https://http.kali.org/pool/main/p/pcsc-tools/pcsc-
  tools_1.5.4-1_amd64.deb

  cd ..

  sudo apt-get -f install -y

  sudo apt purge lib-pcsc* pcscd* -y

  sudo apt install ./debs/*.deb --install-recommends -y sudo apt-get
  install libusb-1.0-0-dev sudo wget https://alioth-
  archive.debian.org/releases/pcsclite/ccid/1.4.25/ccid-1.4.25.tar.bz2

  sudo tar xvfj ccid-*.tar.bz2

  cd ccid-1.4.25/

  ./configure

  sudo make

  sudo make install

  sudo cp src/92_pcscd_ccid.rules /etc/udev/rules.d/


  sudo systemctl restart pcscd

  sudo systemctl status pcscd

  sudo pcsc_scan


  Additionally, the following commands, which do the same thing as the
  above in a cleaner way, do NOT resolve the issue in both the OEM and
  public image:

  sudo apt install -y libpcsclite-dev libpcsclite1 pcscd pcsc-tools
  libusb-1.0-0 libusb-1.0-0-dev libccid libacsccid1

  sudo systemctl restart pcscd

  sudo systemctl status pcscd

  sudo pcsc_scan

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1835297/+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 1835297] Re: Precision 7730 smart card reader does not work out of box

2019-07-18 Thread Jill Manfield
Does this cert indicate only Realtek is certified?

The lsusb output is:
Bus 001 Device 002: ID 0a5c:5832 Broadcom Corp. 
Device Descriptor:
  bLength18
  bDescriptorType 1
  bcdUSB   1.10
  bDeviceClass0 (Defined at Interface level)
  bDeviceSubClass 0 
  bDeviceProtocol 0 
  bMaxPacketSize064
  idVendor   0x0a5c Broadcom Corp.
  idProduct  0x5832 
  bcdDevice1.01
  iManufacturer   1 Broadcom Corp
  iProduct2 5880
  iSerial 3 0123456789ABCD
  bNumConfigurations  1
  Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength  139
bNumInterfaces  2
bConfigurationValue 1
iConfiguration  0 
bmAttributes 0xe0
  Self Powered
  Remote Wakeup
MaxPower  100mA
Interface Descriptor:
  bLength 9
  bDescriptorType 4
  bInterfaceNumber0
  bAlternateSetting   0
  bNumEndpoints   3
  bInterfaceClass   254 Application Specific Interface
  bInterfaceSubClass  0 
  bInterfaceProtocol  0 
  iInterface  4 Broadcom USH
  ** UNRECOGNIZED:  10 25 00 00 00 00 00 00 00 00 00 00 00 00 00 00
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81  EP 1 IN
bmAttributes2
  Transfer TypeBulk
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0040  1x 64 bytes
bInterval   0
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01  EP 1 OUT
bmAttributes2
  Transfer TypeBulk
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0040  1x 64 bytes
bInterval   0
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x85  EP 5 IN
bmAttributes3
  Transfer TypeInterrupt
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0010  1x 16 bytes
bInterval   1
Interface Descriptor:
  bLength 9
  bDescriptorType 4
  bInterfaceNumber1
  bAlternateSetting   0
  bNumEndpoints   3
  bInterfaceClass11 Chip/SmartCard
  bInterfaceSubClass  0 
  bInterfaceProtocol  0 
  iInterface  5 Contacted SmartCard
  ChipCard Interface Descriptor:
bLength54
bDescriptorType33
bcdCCID  1.00
nMaxSlotIndex   0
bVoltageSupport 7  5.0V 3.0V 1.8V 
dwProtocols 3  T=0 T=1
dwDefaultClock   4000
dwMaxiumumClock  4000
bNumClockSupported  0
dwDataRate   9600 bps
dwMaxDataRate  25 bps
bNumDataRatesSupp.  0
dwMaxIFSD 247
dwSyncProtocols   
dwMechanical  
dwFeatures   000102BA
  Auto configuration based on ATR
  Auto voltage selection
  Auto clock change
  Auto baud rate change
  Auto PPS made by CCID
  NAD value other than 0x00 accepted
  TPDU level exchange
dwMaxCCIDMsgLen   271
bClassGetResponse  00
bClassEnvelope 00
wlcdLayout   none
bPINSupport 0 
bMaxCCIDBusySlots   1
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82  EP 2 IN
bmAttributes2
  Transfer TypeBulk
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0040  1x 64 bytes
bInterval   0
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02  EP 2 OUT
bmAttributes2
  Transfer TypeBulk
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0040  1x 64 bytes
bInterval   0
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x86  EP 6 IN
bmAttributes3
  Transfer TypeInterrupt
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0010  1x 16 bytes

[Touch-packages] [Bug 1835297] Re: Precision 7730 smart card reader does not work out of box

2019-07-18 Thread Jill Manfield
To add to this the following URL suggests the support and drivers should be 
bundled:
https://certification.ubuntu.com/hardware/201803-26164/

The Dell OEM image does not house the drivers, nor does the Canonical
image.  Is this expected?  Should there be documentation on how to get
this working without using opensource drivers since it is certified?

What does the certification mean?

Is there anything we need to do at Dell to get canonical and Dell to
work on getting the Kati.org pcscd* drivers bundled?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu.
https://bugs.launchpad.net/bugs/1835297

Title:
  Precision 7730 smart card reader does not work out of box

Status in pcsc-lite package in Ubuntu:
  New

Bug description:
  The Canonical certified smart card reader will not function until the
  following commands are run:

  sudo mkdir /tmp/USH

  cd /tmp/USH

  sudo mkdir debs

  cd debs

  sudo wget https://http.kali.org/pool/main/p/pcsc-lite/libpcsclite-
  dev_1.8.24-1_amd64.deb

  sudo wget https://http.kali.org/pool/main/p/pcsc-
  lite/libpcsclite1_1.8.24-1_amd64.deb

  sudo wget https://http.kali.org/pool/main/p/pcsc-
  lite/pcscd_1.8.24-1_amd64.deb

  sudo wget https://http.kali.org/pool/main/p/pcsc-tools/pcsc-
  tools_1.5.4-1_amd64.deb

  cd ..

  sudo apt-get -f install -y

  sudo apt purge lib-pcsc* pcscd* -y

  sudo apt install ./debs/*.deb --install-recommends -y sudo apt-get
  install libusb-1.0-0-dev sudo wget https://alioth-
  archive.debian.org/releases/pcsclite/ccid/1.4.25/ccid-1.4.25.tar.bz2

  sudo tar xvfj ccid-*.tar.bz2

  cd ccid-1.4.25/

  ./configure

  sudo make

  sudo make install

  sudo cp src/92_pcscd_ccid.rules /etc/udev/rules.d/


  sudo systemctl restart pcscd

  sudo systemctl status pcscd

  sudo pcsc_scan


  Additionally, the following commands, which do the same thing as the
  above in a cleaner way, do NOT resolve the issue in both the OEM and
  public image:

  sudo apt install -y libpcsclite-dev libpcsclite1 pcscd pcsc-tools
  libusb-1.0-0 libusb-1.0-0-dev libccid libacsccid1

  sudo systemctl restart pcscd

  sudo systemctl status pcscd

  sudo pcsc_scan

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1835297/+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 1820323] [NEW] xorg crash

2019-03-15 Thread Jill Manfield
Public bug reported:

This is on Precision 3620, Precision 5820, Precision 7820 - systems with
AMD bundled for OEM fail to properly boot after update/upgrade.  I
believe this is related to this issue:

https://www.amd.com/en/support/kb/faq/amdgpupro-ubuntu-advisory

Since our image contains the amdgpu-pro package we are impacted.
Canonical image is not impacted.

Various systems (Precision 3420, 3620, 5820, and 7820) are having login issues 
with AMD GPUs after running system updates on the OEM Ubuntu image.
After running sudo apt-get update && apt-get upgrade, the system will exhibit 
one of a few different behaviors:
•   Boots to a black screen
•   Loops at login
•   Boots to a screen indicating the system has been forced to low graphics 
mode and hard locks.
I have a systems in the lab that exhibits this issue and I don’t know how to 
get around it.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3.1
ProcVersionSignature: Ubuntu 4.4.0-143.169-generic 4.4.170
Uname: Linux 4.4.0-143-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
BootLog:
 Scanning for Btrfs filesystems
 UBUNTU: clean, 267691/28237824 files, 3796147/112924672 blocks
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
Date: Fri Mar 15 13:22:36 2019
DistUpgraded: Fresh install
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-xenial-amd64-20160624-2
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Subsystem: Dell Device [1028:06c7]
 Advanced Micro Devices, Inc. [AMD/ATI] Lexa XT [Radeon PRO WX 2100] 
[1002:6995] (prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:0b0c]
InstallationDate: Installed on 2019-03-14 (0 days ago)
InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
MachineType: Dell Inc. Precision Tower 3420
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-143-generic 
root=UUID=ced18cfc-68aa-461d-a69d-d482f5880d16 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/07/2018
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.11.2
dmi.board.name: 02K9CR
dmi.board.vendor: Dell Inc.
dmi.board.version: A02
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr2.11.2:bd11/07/2018:svnDellInc.:pnPrecisionTower3420:pvr:rvnDellInc.:rn02K9CR:rvrA02:cvnDellInc.:ct3:cvr:
dmi.product.name: Precision Tower 3420
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.91-2~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Fri Mar 15 13:21:28 2019
xserver.configfile: default
xserver.devices:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.18.4-0ubuntu0.8

** Affects: xorg (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug crash ubuntu xenial

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1820323

Title:
  xorg crash

Status in xorg package in Ubuntu:
  New

Bug description:
  This is on Precision 3620, Precision 5820, Precision 7820 - systems
  with AMD bundled for OEM fail to properly boot after update/upgrade.
  I believe this is related to this issue:

  https://www.amd.com/en/support/kb/faq/amdgpupro-ubuntu-advisory

  Since our image contains the amdgpu-pro package we are impacted.
  Canonical image is not impacted.

  Various systems (Precision 3420, 3620, 5820, and 7820) are having login 
issues with AMD GPUs after running system updates on the OEM Ubuntu image.
  After running sudo apt-get update && apt-get upgrade, the system will exhibit 
one of a few different behaviors:
  • Boots to a black screen
  • Loops at login
  • Boots to a screen indicating the system has been forced to low graphics 
mode and hard locks.
  I have a systems in the lab that exhibits this issue and I don’t know how to 
get around it.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: 

[Touch-packages] [Bug 1814925] Re: Bluetooth mouse stops responding after extended deep sleep

2019-02-13 Thread Jill Manfield
Dell OEM image with updated kernel has the qca\qca6174 fix.  I reloaded
the dell image and have not been able to reproduce this issue with LE BT
mouses.  I will let it run and confirm.  So it looks like the issue is
just with the generic image not dell image.  non-oem.

-- 
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/1814925

Title:
  Bluetooth mouse stops responding after extended deep sleep

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  Tested on Dell XPS 9370, Ubuntu 18.04 Dell OEM iso

  Bluetooth mouse tested with HP X4b BT Last mouse stops responding
  after long extended deep sleep (24-48 hours).

  Bluetooth settings window which  initially reported Bluetooth as
  connected now shows disconnected.  Pushing the button within the
  settings window to reconnect takes me back to off.  Switching back to
  on and off keeps bringing me back to off unless I reboot the device
  and or turn off the mouse via the underneath portion of the BT device.

  Demsg logs shows an extremely large number of "Bluetooth: hci:0 last
  event is not cmd complete (0x0f)"

  Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Package: bluez 5.48-0ubuntu3.1
  XPS 13 9370 bios 1.6.3

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3.1
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Wed Feb  6 10:16:07 2019
  InstallationDate: Installed on 2019-01-03 (33 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. XPS 13 9370
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic 
root=UUID=9a57d978-48d7-4ef3-9f67-5e6b72107fcf ro mem_sleep_default=deep 
initrdefi /acpi_override quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/04/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.3
  dmi.board.name: 0H0VG3
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.3:bd11/04/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0H0VG3:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
    BD Address: 9C:B6:D0:90:A0:16  ACL MTU: 1024:8  SCO MTU: 50:8
    UP RUNNING PSCAN ISCAN
    RX bytes:748157 acl:263 sco:0 events:22281 errors:0
    TX bytes:15577 acl:124 sco:0 commands:1167 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1814925/+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 1814925] Re: Bluetooth mouse stops responding after extended deep sleep

2019-02-07 Thread Jill Manfield
I am told by internal engineering the Qualcom fix below is being tested
for this issue:

https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-
firmware.git/commit/?id=2ddd8f0f33972a96f34722de6165ed88a6231f9d

Can you get me more information about this and when it is being
released?

-- 
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/1814925

Title:
  Bluetooth mouse stops responding after extended deep sleep

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  Tested on Dell XPS 9370, Ubuntu 18.04 Dell OEM iso

  Bluetooth mouse tested with HP X4b BT Last mouse stops responding
  after long extended deep sleep (24-48 hours).

  Bluetooth settings window which  initially reported Bluetooth as
  connected now shows disconnected.  Pushing the button within the
  settings window to reconnect takes me back to off.  Switching back to
  on and off keeps bringing me back to off unless I reboot the device
  and or turn off the mouse via the underneath portion of the BT device.

  Demsg logs shows an extremely large number of "Bluetooth: hci:0 last
  event is not cmd complete (0x0f)"

  Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Package: bluez 5.48-0ubuntu3.1
  XPS 13 9370 bios 1.6.3

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3.1
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Wed Feb  6 10:16:07 2019
  InstallationDate: Installed on 2019-01-03 (33 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. XPS 13 9370
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic 
root=UUID=9a57d978-48d7-4ef3-9f67-5e6b72107fcf ro mem_sleep_default=deep 
initrdefi /acpi_override quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/04/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.3
  dmi.board.name: 0H0VG3
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.3:bd11/04/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0H0VG3:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
    BD Address: 9C:B6:D0:90:A0:16  ACL MTU: 1024:8  SCO MTU: 50:8
    UP RUNNING PSCAN ISCAN
    RX bytes:748157 acl:263 sco:0 events:22281 errors:0
    TX bytes:15577 acl:124 sco:0 commands:1167 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1814925/+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 1814925] Re: Bluetooth mouse stops responding after extended deep sleep

2019-02-06 Thread Jill Manfield
More detailed information on this issue is below:
The customer has Ubuntu OEM through Dell.  The laptop goes into deep sleep over 
night and they can no longer use their BT devices.  You click on bt via GUI and 
try to toggle on and it looks like it is doing something and goes right back to 
off.  

BIOS 1.6.3
XPS 13 9370
Ubuntu 18.04- Kernel 4.15.0-43-generic

Lspci shows 
02:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network 
Adapter (rev 32)
 lsusb
Bus 001 Device 005: ID 0489:e0a2 Foxconn / Hon Hai 
Bluetooth show
Controller 9C:B6:D0:8D:D2:C8 (public)
Name: dell-XPS-13-9370
Alias: dell-XPS-13-9370
Class: 0x001c010c
Powered: yes
Discoverable: yes
Pairable: yes
UUID: Headset AG(1112--1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb)
UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
UUID: OBEX File Transfer(1106--1000-8000-00805f9b34fb)
UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb)
UUID: OBEX Object Push  (1105--1000-8000-00805f9b34fb)
UUID: PnP Information   (1200--1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
UUID: IrMC Sync (1104--1000-8000-00805f9b34fb)
UUID: Audio Source  (110a--1000-8000-00805f9b34fb)
UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
UUID: Vendor specific   (5005--1000-8000-0002ee01)
UUID: Message Notification Se.. (1133--1000-8000-00805f9b34fb)
UUID: Phonebook Access Server   (112f--1000-8000-00805f9b34fb)
UUID: Message Access Server (1132--1000-8000-00805f9b34fb)
UUID: Headset   (1108--1000-8000-00805f9b34fb)
Modalias: usb:v1D6Bp0246d0530
Discovering: yes

   ... 
[HP Bluetooth Mouse X4000b]# list
Controller 9C:B6:D0:8D:D2:C8 dell-XPS-13-9370 [default]
rtlwifi_new$ hciconfig -a
hci0:Type: Primary  Bus: USB
BD Address: 9C:B6:D0:8D:D2:C8  ACL MTU: 1024:8  SCO MTU: 50:8
UP RUNNING PSCAN ISCAN INQUIRY 
RX bytes:1189167 acl:6900 sco:0 events:36422 errors:0
TX bytes:31398 acl:80 sco:0 commands:3310 errors:0
Features: 0xff 0xfe 0x8f 0xfe 0xd8 0x3f 0x5b 0x87
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 
Link policy: RSWITCH HOLD SNIFF 
Link mode: SLAVE ACCEPT 
Name: 'dell-XPS-13-9370'
Class: 0x1c010c
Service Classes: Rendering, Capturing, Object Transfer
Device Class: Computer, Laptop
HCI Version: 4.2 (0x8)  Revision: 0x0
LMP Version: 4.2 (0x8)  Subversion: 0x25a
Manufacturer: Qualcomm (29)


dell@dell-XPS-13-9370:~/rtlwifi_new$ lsusb
Bus 001 Device 005: ID 0489:e0a2 Foxconn / Hon Hai 
 lsusb -v -d 0489:e0a2

Bus 001 Device 005: ID 0489:e0a2 Foxconn / Hon Hai 
Couldn't open device, some information will be missing
Device Descriptor:
  bLength18
  bDescriptorType 1
  bcdUSB   1.10
  bDeviceClass  224 Wireless
  bDeviceSubClass 1 Radio Frequency
  bDeviceProtocol 1 Bluetooth
  bMaxPacketSize064
  idVendor   0x0489 Foxconn / Hon Hai
  idProduct  0xe0a2 
  bcdDevice0.01
  iManufacturer   0 
  iProduct0 
  iSerial 0 
  bNumConfigurations  1
  Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength  177
bNumInterfaces  2
bConfigurationValue 1
iConfiguration  0 
bmAttributes 0xe0
  Self Powered
  Remote Wakeup
MaxPower  100mA
Interface Descriptor:
  bLength 9
  bDescriptorType 4
  bInterfaceNumber0
  bAlternateSetting   0
  bNumEndpoints   3
  bInterfaceClass   224 Wireless
  bInterfaceSubClass  1 Radio Frequency
  bInterfaceProtocol  1 Bluetooth
  iInterface  0 
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81  EP 1 IN
bmAttributes3
  Transfer TypeInterrupt
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0010  1x 16 bytes
bInterval   1
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82  EP 2 IN
bmAttributes2
  Transfer TypeBulk
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0040  1x 64 bytes
bInterval   1
  Endpoint Descriptor:
bLength 7

[Touch-packages] [Bug 1814925] Re: Bluetooth mouse stops responding after extended deep sleep

2019-02-06 Thread Jill Manfield
** Description changed:

  Tested on Dell XPS 9370, Ubuntu 18.04 Dell OEM iso
  
- Bluetotth mouse tested with HP X4b BT Last mouse stops responding
+ Bluetooth mouse tested with HP X4b BT Last mouse stops responding
  after long extended deep sleep (24-48 hours).
  
  Bluetooth settings window which  initially reported Bluetooth as
  connected now shows disconnected.  Pushing the button within the
  settings window to reconnect takes me back to off.  Switching back to on
  and off keeps bringing me back to off unless I reboot the device and or
  turn off the mouse via the underneath portion of the BT device.
  
  Demsg logs shows an extremely large number of "Bluetooth: hci:0 last
  event is not cmd complete (0x0f)"
  
  Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Package: bluez 5.48-0ubuntu3.1
  XPS 13 9370 bios 1.6.3
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3.1
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Wed Feb  6 10:16:07 2019
  InstallationDate: Installed on 2019-01-03 (33 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. XPS 13 9370
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic 
root=UUID=9a57d978-48d7-4ef3-9f67-5e6b72107fcf ro mem_sleep_default=deep 
initrdefi /acpi_override quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/04/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.3
  dmi.board.name: 0H0VG3
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.3:bd11/04/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0H0VG3:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.sys.vendor: Dell Inc.
  hciconfig:
-  hci0:Type: Primary  Bus: USB
-   BD Address: 9C:B6:D0:90:A0:16  ACL MTU: 1024:8  SCO MTU: 50:8
-   UP RUNNING PSCAN ISCAN 
-   RX bytes:748157 acl:263 sco:0 events:22281 errors:0
-   TX bytes:15577 acl:124 sco:0 commands:1167 errors:0
+  hci0:Type: Primary  Bus: USB
+   BD Address: 9C:B6:D0:90:A0:16  ACL MTU: 1024:8  SCO MTU: 50:8
+   UP RUNNING PSCAN ISCAN
+   RX bytes:748157 acl:263 sco:0 events:22281 errors:0
+   TX bytes:15577 acl:124 sco:0 commands:1167 errors:0

-- 
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/1814925

Title:
  Bluetooth mouse stops responding after extended deep sleep

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  Tested on Dell XPS 9370, Ubuntu 18.04 Dell OEM iso

  Bluetooth mouse tested with HP X4b BT Last mouse stops responding
  after long extended deep sleep (24-48 hours).

  Bluetooth settings window which  initially reported Bluetooth as
  connected now shows disconnected.  Pushing the button within the
  settings window to reconnect takes me back to off.  Switching back to
  on and off keeps bringing me back to off unless I reboot the device
  and or turn off the mouse via the underneath portion of the BT device.

  Demsg logs shows an extremely large number of "Bluetooth: hci:0 last
  event is not cmd complete (0x0f)"

  Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Package: bluez 5.48-0ubuntu3.1
  XPS 13 9370 bios 1.6.3

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3.1
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Wed Feb  6 10:16:07 2019
  InstallationDate: Installed on 2019-01-03 (33 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. XPS 13 9370
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic 
root=UUID=9a57d978-48d7-4ef3-9f67-5e6b72107fcf ro mem_sleep_default=deep 
initrdefi /acpi_override quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/04/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.3
  dmi.board.name: 0H0VG3
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 

[Touch-packages] [Bug 1812446] Re: Bluetooth mouse stops responding after 24-48 hours of connectivity

2019-02-06 Thread Jill Manfield
*** This bug is a duplicate of bug 1814925 ***
https://bugs.launchpad.net/bugs/1814925

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

** This bug has been marked a duplicate of bug 1814925
   Bluetooth mouse stops responding after extended deep sleep

-- 
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/1812446

Title:
  Bluetooth mouse stops responding after 24-48 hours of connectivity

Status in bluez package in Ubuntu:
  Incomplete

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)”

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1812446/+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 1813208] Re: Paired bluetooth mice irregularities after resume from suspend

2019-02-06 Thread Jill Manfield
*** This bug is a duplicate of bug 1814925 ***
https://bugs.launchpad.net/bugs/1814925

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

** This bug has been marked a duplicate of bug 1814925
   Bluetooth mouse stops responding after extended deep sleep

-- 
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/1813208

Title:
  Paired bluetooth mice irregularities after resume from suspend

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  System model: Dell XPS 9370
  Killer Wireless 1435
  Ubuntu Dell OEM - 18.04.1 LTS

  If a Bluetooth device is paired while system is in suspend, upon resuming the 
system's Bluetooth functionality will intermittently be lost whereas the 
expectation is the functionality would resume as before.
  Bluetooth functionality can be restored by restarting system, entering BIOS, 
and then exiting BIOS even if nothing is changed.
  Standard reboots without entering BIOS will not restore Bluetooth 
functionality.
  Note: Sometimes Wireless is missing as well, but that can be restored through 
normal reboots without going into BIOS.

  Tested on XPS 9370 with Ubuntu 18.04 Dell OEM clean install.
  Issue was observed to occur with both of the following devices:
  HP x4000b Bluetooth mouse
  Logitech G603 Bluetooth mouse

  Issue does not seem to occur if system is only allowed to suspend for
  a short time, issue only occurred if system was left in suspend
  overnight.

  Issue observed to occur both on battery and AC power, power source did
  not seem to affect the issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1813208/+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 1814925] [NEW] Bluetooth mouse stops responding after extended deep sleep

2019-02-06 Thread Jill Manfield
Public bug reported:

Tested on Dell XPS 9370, Ubuntu 18.04 Dell OEM iso

Bluetooth mouse tested with HP X4b BT Last mouse stops responding
after long extended deep sleep (24-48 hours).

Bluetooth settings window which  initially reported Bluetooth as
connected now shows disconnected.  Pushing the button within the
settings window to reconnect takes me back to off.  Switching back to on
and off keeps bringing me back to off unless I reboot the device and or
turn off the mouse via the underneath portion of the BT device.

Demsg logs shows an extremely large number of "Bluetooth: hci:0 last
event is not cmd complete (0x0f)"

Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Package: bluez 5.48-0ubuntu3.1
XPS 13 9370 bios 1.6.3

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: bluez 5.48-0ubuntu3.1
ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
Uname: Linux 4.15.0-45-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
Date: Wed Feb  6 10:16:07 2019
InstallationDate: Installed on 2019-01-03 (33 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: Dell Inc. XPS 13 9370
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic 
root=UUID=9a57d978-48d7-4ef3-9f67-5e6b72107fcf ro mem_sleep_default=deep 
initrdefi /acpi_override quiet splash vt.handoff=1
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/04/2018
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.6.3
dmi.board.name: 0H0VG3
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.3:bd11/04/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0H0VG3:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 13 9370
dmi.sys.vendor: Dell Inc.
hciconfig:
 hci0:  Type: Primary  Bus: USB
  BD Address: 9C:B6:D0:90:A0:16  ACL MTU: 1024:8  SCO MTU: 50:8
  UP RUNNING PSCAN ISCAN
  RX bytes:748157 acl:263 sco:0 events:22281 errors:0
  TX bytes:15577 acl:124 sco:0 commands:1167 errors:0

** Affects: bluez (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: amd64 apport-bug bionic

-- 
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/1814925

Title:
  Bluetooth mouse stops responding after extended deep sleep

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  Tested on Dell XPS 9370, Ubuntu 18.04 Dell OEM iso

  Bluetooth mouse tested with HP X4b BT Last mouse stops responding
  after long extended deep sleep (24-48 hours).

  Bluetooth settings window which  initially reported Bluetooth as
  connected now shows disconnected.  Pushing the button within the
  settings window to reconnect takes me back to off.  Switching back to
  on and off keeps bringing me back to off unless I reboot the device
  and or turn off the mouse via the underneath portion of the BT device.

  Demsg logs shows an extremely large number of "Bluetooth: hci:0 last
  event is not cmd complete (0x0f)"

  Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Package: bluez 5.48-0ubuntu3.1
  XPS 13 9370 bios 1.6.3

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3.1
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Wed Feb  6 10:16:07 2019
  InstallationDate: Installed on 2019-01-03 (33 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. XPS 13 9370
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic 
root=UUID=9a57d978-48d7-4ef3-9f67-5e6b72107fcf ro mem_sleep_default=deep 
initrdefi /acpi_override quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/04/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.3
  dmi.board.name: 0H0VG3
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.3:bd11/04/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0H0VG3:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
    BD Address: 9C:B6:D0:90:A0:16  ACL MTU: 1024:8  SCO MTU: 50:8
    UP RUNNING PSCAN ISCAN
    RX bytes:748157 acl:263 sco:0 events:22281 errors:0
    TX bytes:15577 acl:124 sco:0 commands:1167 

[Touch-packages] [Bug 1812446] Re: Bluetooth mouse stops responding after 24-48 hours of connectivity

2019-02-06 Thread Jill Manfield
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?

-- 
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/1812446

Title:
  Bluetooth mouse stops responding after 24-48 hours of connectivity

Status in bluez package in Ubuntu:
  Incomplete

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)”

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1812446/+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 1812446] Re: Bluetooth mouse stops responding after 24-48 hours of connectivity

2019-02-06 Thread Jill Manfield
1813208 is a duplicate of this bug.

-- 
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/1812446

Title:
  Bluetooth mouse stops responding after 24-48 hours of connectivity

Status in bluez package in Ubuntu:
  Incomplete

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)”

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1812446/+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 1813208] Re: Paired bluetooth mice irregularities after resume from suspend

2019-02-06 Thread Jill Manfield
I am asking our colleague Juan to respond but yes these are 2 bugs that
are duplicate of each other.  Let Juan know what you need from us to
take this further?

-- 
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/1813208

Title:
  Paired bluetooth mice irregularities after resume from suspend

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  System model: Dell XPS 9370
  Killer Wireless 1435
  Ubuntu Dell OEM - 18.04.1 LTS

  If a Bluetooth device is paired while system is in suspend, upon resuming the 
system's Bluetooth functionality will intermittently be lost whereas the 
expectation is the functionality would resume as before.
  Bluetooth functionality can be restored by restarting system, entering BIOS, 
and then exiting BIOS even if nothing is changed.
  Standard reboots without entering BIOS will not restore Bluetooth 
functionality.
  Note: Sometimes Wireless is missing as well, but that can be restored through 
normal reboots without going into BIOS.

  Tested on XPS 9370 with Ubuntu 18.04 Dell OEM clean install.
  Issue was observed to occur with both of the following devices:
  HP x4000b Bluetooth mouse
  Logitech G603 Bluetooth mouse

  Issue does not seem to occur if system is only allowed to suspend for
  a short time, issue only occurred if system was left in suspend
  overnight.

  Issue observed to occur both on battery and AC power, power source did
  not seem to affect the issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1813208/+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