python2.7 crashed with SIGSEGV in PyObject_Call()

Bug #1290571 reported by michael idowu
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
virt-manager (Ubuntu)
Expired
Medium
Unassigned

Bug Description

I really don't know why it crashed.

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: python2.7-minimal 2.7.6-7
ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5
Uname: Linux 3.13.0-16-generic x86_64
ApportVersion: 2.13.3-0ubuntu1
Architecture: amd64
CurrentDesktop: KDE
Date: Mon Mar 10 17:39:09 2014
ExecutablePath: /usr/bin/python2.7
InstallationDate: Installed on 2014-03-02 (7 days ago)
InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140227)
ProcCmdline: python /usr/share/virt-manager/virt-manager.py
ProcEnviron:
 LANGUAGE=en_CA:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x5319f9 <PyEval_CallObjectWithKeywords+57>: mov 0x80(%r10),%r12
 PC (0x005319f9) ok
 source "0x80(%r10)" (0x10000007f) not located in a known VMA region (needed readable region)!
 destination "%r12" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: python2.7
StacktraceTop:
 PyEval_CallObjectWithKeywords ()
 PyEval_CallFunction ()
 ?? () from /usr/lib/python2.7/dist-packages/gtk-2.0/gtk/_gtk.so
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
Title: python2.7 crashed with SIGSEGV in PyEval_CallObjectWithKeywords()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo

Revision history for this message
michael idowu (idowu-michael) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 PyObject_Call (kw=0x0, arg=0x7f3df4086be0, func=0x20ebbd0) at ../Objects/abstract.c:2525
 PyEval_CallObjectWithKeywords (func=0x20ebbd0, arg=0x7f3df4086be0, kw=0x0) at ../Python/ceval.c:3889
 PyEval_CallFunction (obj=0x20ebbd0, format=format@entry=0x7f3e0947f9da "(NNO)") at ../Python/modsupport.c:557
 pygtk_combo_box_row_separator_func_cb (model=<optimized out>, iter=0x7fff6b2515a0, user_data=0x20ebca0) at /build/buildd/pygtk-2.24.0/gtk/gtk.override:6200
 row_is_separator (path=0x0, iter=0x7fff6b251640, tree_view=0x1ead120) at /build/buildd/gtk+2.0-2.24.22/gtk/gtktreeview.c:2554

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in python2.7 (Ubuntu):
importance: Undecided → Medium
summary: - python2.7 crashed with SIGSEGV in PyEval_CallObjectWithKeywords()
+ python2.7 crashed with SIGSEGV in PyObject_Call()
tags: removed: need-amd64-retrace
Matthias Klose (doko)
affects: python2.7 (Ubuntu) → virt-manager (Ubuntu)
information type: Private → Public
Revision history for this message
Serge Hallyn (serge-hallyn) wrote :

Thanks for reporting this bug. Could you describe what you were doing at the time that it crashed? (i.e. were you using the 'create a vm' wizard) Can you easily reproduce it?

Changed in virt-manager (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for virt-manager (Ubuntu) because there has been no activity for 60 days.]

Changed in virt-manager (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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