usb-creator-gtk crashes with error "An unhandled exception occurred: Argument 3 does not allow None as a value"

Bug #841713 reported by CaptainMark on 2011-09-05
This bug affects 1 person
Affects Status Importance Assigned to Milestone
usb-creator (Ubuntu)

Bug Description

Error on launch of program. Renders program unusable, seems only to affect 11.10

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: usb-creator-gtk
ProcVersionSignature: Ubuntu 3.0.0-10.16-generic 3.0.4
Uname: Linux 3.0.0-10-generic x86_64
Architecture: amd64
Date: Mon Sep 5 11:24:27 2011
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110825.1)
PackageArchitecture: all
SourcePackage: usb-creator
UpgradeStatus: No upgrade log present (probably fresh install)

CaptainMark (imark-skinner) wrote :
description: updated
Brian Murray (brian-murray) wrote :

From UsbCreatorLog.txt:
usb-creator 2011-09-05 11:24:06,212 (DEBUG) add_source: /home/mark/Downloads/lubuntu-11.10-beta1-desktop-amd64.iso
usb-creator 2011-09-05 11:24:06,216 (ERROR) usb-creator-gtk:79: Unhandled exception:
Traceback (most recent call last):
  File "/usr/bin/usb-creator-gtk", line 62, in <module>
  File "/usr/lib/python2.7/dist-packages/usbcreator/frontends/gtk/", line 144, in __init__
    self.backend.add_image(os.path.join(download_dir, fname))
  File "/usr/lib/python2.7/dist-packages/usbcreator/backends/base/", line 51, in add_image
  File "/usr/lib/python2.7/dist-packages/usbcreator/frontends/gtk/", line 185, in add_source
  File "/usr/lib/python2.7/dist-packages/usbcreator/frontends/gtk/", line 764, in _append_to_list_and_select
    treeview.set_cursor(model.get_path(new_iter), None, None)
  File "/usr/lib/python2.7/dist-packages/gi/", line 43, in function
    return info.invoke(*args, **kwargs)
TypeError: Argument 3 does not allow None as a value

Brian Murray (brian-murray) wrote :

I was unable to recreate this using the same lubuntu iso and usb-creator version 0.2.32.

Changed in usb-creator (Ubuntu):
importance: Undecided → Medium
CaptainMark (imark-skinner) wrote :

possibly a conflicting dependency has been updated within the last 24 hours, i can no longer reproduce this either, it was occuring on 2 completely separate machines and now both machines are working correctly after 06/09/2011 updates

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers