Hi everyone, A cursory glance of the backtrace logs points to libexiv2 being the issue. Unfortunately, exiv2's maintainer seems overwhelmed or unwilling to harden the library, and thus it has many documented issues handling malformed data. Nevertheless, many programs depend on it either directly or transitively via wrappers - in this case, Variety is using it via GExiv2. https://bugzilla.gnome.org/show_bug.cgi?id=785547 and http://dev.exiv2.org/issues/1248 have more background on the issue.
For us to fix these problems would likely involve either porting to a different EXIF framework (Python-native examples: [1][2]), or dropping our use of EXIF metadata entirely[3]. [1]: https://github.com/ianare/exif-py [2]: https://pypi.python.org/pypi/pexif [3]: https://bugs.launchpad.net/variety/+bug/1593254 ** Bug watch added: GNOME Bug Tracker #785547 https://bugzilla.gnome.org/show_bug.cgi?id=785547 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1552179 Title: Variety segfaults on libexiv/std::_Rb_tree on autostart, but not when started manually To manage notifications about this bug go to: https://bugs.launchpad.net/variety/+bug/1552179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
