I think I forgot two edge cases in my previous pull request that can both be triggered on a system with multiple bluetooth controllers present.
The first issue is that bt->cur_controller_.has_value() isn’t being checked in onObjectRemoved(), which leads to a failed assertion if a bluetooth controller is removed from the system while no controller was currently displayed by waybar.
The second issue is that the list of connected devices isn’t being updated when switching the displayed controller in onObjectRemoved().
Unfortunately due to a lack of multiple bluetooth controllers I can’t test if the bugs are actually triggerable or if this pull request fixes it. I’m quite confident in both, but I’ll try to get my hands on a usb bluetooth dongle next week in order to test it.
I think I forgot two edge cases in my previous pull request that can both be triggered on a system with multiple bluetooth controllers present.
The first issue is that
bt->cur_controller_.has_value()isn’t being checked inonObjectRemoved(), which leads to a failed assertion if a bluetooth controller is removed from the system while no controller was currently displayed by waybar.The second issue is that the list of connected devices isn’t being updated when switching the displayed controller in
onObjectRemoved().Unfortunately due to a lack of multiple bluetooth controllers I can’t test if the bugs are actually triggerable or if this pull request fixes it. I’m quite confident in both, but I’ll try to get my hands on a usb bluetooth dongle next week in order to test it.