nautilus crashed with SIGSEGV in gdu_device_get_object_path()

Bug #681902 reported by Cristian Aravena Romero
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
GNOME Disks
Unknown
Medium
gnome-disk-utility (Ubuntu)
New
Medium
Unassigned

Bug Description

Binary package hint: gnome-disk-utility

I umount CD and open apport

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: gnome-disk-utility 2.30.1-2
Uname: Linux 2.6.37-020637rc3-generic x86_64
Architecture: amd64
CrashCounter: 1
Date: Fri Nov 26 16:30:57 2010
ExecutablePath: /usr/bin/nautilus
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
ProcCmdline: nautilus
ProcEnviron:
 LANG=es_ES.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fb116d2ccd0 <gdu_device_get_object_path>: mov 0x18(%rdi),%rax
 PC (0x7fb116d2ccd0) ok
 source "0x18(%rdi)" (0x00000018) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-disk-utility
StacktraceTop:
 gdu_device_get_object_path () from /usr/lib/libgdu.so.0
 gdu_pool_new_for_address () from /usr/lib/libgdu.so.0
 gdu_pool_new () from /usr/lib/libgdu.so.0
 ?? () from /usr/lib/nautilus/extensions-2.0/libnautilus-gdu.so
 ?? ()
Title: nautilus crashed with SIGSEGV in gdu_device_get_object_path()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Cristian Aravena Romero (caravena) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 gdu_device_get_object_path (device=0x0) at gdu-device.c:835
 gdu_pool_new_for_address (
 gdu_pool_new () at gdu-pool.c:1929
 nautilus_gdu_get_file_items (
 ?? ()

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in gnome-disk-utility (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Changed in gnome-disk-utility:
importance: Unknown → Medium
status: Unknown → New
Changed in gnome-disk-utility:
status: New → Unknown
Revision history for this message
Vincent Povirk (madewokherd) wrote :

Does this happen consistently, or was it only once?

Maybe it's a race condition? I think that _gdu_device_new_from_object_path may return NULL if the device goes away before it completes.

Revision history for this message
Cristian Aravena Romero (caravena) wrote :

Hello Vincent, please add comment in: https://bugzilla.gnome.org/show_bug.cgi?id=591660

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.