totem crashed with SIGSEGV in grl_tracker_setup_key_mappings()

[Bill (franksmcb)]

Ubuntu 20.04 daily - updated 27 Jan 2020

Expected result:Launch Totem and application opens

Actual result: Totem segfaults and apport pop-up appears.

ProblemType: Crash
DistroRelease: Ubuntu 20.04
Package: totem 3.34.1-2ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
Uname: Linux 5.4.0-12-generic x86_64
ApportVersion: 2.20.11-0ubuntu15
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Jan 27 22:36:39 2020
ExecutablePath: /usr/bin/totem
InstallationDate: Installed on 2020-01-15 (12 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200106)
ProcCmdline: /usr/bin/totem --gapplication-service
ProcEnviron:
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
 PATH=(custom, no user)
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7fa4ba580dd6: movzbl (%rax),%eax
 PC (0x7fa4ba580dd6) ok
 source "(%rax)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: totem
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/grilo-0.3/libgrltracker.so
 grl_tracker_setup_key_mappings () from /usr/lib/x86_64-linux-gnu/grilo-0.3/libgrltracker.so
 ?? () from /usr/lib/x86_64-linux-gnu/grilo-0.3/libgrltracker.so
 ?? () from /usr/lib/x86_64-linux-gnu/grilo-0.3/libgrltracker.so
 ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0
Title: totem crashed with SIGSEGV in grl_tracker_setup_key_mappings()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'
separator:

[Apport retracing service (apport)]

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 #1856927, 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.