Nautilus segfault when "eject"ing SD media; nautilus crashed with SIGSEGV in gdu_device_get_object_path()

[Nick Moffitt]

Binary package hint: gnome-disk-utility

This looks similar, if not identical, to bug#468864 but I figured that since I'm on amd64 instead of i386 it could be helpful to get a second crash report.

I tried to "eject" an SD card that I had successfully used in my internal SD reader in pursuit of more information on bug#549644, and was watching syslog at the time and saw:

Mar 28 18:43:12 vezza kernel: [116337.110142] usb 2-6: new high speed USB device using ehci_hcd and address 12
Mar 28 18:43:12 vezza kernel: [116337.262595] usb 2-6: configuration #1 chosen from 1 choice
Mar 28 18:43:12 vezza kernel: [116337.263045] scsi11 : SCSI emulation for USB Mass Storage devices
Mar 28 18:43:12 vezza kernel: [116337.263288] usb-storage: device found at 12
Mar 28 18:43:12 vezza kernel: [116337.263292] usb-storage: waiting for device to settle before scanning
Mar 28 18:43:17 vezza kernel: [116342.270271] usb-storage: device scan complete
Mar 28 18:43:17 vezza kernel: [116342.270866] scsi 11:0:0:0: Direct-Access RICOH R5U880FlashMedia 0000 PQ: 0 ANSI: 2
Mar 28 18:43:17 vezza kernel: [116342.271325] sd 11:0:0:0: Attached scsi generic sg1 type 0
Mar 28 18:43:17 vezza kernel: [116342.494021] sd 11:0:0:0: [sdb] 3853967360 512-byte logical blocks: (1.97 TB/1.79 TiB)
Mar 28 18:43:17 vezza kernel: [116342.494669] sd 11:0:0:0: [sdb] Write Protect is off
Mar 28 18:43:17 vezza kernel: [116342.494676] sd 11:0:0:0: [sdb] Mode Sense: 0b 00 00 08
Mar 28 18:43:17 vezza kernel: [116342.494682] sd 11:0:0:0: [sdb] Assuming drive cache: write through
Mar 28 18:43:17 vezza kernel: [116342.497662] sd 11:0:0:0: [sdb] Assuming drive cache: write through
Mar 28 18:43:17 vezza kernel: [116342.497671] sdb: sdb1
Mar 28 18:43:17 vezza kernel: [116342.504058] sd 11:0:0:0: [sdb] Assuming drive cache: write through
Mar 28 18:43:17 vezza kernel: [116342.504067] sd 11:0:0:0: [sdb] Attached SCSI removable disk
Mar 28 18:44:04 vezza kernel: [116389.726494] sd 11:0:0:0: [sdb] Assuming drive cache: write through
Mar 28 18:44:04 vezza kernel: [116389.726506] sdb: sdb1
Mar 28 18:44:04 vezza kernel: [116389.758544] nautilus[2037]: segfault at 18 ip 00007fea6e09ddc0 sp 00007ffff7db8138 error 4 in libgdu.so.0.0.0[7fea6e088000+37000]

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: gnome-disk-utility 2.30.0-1build1
ProcVersionSignature: Ubuntu 2.6.32-17.26-generic 2.6.32.10+drm33.1
Uname: Linux 2.6.32-17-generic x86_64
Architecture: amd64
Date: Sun Mar 28 18:44:05 2010
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/nautilus
ProcCmdline: nautilus
ProcEnviron:
 PATH=(custom, user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fea6e09ddc0 <gdu_device_get_object_path>: mov 0x18(%rdi),%rax
 PC (0x7fea6e09ddc0) 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 ()
 gdu_pool_new_for_address ()
 gdu_pool_new () from /usr/lib/libgdu.so.0
 ?? ()
 ?? ()
Title: nautilus crashed with SIGSEGV in gdu_device_get_object_path()
UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:
 gdu_device_get_detection_time (device=0x0) at gdu-device.c:906
 gdu_pool_new_for_address (
 gdu_pool_new () at gdu-pool.c:1940
 nautilus_gdu_get_file_items (
 ?? ()

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.