Description of problem:
The gvfs-gdu-volume-monitor process was aborted during system shutdown.
The cause of abort is that it did not meet the g_assert() conditions.
#0 0x00000030f8432925 in raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#1 0x00000030f8434105 in abort () at abort.c:92
#2 0x00000030f9c661c4 in g_assertion_message (domain=<value optimized out>, file=<value optimized out>, line=<value optimized out>,
func=0x3102c2d690 "gdu_pool_get_presentables", message=0x9582c0 "assertion failed: (pool != NULL)") at gtestutils.c:1358
#3 0x00000030f9c66790 in g_assertion_message_expr (domain=0x3102c2a224 "libgdu", file=0x3102c2c545 "gdu-pool.c", line=2565,
func=0x3102c2d690 "gdu_pool_get_presentables", expr=<value optimized out>) at gtestutils.c:1369
2561 GList *
2562 gdu_pool_get_presentables (GduPool *pool)
2564 GList *ret;
2565 g_assert (pool != NULL);
Version-Release number of selected component (if applicable):
Steps to Reproduce:
It occurred during the shutdown.
The other reproducer is not known.
The process was aborted with a coredump.
The process is completed correctly.
* I assume that desktop processes were not completed correctly.
-rw------- 1 root root 819200 2014-09-04 18:00:42.606894061 +0900 /core.17549
Sep 4 18:00:39 TESTHOST abrtd: Got signal 15, exiting
Sep 4 18:00:40 TESTHOST snmpd: Received TERM or STOP signal... shutt
Sep 4 18:00:41 TESTHOST ntpd: ntpd exiting on signal 15
Sep 4 18:00:41 TESTHOST init: Disconnected from system bus
Sep 4 18:00:41 TESTHOST multipathd: mpath00d0: stop event checker thread (4
Sep 4 18:00:41 TESTHOST gnome-keyring-daemon: GVFS-RemoteVolumeMonito
r: Owner :1.47 of volume monitor org.gtk.Private.GduVolumeMonitor disconnected f
rom the bus; removing drives/volumes/mounts
Sep 4 18:00:44 TESTHOST kernel: talpa-vfshook: Disabled
* I found the similar cases:
- Bug 609108
- Bug 683315
- Bug 713865
It also happens in different situations according the mentioned similar cases, not only during shutdown. The root cause are problems with dbus, unfortunately we haven't reliable reproducer. However we can handle those problems better to avoid crashes. There is upstream patch to do that:
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.