gvfs-gdu-volume-monitor crashed with SIGABRT in raise()

Bug #832379 reported by Josh Dalziel on 2011-08-23
224
This bug affects 24 people
Affects Status Importance Assigned to Milestone
gvfs
Invalid
Critical
gvfs (Ubuntu)
Medium
Unassigned

Bug Description

Error happens at start up

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: gvfs 1.9.3-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-9.13-generic 3.0.3
Uname: Linux 3.0.0-9-generic x86_64
Architecture: amd64
Date: Tue Aug 23 14:36:25 2011
ExecutablePath: /usr/lib/gvfs/gvfs-gdu-volume-monitor
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
ProcCmdline: /usr/lib/gvfs/gvfs-gdu-volume-monitor
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=en_US.UTF-8
Signal: 6
SourcePackage: gvfs
StacktraceTop:
 raise () from /lib/x86_64-linux-gnu/libc.so.6
 abort () from /lib/x86_64-linux-gnu/libc.so.6
 g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 gdu_pool_get_presentables () from /usr/lib/libgdu.so.0
Title: gvfs-gdu-volume-monitor crashed with SIGABRT in raise()
UpgradeStatus: Upgraded to oneiric on 2011-08-22 (1 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Related branches

Josh Dalziel (josh-dalziel) wrote :

StacktraceTop:
 g_assertion_message (domain=<optimized out>, file=<optimized out>, line=<optimized out>, func=0x7f00d929cd40 "gdu_pool_get_presentables", message=0x25bba60 "assertion failed: (pool != NULL)") at /build/buildd/glib2.0-2.29.16/./glib/gtestutils.c:1425
 g_assertion_message_expr (domain=0x7f00d9299cde "libgdu", file=0x7f00d929be0c "gdu-pool.c", line=2565, func=0x7f00d929cd40 "gdu_pool_get_presentables", expr=<optimized out>) at /build/buildd/glib2.0-2.29.16/./glib/gtestutils.c:1436
 gdu_pool_get_presentables () from /tmp/tmpgC9Hk3/usr/lib/libgdu.so.0
 update_drives (removed_drives=<synthetic pointer>, added_drives=<synthetic pointer>, monitor=0x25a2010) at ggduvolumemonitor.c:1238
 update_all (monitor=0x25a2010, emit_changes=0) at ggduvolumemonitor.c:1014

Changed in gvfs (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Changed in gvfs (Ubuntu):
status: New → Confirmed
tags: added: bugpattern-needed
visibility: private → public
Pedro Villavicencio (pedro) wrote :

Thank you for your bug report. This bug has been reported to the developers of the software. You can track it and make comments at:
 https://bugzilla.gnome.org/show_bug.cgi?id=662189

Changed in gvfs (Ubuntu):
status: Confirmed → Triaged
Changed in gvfs:
importance: Unknown → Critical
status: Unknown → New
Lisa Simpson (lisa-p) wrote :

I have to say that this particular bug really sucks rocks. I had to completely reinstall my video drivers and redo my xorg.conf in order to get my desktop to come back up.

SInce my networking is still pooched, Im probably going to be reinstalling over the holiday.

Thanks :/

Changed in gvfs:
status: New → Invalid
Launchpad Janitor (janitor) wrote :

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 <email address hidden> Wed, 11 Apr 2012 16:01:32 -0400

Changed in gvfs (Ubuntu):
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.