unity-control-center crashed with SIGSEGV in __GI___pthread_mutex_lock()

Bug #1281590 reported by Pilot6 on 2014-02-18
This bug affects 104 people
Affects Status Importance Assigned to Milestone
virtualbox (Ubuntu)
Nominated for Trusty by Alberto Salvia Novella
Nominated for Utopic by Alberto Salvia Novella

Bug Description

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: unity-control-center 14.04.3-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2
Uname: Linux 3.13.0-8-generic x86_64
ApportVersion: 2.13.2-0ubuntu4
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Feb 18 18:21:43 2014
ExecutablePath: /usr/bin/unity-control-center
InstallationDate: Installed on 2013-12-08 (72 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20131206)
ProcCmdline: unity-control-center
 PATH=(custom, no user)
 Segfault happened at: 0x7fc2f30cc414 <__GI___pthread_mutex_lock+4>: mov 0x10(%rdi),%esi
 PC (0x7fc2f30cc414) ok
 source "0x10(%rdi)" (0x000020d8) not located in a known VMA region (needed readable region)!
 destination "%esi" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: unity-control-center
 __GI___pthread_mutex_lock (mutex=0x0) at ../nptl/pthread_mutex_lock.c:66
 ?? () from /usr/lib/x86_64-linux-gnu/dri/vboxvideo_dri.so
 ?? () from /usr/lib/x86_64-linux-gnu/dri/vboxvideo_dri.so
 ?? () from /usr/lib/x86_64-linux-gnu/dri/vboxvideo_dri.so
 start_thread (arg=0x7fc2c19a5700) at pthread_create.c:312
Title: unity-control-center crashed with SIGSEGV in __GI___pthread_mutex_lock()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
 activity-log-manager 0.9.7-0ubuntu10
 deja-dup 29.5-0ubuntu2
 gnome-control-center 1:3.6.3-0ubuntu50

Pilot6 (hanipouspilot) wrote :

 __GI___pthread_mutex_lock (mutex=0x0) at ../nptl/pthread_mutex_lock.c:66
 crLockMutex (mutex=<optimized out>) at /build/buildd/virtualbox-4.3.6-dfsg/src/VBox/GuestHost/OpenGL/util/threads.c:166
 crHashtableLock (h=<optimized out>) at /build/buildd/virtualbox-4.3.6-dfsg/src/VBox/GuestHost/OpenGL/util/hash.c:434
 stubSyncThreadProc (ThreadSelf=0x1eb4a00, pvUser=<optimized out>) at /build/buildd/virtualbox-4.3.6-dfsg/src/VBox/Additions/common/crOpenGL/load.c:898
 rtThreadMain (pThread=0x1eb4a00, NativeThread=<optimized out>, pszThreadName=<optimized out>) at /build/buildd/virtualbox-4.3.6-dfsg/src/VBox/Runtime/common/misc/thread.cpp:712

Changed in unity-control-center (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in unity-control-center (Ubuntu):
status: New → Confirmed
information type: Private → Public
affects: unity-control-center (Ubuntu) → virtualbox (Ubuntu)
Changed in virtualbox (Ubuntu):
importance: Medium → High
Shwan (shwan-ciyako) wrote :

After an update the system font is huge and I can't change that cause system-setting is crashing.

description: updated
Changed in virtualbox (Ubuntu):
status: Confirmed → Triaged
Changed in virtualbox:
status: Unknown → New
Ubuntu QA Website (ubuntuqa) wrote :

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:

tags: added: iso-testing
Changed in virtualbox:
status: New → Unknown
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

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