[Bug 1362538] Re: bluetoothd crashed with SIGSEGV in server_disconnect()

[Tyson Clugg]

That's odd - the error had been annoying me every boot for months has
now gone, even after "apt-get --purge bluez-dbg; reboot" and then the
same for bluez-dbg.  To be clear, the last time the error appeared was
at boot time before installing both bluez-dbg and libbluetooth3-dbg as
per comment #7.

I tried both warm and cold booting (at *every* reboot I've mentioned in
this and the other comment) to see if it was some weird state the BIOS
was setting on the hardware, but it's not apparent that warm versus cold
booting is making any difference.

It appears to me that rebooting with debug libraries installed has
either allowed the failing branch of code to complete without error, or
caused some alternate branch of code to be executed instead. In either
case, the lack of crashing suggests that bluez has saved it's new state
in some as yet unresolved location - does bluez keep/alter state
anywhere in the code, or am I getting carried away here?

Marcos K: Can you try installing just libbluetooth3-dbg and rebooting?
Submit the stack trace if the error persists, then try installing bluez-
dbg and rebooting again once again submitting the stack trace if it
crashes?

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

Title:
  bluetoothd crashed with SIGSEGV in server_disconnect()

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