Bug 573395

Summary: [abrt] crash in virt-manager-0.8.2-1.fc12: Process /usr/bin/python was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Philippe Harrand <philippeharrand>
Component: virt-managerAssignee: Cole Robinson <crobinso>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: berrange, cristian.ciupitu, crobinso, dcwilbur, ffecko, gaetan, hbrock, jforbes, kparal, virt-maint
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:0f2c7f5cccef66b0af93f379a72e58045e2549d0
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-04-05 16:09:53 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace none

Description Philippe Harrand 2010-03-14 16:11:40 UTC 
abrt 1.0.8 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: python /usr/share/virt-manager/virt-manager.py
comment: As explained above
component: virt-manager
executable: /usr/bin/python
kernel: 2.6.32.9-70.fc12.x86_64
package: virt-manager-0.8.2-1.fc12
rating: 4
reason: Process /usr/bin/python was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)

How to reproduce
-----
1.a virtual machine Fedora Core 5 with 4 scsi virtual disk on files
2.Create a RAID5 with mdadm
3.At the end of synchronising the virtual machine crashes
Comment 1 Philippe Harrand 2010-03-14 16:11:44 UTC 
Created attachment 400003 [details]
File: backtrace
Comment 2 Cristian Ciupitu 2010-03-19 16:53:41 UTC 

Comment
-----
I was using (running or rebooting) a Windows XP x86 (i686) virtual machine.
Comment 3 Claude G Wilbur 2010-03-25 22:02:29 UTC 

How to reproduce
-----
1. Install Windows Vista under QEMU (yes, I know that is not a *simple* step),
2. Launch the vm, using Virtual Machine Manager
3. *Immediately* launch the vnc console and give your password.


Comment
-----
Second attempt to launch the vnc console always succeeds.
Comment 4 firefox 2010-04-03 17:10:38 UTC 

How to reproduce
-----
1. Open Virtual Machine Manager
2. Run two instances of virtual machines simultaneously (e.g. Fedora and Ubuntu)
3. Force shutdown of one of them (Ubuntu)
Comment 5 Cole Robinson 2010-04-05 16:09:53 UTC 

*** This bug has been marked as a duplicate of bug 540810 ***