Red Hat Bugzilla – Bug 141060
Anaconda crashes with network_gui.py assertion failure
Last modified: 2007-11-30 17:10:55 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040510
Description of problem:
I have successfully installed FC3 on two other systems. On one system
I have problems. It is an amd64 system. Note that I am trying to
install the 32 bit version of FC3. (because there is no Java plugin
yet for amd64). This should not be a problem.
The system installs and runs fine with both FC2 and FC2_64.
On this system the graphical installation process starts and gets
through all the user input. But after formatting the partitions
anaconda crashes with:
/usr/lib/anaconda/iw/network_gui.py: 265: GtkWarning: file Gtktable.c
line 515 (gtk_table_resize): assertion n_rows > 0 && n_rows < 65536
'failed devTable = Table(len(devopts), 2)
I tried installing FC3 using the text installer and it crashes hard
... seemingly at about the same place in the installation ... after
formatting the partitions.
I was unable to get the diagnostics from the text install crash. If
you tell me how to collect the data then I will reinstall.
I suspect that this may be videocard related. After reinstalling FC2
(32 bit) my /etc/X11/xorg.conf has:
BoardName "NVIDEA GeForce 4 MX (generic)"
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Try to install FC3 on my system
2. start the process ... watch drives get formatted
3. see it anaconda crash with assertion failure
I will be glad to try to reinstall if you can tell me how to collect
data to determine what is failing.
I had no troubles with installation of FC2 ... FC3 dies.
Can you verify your install media according to the instructions at
This seems to only happen if you don't leave it set as DHCP in the
network configuration during installation, and try to configure
specific IP/GW/DNS and hostname settings.
I did a media check before the installation.
I have installed two other FC3 systems from the same media.
Per Vic's comment, I also turned off DHCP and manually configured the
IP/GW/DNS settings. And I did this in the text installer as well
(which crashed very hard)
But I am quite sure that I set a fixed IP address at install time on
one of my other FC3 system as well ... and that one had no problems.
Actually, that's just a warning from pygtk -- it doesn't actually lead
to the crash you're seeing. Can you hit ctrl-s when it crashes and
switch to tty2 to grab both /tmp/anaconda.log and /tmp/syslog?
"Can you hit ctrl-s when it crashes and
switch to tty2 to grab both /tmp/anaconda.log and /tmp/syslog?"
Q: Please confirm that you are referring the text mode installer for
FC3. You would like me to attempt to reinstall with the text mode
installer, hit ctrl-s to halt the screen output, and hit alt-f2 to
swith to tty2
Q: How do I 'grab' these files? What device can I write them to?
Yes, that's fine for text-mode. You can grab the files either by
copying them to a floppy or by copying them off via the network.
I don't have a floppy.
I will be in the middle of an installation that just crapped out
because I put in a fixed IP address ... do you think that the network
is going to be up?
Will the USB drivers be running so that I can copy it to a USB device?
I installed a floppy in order to grab the logs.
I ran a bunch of other tests:
- tried two other video cards ... still died
- tried different monitor ... still died
(I thought that perhaps 'unknown/unrecognized monitor' was an issue)
- tried with DHCP instead of fixed IP ... still died
Created attachment 108384 [details]
anaconda.log and syslog files
anaconda.log and syslog files for failed installation of FC3
I am ready to pick up this thread and try to help get this issue
After crash on my box tty4 says:
<3> Out of memory: process 360 killed (anaconda)
I have 128M of RAM and no swap partition. Trying to add more memory and see
what will happen.
512M RAM - it works just fine!
Glad that additional memory seemed to solve your problem.
This bug report was originally filed on a system that has 1Gb RAM.
Issue is still not resolved and I am still willing to work on it.
I recommend that this bug be closed.
My previous install was into a new logical volume of a lvm1 volume group.
Doing a completely clean installation on to a wiped hard drive works OK.