To clarify: The message router likely resolves to an already dead object, and the access to the associated mutex is undefined behavior as the member has been freed when the respective object died away before. I'm proposing a change to dbus-cpp to robustify handling of such situations. However, downstream projects should make sure that they clean up correctly dynamically created objects.
** Branch linked: lp:~thomas-voss/dbus-cpp/robustify-against-dead- objects-hanging-around ** Changed in: location-service (Ubuntu) Status: Invalid => Confirmed ** Changed in: location-service (Ubuntu) Assignee: (unassigned) => Thomas Voß (thomas-voss) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1382595 Title: [TOPBLOCKER] /usr/lib/arm-linux-gnueabihf/indicator-network/indicator- network-service:indicator-network-service: pthread_mutex_lock.c:80: __pthread_mutex_lock: Assertion `mutex->__data.__owner == 0' failed. To manage notifications about this bug go to: https://bugs.launchpad.net/dbus-cpp/+bug/1382595/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs