python2.7 crashed with SIGSEGV in dbus_message_get_reply_serial()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
dbus-python (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
I don't know what triggered this. I ended a Skype call and started a chat, but it might have been something in the backround.
Quantal (dev. branch) 12.10 Beta1
ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: python2.7-minimal 2.7.3-5ubuntu2
ProcVersionSign
Uname: Linux 3.5.0-15-generic x86_64
ApportVersion: 2.5.2-0ubuntu4
Architecture: amd64
Date: Tue Sep 25 21:59:26 2012
ExecutablePath: /usr/bin/python2.7
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120905.2)
ProcCmdline: python indicator-
ProcEnviron:
PATH=(custom, no user)
LANG=de_DE.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7f546fc1e7a3: movzbl (%rax),%eax
PC (0x7f546fc1e7a3) ok
source "(%rax)" (0x00000108) not located in a known VMA region (needed readable region)!
destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: python2.7
StacktraceTop:
?? () from /lib/x86_
?? () from /lib/x86_
dbus_message_
?? () from /lib/x86_
?? () from /lib/x86_
Title: python2.7 crashed with SIGSEGV in dbus_message_
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
visibility: | private → public |
affects: | python2.7 (Ubuntu) → dbus-python (Ubuntu) |
StacktraceTop:
?? ()
?? ()
?? ()
?? ()
?? ()