palimpsest crashed with SIGSEGV 10.4

[Jonatan]

Binary package hint: gnome-disk-utility

Was trying disk utility, and choose the option power down for safe removal on my 500 gb external hdd, when it all crashed, now the disk needs a format, splendid!

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: gnome-disk-utility 2.30.1-1
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
Uname: Linux 2.6.31-14-generic i686
Architecture: i386
Date: Tue Apr 13 19:51:59 2010
ExecutablePath: /usr/bin/palimpsest
ProcCmdline: palimpsest
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x80505c7: mov 0xc(%eax),%eax
 PC (0x080505c7) 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: gnome-disk-utility
StacktraceTop:
 ?? ()
 ?? () from /usr/lib/libgdu.so.0
 ?? () from /usr/lib/libgdu.so.0
 ?? () from /usr/lib/libdbus-glib-1.so.2
 ?? () from /lib/libdbus-1.so.3
Title: palimpsest crashed with SIGSEGV
UserGroups: adm admin audio cdrom dialout dip fax fuse lpadmin netdev plugdev sambashare tape video

[Apport retracing service (apport)]

StacktraceTop:
 gdu_shell_get_toplevel (shell=0x9b2a980) at gdu-shell.c:119
 op_detach_cb (proxy=0x9b32ee0, error=0x9b0a538,
 org_freedesktop_UDisks_Device_drive_detach_async_callback (
 d_pending_call_notify (dcall=0x9b55ba8, data=0x9b29f48)
 _dbus_pending_call_complete (pending=0x9b55ba8)

[Pedro Villavicencio (pedro)]

Thanks for the report, it has been some time without any response or feedback in this bug report and we are wondering if this is still an issue for you with the latest release of Ubuntu the Natty Narwhal, May you please test with that version and comment back if you're still having or not the issue? Please have a look at http://www.ubuntu.com/download to know how to install that version.Thanks in advance.

[Pedro Villavicencio (pedro)]

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.