Bug 178952 - Installer crashes with python 'GC Object is already tracked' in vmware WS 5.5.1
Summary: Installer crashes with python 'GC Object is already tracked' in vmware WS 5.5.1
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 5
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Mike McLean
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-01-25 18:17 UTC by Hugo Van den Berg
Modified: 2007-11-30 22:11 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2006-01-28 05:43:06 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Hugo Van den Berg 2006-01-25 18:17:21 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20050922 Fedora/1.0.7-1.1.fc3 Firefox/1.0.7

Description of problem:
When I try to install FC5test2 on a VMWare virtual machine (WS 5.5.1) the installer crashes at unpredictable moments with the message 'GC Object is already tracked' I've run memtest86-3.2 on both the virtual and on the physical machine: no memory errors where detected. I've tried different memory setups and different disk configurations (IDE/SCSI-BusLogic/LSI).

I tried the install from the DVD iso image. VMWare can publish this as a physical drive to the virtual machine.

The crash always occurs somewhere between the start of package selection and the start of instalation. The exact point is variable, but I never get past resoving dependancies.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Create a new virtual machine with the ISO image as cdrom drive
2. Boot from the virtual DVD drive
3. Walk through the installation menus
  

Actual Results:  The installer bails out with a fatal error as described above

Expected Results:  The installation should complete

Additional info:

Contact me if you want me to try things out

Comment 1 Jeremy Katz 2006-01-28 05:43:06 UTC
This works fine on physical hardware and an error like that really sounds a lot
like a VMware bug.


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