after setting the iso in one usb and setting the startup on the ssd card the app hang
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
usb-creator (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: usb-creator
-- Starting up at 21:36:51 --
[21:36:51] new device:
{'capacity': dbus.UInt64(
[21:36:51] adding: /dev/sdd1
[21:36:51] new device:
{'capacity': dbus.UInt64(
[21:36:51] adding: /dev/sde1
[21:36:52] new device:
{'capacity': dbus.UInt64(
[21:36:52] adding: /dev/sdc1
[21:37:05] mounting /media/
[21:37:05] updating dest_status as part of update_row_state
well i do not get much of it but after setting the input (kingston) and the output the sd card (eeepc) the crash happen...
hope to be of help
ubuntu 8.10
ubuntu@ubuntu:~$ sudo apt-get install usb-creator
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
usb-creator
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 24.1kB of archives.
After this operation, 205kB of additional disk space will be used.
Get:1 http://
Fetched 24.1kB in 0s (43.1kB/s)
Selecting previously deselected package usb-creator.
(Reading database ... 83501 files and directories currently installed.)
Unpacking usb-creator (from .../usb-
Processing triggers for man-db ...
Setting up usb-creator (0.1.10) ...
ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/bin/
InterpreterPath: /usr/bin/python2.5
Package: usb-creator 0.1.10
PackageArchitec
ProcAttrCurrent: unconfined
ProcCmdline: /usr/bin/python /usr/bin/
ProcEnviron:
PATH=/
LANG=en_US.UTF-8
SHELL=/bin/bash
PythonArgs: ['/usr/
SourcePackage: usb-creator
Title: usb-creator crashed with TypeError in update_row_state()
Uname: Linux 2.6.27-8-eeepc i686
UserGroups:
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 #287318, 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.