usb-creator-gtk crashed with SIGSEGV

[RedG]

Binary package hint: usb-creator

1) Raring Ringtail Beta
2) Just now I cant check what version... for some reason I think compiz isnt working right now... (restarted after usb-creator-gtk crash)
3) I expected it to make a bootable USB-drive...
4) usb-creator-gtk crached with a DBus error, the last message from usb-creator-gtk itself was that it was installing bootsector. I'll try to complete this bug-report with what DBus error message.

[RedG (tomas-redgoblin)]

This was the message about DBus:
DBus error org.gtk.Private.RemoteVolumeMonitor.NotFound: The given volume was not found

[Apport retracing service (apport)]

StacktraceTop:?? ()
?? ()
?? ()
?? ()
?? ()

[Apport retracing service (apport)]

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate an useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

python2.6: installed version 2.6.3-0ubuntu2, latest version: 2.6.4~rc1-0ubuntu1
python2.6-minimal: installed version 2.6.3-0ubuntu2, latest version: 2.6.4~rc1-0ubuntu1
libglib2.0-0: installed version 2.22.1-0ubuntu2, latest version: 2.22.2-0ubuntu1
lsb-base: installed version 4.0-0ubuntu4, latest version: 4.0-0ubuntu5
python-gobject: installed version 2.18.0-0ubuntu1, latest version: 2.18.0-0ubuntu2
libxml2: installed version 2.7.3.dfsg-1ubuntu2, latest version: 2.7.5.dfsg-1ubuntu1
devicekit-disks: installed version 007-1karmic1, latest version: 007-2

Please upgrade your system to the latest package versions. If you still
encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!

[Launchpad Janitor (janitor)]

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

[Bruce Pieterse (octoquad)]

This has recently occurred in raring as well.

[cariboo (cariboo)]

I can boot from the usb device after the crash, but unfortunately due to a momentary lack of reason, I created it using and AMD64 image when I needed to use an i386 iso

[Bruce Pieterse (octoquad)]

Mar 10 21:52:39 hostname kernel: [ 819.667145] usb-creator-gtk[4432]: segfault at 2f76000 ip 00007ff2d8fd6a33 sp 00007fffb7879c98 error 4 in libc-2.17.so[7ff2d8e81000+1be000]

[skybon (skybon-deactivatedaccount-deactivatedaccount)]

Does not affect usb-creator-kde.

[IC Raibow (icrbow)]

For some reason, it doesn't crash after relaunching (and not rebooting) and finishes cleanly.

[SongkrantMuneenaem (song.pdx)]

I got the same experience as wiz (wiz). It didn't crash after relaunching (and not rebooting) and finished cleanly.

[3vi1 (launchpad-net-eternaldusk)]

I tried this today on completely up to date Saucy desktop (writing the daily saucy .iso). My experience mirrors wiz's. First run crashes right after it starts on the bootsector. Relaunched when reporting this bug and second run completed successfully with exact same file/options.

[Michael Hastrup Bendsen (michael-bendsen)]

Looks like it's the same on Saucy too 13.10 X86_64 version too here, exactly the same issue

[Michael Hastrup Bendsen (michael-bendsen)]

Running daily Saucy builds too, in hope for seing some better things in the new release, to make me stay on ubuntu....sadly I see more and more issues that make me wanna leave ubuntu for good. have used since May 1th 2004. Ubuntu is just not Ubuntu any more.

[Shashank VRSN Sabniveesu (fossterer)]

It is still unresolved.. taking hours of time but giving no results...

[userDepth (binarydepth)]

KDE version works.

[bwallum (rbw2)]

Using Daily Build 5/10/13. Unable to create USB start up live install. AMD64 13.10, Saucy pc desktop

[Mr.Erbutw (erbutw)]

Aku sarankan untuk menggunakan ubuntu 12.04 atau 14.04
Semua yang lain versi tidak merekomendasikan jadi sangat buruk. dan hilang beberapa stabil versi untuk normal operasi.

[Bruce Pieterse (octoquad)]

Saucy and Raring are End of Life now. For those that did encounter this problem, please can you try again with 14.04 or 14.10 and post your result here. Since 14.04 I haven't had this problem again.