usb-creator shrows segmentation fault when trying to create Ubuntu 10.04 i386 disk

Confirmed.

I'll just add that I have the same issue - I have tried usb-creator on two different ISOs (one for FreeBSD 8.1 LiveCD, the other for Ubuntu 10.10 netbook), both onto a 16 GB Corsair. This flash drive has had other OS on it before, notably Backtrack 4.

I set the Persistence file to 4 GB in the options the first time, I think 3GB the second time.

The program took 8 or 10 minutes to build the persistence file. I was off doing other things at the time that ended, so it may be that it crashed right at the end of that portion of the process.

This line showed up in my .xsessions-errors - perhaps it is indicative of something. The lines around it were not relevant.

computer:///Corsair Flash Voyager.drive -> /usr/share/icons/Humanity/devices/48/drive-removable-media-usb.svg

And this is the end of .usb-creator.log:
usb-creator 2010-09-07 19:34:39,463 (DEBUG) install.py:519: Writing /media/B330-3EB6/.disk/casper-uuid-generic
usb-creator 2010-09-07 19:34:39,463 (DEBUG) install.py:519: Writing /media/B330-3EB6/.disk/cd_type
usb-creator 2010-09-07 19:34:39,463 (DEBUG) install.py:519: Writing /media/B330-3EB6/.disk/info
usb-creator 2010-09-07 19:34:39,464 (DEBUG) install.py:219: mangle_syslinux
usb-creator 2010-09-07 19:34:39,467 (DEBUG) install.py:310: create_persistence
usb-creator 2010-09-07 19:34:39,469 (DEBUG) misc.py:127: ['dd', 'if=/dev/zero', 'bs=1M', 'of=/media/B330-3EB6/casper-rw', 'count=4095']
usb-creator 2010-09-07 19:42:08,982 (DEBUG) misc.py:127: ['mkfs.ext3', '-F', '/media/B330-3EB6/casper-rw']
usb-creator 2010-09-07 19:43:56,577 (DEBUG) install.py:335: sync

Looking at the mounted flash drive, it appears to have a complete system on it. I will take it home and see if it actually boots my netbook, and report back.

I took it home and booted my netbook. It boots just fine. :) 'df' reports 4GB partition. The actual size is 16 GB. I presume the 4GB is because that's the size of the persistence file? The rest of the stick is apparently nonexistent to the system.

So, bottom line, the segfault appears to occur after everything essential is completed.

Oh - I should correct one thing - the Ubuntu version on the stick was also 10.04, not 10.10 as I reported above. However the segfault occurs regardless of OS.

ISO: maverick-10.10-i386.iso
OS: maverick-10.10-i386 (fully updated as of now)
Destination: 4GB "0781:5567 SanDisk Corp. Cruszer Blade" (should be cruzer actually...another bug?)

Writing disk until 95%, then starts installing bootloader, and window disappears.
Running as root on terminal, message remaining is 'Segmentation Fault'.

When trying to boot usb stick, isolinux complains there is no default config defined(or similar message)

Note:
This is not the first time I had this problem, sometimes the usb stick works though.
Pity unetbootin does not work well with the new versions of ubuntu(isos).

Tried the same thing with a "ID 0951:1607 Kingston Technology DataTraveler 100" 2GB and it worked fine.
Usb-creator just exits with no message.

Note:on every try I erased the disk first and set to 'not store data on usb'(or similar configuration)

possible solution:
I had the same problem with 10.04.1-AMD64 on my current Ubuntu 10.10 kernel: 2.6.36-020636-generic.
Try another tool e.g. unetbootin, which works perfecty. usb-creator was a rather buggy tool - and still is...

Still crashes in Ubuntu 12.10.

it happens on 12.04 (amd64) also with the 10.04 iso.

It happens in 12.10 32/64 and 13.04 32/64. Here is one of the errors, it is similar to the other versions:

usb-creator-gtk[3310]: segfault at 4 ip 00007fd6b0570d80 sp 00007fffcdfe3718 error 6 in libdbus-1.so.3.7.2[7fd6b054c000+43000]

It also happens in ubuntu 13.04 when trying to create a bootable usb stick for xubuntu 12.04.2.

Is it possible that the bugs #859539, #1184344 and #1076176 are duplicates of this (very old) bug?

And if you google it you find even more people who are affected by this:
- http://askubuntu.com/questions/232775/making-a-12-10-bootable-usb-drive-usb-creator-gtk-fails-with-a-seg-fault
- http://fahmifadin.blogspot.de/2012/03/install-ubuntu-fromusbstick.html#Known_Issues
- http://ubuntuforums.org/showthread.php?t=1597398&p=9980487#post9980487
…

cagliostro, thank you for reporting this and helping make Ubuntu better. However, your crash report is missing. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer. First, execute at a terminal:
cd /var/crash && sudo rm * ; sudo apt-get update && sudo apt-get -y upgrade && sudo service apport start force_start=1

If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart.

Now reproduce the crash, then open your file manager, navigate to your /var/crash directory and open the crash report you wish to submit.
If this fails you will have to open a terminal and file your report with 'ubuntu-bug /var/crash/_my_crash_report.crash' where _my_crash_report.crash is the crash you would like to report. If you get an error that you aren't allowed to access this report you will have to file it with 'sudo ubuntu-bug /var/crash/_my_crash_report.crash'. If you run the command against the crash report and it does nothing, you may be affected by https://bugs.launchpad.net/ubuntu/+source/apport/+bug/994921 . In order to WORKAROUND this, one would need to open the following file via a command line:
gksudo gedit /etc/apport/crashdb.conf

and comment out the line:
'problem_types': ['Bug', 'Package'],

by changing it to:
# 'problem_types': ['Bug', 'Package'],

Save, close, and try to file the crash report again via:
ubuntu-bug /var/crash/_my_crash_report.crash

I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently.

Thank you for your understanding.

Helpful bug reporting tips:
https://help.ubuntu.com/community/ReportingBugs