https://bugzilla.kernel.org/show_bug.cgi?id=198685 --- Comment #7 from Nathaniel McCallum (npmccallum@xxxxxxxxxx) --- (In reply to Luiz Von Dentz from comment #6) > Can you add the output of bluetoothd with debug enabled? Posting it shortly after this. > Btw, you don't really need to dup the fd at the client end, at least not > with libdbus, or is this something to do with systemd D-Bus library? https://github.com/systemd/systemd/issues/8003 > Another > thing that stand out is the fact that there is no check for gatt->snd.not, > perhaps the idea is to reacquire on every request? That would be overkill > and perhaps you would be better off using StartNotify instead then. Yes, we reacquire on every request. I did this because I wanted to avoid holding state in case the device goes out of range. I'm not sure what the right way to do this is. > Both > bluetoothctl and meshctl acquire the notification once and just keep it as > along as the connection exists, though if the problem is really the fact > that you close and acquire in quick succession we should fix that since > nothing should crash bluetootd. +1 -- You are receiving this mail because: You are the assignee for the bug.-- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
