Ubuntu
nautilus package

nautilus crashed with SIGSEGV in gdu_device_get_object_path()

Bug #709572 reported by Cristian Aravena Romero on 2011-01-29

This bug report is a duplicate of: Bug #412237: gdu-notification-daemon crashed with SIGSEGV in gdu_device_get_object_path(). Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	Nautilus	Unknown	Medium	gnome-bugs #640874
	nautilus (Ubuntu)	New	Medium	Unassigned

Bug Description

Binary package hint: nautilus

Umount HardDisk external and open apport

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: nautilus 1:2.32.0-0ubuntu1.3
Uname: Linux 2.6.38-020638rc2-generic x86_64
Architecture: amd64
CrashCounter: 1
Date: Fri Jan 28 21:36:19 2011
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: 0x7fbfe1df6cd0 <gdu_device_get_object_path>: mov 0x18(%rdi),%rax
PC (0x7fbfe1df6cd0) 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: nautilus
StacktraceTop:
gdu_device_get_object_path (device=0x0) at gdu-device.c:835
gdu_pool_new_for_address (ssh_user_name=<value optimized out>, ssh_address=<value optimized out>, error=0x7fff4b0b97f8) at gdu-pool.c:2108
gdu_pool_new () at gdu-pool.c:1929
get_device_for_device_file (provider=<value optimized out>, window=<value optimized out>, files=<value optimized out>) at nautilus-gdu.c:50
get_device_from_nautilus_file (provider=<value optimized out>, window=<value optimized out>, files=<value optimized out>) at nautilus-gdu.c:114
Title: nautilus crashed with SIGSEGV in gdu_device_get_object_path()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Tags:

Revision history for this message

Cristian Aravena Romero (caravena) wrote on 2011-01-29:

Dependencies.txt Edit (5.2 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (858 bytes, text/plain; charset="utf-8")
GConfNonDefault.txt Edit (774 bytes, text/plain; charset="utf-8")
ProcMaps.txt Edit (93.9 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (798 bytes, text/plain; charset="utf-8")
Registers.txt Edit (704 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (7.5 KiB, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (14.3 KiB, text/plain; charset="utf-8")
XsessionErrors.txt Edit (16.9 KiB, text/plain; charset="utf-8")
usr_lib_nautilus.txt Edit (419 bytes, text/plain; charset="utf-8")

visibility:

private → public

Revision history for this message

Apport retracing service (apport) wrote on 2011-01-29:

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 (
get_all_extension_menu_items (window=0x1e9e7f0,

Revision history for this message

Apport retracing service (apport) wrote on 2011-01-29: Stacktrace.txt

Stacktrace.txt Edit (6.2 KiB, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2011-01-29: ThreadStacktrace.txt

ThreadStacktrace.txt Edit (10.5 KiB, text/plain)

Changed in nautilus (Ubuntu):
importance:	Undecided → Medium
tags:	removed: need-amd64-retrace

Bug Watch Updater (bug-watch-updater) on 2011-01-29

Changed in nautilus:
importance:	Unknown → Medium
status:	Unknown → New

Bug Watch Updater (bug-watch-updater) on 2011-01-30

Changed in nautilus:
status:	New → Unknown

Revision history for this message

Pedro Villavicencio (pedro) wrote on 2011-01-31:

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 412237, 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.