gnome-flashback crashed with SIGSEGV in output_key_equal()

[LukeKendall]

I didn't even notice it happening. I'm just completing the bug report in case the information collected is helpful.

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: gnome-flashback 3.18.2-1ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-13.29-generic 4.4.5
Uname: Linux 4.4.0-13-generic x86_64
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
CurrentDesktop: GNOME-Flashback:Unity
Date: Thu Mar 17 15:41:50 2016
ExecutablePath: /usr/bin/gnome-flashback
InstallationDate: Installed on 2014-01-24 (783 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140123)
ProcCmdline: gnome-flashback
SegvAnalysis:
 Segfault happened at: 0x4227cd: mov (%rdi),%rdi
 PC (0x004227cd) ok
 source "(%rdi)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-flashback
StacktraceTop:
 ?? ()
 ?? ()
 g_hash_table_lookup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? ()
 ?? ()
Title: gnome-flashback crashed with SIGSEGV in g_hash_table_lookup()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip disk fax floppy fuse lpadmin mail netdev plugdev sambashare scanner sudo tape video

[Apport retracing service (apport)]

StacktraceTop:
 output_key_equal ()
 config_equal ()
 g_hash_table_lookup () from /tmp/apport_sandbox_bNvm6M/lib/x86_64-linux-gnu/libglib-2.0.so.0
 flashback_monitor_config_apply_stored ()
 flashback_monitor_manager_on_hotplug ()

[Launchpad Janitor (janitor)]

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

[Alberts Muktupāvels (muktupavels)]

Do you have steps and / or some extra info that could help me reproduce this crash?

[LukeKendall (luke-zeta)]

I'm sorry, no, I don't. It hasn't happened since, and it took me a while to notice it had happened.

[Dmitry Shachnev (mitya57)]

This is an old bug, and no steps to reproduce, so assuming it is fixed in a new release. Feel free to reopen if this still happens on ≥ 18.04.