[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.
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.
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
- Manuel de la Peña (community): Needs Information
- Marcus Tomlinson (community): Approve
- Alberto Aguirre (community): Approve
- PS Jenkins bot: Approve (continuous-integration)
-
Diff: 86 lines (+24/-4)5 files modifiedCMakeLists.txt (+1/-1)
debian/changelog (+7/-0)
include/core/dbus/impl/object.h (+6/-0)
include/core/dbus/object.h (+2/-0)
src/core/dbus/bus.cpp (+8/-3)
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 |
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. |
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 |
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 |
Looking at the stacktrace, the assertion error happens inside dbus-cpp worker thread that has called core::dbus: :Bus::run( ).
Some quick googling: stackoverflow. com/questions/ 1105745/ pthread- mutex-assertion -error
http://