usb-creator-gtk crashed with SIGSEGV in PyErr_Restore()

Bug #838167 reported by Tim Gardner on 2011-08-31
46
This bug affects 9 people
Affects Status Importance Assigned to Milestone
usb-creator (Ubuntu)
Medium
Unassigned

Bug Description

usb-creator-gtk crashed with SIGSEGV in PyErr_Restore()

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: usb-creator-gtk 0.2.31.2
ProcVersionSignature: Ubuntu 3.0.0-9.15-generic 3.0.3
Uname: Linux 3.0.0-9-generic x86_64
Architecture: amd64
Date: Wed Aug 31 08:57:11 2011
ExecutablePath: /usr/bin/usb-creator-gtk
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110829.1)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/usb-creator-gtk --iso=ubuntu-11.04-desktop-amd64.iso
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x4cc490 <PyErr_Restore+128>: mov (%rdi),%rax
 PC (0x004cc490) ok
 source "(%rdi)" (0x100007f7640) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: usb-creator
StacktraceTop:
 PyErr_Restore ()
 PyErr_Format ()
 _Py_CheckRecursiveCall ()
 PyObject_Call ()
 ?? () from /usr/lib/python2.7/dist-packages/_dbus_bindings.so
Title: usb-creator-gtk crashed with SIGSEGV in PyErr_Restore()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Tim Gardner (timg-tpi) wrote :
visibility: private → public

StacktraceTop:
 PyErr_Restore (type=<type at remote 0x83c320>, value=<optimized out>, traceback=<optimized out>) at ../Python/errors.c:47
 PyErr_SetObject (value='maximum recursion depth exceeded while calling a Python object', exception=<type at remote 0x83c320>) at ../Python/errors.c:57
 PyErr_Format (exception=<type at remote 0x83c320>, format=<optimized out>) at ../Python/errors.c:549
 _Py_CheckRecursiveCall (where=<optimized out>) at ../Python/ceval.c:629
 PyObject_Call (func=<type at remote 0x7f764fabc2c0>, arg=<optimized out>, kw=<optimized out>) at ../Objects/abstract.c:2527

Changed in usb-creator (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Launchpad Janitor (janitor) wrote :

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

Changed in usb-creator (Ubuntu):
status: New → Confirmed
Fabio Marconi (fabiomarconi) wrote :

present in quantal fully updated at 20120909

tags: added: quantal
Doug McMahon (mc3man) wrote :

On 12.10, Beta1 & current dailies this happens at least 90% of the time. (just tried 7 times, 6 fails, 1 good
All crashes occur either right at the beginning of the 'creating bootloader' or just after the bootloader during the finishing step.
In both cases the usb created is worthless, the only diff is when at the beginning the loop device is left mounted ^ the usb drive remains in use for some time.

have vid's of all 3 possibilities though this is quite simple to recreate, just make some usb boot drives..

Nicola Corti (corti-nico) wrote :

The same happens for me, i'm not able to create a USB disk anymore.
I'm on fully updateded Ubuntu 12.10.
I attach the log of usb-creator.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers