Why is gvfs-gdu-volume-monitor killed by signal 6 (SIGABRT)?

Issue

• Why is gvfs-gdu-volume-monitor killed by signal 6 (SIGABRT)?

Call trace sample:

# rpm -q gvfs gnome-disk-utility-libs
gvfs-1.4.3-15.el6.x86_64
gnome-disk-utility-libs-2.30.1-2.el6.x86_64
# cd /var/spool/abrt/ccpp-Date-Time-Pid-Path
# cat reason 
Process /usr/libexec/gvfs-gdu-volume-monitor was killed by signal 6 (SIGABRT)
# gdb /usr/libexec/gvfs-gdu-volume-monitor ./coredump 
...skip
(gdb) bt
#0  0x00000037a1032625 in raise () from /lib64/libc.so.6
#1  0x00000037a1033e05 in abort () from /lib64/libc.so.6
#2  0x00000037a28661c4 in g_assertion_message () from /lib64/libglib-2.0.so.0
#3  0x00000037a2866790 in g_assertion_message_expr () from /lib64/libglib-2.0.so.0
#4  0x00000037a2010036 in gdu_pool_get_presentables () from /usr/lib64/libgdu.so.0
#5  0x000000000040f39e in ?? ()
#6  0x00000000004103b5 in ?? ()
#7  0x00000037a3013e3a in g_object_newv () from /lib64/libgobject-2.0.so.0
#8  0x00000037a301456c in g_object_new () from /lib64/libgobject-2.0.so.0
#9  0x00000000004104e0 in ?? ()
#10 0x0000000000410621 in ?? ()
#11 0x00000037a101ed5d in __libc_start_main () from /lib64/libc.so.6
#12 0x0000000000407359 in ?? ()
#13 0x00007fffffffe818 in ?? ()
#14 0x000000000000001c in ?? ()
#15 0x0000000000000001 in ?? ()
#16 0x00007fffffffeabb in ?? ()
#17 0x0000000000000000 in ?? ()
(gdb)