usb-creator-kde crashed with SIGSEGV in QWidgetPrivate::deleteTLSysExtra()

[Kornik]

.

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: usb-creator-kde 0.2.54
ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5
Uname: Linux 3.13.0-16-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.13.3-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Mar 11 19:34:13 2014
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/usb-creator-kde
InstallationDate: Installed on 2014-03-08 (3 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140307)
InterpreterPath: /usr/bin/python3.4
ProcCmdline: /usr/bin/python3 /usr/bin/usb-creator-kde
SegvAnalysis:
 Segfault happened at: 0x7fa6179b1bea <_ZN14QWidgetPrivate16deleteTLSysExtraEv+58>: mov 0x10(%rax),%rdi
 PC (0x7fa6179b1bea) ok
 source "0x10(%rax)" (0x00000010) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: usb-creator
StacktraceTop:
 QWidgetPrivate::deleteTLSysExtra() () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
 QWidgetPrivate::deleteExtra() () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
 QWidgetPrivate::~QWidgetPrivate() () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
 ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
 QObject::~QObject() () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
Title: usb-creator-kde crashed with SIGSEGV in QWidgetPrivate::deleteTLSysExtra()
UDisksDump: Error: [Errno 2] No such file or directory: 'udisks'
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 #1289026, 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.