usb-creator-gtk crashed with SIGSEGV
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| usb-creator (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
since i am using 12.10, I oftenly fail to make usb bootable. startup disk creator sometimes crashes while creating persistance file or finishing.
I am unable to see any log error/messages.
ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: usb-creator-gtk 0.2.40ubuntu1
ProcVersionSign
Uname: Linux 3.5.0-22-generic x86_64
ApportVersion: 2.5.2-0ubuntu4
Architecture: amd64
CrashCounter: 1
Date: Mon Jan 28 01:28:39 2013
ExecutablePath: /usr/bin/
InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1)
InterpreterPath: /usr/bin/python2.7
ProcCmdline: /usr/bin/python /usr/bin/
ProcEnviron:
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7fcd1d72ad00: movl $0xffffffff,
PC (0x7fcd1d72ad00) 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 quantal on 2013-01-27 (0 days ago)
UserGroups: adm cdrom dip disk lpadmin plugdev sambashare sudo vboxusers
| abdul wadood (awadoodraj) 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 #915626, 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.