Bug 622902 - [abrt] virt-manager: _Xerror crash
Summary: [abrt] virt-manager: _Xerror crash
Alias: None
Product: Fedora
Classification: Fedora
Component: virt-manager   
(Show other bugs)
Version: 13
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Cole Robinson
QA Contact: Fedora Extras Quality Assurance
Whiteboard: abrt_hash:f410cdcc98541dc7426b59c4ef6...
Depends On:
TreeView+ depends on / blocked
Reported: 2010-08-10 18:19 UTC by Ferry Huberts
Modified: 2010-10-27 15:29 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-10-27 15:29:50 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
File: backtrace (87.65 KB, text/plain)
2010-08-10 18:19 UTC, Ferry Huberts
no flags Details

Description Ferry Huberts 2010-08-10 18:19:29 UTC
abrt 1.1.1 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: python /usr/share/virt-manager/virt-manager.py
component: virt-manager
crash_function: raise
executable: /usr/bin/python
global_uuid: f410cdcc98541dc7426b59c4ef6a6f800bdb9e52
package: virt-manager-0.8.4-2.fc13
rating: 4
reason: Process /usr/bin/python was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)

How to reproduce
1.it crashed right after I created a qcow2 image for a new VM

Comment 1 Ferry Huberts 2010-08-10 18:19:42 UTC
Created attachment 437964 [details]
File: backtrace

Comment 2 Cole Robinson 2010-08-21 22:16:30 UTC
Is this reliably reproducible? If so, can you run virt-manager with the --sync option, it should help track this down.

Comment 3 Ferry Huberts 2010-10-25 07:14:00 UTC
not reproducable.
tried it a few times but could not crash it anymore
sorry :-(

Comment 4 Cole Robinson 2010-10-27 15:29:50 UTC
Thanks, closing as WORKSFORME

Note You need to log in before you can comment on or make changes to this bug.