mission-control-5 crashed with SIGSEGV in __libc_start_main()

This occurred after initial boot and as the desktop came up. The only unusual thing done was that a USB camera was plugged in prior to the desktop coming up.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: telepathy-mission-control-5 1:5.14.1-1ubuntu6
ProcVersionSignature: Ubuntu 3.10.0-5.15-generic 3.10.2
Uname: Linux 3.10.0-5-generic x86_64
ApportVersion: 2.12.5-0ubuntu1
Architecture: amd64
Date: Wed Oct 9 09:17:59 2013
ExecutablePath: /usr/lib/telepathy/mission-control-5
InstallationDate: Installed on 2013-07-28 (72 days ago)
InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Alpha amd64 (20130728)
MarkForUpload: True
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.10.0-5-generic root=UUID=70e9bab0-2e74-4f67-aad1-fba62c8ee425 ro quiet splash vt.handoff=7
ProcEnviron:
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
 PATH=(custom, no user)
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0x410260: mov 0x18(%rdi),%rdi
 PC (0x00410260) ok
 source "0x18(%rdi)" (0x00000018) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: telepathy-mission-control-5
StacktraceTop:
 ?? ()
 ?? ()
 __libc_start_main (main=0x40e2a0, argc=1, ubp_av=0x7fff1d5196f8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fff1d5196e8) at libc-start.c:260
 ?? ()
Title: mission-control-5 crashed with SIGSEGV in __libc_start_main()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip fax floppy fuse lpadmin plugdev sambashare sudo tape video