well, i'm realy impress with such knowledge. would that means it would be possible to hugly-hugly kill dead X socket before starting a new one ? or maybe some magic things to do after instal GTK2-2.4 ?
how can it be seen a logout proceded normally ? in /var/log/messages ? because shutdown messages are 'normal'.
in var log message when X won't start : it says : init(open(/dev/pts/0) No such file or directory, i understood from google that pts where kernel stuff (could be possible as fc1 is kerne 2.4 and gtk2-2.4 is for fC2 - kernel 2.6).
hervé
This may be a variant of the GObject changes - when you log out does the logout proceed normally, or does it hang before X shuts down correctly?
I suspect what is happening is that a known backwards compatibility issue the GObject maintainer refused to fix is deadlocking the GNOME logout screen at some point, but the system shutdown has already started. This means X doesn't shut down correctly as it's grabbed by GNOME, meaning it'll be sent SIGKILL just before the system halts.
Next time the system starts up, the dead X socket is still on the filing system so preventing the new X server from starting.
Total stab in the dark but this is my guess.
thanks -mike