mount.exfat-fuse crashed with SIGABRT in raise()

[Matthew J. Ballard]

This showed up shortly after boot, but not with any exfat formatted devices mounted or being mounted. It mentions a SDXC card that I do use on my camera (Nikon 5100) though that is exfat formatted.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: exfat-fuse 1.0.1-1
ProcVersionSignature: Ubuntu 3.9.0-7.15-generic 3.9.7
Uname: Linux 3.9.0-7-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.10.2-0ubuntu2
Architecture: amd64
Date: Thu Jun 20 04:56:19 2013
ExecutablePath: /sbin/mount.exfat-fuse
InstallationDate: Installed on 2013-06-20 (3 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130618)
MarkForUpload: True
ProcCmdline: /sbin/mount.exfat /dev/mmcblk0p1 /media/matt/NIKON\ D5100 -o rw,nosuid,nodev,uhelper=udisks2
ProcEnviron:

Signal: 6
SourcePackage: fuse-exfat
StacktraceTop:
 raise () from /lib/x86_64-linux-gnu/libc.so.6
 abort () from /lib/x86_64-linux-gnu/libc.so.6
 ?? ()
 ?? ()
 ?? ()
Title: mount.exfat-fuse crashed with SIGABRT in raise()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

[Matthew J. Ballard (sapphiretiger)]

Saw this bug report, but noticed it was for Precise and was suggested to upgrade and resubmit the bug if it persists. It presented using Saucy this time, so...

https://bugs.launchpad.net/ubuntu/+source/fuse-exfat/+bug/1159923

[Apport retracing service (apport)]

StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 fuse_fs_destroy (fs=0x7f6ec82be320) at fuse.c:2610
 fuse_lib_destroy (data=0x7f6ec82be1c0) at fuse.c:2623