Hi @choongin, It'd be great if you could come up with a sequence of crafted RFCOMM packets or sequence of DBus messages to send to the daemon that puts it into this failure state, so we could put together a reproducer in front of upstream (and maybe even propose a solution when having that). A quick inspection of all places in the pulseaudio codebase where the function pa_bluetooth_transport_set_state() is called doesn't raise any specific spot where the transport could be NULL and not caught before calling that function. This seems a really tricky bug. Looking forward to hear from your analysis.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2121311 Title: pulseaudio aborts in pa_bluetooth_transport_set_state() (Bluetooth/BlueZ integration) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2121311/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
