I was resizing a DOS partition. Gparted runs dosfsck prior to the resizing. For some reason dosfsck crashed. Gparted did not detect this - the GUI was frozen (would redraw, but no button could be pressed). Eventually, after a long time the GUI has reached some timeout and informed me something is wrong.
I think gparted should detect the crash of the fsck immediatelly and not wait for a timeout.
Ubuntu 11.10
gparted 0.8.1-1ubuntu4
In the console I see:
$ sudo gparted /dev/sdc
[sudo] password for ...
======================
libparted : 2.3
======================
*** buffer overflow detected ***: dosfsck terminated
======= Backtrace: =========
/lib/i386-linux-gnu/libc.so.6(__fortify_fail+0x45)[0x1f8c75]
/lib/i386-linux-gnu/libc.so.6(+0xe7a77)[0x1f7a77]
/lib/i386-linux-gnu/libc.so.6(+0xe70d5)[0x1f70d5]
/lib/i386-linux-gnu/libc.so.6(_IO_default_xsputn+0x91)[0x17d2f1]
/lib/i386-linux-gnu/libc.so.6(_IO_vfprintf+0xffd)[0x15112d]
/lib/i386-linux-gnu/libc.so.6(__vsprintf_chk+0xc9)[0x1f71a9]
/lib/i386-linux-gnu/libc.so.6(__sprintf_chk+0x2f)[0x1f70bf]
dosfsck[0x804c724]
dosfsck[0x804e8f4]
dosfsck[0x8048f60]
/lib/i386-linux-gnu/libc.so.6(__libc_start_main+0xf3)[0x129113]
dosfsck[0x804904d]
======= Memory map: ========
00110000-00288000 r-xp 00000000 08:03 4460248 /lib/i386-linux-gnu/libc-2.13.so
00288000-0028a000 r--p 00178000 08:03 4460248 /lib/i386-linux-gnu/libc-2.13.so
0028a000-0028b000 rw-p 0017a000 08:03 4460248 /lib/i386-linux-gnu/libc-2.13.so
0028b000-0028e000 rw-p 00000000 00:00 0
0028e000-002aa000 r-xp 00000000 08:03 4460242 /lib/i386-linux-gnu/libgcc_s.so.1
002aa000-002ab000 r--p 0001b000 08:03 4460242 /lib/i386-linux-gnu/libgcc_s.so.1
002ab000-002ac000 rw-p 0001c000 08:03 4460242 /lib/i386-linux-gnu/libgcc_s.so.1
00f5d000-00f7b000 r-xp 00000000 08:03 4456690 /lib/i386-linux-gnu/ld-2.13.so
00f7b000-00f7c000 r--p 0001d000 08:03 4456690 /lib/i386-linux-gnu/ld-2.13.so
00f7c000-00f7d000 rw-p 0001e000 08:03 4456690 /lib/i386-linux-gnu/ld-2.13.so
08048000-08054000 r-xp 00000000 08:03 3835626 /sbin/dosfsck
08054000-08055000 r--p 0000c000 08:03 3835626 /sbin/dosfsck
08055000-08056000 rw-p 0000d000 08:03 3835626 /sbin/dosfsck
08056000-08058000 rw-p 00000000 00:00 0
08ef5000-08f27000 rw-p 00000000 00:00 0 [heap]
b76a3000-b76ea000 rw-p 00000000 00:00 0
b7707000-b770a000 rw-p 00000000 00:00 0
bf847000-bf868000 rw-p 00000000 00:00 0 [stack]
Uf, does not seem to be reproducible. dosfsck does reproducibly crash for that partition, but now gparted shows an error message right away. Maybe it was caused by the operation (FAT resize) being second in the queue? Or it was just some magical glitch. :(