python2.7 crashed with SIGSEGV

Bug #768109 reported by DJ_HOEK
68
This bug affects 13 people
Affects Status Importance Assigned to Milestone
kupfer
Invalid
Undecided
Unassigned
dbus-python (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Binary package hint: python2.7

1) ubuntu 11.04
2) 2.7.1-5ubuntu2 (python2.7)
3) i didn't expect anything to happen because it happens right after booting
4) crash

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: python2.7-minimal 2.7.1-5ubuntu2
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Wed Apr 20 21:41:36 2011
ExecutablePath: /usr/bin/python2.7
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
ProcCmdline: python indicator-applet-skype.py
ProcEnviron:
 LANGUAGE=en_US:en
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f5a56320ad0: movl $0xffffffff,0x4(%rdi)
 PC (0x7f5a56320ad0) ok
 source "$0xffffffff" ok
 destination "0x4(%rdi)" (0x00000004) 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 natty on 2011-04-18 (2 days ago)
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev sambashare tape video

Revision history for this message
DJ_HOEK (dirkjanhoek) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

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

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
tags: added: apport-failed-retrace
tags: removed: need-amd64-retrace
Revision history for this message
Matthias Klose (doko) wrote :

likely an issue with the bindings

visibility: private → public
affects: python2.7 (Ubuntu) → dbus-python (Ubuntu)
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in dbus-python (Ubuntu):
status: New → Confirmed
Revision history for this message
Karol Będkowski (karol-bedkowski) wrote :
Changed in kupfer:
status: New → Confirmed
Revision history for this message
KSSG (kssg) wrote :

I also get this, but I couldn't get any debug information (crash is silent even in debug mode). I am glad someone reported it first with more relevant data.

Revision history for this message
mcsan (octagonhead) wrote :

As a workaround, try disabling all of the following plugins (which use dbus-python):

Empathy
Gajim
Getting Things GNOME
Gwibber
Gwibber (Simple)
Selected File
Notes
Pidgin
System Services
Skype
Thunar
Tracker
Tracker 0.6

Revision history for this message
Karol Będkowski (karol-bedkowski) wrote :

This bug can't be reproduced in current version of kupfer & python-dbus.

Changed in kupfer:
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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