evince-thumbnailer crashed with SIGSEGV in tcache_get()

[nabin]

On ubuntu 18.04 bionic. Just logged in and this error comes out of nowhere.

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: evince 3.28.0-1
Uname: Linux 4.15.12-041512-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
Date: Fri Mar 23 22:55:53 2018
ExecutablePath: /usr/bin/evince-thumbnailer
ProcAttrCurrent: /usr/bin/evince-thumbnailer (enforce)
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.12-041512-generic root=UUID=2f562704-a71b-4cb3-b9ca-86a2ff427b5e ro quiet splash vt.handoff=1
SegvAnalysis:
 Segfault happened at: 0x7fbec65d6207 <__GI___libc_malloc+407>: mov (%rdx),%rdi
 PC (0x7fbec65d6207) ok
 source "(%rdx)" (0x666e6f63746e6f66) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: evince
StacktraceTop:
 tcache_get (tc_idx=1) at malloc.c:2943
 __GI___libc_malloc (bytes=32) at malloc.c:3050
 () at /lib/x86_64-linux-gnu/libexpat.so.1
 () at /lib/x86_64-linux-gnu/libexpat.so.1
 () at /lib/x86_64-linux-gnu/libexpat.so.1
Title: evince-thumbnailer crashed with SIGSEGV in tcache_get()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[tomatomat (mkatzer)]

Just found out that it was caused by files from an old version of font-manager in my home directory (namely .fonts.conf as well as folders under .local, .config and .cache)
Removing .fonts.conf resolved the problem for me.

Running evince inside 'valgrind' did work even with the font-manager configuration files in place. It produced a few "Conditional jump or move depends on uninitialised value(s)" messages, but I still get those after cleaning out the font manager config files.

Regards,
  Mathias

[Sebastien Bacher (seb128)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. Closing since one since it sounds like it was a font configuration issue and not one with the pdf viewer