[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.

Bug #1382595 reported by errors.ubuntu.com bug bridge
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
dbus-cpp
Fix Released
Undecided
Unassigned
dbus-cpp (Ubuntu)
Fix Released
Critical
Thomas Voß
dbus-cpp (Ubuntu RTM)
Fix Released
Critical
Thomas Voß
indicator-network (Ubuntu)
Invalid
Critical
Unassigned
indicator-network (Ubuntu RTM)
Fix Released
Critical
Unassigned
location-service (Ubuntu)
Invalid
Critical
Unassigned

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.

Related branches

tags: added: qa-daily-testing qa-touch qasoak rtm14
description: updated
Changed in indicator-network (Ubuntu):
assignee: nobody → Antti Kaijanmäki (kaijanmaki)
status: New → Confirmed
importance: Undecided → Critical
Alexander Sack (asac)
summary: - /usr/lib/arm-linux-gnueabihf/indicator-network/indicator-network-
- service:indicator-network-service: pthread_mutex_lock.c:80:
+ [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.
Revision history for this message
Antti Kaijanmäki (kaijanmaki) wrote :

Looking at the stacktrace, the assertion error happens inside dbus-cpp worker thread that has called core::dbus::Bus::run().

Some quick googling:
http://stackoverflow.com/questions/1105745/pthread-mutex-assertion-error

Changed in dbus-cpp:
status: New → Confirmed
Changed in dbus-cpp (Ubuntu):
status: New → Confirmed
Changed in dbus-cpp (Ubuntu RTM):
status: New → Confirmed
Changed in dbus-cpp (Ubuntu):
importance: Undecided → Critical
Changed in dbus-cpp (Ubuntu RTM):
importance: Undecided → Critical
Changed in dbus-cpp (Ubuntu):
assignee: nobody → Thomas Voß (thomas-voss)
Changed in dbus-cpp (Ubuntu RTM):
assignee: nobody → Thomas Voß (thomas-voss)
Changed in indicator-network (Ubuntu):
status: Confirmed → Invalid
Revision history for this message
Manuel de la Peña (mandel) wrote :
Changed in location-service (Ubuntu):
status: New → Confirmed
importance: Undecided → Critical
status: Confirmed → Invalid
Revision history for this message
Thomas Voß (thomas-voss) wrote :

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.

Changed in location-service (Ubuntu):
status: Invalid → Confirmed
assignee: nobody → Thomas Voß (thomas-voss)
Revision history for this message
Antti Kaijanmäki (kaijanmaki) wrote :

i-network needs a rebuild as well.

Changed in indicator-network (Ubuntu):
status: Invalid → Triaged
Revision history for this message
Pat McGowan (pat-mcgowan) wrote :

Added missing date tag

tags: added: touch-2014-10-30
removed: rtm-14.09
Changed in location-service (Ubuntu):
status: Confirmed → In Progress
Changed in dbus-cpp (Ubuntu RTM):
status: Confirmed → In Progress
Changed in indicator-network (Ubuntu):
status: Triaged → In Progress
Changed in indicator-network (Ubuntu):
assignee: Antti Kaijanmäki (kaijanmaki) → Thomas Voß (thomas-voss)
Changed in indicator-network (Ubuntu RTM):
importance: Undecided → Critical
status: New → In Progress
Changed in dbus-cpp:
status: Confirmed → In Progress
Changed in dbus-cpp (Ubuntu):
status: Confirmed → In Progress
Revision history for this message
Olli Ries (ories) wrote :
Revision history for this message
Antti Kaijanmäki (kaijanmaki) wrote :

based in the ofono and urfkill bugs linked to the #1388065 I would say these are not related.

Changed in dbus-cpp:
status: In Progress → Fix Released
Changed in dbus-cpp (Ubuntu RTM):
status: In Progress → Fix Released
Changed in indicator-network (Ubuntu RTM):
status: In Progress → Fix Released
Changed in indicator-network (Ubuntu):
assignee: Thomas Voß (thomas-voss) → nobody
Changed in location-service (Ubuntu):
assignee: Thomas Voß (thomas-voss) → nobody
Changed in indicator-network (Ubuntu):
status: In Progress → Invalid
Changed in location-service (Ubuntu):
status: In Progress → Invalid
Changed in dbus-cpp (Ubuntu):
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.