I will try to come up with a distilled down test case illustrating that libdbus-cpp is not the cause but a symptom of the issue. Point being that it certainly shows up in the stack traces, but it sits waiting in all of them (specifically for the system settings crash).
I will try to come up with a distilled down test case illustrating that libdbus-cpp is not the cause but a symptom of the issue. Point being that it certainly shows up in the stack traces, but it sits waiting in all of them (specifically for the system settings crash).