usb-creator-gtk crashed with SIGSEGV
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| usb-creator (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
usb-creator reliably crashes when trying to create a USB startup disc of the current Saucy daily (circa 2013/08/06). It does this at about the 42% mark of "copying files", and does it regardless of whether or not a persistence file is selected.
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: usb-creator-gtk 0.2.48
ProcVersionSign
Uname: Linux 3.10.0-6-generic x86_64
ApportVersion: 2.12-0ubuntu2
Architecture: amd64
CrashCounter: 1
Date: Tue Aug 6 12:49:24 2013
ExecutablePath: /usr/bin/
InterpreterPath: /usr/bin/python3.3
MarkForUpload: True
ProcCmdline: /usr/bin/python3 /usr/bin/
ProcEnviron:
LANGUAGE=en_AU:en
PATH=(custom, user)
XDG_RUNTIME_
LANG=en_AU.UTF-8
SHELL=/bin/zsh
SegvAnalysis:
Segfault happened at: 0x7fd52918dd80: movl $0xffffffff,
PC (0x7fd52918dd80) ok
source "$0xffffffff" ok
destination "0x4(%rdi)" (0x00000004) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: usb-creator
StacktraceTop:
?? () from /lib/x86_
?? () from /lib/x86_
?? () from /lib/x86_
?? () from /lib/x86_
?? () from /lib/x86_
Title: usb-creator-gtk crashed with SIGSEGV
UpgradeStatus: Upgraded to saucy on 2013-07-29 (7 days ago)
UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sbuild sudo
| Chris Halse Rogers (raof) wrote | #1 |
| Apport retracing service (apport) wrote This bug is a duplicate | #2 |
| information type: | Private → Public |
| tags: | removed: need-amd64-retrace |
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #649139, 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.