usb-creator-gtk crashed with SIGSEGV

Bug #1199344 reported by Timo Jyrinki
This bug report is a duplicate of:  Edit Remove
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
usb-creator (Ubuntu)
New
Undecided
Unassigned

Bug Description

Happened on saucy when trying to write 12.04.2 LTS image onto USB stick.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: usb-creator-gtk 0.2.48
ProcVersionSignature: Ubuntu 3.10.0-2.10-generic 3.10.0
Uname: Linux 3.10.0-2-generic x86_64
ApportVersion: 2.10.2-0ubuntu4
Architecture: amd64
CheckboxSubmission: 1896b893828b4203b948b1eb6546be06
CheckboxSystem: d00f84de8a555815fa1c4660280da308
Date: Tue Jul 9 15:04:39 2013
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/usb-creator-gtk
InstallationDate: Installed on 2012-03-16 (479 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120316)
InterpreterPath: /usr/bin/python3.3
MarkForUpload: True
ProcCmdline: /usr/bin/python3 /usr/bin/usb-creator-gtk
SegvAnalysis:
 Segfault happened at: 0x7f64e199edb0: movl $0xffffffff,0x4(%rdi)
 PC (0x7f64e199edb0) ok
 source "$0xffffffff" ok
 destination "0x4(%rdi)" (0x00000004) not located in a known VMA region (needed writable region)!
 Stack memory exhausted (SP below stack segment)
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: usb-creator
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
 ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
 ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
 ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
 ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
Title: usb-creator-gtk crashed with SIGSEGV
UpgradeStatus: Upgraded to saucy on 2013-06-04 (34 days ago)
UserGroups: adm autopilot cdrom dip lp lpadmin motion plugdev sambashare sudo

Revision history for this message
Timo Jyrinki (timo-jyrinki) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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 #1199158, 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.

information type: Private → Public
tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
  • Duplicate of a private bug Remove

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.