gpartedbin crashed when resizing HFS+

Bug #488819 reported by Dave Hope on 2009-11-26
This bug affects 4 people
Affects Status Importance Assigned to Milestone
gparted (Ubuntu)

Bug Description

Binary package hint: gparted

Ubuntu 9.10 using the i386 desktop install CD, running the live CD and launching gparted (GParted 0.4.5):

# apt-cache policy gparted
  Installed: 0.4.5-2ubuntu1
  Candidate: 0.4.5-2ubuntu1
  Version table:
 *** 0.4.5-2ubuntu1 0
        500 karmic/main Packages
        100 /var/lib/dpkg/status

When applying a single operation, resizing a 111.47GiB HFS+ partition to 60GiB (ish) gparted crashed almost instantly. Using 'parted', it seems no changes to the drive actually took place:

(parted) print all
Model: ATA TOSHIBA MK1234GS (scsi)
Disk /dev/sda: 120GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt

Number Start End Size File system Name Flags
 1 20.5kB 210MB 210MB fat32 EFI System Partition boot
 2 210MB 120GB 120GB hfs+ Apple_HFS_Untitled_1

Crash information should be attached.

ProblemType: Crash
Architecture: i386
Date: Thu Nov 26 15:44:39 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/sbin/gpartedbin
LiveMediaBuild: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
Package: gparted 0.4.5-2ubuntu1
ProcCmdline: /usr/sbin/gpartedbin
 PATH=(custom, no user)
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
 Segfault happened at: 0x75d45a8: mov 0xa0075d45,%al
 PC (0x075d45a8) in non-executable VMA region: 0x075d4000-0x075d7000 rw-p None
 source "0xa0075d45" (0xa0075d45) not located in a known VMA region (needed readable region)!
 destination "%al" ok
 executing writable VMA None
 reading unknown VMA
Signal: 11
SourcePackage: gparted
 ?? () from /lib/tls/i686/cmov/
 ?? ()
 Glib::SignalProxyNormal::slot0_void_callback(_GObject*, void*) () from /usr/lib/
 g_cclosure_marshal_VOID__VOID ()
 g_closure_invoke () from /usr/lib/
Title: gpartedbin crashed with SIGSEGV in Glib::SignalProxyNormal::slot0_void_callback()
Uname: Linux 2.6.31-14-generic i686

visibility: private → public

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #462743, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

tags: removed: need-i386-retrace
Dave Hope (dave-davehope) wrote :


The other bug seems to be marked as private, so I and others having this problem can't access it.

Can you either change the visibility of the other bug, or leave this one open so others can avoid reporting duplicates?

description: updated
Dave Hope (dave-davehope) wrote :

With the bug marked as a duplicate, nobody else could see it, and the one the Apport retracing service flagged it as a duplicate of is marked as private (so again, can't be found).

Can the other bug me made private, or this one? - that way others are less likely to re-raise this issue.

Amgine (amgine-saewyc) wrote :

Ditto. If I cannot determine if the other bug is a duplicate, marking this as my problem.

Phillip Susi (psusi) wrote :

9.10 reached end of life some time ago and is no longer supported.

Changed in gparted (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers