virt-manager.py crashed with SIGSEGV in PyGILState_Ensure()

Bug #1101687 reported by Jeremy Bicha on 2013-01-19
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
virt-manager (Ubuntu)
Medium
Unassigned

Bug Description

.

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: virt-manager 0.9.4-2ubuntu1
ProcVersionSignature: Ubuntu 3.8.0-0.4-generic 3.8.0-rc3
Uname: Linux 3.8.0-0-generic x86_64
ApportVersion: 2.8-0ubuntu2
Architecture: amd64
Date: Sat Jan 19 00:00:24 2013
ExecutablePath: /usr/share/virt-manager/virt-manager.py
InterpreterPath: /usr/bin/python2.7
MarkForUpload: True
PackageArchitecture: all
ProcCmdline: python /usr/share/virt-manager/virt-manager.py
SegvAnalysis:
 Segfault happened at: 0x521c6d: mov 0x8(%rbp),%rax
 PC (0x00521c6d) ok
 source "0x8(%rbp)" (0x00000008) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: virt-manager
StacktraceTop:
 ?? ()
 PyGILState_Ensure ()
 ?? () from /usr/lib/python2.7/dist-packages/libvirtmod.so
 virNetSocketUpdateIOCallback () from /usr/lib/libvirt.so.0
 ?? () from /usr/lib/libvirt.so.0
Title: virt-manager.py crashed with SIGSEGV in PyGILState_Ensure()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip libvirtd lpadmin plugdev sambashare sbuild sudo

Jeremy Bicha (jbicha) wrote :

StacktraceTop:
 ?? ()
 PyGILState_Ensure ()
 libvirt_virEventUpdateHandleFunc (watch=1, event=1) at /build/buildd/libvirt-1.0.0/./python/libvirt-override.c:4713
 virNetSocketUpdateIOCallback (sock=0x7f9648002c10, events=1) at /build/buildd/libvirt-1.0.0/./src/rpc/virnetsocket.c:1679
 virNetClientIOUpdateCallback (client=client@entry=0x7f9648002ac0, enableCallback=enableCallback@entry=true) at /build/buildd/libvirt-1.0.0/./src/rpc/virnetclient.c:1645

Changed in virt-manager (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Jeremy Bicha (jbicha) on 2013-01-19
information type: Private → Public
Launchpad Janitor (janitor) wrote :

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

Changed in virt-manager (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