touch-packages team mailing list archive
-
touch-packages team
-
Mailing list archive
-
Message #28759
[Bug 1382595] Re: [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 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
Touch seeded packages, which is subscribed to indicator-network 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.
Status in DBus C++:
Confirmed
Status in “dbus-cpp” package in Ubuntu:
Confirmed
Status in “indicator-network” package in Ubuntu:
Invalid
Status in “location-service” package in Ubuntu:
Confirmed
Status in “dbus-cpp” package in Ubuntu RTM:
Confirmed
Bug description:
The Ubuntu Error Tracker has been receiving reports about a problem
regarding indicator-network. This problem was most recently seen with
version 0.5.1+14.10.20141015-0ubuntu1, the problem page at
https://errors.ubuntu.com/problem/ecc14b5d54f3e0a0f1720cad0c623f81c8a16988
contains more details.
steps to reproduce: (need to trigger race condition)
1. pull down network indicator
2. toggle flight mode on and off quickly a few times
3. click sim card 1 and 2
4. toggle flight mode
5. swipe up close indicators
6. repeat steps 1-5 until crash occurs
expected results:
no crash happens
actual results:
Bluetooth indicator blinks (appear and disappear) in indicator bar at top of screen, and network indicator crashes.
additional info:
eventually the bluetooth indicator appears stable in the indicators at the top of the screen.
To manage notifications about this bug go to:
https://bugs.launchpad.net/dbus-cpp/+bug/1382595/+subscriptions
References