Ubuntu
dbus-python package

python2.7 crashed with SIGSEGV in dbus_message_get_reply_serial()

Bug #1051756 reported by Charles Lease on 2012-09-17

26

This bug affects 3 people

Affects		Status	Importance	Assigned to	Milestone
	dbus-python (Ubuntu)	Confirmed	Undecided	Unassigned

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 indicator-applet-skype.py
ProcEnviron:
PATH=(custom, no username)
LANG=en_US.UTF-8
SHELL=/bin/bash
SegvAnalysis:
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
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: 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

Tags:

Revision history for this message

Charles Lease (mellowchuck-y) wrote on 2012-09-17:

#1

Dependencies.txt Edit (890 bytes, text/plain; charset="utf-8")
Disassembly.txt Edit (594 bytes, text/plain; charset="utf-8")
ProcMaps.txt Edit (49.8 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (796 bytes, text/plain; charset="utf-8")
Registers.txt Edit (715 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (2.7 KiB, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (10.9 KiB, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2012-09-17:

#2

StacktraceTop:
?? ()
?? ()
?? ()
?? ()
?? ()

Revision history for this message

Apport retracing service (apport) wrote on 2012-09-17: Stacktrace.txt

#3

Stacktrace.txt Edit (383 bytes, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2012-09-17: StacktraceSource.txt

#4

StacktraceSource.txt Edit (192 bytes, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2012-09-17: ThreadStacktrace.txt

#5

ThreadStacktrace.txt Edit (39.0 KiB, text/plain)

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

Revision history for this message

Launchpad Janitor (janitor) wrote on 2013-02-16:

#6

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

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

Revision history for this message

Daniel Letzeisen (dtl131) wrote on 2013-02-16:

#7

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

Revision history for this message

Charles Lease (mellowchuck-y) wrote on 2013-02-16:

#8

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

Report a bug

This report contains Public information

Everyone can see this information.

Duplicates of this bug

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

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