touch-packages team mailing list archive

[b8e5n <1541392@xxxxxxxxxxxxxxxxxx>]

Ok, I managed to get it to crash and not wanting to restart. For now hciconfig does see it:
hci0:	Type: BR/EDR  Bus: USB
	BD Address: 00:26:83:33:58:D5  ACL MTU: 1022:8  SCO MTU: 121:3
	DOWN INIT RUNNING 
	RX bytes:395790 acl:133 sco:0 events:55401 errors:0
	TX bytes:36922154 acl:54927 sco:0 commands:362 errors:9
	Features: 0xff 0xfe 0x0d 0xfe 0x98 0x7f 0x79 0x87
	Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 
	Link policy: RSWITCH HOLD SNIFF 
	Link mode: SLAVE ACCEPT 

I will try to reboot.

Method for crashing:
Disconnected my headset
from the indicator:
stopped the bluetooth
started the bluetooth (many times and it managed to start)
re-stopped the bluetooth
indicator --> device name --> connection --> on (was off)
start bluetooth
does not start anymore.

$ sudo hciconfig hci0 up
Can't init device hci0: Connection timed out (110)

Also, I tried to :
$ sudo service bluetooth force-reload
then I got an apport crash pumping out. Afterwards, a stop start did not pose problem. Neither doing another force-reload.

I will try to reboot and see if it still see it in hciconfig.

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

Title:
  AR3011 Bluetooth not starting after being stoped (but detected)

Status in bluez package in Ubuntu:
  New

Bug description:
  kernel : 4.2.0-27
  onboard bluetooth controller : AR3011
  The Bluetooth was working great. I deactivated the bluetooth via the indicator, and then, impossible to start it. Neither from the settings bluetooth interface, neither via hciconfig. The service was of course started without problems.
  The device was well recognized and started, could find which usb port and everything. However hciconfig could not see it:

  $ hciconfig -a hci0                                                                                                                                                                                                                        
  hci0:   Type: BR/EDR  Bus: USB
          BD Address: 00:00:00:00:00:00  ACL MTU: 0:0  SCO MTU: 0:0
          DOWN 
          RX bytes:0 acl:0 sco:0 events:0 errors:0
          TX bytes:12 acl:0 sco:0 commands:4 errors:0

  Of course I restarted the system, tried purging all bluetooth related packages, tried installing blueman. Nothing would make it start.
  Finally I found this thread of arch linux :
  https://bbs.archlinux.org/viewtopic.php?id=171357

  So basically I shut down the computer, waited a while, started the computer and the bluetooth is functional again.
  I will try reproducing the bug. I tried, but it did not happen again. Maybe it's because I was listening music, lost signal, came back to the pc and closed bluetooth.

  Any thoughts of what is this caused by?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1541392/+subscriptions