upstart-file-bridge crashed with SIGABRT in raise()

[siucdude]

Just got this after updates.
TJ

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: upstart 1.9-0ubuntu1
ProcVersionSignature: Ubuntu 3.10.0-2.9-generic 3.10.0
Uname: Linux 3.10.0-2-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.10.2-0ubuntu3
Architecture: amd64
Date: Tue Jul 2 20:14:24 2013
ExecutablePath: /sbin/upstart-file-bridge
InstallationDate: Installed on 2011-04-03 (821 days ago)
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta amd64 (20110330)
MarkForUpload: True
ProcCmdline: upstart-file-bridge --daemon
ProcEnviron:
 PATH=(custom, no user)
 TERM=linux
Signal: 6
SourcePackage: upstart
StacktraceTop:
 raise () from /lib/x86_64-linux-gnu/libc.so.6
 abort () from /lib/x86_64-linux-gnu/libc.so.6
 nih_str_split () from /lib/x86_64-linux-gnu/libnih.so.1
 ?? ()
 __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6
Title: upstart-file-bridge crashed with SIGABRT in raise()
UpgradeStatus: No upgrade log present (probably fresh install)
UpstartBugCategory: Session
UpstartRunningSessionVersion: init (upstart 1.9)
UpstartRunningSystemVersion: init (upstart 1.9)
UserGroups:

[Apport retracing service (apport)]

StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()

[Launchpad Janitor (janitor)]

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

[Adam Conrad (adconrad)]

Crashed on upgrade from upstart 1.8-0ubuntu7 to 1.9-0ubuntu1

[fantab (fantab)]

Got this when I was upgrading from Synaptic, ignored it. Then it happened again when I restarted after upgrade.

[IanW (launchpad-washuu)]

As above. Crash immediately after an update.