Hi all,

I was using F7 test 3 which installed and worked fine, but the F7 release install hangs in both graphical and text mode just after selecting which keyboard layout to use (switching to a terminal and running top shows that anaconda is using 50% cpu, which I assume means that it's stuck using 100% of one of the two cores).

I booted back into the installed F7 test 3 and ran a yum --disablerepo extras-development upgrade (had to disable extras-development as repomd.xml for it somehow got nuked, when or how I don't know), but on rebooting X doesn't start properly. It repeatedly attempts to start, sometimes gets to showing the mouse pointer with the animated fedora cursor on a black background (with the rotating blue circles) but then stops. After a while it gives up.

doing a dmesg | tail shows lots of entries like this:
attempt to access beyond end of device
dm-2: rw=0, want=34225520688, limit=41943040

SELinux is in permissive mode and the Xorg logs show no errors. I'm stumped.

The system is a core 2 duo based, Intel G965 graphics, /home /usr and /var are on LVM on a software RAID 5 array.

Has anyone experienced this kind of weirdness?

Cheers!
-PN

Ok, as the lack of error messages suggests it was not X that was broken. Running startx from the command line gave a load of glib sanity check errors, suggesting that GDM or something associated with it was broken. Running KDM fixed this.