usb creator crashes after asking for password

[waspinator]

Using the USB creator to create a startup disk of ubuntu 12.10 32bit.

USB creator asks for a password because of a "System policy prevents installing the bootloader". (I do not remember setting any such policy, and the details do not give any instructions on where you change system policy in System Settings.)

I assume that it wants my login password, although it does not say that anywhere. I input my password and then a window pops up that says "The application Startup Disk Creator has closed unexpectedly". I have attempted to relaunch it several times and redo the operation without success.

I am disappointed that it is easier to make a start up disk for ubuntu in windows using http://www.linuxliveusb.com .

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: usb-creator-gtk 0.2.40ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7
Uname: Linux 3.5.0-18-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 2.6.1-0ubuntu6
Architecture: i386
Date: Tue Nov 13 17:18:50 2012
InstallationDate: Installed on 2012-10-20 (24 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2)
MarkForUpload: True
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: usb-creator
UpgradeStatus: No upgrade log present (probably fresh install)

[Benjamin Kerensa (bkerensa)]

I do not believe that this is a bug in reviewing the UsbCreatorLog I can see that the reason the application crashed was because you did not provide a correct password.

I would encourage you to read about User Management in Ubuntu https://help.ubuntu.com/12.10/serverguide/user-management.html

Then check your password and try again and if that does not resolve the issue please comment back here so we can help you further.

[waspinator (patrickwasp)]

You're telling me that crashing because of an incorrect password is the expected behaviour? How is this acceptable in any circumstance? Never mind the fact that it doesn't say which password it wants. I only have one user account on this computer, and so only one password I know of.

The bottom line is that usb creator shouldn't crash even if entered the wrong password.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Prada (pradacr)]

For the moment it is better to use the command dd, as in this guide:

http://www.geeks3d.com/20130712/how-to-create-a-linux-mint-15-bootable-usb-flash-drive

It solves the problem.

[James G. Garner (cominatyalive)]

USB dd does not always work either. I used the command "dd if=path/to/iso of=/dev/sdf and it creates the image just fine with no errors. It also shows the complete & written counts. But when rebooting my machine to USB drive, it does not load and says please choose the correct boot device.

[James G. Garner (cominatyalive)]

I am also experiencing the password prompt & the error "failed to install bootloader" when using (startup Disk Creator) on 14.10 64-bit Ubuntu.

[James G. Garner (cominatyalive)]

Ok, I started the procedure all over again from the beginning using Startup Disk Creator. It hangs upon 70% for like ages, then this time, when it asks for your password to install the boot loader, I quickly entered my password this time. Last time I was away from my computer for several minutes when it did this and it did not take. This time I was eyeballing for the message, quickly entered my password on the spot and it finished successfully. Now I will see if my pen drive actually loads the iso image upon boot from the USB. If it does not, I will let you know either way. I am also wary of iso images one receives from sourceforge.net, as one does not always receive an undamaged iso. Regards: James

[James G. Garner (cominatyalive)]

No, it did not boot my ISO. Again, yet another error at boot (Failed To Load COM32 file gfxboot.c32) Well, I am at my wits end with this. What can you do if one cannot simply create a bootable usb pendrive with your iso of choice? I will go back to using DVD disks. This is why so many go back to windows. Using Syslinux dd did not work either. May be a bad iso, I will try a newer iso image. Will inform. I tried. But just too many stop signs.

[Yu Ning (yuningdodo)]

Hi James, the "COM32" error is actually bug #1325801, as a workaround you can type "live" and press enter when you saw that error message, that will boot to the live mode, and you can find the installer icon on the live desktop. Would you like to give it a try?