usb-creator-gtk crashed with SIGSEGV

Bug #704198 reported by Mario Limonciello
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
usb-creator (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: usb-creator

usb-creator-gtk was launched as root from within an oem-config plugin. It was launched just using subprocess.call(['usb-creator-gtk', '-n', '-i', 'FILENAME']) or so.

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: usb-creator-gtk 0.2.25
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic i686
Architecture: i386
Date: Mon Jan 17 16:55:38 2011
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-dell-maverick-une-20101010-0
ExecutablePath: /usr/bin/usb-creator-gtk
InstallationMedia: Ubuntu 10.10 "Maverick" - Build i386 LIVE Binary 20101010-01:50
InterpreterPath: /usr/bin/python2.6
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/usb-creator-gtk -n --iso /tmp/dell.iso
ProcCwd: /
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 LANGUAGE=en_US.UTF-8
 LC_COLLATE=C
SegvAnalysis:
 Segfault happened at: 0xfb3e86: movl $0xffffffff,0x4(%eax)
 PC (0x00fb3e86) ok
 source "$0xffffffff" ok
 destination "0x4(%eax)" (0x00000004) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: usb-creator
StacktraceTop:
 ?? () from /lib/libdbus-1.so.3
 ?? () from /lib/libdbus-1.so.3
 ?? () from /lib/libdbus-1.so.3
 ?? () from /lib/libdbus-1.so.3
 ?? () from /lib/libdbus-1.so.3
Title: usb-creator-gtk crashed with SIGSEGV
UserGroups:

Revision history for this message
Mario Limonciello (superm1) 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 Ubuntu 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.

visibility: private → public
tags: removed: need-i386-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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