Ubuntu
usb-creator package

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

Bug #811026 reported by Tim Gardner
104
This bug affects 22 people
Affects Status Importance Assigned to Milestone
usb-creator (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Crash happens at the very end.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: usb-creator-gtk 0.2.30 [modified: usr/share/doc/usb-creator-gtk/changelog.gz]
ProcVersionSignature: Ubuntu 3.0.0-5.6-generic 3.0.0-rc7
Uname: Linux 3.0.0-5-generic x86_64
Architecture: amd64
CrashCounter: 1
Date: Thu Jul 14 12:41:55 2011
ExecutablePath: /usr/bin/usb-creator-gtk
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/usb-creator-gtk --iso oneiric-desktop-amd64-daily.iso
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7faf7eff8925: mov (%r12,%rdx,1),%edx
 PC (0x7faf7eff8925) ok
 source "(%r12,%rdx,1)" (0x0000005a) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading 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
 dbus_message_get_reply_serial () 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 in dbus_message_get_reply_serial()
UpgradeStatus: Upgraded to oneiric on 2011-06-09 (35 days ago)
UserGroups:

Revision history for this message
Tim Gardner (timg-tpi) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 _dbus_marshal_read_basic (str=0x1a4f638, pos=0, type=117, value=0x7fffff4ed46c, byte_order=255, new_pos=0x0) at ../../dbus/dbus-marshal-basic.c:549
 _dbus_header_get_field_basic (header=0x1a4f638, field=<value optimized out>, type=<value optimized out>, value=<value optimized out>) at ../../dbus/dbus-marshal-header.c:1342
 dbus_message_get_reply_serial (message=<value optimized out>) at ../../dbus/dbus-message.c:1030
 _dbus_connection_queue_received_message_link (connection=0x1a52570, link=0x1ac6f98) at ../../dbus/dbus-connection.c:478
 _dbus_transport_queue_messages (transport=0x1aae3d0) at ../../dbus/dbus-transport.c:1148

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in usb-creator (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Tim Gardner (timg-tpi)
visibility: private → public
Launchpad Janitor (janitor)
Changed in usb-creator (Ubuntu):
status: New → Confirmed
Jeremiah Njoroge (jnjoroge)
tags: added: raring
Revision history for this message
Cliff Carson (ccarson1) wrote :

Appears to be a consistant failure, unable to complete a run.

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

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

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