python2.7 crashed with SIGSEGV in dbus_message_get_reply_serial()

Bug #1052204 reported by Ramo on 2012-09-17
This bug affects 3 people
Affects Status Importance Assigned to Milestone
dbus-python (Ubuntu)

Bug Description

rythmbox :p

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: python2.7-minimal 2.7.3-5ubuntu2
ProcVersionSignature: Ubuntu 3.5.0-14.19-generic 3.5.3
Uname: Linux 3.5.0-14-generic i686
ApportVersion: 2.5.2-0ubuntu1
Architecture: i386
CrashCounter: 1
Date: Mon Sep 17 22:35:15 2012
ExecutablePath: /usr/bin/python2.7
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha i386 (20120813.1)
ProcCmdline: python
 PATH=(custom, no user)
 Segfault happened at: 0xb6cf0ab6: movzbl (%eax),%eax
 PC (0xb6cf0ab6) ok
 source "(%eax)" (0x000000ff) 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: python2.7
 ?? () from /lib/i386-linux-gnu/
 ?? () from /lib/i386-linux-gnu/
 dbus_message_get_reply_serial () from /lib/i386-linux-gnu/
 ?? () from /lib/i386-linux-gnu/
 ?? () from /lib/i386-linux-gnu/
Title: python2.7 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

Ramo (zomar-net) wrote :

 #0 0xb6cf0ab6 in ?? ()
 No symbol table info available.
StacktraceSource: #0 0xb6cf0ab6 in ?? ()
StacktraceTop: ?? ()

tags: added: apport-failed-retrace
tags: removed: need-i386-retrace
visibility: private → public
Matthias Klose (doko) on 2012-10-04
affects: python2.7 (Ubuntu) → dbus-python (Ubuntu)
Launchpad Janitor (janitor) wrote :

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

Changed in dbus-python (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers