kernel-packages team mailing list archive

[Stunts <1539158@xxxxxxxxxxxxxxxxxx>]

Ok, I have generated a verbose bluetooth log.
However, this log contains some personal information,  that I would prefer not to make public (email address, partial wifi credentials, etc). How can I make it avaialable to devs in a more private way?

Here is what I did:
Make "/" rw
Edit /etc/init/bluetooth.conf and add a "-d" after the exec line
Reboot the phone
Turn on bluetooth
Attempt to pair with car's hands free system
Phone is found
Pairing fails
Tried pairing again
Pairing fails
Go to terminal,
cp /var/log/syslog ~/
mount "/" as rw again
Remove the "-d" from /etc/init/bluetooth.conf
Reboot to stop log from growing to much again.

I have stripped the syslog to include only data from after the first reboot (I doubt what was before would be interesting).
Feedback, on how to proceed, please. Is this the correct procedure for getting detailed bluetooth logs?
Tonight I might have the chance to strip personal info from the file I want to upload.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1539158

Title:
  Unable to pair with in-car hands-free system after OTA-9 update

Status in Canonical System Image:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  After OTA-9 I started having trouble with my bluetooth connection to the car hands-free system (no sound, and incoming calls no longer displayed the number), so I have reset both the car and the phone connections (eg. forgot the devices).
  Now I can't even pair the phone with the car's system. 
  The car finds the phone, and then asks me to enter the code "0000" to pair the device, but after a few moments, it just says the connection failed and asks me to try again. Which fails again.

  It was working fine just before the update.

  Any logs I should post to help debug?

  PS - The car is a 2015 Honda Civic Tourer, if that matters.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1539158/+subscriptions