variety crashed with SIGSEGV in std::_Rb_tree<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::pair<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > >, std::_Select1st<std::pair<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > >, std::less<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > >, std::allocator<std::pair<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > > >::_M_get_insert_hint_unique_pos()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
variety (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Sometimes happen
ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: variety 0.6.0-1
ProcVersionSign
Uname: Linux 4.4.0-13-generic x86_64
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
CrashCounter: 1
CurrentDesktop: Unity
Date: Wed Mar 16 06:33:15 2016
ExecutablePath: /usr/bin/variety
InstallationDate: Installed on 2016-03-02 (14 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160212)
InterpreterPath: /usr/bin/python2.7
PackageArchitec
ProcCmdline: /usr/bin/python /usr/bin/variety
ProcEnviron:
LANGUAGE=es_MX:es
PATH=(custom, no user)
XDG_RUNTIME_
LANG=es_MX.UTF-8
SHELL=/bin/bash
Signal: 11
SourcePackage: variety
Title: variety crashed with SIGSEGV in std::_Rb_
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo
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 #1552179, 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.