Bug 680704

Summary: [abrt] virt-manager-0.8.5-1.fc14: __libc_message: Process /usr/bin/python was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: shashank <shashank.neelam>
Component: virt-managerAssignee: Cole Robinson <crobinso>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: berrange, crobinso, hamed106, hbrock, jforbes, virt-maint
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:84a62ce666b307893dc2e573418f40e6b6845fd4
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-07-11 16:34:34 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 shashank 2011-02-27 08:25:40 UTC 
abrt version: 1.1.17
architecture: x86_64
Attached file: backtrace, 55169 bytes
cmdline: python /usr/share/virt-manager/virt-manager.py
component: virt-manager
Attached file: coredump, 84299776 bytes
crash_function: __libc_message
executable: /usr/bin/python
kernel: 2.6.35.11-83.fc14.x86_64
package: virt-manager-0.8.5-1.fc14
rating: 4
reason: Process /usr/bin/python was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1298794598
uid: 500

How to reproduce
-----
1. Started Virtual Machine Manager
2. Created a new Machine
3. Selected the Windows XP disc iso as the installation media
Comment 1 shashank 2011-02-27 08:25:45 UTC 
Created attachment 481218 [details]
File: backtrace
Comment 2 hamed106 2011-04-05 06:08:57 UTC 
Package: virt-manager-0.8.5-1.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1.start virtual machine
2.open my guest os
3.mapping network drive
4.linux freeze & have to reboot
Comment 3 Cole Robinson 2011-07-11 16:34:34 UTC 

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