unity-control-center crashed with SIGSEGV in __GI___pthread_mutex_lock()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
unity-control-center (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
I have no details
ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: unity-control-
ProcVersionSign
Uname: Linux 3.13.0-8-generic x86_64
ApportVersion: 2.13.2-0ubuntu4
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Feb 18 22:18:34 2014
ExecutablePath: /usr/bin/
InstallationDate: Installed on 2014-02-18 (0 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140218)
ProcCmdline: unity-control-
SegvAnalysis:
Segfault happened at: 0x7f0baa423414 <__GI__
PC (0x7f0baa423414) 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-
StacktraceTop:
__GI__
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
start_thread (arg=0x7f0b9809
Title: unity-control-
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
usr_lib_
activity-
deja-dup 29.5-0ubuntu2
gnome-
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1281590, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.