gpartedbin crashed when resizing HFS+
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gparted (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
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
gparted:
Installed: 0.4.5-2ubuntu1
Candidate: 0.4.5-2ubuntu1
Version table:
*** 0.4.5-2ubuntu1 0
500 http://
100 /var/lib/
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_
Crash information should be attached.
ProblemType: Crash
Architecture: i386
Date: Thu Nov 26 15:44:39 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/sbin/
LiveMediaBuild: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
Package: gparted 0.4.5-2ubuntu1
ProcCmdline: /usr/sbin/
ProcEnviron:
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSign
SegvAnalysis:
Segfault happened at: 0x75d45a8: mov 0xa0075d45,%al
PC (0x075d45a8) in non-executable VMA region: 0x075d4000-
source "0xa0075d45" (0xa0075d45) not located in a known VMA region (needed readable region)!
destination "%al" ok
SegvReason:
executing writable VMA None
reading unknown VMA
Signal: 11
SourcePackage: gparted
StacktraceTop:
?? () from /lib/tls/
?? ()
Glib::
g_cclosure_
g_closure_invoke () from /usr/lib/
Title: gpartedbin crashed with SIGSEGV in Glib::SignalPro
Uname: Linux 2.6.31-14-generic i686
UserGroups:
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.