Bug 759446

Summary: libvirt: GIL crash from python libvirt_virEventUpdateHandleFunc
Product: [Fedora] Fedora Reporter: Stanislav Graf <sgraf>
Component: libvirtAssignee: Libvirt Maintainers <libvirt-maint>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 16CC: berrange, clalancette, crobinso, dougsland, dpierce, hbrock, itamar, jforbes, laine, libvirt-maint, veillard, virt-maint
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:e52b89096a86b84bdd6e46f5c8d519e397d99d5e
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-06-07 15:51:46 EDT Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Description Flags
File: dso_list
File: build_ids
File: maps
File: backtrace none

Description Stanislav Graf 2011-12-02 07:16:35 EST
libreport version: 2.0.7
abrt_version:   2.0.6
backtrace_rating: 4
cmdline:        python /usr/share/virt-manager/virt-manager.py
crash_function: new_threadstate
executable:     /usr/bin/python
kernel:         3.1.2-1.fc16.x86_64
pid:            15142
pwd:            /home/sgraf
reason:         Process /usr/bin/python was killed by signal 11 (SIGSEGV)
time:           Fri 02 Dec 2011 12:58:01 PM CET
uid:            1000
username:       sgraf

backtrace:      Text file, 49601 bytes
build_ids:      Text file, 7954 bytes
dso_list:       Text file, 18815 bytes
maps:           Text file, 80091 bytes

:'LESSOPEN=||/usr/bin/lesspipe.sh %s'

:Nov 29 08:38:44 localhost yum[15730]: Updated: python-slip-0.2.20-1.fc16.noarch
:Nov 29 08:38:51 localhost yum[15730]: Updated: python-slip-gtk-0.2.20-1.fc16.noarch
:Nov 29 08:38:52 localhost yum[15730]: Updated: python-slip-dbus-0.2.20-1.fc16.noarch
:Nov 30 10:42:09 localhost yum[2957]: Updated: libselinux-python-2.1.6-5.fc16.x86_64
:Dec  1 19:58:17 localhost yum[2901]: Installed: python-setuptools-0.6.24-1.fc16.noarch
:Dec  1 19:58:18 localhost yum[2901]: Installed: python-nose-1.1.2-1.fc16.noarch
:Dec  1 19:58:25 localhost yum[2901]: Installed: python-simplegeneric-0.7-2.fc15.noarch
:Dec  1 19:58:27 localhost yum[2901]: Installed: python-zmq-2.1.9-1.fc16.x86_64
:Dec  1 19:58:29 localhost yum[2901]: Installed: python-mglob-0.4-3.fc15.noarch
:Dec  1 19:58:32 localhost yum[2901]: Installed: python-dateutil-1.5-3.fc16.noarch
:Dec  1 19:58:35 localhost yum[2901]: Installed: python-matplotlib-1.0.1-12.fc16.x86_64
:Dec  1 19:58:39 localhost yum[2901]: Installed: ipython-0.11-3.fc16.noarch
:Dec  2 11:30:12 localhost kernel: [12748.597371] python[3661]: segfault at 24 ip 00000033c385991c sp 00007fff24e66000 error 4 in libgtk-x11-2.0.so.0.2400.8[33c3600000+46c000]
:Dec  2 11:30:18 localhost abrt[14861]: Saved core dump of pid 3661 (/usr/bin/python) to /var/spool/abrt/ccpp-2011-12-02-11:30:12-3661 (1784991744 bytes)
:Dec  2 12:58:00 localhost kernel: [18015.805977] python[18414]: segfault at 8 ip 00000033d98faa8a sp 00007f1fd92ed970 error 4 in libpython2.7.so.1.0[33d9800000+171000]
:Dec  2 12:58:06 localhost abrt[18415]: Saved core dump of pid 15142 (/usr/bin/python) to /var/spool/abrt/ccpp-2011-12-02-12:58:01-15142 (382136320 bytes)
Comment 1 Stanislav Graf 2011-12-02 07:16:42 EST
Created attachment 539602 [details]
File: dso_list
Comment 2 Stanislav Graf 2011-12-02 07:16:44 EST
Created attachment 539603 [details]
File: build_ids
Comment 3 Stanislav Graf 2011-12-02 07:16:47 EST
Created attachment 539604 [details]
File: maps
Comment 4 Stanislav Graf 2011-12-02 07:16:51 EST
Created attachment 539605 [details]
File: backtrace
Comment 5 abrt-bot 2012-03-20 11:41:39 EDT
Backtrace analysis found this bug to be similar to bug #796505 from component virt-manager. You might want to check that bug for additional information.

This comment is automatically generated.
Comment 6 Cole Robinson 2012-06-07 15:51:46 EDT
I think this is virt-manager thread issues which are tracked in other reports. Please reopen if you can consistently reproduce though