Bug 590671

Summary: [abrt] crash in virt-manager-0.8.2-3.fc12: memcpy: Process /usr/bin/python was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Peter Green <peter.green>
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, crobinso, hbrock, jforbes, virt-maint
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:02ec263c53f8a9ac0070e3a3198b11de2dc577f6
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-05-10 15:52:00 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 Peter Green 2010-05-10 13:10:50 UTC 
abrt 1.0.9 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: python /usr/share/virt-manager/virt-manager.py
comment: Reconfiguring a VM then quickly starting and switching to the console view.
component: virt-manager
crash_function: memcpy
executable: /usr/bin/python
global_uuid: 02ec263c53f8a9ac0070e3a3198b11de2dc577f6
kernel: 2.6.32.11-99.fc12.x86_64
package: virt-manager-0.8.2-3.fc12
rating: 3
reason: Process /usr/bin/python was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)

How to reproduce
-----
1. "Opened" an existing virtual machine
2. Reconfigured machine: removed virtIO HDD and added IDE HDD (pointing to same Logical Volume on host)
3. Hit the "play" button
4. Hit the console button to view VM booting.
5 . virt-manager crashed
Comment 1 Peter Green 2010-05-10 13:10:54 UTC 
Created attachment 412830 [details]
File: backtrace
Comment 2 Cole Robinson 2010-05-10 15:52:00 UTC 
Should be fixed by gtk-vnc-0.3.10-3.fc12 which is heading to stable soon.

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