nautilus crashed with SIGSEGV in g_path_get_dirname()

[Julian Lam]

Binary package hint: nautilus

Test scenario: Nautilus attempting to access a corrupted ntfs file system on a USB drive.

Nautilus should exit with a graceful error, but instead crashes to desktop and is restarted automatically.

(The USB drive got formatted later on, so it works now, but that's hardly the point, lol)

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Wed Jul 22 20:05:10 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/nautilus
Package: nautilus 1:2.27.4-0ubuntu2
ProcCmdline: nautilus
ProcEnviron:
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-3.19-generic
SegvAnalysis:
 Segfault happened at: 0x986f8c <g_path_get_dirname+12>: call 0x92af87 <freopen64@plt+207>
 PC (0x00986f8c) ok
 source "0x92af87" (0x0092af87) ok
 Reason could not be automatically determined.
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 g_path_get_dirname () from /usr/lib/libglib-2.0.so.0
 ?? () from /usr/lib/gio/modules/libgvfsdbus.so
 ?? () from /usr/lib/gio/modules/libgvfsdbus.so
 ?? () from /usr/lib/gio/modules/libgvfsdbus.so
 ?? () from /usr/lib/gio/modules/libgvfsdbus.so
Title: nautilus crashed with SIGSEGV in g_path_get_dirname()
Uname: Linux 2.6.31-3-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:IA__g_path_get_dirname (
meta_tree_init (tree=0x9ab47e8) at metatree.c:293
meta_tree_init (tree=<value optimized out>)
meta_tree_init (tree=<value optimized out>)
meta_tree_init (tree=<value optimized out>)

[Pedro Villavicencio (pedro)]

could you reproduce this? the trace doesn't help that much

[Julian Lam (julian-lam)]

Unfortunately not, as a requirement for this was a broken USB drive. I've re-formatted the drive since, so I can no longer reproduce this on demand.

If you're interested, the only reason the USB drive became corrupted in the first place was because I unplugged the VGA cable to my laptop, which caused Ubuntu to freeze. (No bug # yet)

[Sebastien Bacher (seb128)]

We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and don't hesitate to submit bug reports in the future.