gnome-control-center.real crashed with SIGSEGV in __GI___pthread_mutex_lock()

Bug #1289926 reported by Boris Đurkan
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-control-center (Ubuntu)
New
Medium
Unassigned

Bug Description

I don't know any details.

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: gnome-control-center 1:3.6.3-0ubuntu53
ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5
Uname: Linux 3.13.0-16-generic x86_64
ApportVersion: 2.13.3-0ubuntu1
Architecture: amd64
CurrentDesktop: GNOME
Date: Sun Mar 9 03:21:55 2014
ExecutablePath: /usr/bin/gnome-control-center.real
InstallationDate: Installed on 2014-03-08 (0 days ago)
InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140226)
ProcCmdline: /usr/bin/gnome-control-center.real network
SegvAnalysis:
 Segfault happened at: 0x7f812b6bd414 <__GI___pthread_mutex_lock+4>: mov 0x10(%rdi),%esi
 PC (0x7f812b6bd414) 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: gnome-control-center
StacktraceTop:
 __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=0x7f8102371700) at pthread_create.c:312
Title: gnome-control-center.real crashed with SIGSEGV in __GI___pthread_mutex_lock()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxsf
usr_lib_gnome-control-center: deja-dup 29.5-0ubuntu2

Revision history for this message
Boris Đurkan (boris-djurkan) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 __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=0x1111160, pvUser=<optimized out>) at /build/buildd/virtualbox-4.3.6-dfsg/src/VBox/Additions/common/crOpenGL/load.c:898
 rtThreadMain (pThread=0x1111160, NativeThread=<optimized out>, pszThreadName=<optimized out>) at /build/buildd/virtualbox-4.3.6-dfsg/src/VBox/Runtime/common/misc/thread.cpp:712

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in gnome-control-center (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Boris Đurkan (boris-djurkan) wrote :

Bug was happened on VirtualBox whit check "Enable 3D Acceleration".

Changed in gnome-control-center (Ubuntu):
status: New → Opinion
status: Opinion → New
information type: Private → Public
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.