gvfs-gdu-volume-monitor crashed with SIGSEGV in gdu_pool_get_presentables(), wasn't even doing anything special (shortly after logging in)

[Tonnerre LOMBARD]

Binary package hint: gvfs

I know there are some bugs out there with the exact same description, but this one happened after I logged in right after rebooting from an upgrade. This means that I'm using whatever was in karmic at 20:00 UTC today.

Description: Ubuntu karmic (development branch)
Release: 9.10
gvfs:
  Installed: 1.4.0-0ubuntu1
  Candidate: 1.4.0-0ubuntu1

I expected it to not crash, but it did. As mentioned, I was just logging in and started doing stuff when it suddenly announced its demise.

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Fri Sep 25 22:13:59 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/lib/gvfs/gvfs-gdu-volume-monitor
Package: gvfs 1.4.0-0ubuntu1
ProcCmdline: /usr/lib/gvfs/gvfs-gdu-volume-monitor
ProcEnviron:
 SHELL=/bin/zsh
 LANG=en_US.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-10.35-generic
SegvAnalysis:
 Segfault happened at: 0x4b8b2a <gdu_pool_get_presentables+26>: mov 0xc(%eax),%eax
 PC (0x004b8b2a) ok
 source "0xc(%eax)" (0x0000000c) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gvfs
StacktraceTop:
 gdu_pool_get_presentables () from /usr/lib/libgdu.so.0
 ?? ()
 ?? ()
 g_object_newv () from /usr/lib/libgobject-2.0.so.0
 g_object_new_valist () from /usr/lib/libgobject-2.0.so.0
Tags: ubuntu-unr
Title: gvfs-gdu-volume-monitor crashed with SIGSEGV in gdu_pool_get_presentables()
Uname: Linux 2.6.31-10-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:gdu_pool_get_presentables (pool=0x0) at gdu-pool.c:1378
update_all (monitor=<value optimized out>,
g_gdu_volume_monitor_constructor (type=158025896,
g_object_newv () from /usr/lib/libgobject-2.0.so.0
g_object_new_valist () from /usr/lib/libgobject-2.0.so.0

[Michael Terry (mterry)]

Duplicate reports stopped right before 10.04's release. Is this still an issue for anyone?

(I looked at code real quick, it seems to be because gdu_pool_new() can return NULL in some error situations, which gvfs does not check for. But since this hasn't been reported in forever, I'm assuming those error situations no longer happen.)

[Rob Candee (rob-candee)]

Not a problem here; currently on Ubuntu 11.10.

Rob Candee

On 04/11/2012 11:42 AM, Michael Terry wrote:
> *** This bug is a duplicate of bug 376145 ***
> https://bugs.launchpad.net/bugs/376145
>
> Duplicate reports stopped right before 10.04's release. Is this still
> an issue for anyone?
>
> (I looked at code real quick, it seems to be because gdu_pool_new() can
> return NULL in some error situations, which gvfs does not check for.
> But since this hasn't been reported in forever, I'm assuming those error
> situations no longer happen.)
>
> ** Changed in: gvfs (Ubuntu)
> Status: Triaged => Incomplete
>