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

Bug #1167029 reported by userDepth on 2013-04-09
This bug affects 5 people
Affects Status Importance Assigned to Milestone
usb-creator (Ubuntu)

Bug Description

Crash while making a maximum size persistence file.

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: usb-creator-gtk 0.2.47
ProcVersionSignature: Ubuntu 3.8.0-17.27-generic 3.8.6
Uname: Linux 3.8.0-17-generic x86_64
ApportVersion: 2.9.2-0ubuntu5
Architecture: amd64
CrashCounter: 1
Date: Tue Apr 9 17:40:36 2013
ExecutablePath: /usr/bin/usb-creator-gtk
InstallationDate: Installed on 2013-03-29 (11 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130328)
InterpreterPath: /usr/bin/python3.3
MarkForUpload: True
ProcCmdline: /usr/bin/python3 /usr/bin/usb-creator-gtk
 Segfault happened at: 0x7f0f782237c3: movzbl (%rax),%eax
 PC (0x7f0f782237c3) ok
 source "(%rax)" (0x00000040) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: usb-creator
 ?? () from /lib/x86_64-linux-gnu/
 ?? () from /lib/x86_64-linux-gnu/
 dbus_message_get_reply_serial () from /lib/x86_64-linux-gnu/
 ?? () from /lib/x86_64-linux-gnu/
 ?? () from /lib/x86_64-linux-gnu/
Title: usb-creator-gtk crashed with SIGSEGV in dbus_message_get_reply_serial()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

userDepth (markonuvo) wrote :
information type: Private → Public
Launchpad Janitor (janitor) wrote :

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

Changed in usb-creator (Ubuntu):
status: New → Confirmed
Ryan Sevelj (rsevs3) wrote :

I found that when i resized my usb partition to 2gb and formatted to FAT16 then USB Creator did not crash.

 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()

tags: added: apport-failed-retrace
tags: removed: need-amd64-retrace
Marco Lackovic (marco-lackovic) wrote :

Formatting my 2GB drive to FAT16 didn't work for me.
Screenshot attached.

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

Other bug subscribers