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
Description: Ubuntu Trusty Tahr (development branch)
Release: 14.04
unity-control-
Installiert: 14.04.3+
Installations
Versionstabelle:
*** 14.04.3+
500 http://
100 /var/lib/
Tried to start the system settings app which produced this error while starting. Functionality didn't seem to be affected.
ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: unity-control-
ProcVersionSign
Uname: Linux 3.13.0-11-generic x86_64
ApportVersion: 2.13.2-0ubuntu5
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Feb 21 16:32:36 2014
ExecutablePath: /usr/bin/
InstallationDate: Installed on 2014-02-21 (0 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140221)
ProcCmdline: unity-control-
ProcEnviron:
LANGUAGE=de_DE
PATH=(custom, no user)
XDG_RUNTIME_
LANG=de_DE.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7feb02493414 <__GI__
PC (0x7feb02493414) 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=0x7feacf3c
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
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.