usb disk start creator crash

[Rene]

Binary package hint: usb-creator

When open, shows a crasah alert.

ProblemType: Crash
Architecture: i386
CheckboxSubmission: 0e9cfd361a8107bcb407e297ce1d5607
CheckboxSystem: 87880255eb25c225eddac4c3b69ee22f
Date: Mon Oct 12 13:22:42 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/usb-creator-gtk
InterpreterPath: /usr/bin/python2.6
Package: usb-creator-gtk 0.2.9
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/usb-creator-gtk
ProcEnviron:
 LANG=es_CL.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-13.44-generic
PythonArgs: ['/usr/bin/usb-creator-gtk']
SourcePackage: usb-creator
Title: usb-creator-gtk crashed with NameError in pixbuf_data_func()
Traceback:
 Traceback (most recent call last):
   File "/usr/lib/python2.6/dist-packages/usbcreator/frontends/gtk/frontend.py", line 315, in pixbuf_data_func
     cell.set_property('icon-name', icon)
 NameError: global name 'icon' is not defined
Uname: Linux 2.6.31-13-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors:
 (gnome-settings-daemon:2050): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (polkit-gnome-authentication-agent-1:2153): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (nautilus:2142): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed
 (gnome-panel:2141): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -15 and height 24
 (gnome-panel:2141): Gdk-WARNING **: /build/buildd/gtk+2.0-2.18.2/gdk/x11/gdkdrawable-x11.c:952 drawable is not a pixmap or window

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #436469, 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.