gconf failure after last batch of updates

[g8jvm]

Hi
Has anyone else had a gconf failure, Xserver fails to start after the last update with glibc etc.
This machine is OK, but my dell laptop, 64 bit now has a gconf failure after login.
The unit will still runs in init 1

Is there a nice yum command like yum undo screwup ?, else its a possible reinstall with no updates

Tia
Richard

[sea]

yum remove package

Do you think of something like that?

[g8jvm]

"yum remove package" would NOT be useful with glibc
Yum downgrade might but it was a large update with many packages.
the only difference between machines is this one has kernel 2.6.40.1 installed.

The exact message after login is

There is a problem with the configuration server (usr/libexec/gconf-sanity-check-2 exited with status 256

Maybe someone will add a yum function to undo ] all the last upgrades, other wise its run a backup every time before upgrading , which should not be necessary.

cheers
Richard

[Bazu135]

I could be going down completely the wrong track here (I'm new to Linux as a whole), but I was reading some threads last night that referred to the 'usr/libexec/gconf-sanity-check-2 exited with status 256' error, and in each case it was a problem with the /tmp directory.

In each case that I read, the issue seemed to crop up after updates, and was resolved by changing the /tmp access settings to rwx-rwx-rwx - no idea if that'd help here or not, but thought it was worth putting it out there

[g8jvm]

The /tmp directory was too small, 500MB,

2 fresh live-installs failed right at the end of install when the bootloader was written.
In the end I just let it overwrite the linux partitions and it installed,
PIA getting the updates 725 !
It looks like a minimum of 1GB of /tmp is now needed
so sorted ,but not the way I liked.
I had tried renaming /tmp and creating another, but thats not allowed.