When suddenly a banner advertisement appears,sense and attempts to eradicate the nuisance variety goes into a tail spin.
ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: variety 0.6.0-1
ProcVersionSignature: Ubuntu 4.4.0-7.22-generic 4.4.2
Uname: Linux 4.4.0-7-generic x86_64
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
CurrentDesktop: MATE
Date: Sun Mar 27 14:56:53 2016
ExecutablePath: /usr/bin/variety
InstallationDate: Installed on 2016-03-27 (0 days ago)
InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160224)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/variety
ProcEnviron:
LANGUAGE=en_GB:en
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=en_GB.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7f5b6c210694: mov 0x10(%rax),%r13
PC (0x7f5b6c210694) ok
source "0x10(%rax)" (0x00000010) not located in a known VMA region (needed readable region)!
destination "%r13" ok
Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: variety
StacktraceTop:
?? () from /usr/lib/x86_64-linux-gnu/libexiv2.so.14
?? () from /usr/lib/x86_64-linux-gnu/libexiv2.so.14
?? () from /usr/lib/x86_64-linux-gnu/libexiv2.so.14
Exiv2::XmpParser::initialize(void (*)(void*, bool), void*) () from /usr/lib/x86_64-linux-gnu/libexiv2.so.14
Exiv2::XmpParser::decode(Exiv2::XmpData&, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&) () from /usr/lib/x86_64-linux-gnu/libexiv2.so.14
Title: variety crashed with SIGSEGV in Exiv2::XmpParser::initialize()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip 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 #1554367, 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.