This bug was fixed in the package gvfs - 1.12.0-0ubuntu5
---------------
gvfs (1.12.0-0ubuntu5) precise; urgency=low
* debian/patches/metadata-dont-flush-null-tree.patch:
- Don't try to flush a tree that doesn't exist. Fixes crash bug
LP: #405432. Patch from upstream's Christian Kellner.
* debian/patches/metadata-nuke-junk-data.patch:
- If metadata file is bogus, erase it and start over. Related to
above bug, to be able to recover from junk data in addition to
not crashing. Patch from upstream's Christian Kellner.
* debian/patches/dont-crash-on-null-job.patch:
- Don't try to announce the finish of a NULL job. LP: #345754,
LP: #838464
* debian/patches/check-gdu-pool.patch:
- If gdu_pool_new() returns NULL, handle it gracefully.
LP: #832379
* debian/patches/handle-inactive-vfs.patch:
- If the VFS never initialized, don't crash when creating volume
monitors. LP: #832533
-- Michael Terry <mte...@ubuntu.com> Wed, 11 Apr 2012 16:01:32 -0400
** Changed in: gvfs (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/832379
Title:
gvfs-gdu-volume-monitor crashed with SIGABRT in raise()
To manage notifications about this bug go to:
https://bugs.launchpad.net/gvfs/+bug/832379/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
