gparted crashes after unmounting a partition

[Duncan Lithgow]

Binary package hint: gparted

Gutsy, updated Oct 19th. gParted 0.3.3
When I unmounted my NTFS and then an EXT3 partition gparted hung and dissappeared. This did not get picked up by the crash detector thingy. So I installed gparted-dbgsym and gdb and produced this text when I unmounted another EXT3 partition. None of the partitions involved are needed by my system.

This GDB was configured as "i486-linux-gnu"...
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(gdb) handle SIG33 pass nostop noprint
Signal Stop Print Pass to program Description
SIG33 No No Yes Real-time event 33
(gdb) set pagination 0
(gdb) run
Starting program: /usr/bin/gparted
[Thread debugging using libthread_db enabled]
[New Thread -1225709888 (LWP 7336)]
======================
libparted : 1.7.1
======================
[New Thread -1241031792 (LWP 7339)]
[Thread -1241031792 (LWP 7339) exited]
[New Thread -1241031792 (LWP 7375)]
[Thread -1241031792 (LWP 7375) exited]
[New Thread -1241031792 (LWP 7378)]
[Thread -1241031792 (LWP 7378) exited]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1225709888 (LWP 7336)]
0xb719cf75 in std::basic_string<char, std::char_traits<char>, std::allocator<char> >::basic_string () from /usr/lib/libstdc++.so.6
(gdb)

[moschops (simon-waddington)]

I also have experienced the same problem - after unmounting an NTFS partition the first time it unmounted it and then hung while in the rescaning devices phase, subsequent times I've seen it segmentation fault immediately on clicking the unmount button. Running gparted again shows that the partition was actually unmounted.
This is a clean install of Gutsy 7.10 Release Candidate 1 on a dell Inspiron 700m

The about dialog says I have gparted 0.3.3 and the segmentation fault (if I run from command line) looks like this:

======================
libparted : 1.7.1
======================
Segmentation fault (core dumped)

I notice if I start gparted and just do 'refresh devices' on its own I get the same result - immediate segementation fault.

[Mantas Kriaučiūnas (mantas)]

It seems this bug is a duplicate of bug #141516