python2.7 crashed with SIGSEGV

Bug #1052045 reported by michael da cova on 2012-09-17
22
This bug affects 4 people
Affects Status Importance Assigned to Milestone
dbus-python (Ubuntu)
Undecided
Unassigned

Bug Description

go this crash after installing skype wrapper from

http://www.omgubuntu.co.uk/2012/09/skype-wrapper-for-ubuntu-gets-updated?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+d0od+%28OMG!+Ubuntu!%29&utm_content=FaceBook

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.2-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Mon Sep 17 17:12:29 2012
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/python2.7
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
ProcCmdline: python indicator-applet-skype.py
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7ff7d3e99d1c: mov %rax,0x8(%rdx)
 PC (0x7ff7d3e99d1c) ok
 source "%rax" ok
 destination "0x8(%rdx)" (0x00000008) not located in a known VMA region (needed writable region)!
 Stack memory exhausted (SP below stack segment)
SegvReason: writing 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
 ?? () 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
UpgradeStatus: Upgraded to quantal on 2012-09-07 (9 days ago)
UserGroups: adm cdrom dip floppy lpadmin plugdev sambashare sudo vboxusers

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

tags: added: apport-failed-retrace
tags: removed: need-amd64-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