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

2017-07-02 Thread Launchpad Bug Tracker
[Expired for bluez (Ubuntu) because there has been no activity for 60 days.] ** Changed in: bluez (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu.

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

2017-05-03 Thread Daniel van Vugt
Thank you for reporting this bug to Ubuntu. Ubuntu 14.10 (utopic) reached end-of-life on July 23, 2015. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases Please upgrade to the latest version and re-test. ** Changed in: bluez (Ubuntu) Status:

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

2014-11-02 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: bluez (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu.

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

2014-11-02 Thread Tyson Clugg
I was looking at the details before letting apport submit the bug and I noticed that the stack trace I was just like the one submitted here having no debug information available. So I ran 'sudo apt-get install bluez-dbg libbluetooth3-dbg', rebooted and the problem went away... it's a hiesenbug.

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

2014-11-02 Thread 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