python2.7 crashed with SIGSEGV in dbus_message_get_reply_serial()

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

Bug Description

All I did was boot and log into Ubuntu.

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 x86_64
NonfreeKernelModules: wl
ApportVersion: 2.5.1-0ubuntu7
Architecture: amd64
Date: Sun Sep 16 21:21:07 2012
ExecutablePath: /usr/bin/python2.7
InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64+mac (20120822.4)
ProcCmdline: python
 PATH=(custom, no username)
 Segfault happened at: 0x7f774245a653: movzbl (%rax),%eax
 PC (0x7f774245a653) ok
 source "(%rax)" (0x000000b2) 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/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: python2.7 crashed with SIGSEGV in dbus_message_get_reply_serial()
UpgradeStatus: Upgraded to quantal on 2012-09-15 (1 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Charles Lease (mellowchuck-y) wrote :

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

tags: added: apport-failed-retrace
tags: removed: need-amd64-retrace
Matthias Klose (doko) on 2012-11-28
affects: python2.7 (Ubuntu) → dbus-python (Ubuntu)
information type: Private → Public
Launchpad Janitor (janitor) wrote :

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

Changed in dbus-python (Ubuntu):
status: New → Confirmed

If this error is still occurring, it might be helpful if dbus-1-dbg package was installed to give a better stacktrace.

Charles Lease (mellowchuck-y) wrote :

Actually, this error has stopped occurring for me since I've received some python updates to my system.

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

Duplicates of this bug

Other bug subscribers