gvfs-gdu-volume-monitor crashed with SIGSEGV in gdu_pool_get_presentables()

Bug #521481 reported by Mario Limonciello
26
This bug affects 4 people
Affects Status Importance Assigned to Milestone
GNOME Disks
Invalid
Medium
gnome-disk-utility (Ubuntu)
Triaged
Medium
Unassigned
Lucid
Triaged
Medium
Unassigned

Bug Description

Binary package hint: gvfs

Starting mythbuntu control centre on lucid.

ProblemType: Crash
Architecture: i386
Date: Sat Feb 13 13:21:04 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/lib/gvfs/gvfs-gdu-volume-monitor
InstallationMedia: Mythbuntu 10.04 "Lucid Lynx" - Alpha i386 (20100213)
Package: gvfs 1.5.3-0ubuntu2
ProcCmdline: /usr/lib/gvfs/gvfs-gdu-volume-monitor
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.UTF-8
ProcVersionSignature: Ubuntu 2.6.32-13.18-generic
SegvAnalysis:
 Segfault happened at: 0x71780a <gdu_pool_get_presentables+26>: mov 0xc(%eax),%eax
 PC (0x0071780a) 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
 update_drives (monitor=0x89ea420,
 update_all (monitor=0x89ea420, emit_changes=<value optimized out>)
 g_gdu_volume_monitor_constructor (type=144607000,
 g_object_newv () from /usr/lib/libgobject-2.0.so.0
Title: gvfs-gdu-volume-monitor crashed with SIGSEGV in gdu_pool_get_presentables()
Uname: Linux 2.6.32-13-generic i686
UserGroups: adm admin cdrom dialout lpadmin mythtv plugdev sambashare video

Revision history for this message
Mario Limonciello (superm1) wrote :
Revision history for this message
Mario Limonciello (superm1) wrote :

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

Revision history for this message
Mario Limonciello (superm1) wrote : Stacktrace.txt
Revision history for this message
Mario Limonciello (superm1) wrote : StacktraceSource.txt
Revision history for this message
Mario Limonciello (superm1) wrote : ThreadStacktrace.txt
tags: removed: need-i386-retrace
Changed in gvfs (Ubuntu):
importance: Undecided → Medium
visibility: private → public
affects: gvfs (Ubuntu) → gnome-disk-utility (Ubuntu)
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package gnome-disk-utility - 2.28.1-2ubuntu1

---------------
gnome-disk-utility (2.28.1-2ubuntu1) lucid; urgency=low

  * debian/patches/03-null-presentables-pool.patch:
    - Fixes sigsegv when called with a null pool pointer. (LP: #521481)
 -- Mario Limonciello <email address hidden> Sat, 13 Feb 2010 13:54:35 -0600

Changed in gnome-disk-utility (Ubuntu):
status: New → Fix Released
Revision history for this message
Chris Coulson (chrisccoulson) wrote :

This isn't the right fix for this - all it's doing is masking the real bug, which is that gdu_pool_new returns a NULL pointer

Revision history for this message
Chris Coulson (chrisccoulson) wrote :

We discussed this on #ubuntu-desktop this morning - we really need to find a proper fix for this, so I'm reopening it for now

Changed in gnome-disk-utility (Ubuntu):
status: Fix Released → Triaged
Revision history for this message
Sebastien Bacher (seb128) wrote :

lucid still collects crashes on this issue adding a lucid task it would be nice to fix in a stable update

Revision history for this message
lowlux (lowlux) wrote :

FIX IT

Revision history for this message
ralph (rmcknight) wrote :

I have this issue as well.

Changed in gnome-disk-utility:
importance: Unknown → Medium
status: Unknown → Invalid
Revision history for this message
Brian Murray (brian-murray) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 436871, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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