Then I suppose the stack/backtrace of _usr_lib_gnome-disk-utility_gdu-
notification-daemon.1000.crash also can be helpful:
Core was generated by `/usr/lib/gnome-disk-utility/gdu-notification-daemon'.
Program terminated with signal 6, Aborted.
#0 0x00a32422 in __kernel_vsyscall ()
(gdb) bt
#0 0x00a32422 in __kernel_vsyscall ()
#1 0x06e20641 in *__GI_raise (sig=6) at
../nptl/sysdeps/unix/sysv/linux/raise.c:64
#2 0x06e23a72 in *__GI_abort () at abort.c:92
#3 0x006dadd3 in IA__g_assertion_message (domain=0x332484 "libgdu",
file=0x334725 "gdu-pool.c", line=2459,
func=0x33583d "gdu_pool_get_devices", message=0x81d7b60 "assertion failed:
(pool != NULL)")
at /build/buildd/glib2.0-2.24.0/glib/gtestutils.c:1318
#4 0x006db42d in IA__g_assertion_message_expr (domain=0x332484 "libgdu",
file=0x334725 "gdu-pool.c", line=2459,
func=0x33583d "gdu_pool_get_devices", expr=0x334718 "pool != NULL")
at /build/buildd/glib2.0-2.24.0/glib/gtestutils.c:1329
#5 0x00316d57 in gdu_pool_get_devices (pool=0x0) at gdu-pool.c:2471
#6 0x0804b1f8 in update_unmount_dialogs (data=0x81d2948) at
notification-main.c:317
#7 update_all (data=0x81d2948) at notification-main.c:81
#8 0x0804bb92 in main (argc=1, argv=0xbf8cbfc4) at notification-main.c:701
(gdb)
--
gvfs-gdu-volume-monitor crashes on login
https://bugs.launchpad.net/bugs/531731
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
