| Summary: | [abrt] virt-manager-0.9.0-6.fc16: __GI___poll: Process /usr/bin/python was killed by signal 11 (SIGSEGV) | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Richard Marko <rmarko> | ||||||||||||||||
| Component: | virt-manager | Assignee: | Cole Robinson <crobinso> | ||||||||||||||||
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||||||
| Severity: | unspecified | Docs Contact: | |||||||||||||||||
| Priority: | unspecified | ||||||||||||||||||
| Version: | 16 | CC: | awilliam, berrange, clalancette, crobinso, dallan, dimapunk80, dougsland, dpierce, hbrock, henryrust89, itamar, jberan, jfbeltran, jforbes, j.orti.alcaine, kahlil.hodgson, laine, mailings, martin, mihkel.vain, RMuscaritolo, sgraf, stdietsch, veillard, virt-maint | ||||||||||||||||
| Target Milestone: | --- | ||||||||||||||||||
| Target Release: | --- | ||||||||||||||||||
| Hardware: | x86_64 | ||||||||||||||||||
| OS: | Unspecified | ||||||||||||||||||
| Whiteboard: | abrt_hash:fac8916309871f3aa0f0a01eec0240771dde2375 | ||||||||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||||||
| Clone Of: | Environment: | ||||||||||||||||||
| Last Closed: | 2012-06-26 15:32:18 UTC | Type: | --- | ||||||||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||||||||
| Documentation: | --- | CRM: | |||||||||||||||||
| Verified Versions: | Category: | --- | |||||||||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||||||||
| Attachments: |
|
||||||||||||||||||
|
Description
Richard Marko
2011-10-26 14:40:27 UTC
Created attachment 530297 [details]
File: maps
Created attachment 530298 [details]
File: backtrace
*** Bug 749363 has been marked as a duplicate of this bug. *** Package: virt-manager-0.9.0-7.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- Tried to delete a storage from the storage pool. Storage was used for a Xen Guest, which no longer existed. This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component. This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component. This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component. This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component. Opened the KVM virtmanager clicked the delete volume button on a raw storage file in my home folder. backtrace_rating: 4 Package: virt-manager-0.9.1-2.fc16 OS Release: Fedora release 16 (Verne) Created attachment 566986 [details]
File: backtrace
? backtrace_rating: 4 Package: virt-manager-0.9.1-2.fc16 OS Release: Fedora release 16 (Verne) Created attachment 567065 [details]
File: backtrace
Removed raw volume (image file) from Storage tab on "localhost Connection Details". backtrace_rating: 4 Package: virt-manager-0.9.1-2.fc16 OS Release: Fedora release 16 (Verne) Created attachment 570009 [details]
File: backtrace
Backtrace analysis found this bug to be similar to bug #767651 from component virt-manager. You might want to check that bug for additional information. This comment is automatically generated. Deleting a volume from disk storage via the GUI. The volume was really just a plain file rarther than a disk image that had been missplaced and I was just too lazy to shell in and remove it manaually backtrace_rating: 4 Package: virt-manager-0.9.1-2.fc16 OS Release: Fedora release 16 (Verne) Created attachment 571896 [details]
File: backtrace
I was deleting storage volumes on the local system via the GUI. backtrace_rating: 4 Package: virt-manager-0.9.1-2.fc17 OS Release: Fedora release 17 (Beefy Miracle) Deleted volume in the default pool backtrace_rating: 4 Package: virt-manager-0.9.1-2.fc16 OS Release: Fedora release 16 (Verne) Created attachment 575222 [details]
File: backtrace
This is 100% reproducible for me on f16. Peter, is this BZ a dup of BZ 803600 ? Yes, it is. It's some kind of bug either in PyGtk or in virt-manager that was worked around in current upstream of virt-manager, as I'm not able to crash it with this procedure, but with an older release it's a matter of a few clicks. Most of the backtraces for this bug, that I've seen indicate that the segfault happened in: #0 0x00000038dbc598fc in validate_row (tree_view=0x2729720, tree=0x7f9eb4060d00, node=0x295bb20, iter=0x7fff2ce094c0, path=<optimized out>) at gtktreeview.c:5827 in thread 0 of virt-manager. I't gets easily confused as bug in libvirt as the thread on the top of the backtrace (It's a full backtrace of python, so it's really long) is executing a libvirt call at that exact moment, when the volume list is being refreshed. Re-assigning back to virt-manager as the crash was caused by #0 gtk_widget_propagate_hierarchy_changed_recurse (widget=0x0, client_data=0x7fff8b08c030) at gtkwidget.c:7036 and not by the libvirt call. ABRT reports incorrect crash functions ( https://bugzilla.redhat.com/show_bug.cgi?id=811147 ). *** This bug has been marked as a duplicate of bug 805950 *** |