usb-creator-gtk crashed with SIGSEGV

[Mathieu Trudel-Lapierre]

Crashing while creating a GPT-formatted usb drive; somewhere during, or not long after running grub.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: usb-creator-gtk 0.2.40ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-15.23-generic 3.5.4
Uname: Linux 3.5.0-15-generic x86_64
ApportVersion: 2.5.2-0ubuntu4
Architecture: amd64
Date: Wed Sep 26 11:28:44 2012
ExecutablePath: /usr/bin/usb-creator-gtk
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20120925)
InterpreterPath: /usr/bin/python2.7
ProcCmdline: /usr/bin/python /usr/bin/usb-creator-gtk
ProcEnviron:
 LANGUAGE=fr_CA:fr
 PATH=(custom, user)
 LANG=fr_CA.UTF-8
 SHELL=/bin/zsh
SegvAnalysis:
 Segfault happened at: 0x7f0e6722ed00: movl $0xffffffff,0x4(%rdi)
 PC (0x7f0e6722ed00) ok
 source "$0xffffffff" ok
 destination "0x4(%rdi)" (0x00000004) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: usb-creator
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
 ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
 ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
 ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
 ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
Title: usb-creator-gtk crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo

[Ubuntu QA Website (ubuntuqa)]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1057013

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #915626, 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.