unity-system-compositor crashed with SIGSEGV in std::_Hashtable<std::shared_ptr<mir::input::Device>, std::shared_ptr<mir::input::Device>, std::allocator<std::shared_ptr<mir::input::Device> >, std::__detail::_Identity, std::equal_to<std::shared_ptr<mir::input::Device> >, std::hash<std::shared_ptr<mir::input::Device> >, std::__detail::_Mod_range_hashing, std::__detail::_Default_ranged_hash, std::__detail::_Prime_rehash_policy, std::__detail::_Hashtable_traits<false, true, true> >::~_Hashtable()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
unity-system-compositor (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
I attempted to install unity8-
ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: unity-system-
ProcVersionSign
Uname: Linux 4.4.0-15-generic x86_64
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
Date: Mon Mar 28 02:39:05 2016
ExecutablePath: /usr/sbin/
GraphicsCard:
Advanced Micro Devices, Inc. [AMD/ATI] RV730/M96 [Mobility Radeon HD 4650/5165] [1002:9480] (prog-if 00 [VGA controller])
Subsystem: Dell RV730/M96 [Mobility Radeon HD 4650/5165] [1028:0447]
InstallationDate: Installed on 2016-03-28 (0 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
ProcCmdline: /usr/sbin/
ProcEnviron:
SegvAnalysis:
Segfault happened at: 0x7f4a1589f291: mov 0x10(%rax),%rax
PC (0x7f4a1589f291) ok
source "0x10(%rax)" (0x7f4a089e6a70) not located in a known VMA region (needed readable region)!
destination "%rax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: unity-system-
StacktraceTop:
?? () from /usr/lib/
?? ()
std::_
usc::MirInputC
std::_
Title: unity-system-
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
version.libdrm: libdrm2 2.4.67-1
version.lightdm: lightdm 1.18.0-0ubuntu1
version.mesa: libegl1-mesa-dev N/A
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 #1560382, 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.