usb-creator-gtk crashed with SIGSEGV

[ionut]

hello, i got 3 crashes in 13.04:
i downloaded the yesterday (18 03 2013 ddmmyyyy) daily build of 13.04 and when i tried to create a usb start disk i got 3 out of 3 crashes when tried to erase disk (i finally did'it with gparted) second i got when installing bootloder, after the password it crashed, 3'rd time i got an error at the end, after bootloader installation, but the pendrive is good, it's more slow than usually but it boots and enters unity after about 2-3 minutes .

cheers.

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: usb-creator-gtk 0.2.46.1
ProcVersionSignature: Ubuntu 3.8.0-7.15-generic 3.8.0
Uname: Linux 3.8.0-7-generic x86_64
ApportVersion: 2.9.1-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Sun Mar 17 23:51:10 2013
ExecutablePath: /usr/bin/usb-creator-gtk
InstallationDate: Installed on 2013-01-29 (47 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130129)
InterpreterPath: /usr/bin/python3.3
MarkForUpload: True
ProcCmdline: /usr/bin/python3 /usr/bin/usb-creator-gtk
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f08a479bd80: movl $0xffffffff,0x4(%rdi)
 PC (0x7f08a479bd80) 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 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.