usb-creator-gtk crashed with UnboundLocalError in _udisks_partition_added(): local variable 'mount' referenced before assignment
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
usb-creator (Ubuntu) |
Confirmed
|
Medium
|
Unassigned |
Bug Description
Got apport window after running usb-creator-gtk and choosing cleaning (formatting) the usb-drive.
$ usb-creator-gtk
isoinfo: Short read on old image
Traceback (most recent call last):
File "/usr/lib/
self.handles += [self.manager.
File "/usr/lib/
self.
File "/usr/lib/
self.
File "/usr/lib/
if mount:
UnboundLocalError: local variable 'mount' referenced before assignment
Traceback (most recent call last):
File "/usr/lib/
self.handles += [self.manager.
File "/usr/lib/
self.
File "/usr/lib/
self.
File "/usr/lib/
if mount:
UnboundLocalError: local variable 'mount' referenced before assignment
ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: usb-creator-gtk 0.2.52
ProcVersionSign
Uname: Linux 3.12.0-7-generic x86_64
ApportVersion: 2.12.7-0ubuntu3
Architecture: amd64
CurrentDesktop: GNOME
Date: Fri Dec 20 19:20:07 2013
ExecutablePath: /usr/bin/
InstallationDate: Installed on 2013-10-15 (65 days ago)
InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release amd64 (20131015)
InterpreterPath: /usr/bin/python3.3
ProcCmdline: /usr/bin/python3 /usr/bin/
ProcEnviron:
TERM=xterm
SHELL=/bin/bash
PATH=(custom, no user)
LANG=pl_PL.UTF-8
XDG_RUNTIME_
PythonArgs: ['/usr/
SourcePackage: usb-creator
Title: usb-creator-gtk crashed with UnboundLocalError in _udisks_
UpgradeStatus: Upgraded to trusty on 2013-11-05 (45 days ago)
UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo
tags: | removed: need-duplicate-check |
Changed in usb-creator (Ubuntu): | |
importance: | Undecided → Medium |
information type: | Private → Public |
Tobiasz Jarczyk, thank you for reporting this bug and helping make Ubuntu better. This would be a duplicate of bug 1092195 and so I am marking it as such. If for whatever reason the fix for that bug doesn't fix this, we could alway unmark the duplication and take it from there.
Thank you for your understanding.