totem crashed with SIGSEGV

[mikewhatever]

Just opening Totem causes it to segfault:
$ totem
Segmentation fault (core dumped)

The machine in question is an old desktop with Pentium 4 and Radeon 9200 SE AGP graphics card, Radeon driver. The OS is Ubuntu 16.04 with gnome-flashback (metacity).

~$ lscpu
Architecture: i686
CPU op-mode(s): 32-bit
Byte Order: Little Endian
CPU(s): 2
On-line CPU(s) list: 0,1
Thread(s) per core: 2
Core(s) per socket: 1
Socket(s): 1
Vendor ID: GenuineIntel
CPU family: 15
Model: 4
Model name: Intel(R) Pentium(R) 4 CPU 3.00GHz
Stepping: 1
CPU MHz: 3060.436
BogoMIPS: 6120.87
L1d cache: 16K
L2 cache: 1024K
Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx constant_tsc pebs bts pni dtes64 monitor ds_cpl cid xtpr

Full hardware specs are at http://paste.ubuntu.com/15360138/.

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: totem 3.18.1-1ubuntu4
ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4
Uname: Linux 4.4.0-12-generic i686
ApportVersion: 2.20-0ubuntu3
Architecture: i386
CrashCounter: 1
CurrentDesktop: GNOME-Flashback:Unity
Date: Sat Mar 12 17:45:41 2016
Disassembly: => 0x1: Cannot access memory at address 0x1
ExecutablePath: /usr/bin/totem
InstallationDate: Installed on 2016-02-14 (26 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha i386 (20160212)
ProcCmdline: totem
SegvAnalysis:
 Segfault happened at: 0x1: Cannot access memory at address 0x1
 PC (0x00000001) not located in a known VMA region (needed executable region)!
SegvReason: executing NULL VMA
Signal: 11
SourcePackage: totem
StacktraceTop:
 ?? ()
 ?? () from /usr/lib/i386-linux-gnu/libcogl.so.20
 ?? () from /usr/lib/i386-linux-gnu/libcogl.so.20
 ?? () from /usr/lib/i386-linux-gnu/libcogl.so.20
 ?? () from /usr/lib/i386-linux-gnu/libcogl.so.20
Title: totem crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Launchpad Janitor (janitor)]

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