Bug 1307011

Summary:	kvm manager crashes with: python 2.7 killed by SIGBUS
Product:	Red Hat Enterprise Linux 7	Reporter:	Mauro Mozzarelli <mm13>
Component:	pygobject2	Assignee:	Matthew Barnes <mbarnes>
Status:	CLOSED WONTFIX	QA Contact:	Desktop QE <desktop-qa-list>
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	7.2	CC:	chayang, crobinso, juzhang, knoel, mm13, pviktori, qzhang, virt-maint, xfu
Target Milestone:	rc
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-10-25 14:59:41 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Mauro Mozzarelli 2016-02-12 12:49:29 UTC

Description of problem:
Just moving kvm-manager window or any kvm VM window on the the desktop causes the tool to crash with error: python 2.7 killed by SIGBUS

Version-Release number of selected component (if applicable):
qemu-kvm-1.5.3-105.el7_2.3.x86_64

How reproducible:
Launch kvm-manager and move the window

Steps to Reproduce:
1. start kvm-manager
2. move the window on the screen
3.

Actual results:
kvm-manager crashes as above

Expected results:


Additional info:
See related CentOS bug: https://bugs.centos.org/view.php?id=8525

Comment 2 Pavel Hrdina 2016-03-18 08:42:50 UTC

Hi, moving to python component because virt-manager itself cannot crash with SIGBUS.  I'm not sure whether it's python issue or some of the others libraries like gtk+ or glib.

Comment 3 Petr Viktorin 2016-03-18 09:31:35 UTC

Hello,
Can you get a core dump (or better, an ABRT report) from the crash?

Comment 4 Mauro Mozzarelli 2016-03-18 09:37:37 UTC

Please see related bug:
https://bugs.centos.org/view.php?id=8525

Plenty of reports. My bug manager also posted automatically several core dumps.

Comment 5 Petr Viktorin 2016-03-18 10:49:00 UTC

According to the backtrace [0], the crash happens deep in a glib/GTK/GDK call, in a pygi_closure, so I think the pygobject experts have more luck debugging this.

If it turns out to be a Python bug or any Python-specific knowledge is needed, let me know.

[0] https://retrace.fedoraproject.org/faf/reports/617649/