[Bug 1384557] [NEW] gpartedbin crashed with SIGSEGV

[Eliah Kagan]

Public bug reported:

On a Lubuntu Utopic amd64 system, gparted 0.19.0-1build1 crashed when I
created a new partition table (of type Apple Partition Map) on a 16 GB
(~15 GiB) USB flash drive, selecting "mac" (as this type is called in
the GParted interface).

The new partition table was apparently successfully created before the
crash. When I ran GParted again (same version, relaunching immediately
after the crash), it recognized it. I was able to create it again on the
same device, also successfully but this time with no crash. I had also
previously created a "mac" partition table on this USB stick with
GParted, on this machine, that time with no crashes. I don't know for
sure if the version of GParted I'd used before was the same.

I was then able to make a 16 GB (~15 GiB) HFS+ partition in GParted--
both previously, and this time.

Between the original, error-free operations and the partition table
creation operation that succeeded but triggered a crash, I had
reformatted this USB stick, also with an Apple Partition Map partition
table, but with two 8 GB HFS+ partitions with journalling enabled. I did
that on an old Mac OS X 10.4 Tiger system (running on a PowerMac G5). I
don't know if something about the new layout triggered the crash, or
not.

ProblemType: Crash
DistroRelease: Ubuntu 14.10
Package: gparted 0.19.0-1build1
ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
Uname: Linux 3.16.0-23-generic x86_64
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
Date: Thu Oct 23 02:33:15 2014
Disassembly: => 0x7f3600000000:	Cannot access memory at address 0x7f3600000000
ExecutablePath: /usr/sbin/gpartedbin
InstallationDate: Installed on 2014-10-15 (7 days ago)
InstallationMedia: Lubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141014)
ProcCmdline: /usr/sbin/gpartedbin
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f3600000000:	Cannot access memory at address 0x7f3600000000
 PC (0x7f3600000000) not located in a known VMA region (needed executable region)!
 Stack memory exhausted (SP below stack segment)
SegvReason: executing unknown VMA
Signal: 11
SourcePackage: gparted
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
Title: gpartedbin crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

** Affects: gparted (Ubuntu)
     Importance: Undecided
         Status: Invalid


** Tags: amd64 apport-crash utopic

** Information type changed from Private to Public

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to gparted in Ubuntu.
https://bugs.launchpad.net/bugs/1384557

Title:
  gpartedbin crashed with SIGSEGV

Status in “gparted” package in Ubuntu:
  Invalid

Bug description:
  On a Lubuntu Utopic amd64 system, gparted 0.19.0-1build1 crashed when
  I created a new partition table (of type Apple Partition Map) on a 16
  GB (~15 GiB) USB flash drive, selecting "mac" (as this type is called
  in the GParted interface).

  The new partition table was apparently successfully created before the
  crash. When I ran GParted again (same version, relaunching immediately
  after the crash), it recognized it. I was able to create it again on
  the same device, also successfully but this time with no crash. I had
  also previously created a "mac" partition table on this USB stick with
  GParted, on this machine, that time with no crashes. I don't know for
  sure if the version of GParted I'd used before was the same.

  I was then able to make a 16 GB (~15 GiB) HFS+ partition in GParted--
  both previously, and this time.

  Between the original, error-free operations and the partition table
  creation operation that succeeded but triggered a crash, I had
  reformatted this USB stick, also with an Apple Partition Map partition
  table, but with two 8 GB HFS+ partitions with journalling enabled. I
  did that on an old Mac OS X 10.4 Tiger system (running on a PowerMac
  G5). I don't know if something about the new layout triggered the
  crash, or not.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: gparted 0.19.0-1build1
  ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
  Uname: Linux 3.16.0-23-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  Date: Thu Oct 23 02:33:15 2014
  Disassembly: => 0x7f3600000000:	Cannot access memory at address 0x7f3600000000
  ExecutablePath: /usr/sbin/gpartedbin
  InstallationDate: Installed on 2014-10-15 (7 days ago)
  InstallationMedia: Lubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141014)
  ProcCmdline: /usr/sbin/gpartedbin
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f3600000000:	Cannot access memory at address 0x7f3600000000
   PC (0x7f3600000000) not located in a known VMA region (needed executable region)!
   Stack memory exhausted (SP below stack segment)
  SegvReason: executing unknown VMA
  Signal: 11
  SourcePackage: gparted
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
  Title: gpartedbin crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gparted/+bug/1384557/+subscriptions