usb-creator-gtk crashed with SIGSEGV

[Ivan Brasil Fuzzer]

Description: Ubuntu Raring Ringtail (development branch)
Release: 13.04

usb-creator-gtk:
  Instalado: 0.2.46.1
  Candidato: 0.2.46.1
  Tabela de versão:
 *** 0.2.46.1 0
        500 http://ubuntu.c3sl.ufpr.br/ubuntu/ raring/main amd64 Packages
        100 /var/lib/dpkg/status

Trying to make a 12.04 AMD64 USB Key in 13.04. The files are transfered to key, but the key is not bootable.

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: usb-creator-gtk 0.2.46.1
ProcVersionSignature: Ubuntu 3.8.0-12.21-generic 3.8.2
Uname: Linux 3.8.0-12-generic x86_64
ApportVersion: 2.9.1-0ubuntu1
Architecture: amd64
Date: Wed Mar 13 18:55:57 2013
ExecutablePath: /usr/bin/usb-creator-gtk
InstallationDate: Installed on 2012-12-22 (80 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
InterpreterPath: /usr/bin/python3.3
MarkForUpload: True
ProcCmdline: /usr/bin/python3 /usr/bin/usb-creator-gtk
ProcEnviron:
 LANGUAGE=pt_BR:pt:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=pt_BR.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f0a508c4d80: movl $0xffffffff,0x4(%rdi)
 PC (0x7f0a508c4d80) 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: Upgraded to raring on 2013-01-09 (63 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[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.