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()

Bug #1562714 reported by felex
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
unity-system-compositor (Ubuntu)
New
Undecided
Unassigned

Bug Description

I attempted to install unity8-desktop-session-mir through terminal. I did so then logged out. I selected unity8 as the window manager then logged in. It gave me a black session for a while so I pressed the power button which began to shut down. The shutdown process took much longer than usual, about 5 minutes. I powered my computer back on then switched back to the default unity 7 window manager and uninstalled unity8 for now.

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: unity-system-compositor 0.4.2+16.04.20160219.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
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/unity-system-compositor
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/unity-system-compositor --file /run/lightdm-mir-0 --from-dm-fd 12 --to-dm-fd 21 --vt 8
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-compositor
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.38
 ?? ()
 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() ()
 usc::MirInputConfiguration::~MirInputConfiguration() ()
 std::_Sp_counted_ptr_inplace<usc::UnityInputService, std::allocator<usc::UnityInputService>, (__gnu_cxx::_Lock_policy)2>::_M_dispose() ()
Title: 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()
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

Revision history for this message
felex (felex0613) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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.

information type: Private → Public
tags: removed: need-amd64-retrace
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.