usb-creator-gtk crashed with SIGSEGV

[v0v04ka]

lsb_release -rd
Description: Ubuntu 12.10
Release: 12.10

apt-cache policy usb-creator-gtk
usb-creator-gtk:
  Установлен: 0.2.40ubuntu1
  Кандидат: 0.2.40ubuntu1
  Таблица версий:
 *** 0.2.40ubuntu1 0
        500 http://ru.archive.ubuntu.com/ubuntu/ quantal/main i386 Packages
        100 /var/lib/dpkg/status

usb-creator crashed in process of making boot flash drive with segfault in finall stage before boot record.
Second time it went fine w/o crash.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: usb-creator-gtk 0.2.40ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7
Uname: Linux 3.5.0-18-generic i686
NonfreeKernelModules: wl fglrx
ApportVersion: 2.6.1-0ubuntu4
Architecture: i386
Date: Mon Oct 22 23:41:17 2012
ExecutablePath: /usr/bin/usb-creator-gtk
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
InterpreterPath: /usr/bin/python2.7
MarkForUpload: True
ProcCmdline: /usr/bin/python /usr/bin/usb-creator-gtk
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0xb70cbbb4: movl $0xffffffff,0x4(%eax)
 PC (0xb70cbbb4) ok
 source "$0xffffffff" ok
 destination "0x4(%eax)" (0x00000004) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: usb-creator
StacktraceTop:
 ?? () from /lib/i386-linux-gnu/libdbus-1.so.3
 ?? () from /lib/i386-linux-gnu/libdbus-1.so.3
 ?? () from /lib/i386-linux-gnu/libdbus-1.so.3
 ?? () from /lib/i386-linux-gnu/libdbus-1.so.3
 ?? () from /lib/i386-linux-gnu/libdbus-1.so.3
Title: usb-creator-gtk crashed with SIGSEGV
UpgradeStatus: Upgraded to quantal on 2012-10-02 (19 days ago)
UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare

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