I am not sure how comfortable you are with scripting but I do not see why we could not write a short workaround script that would prevent X from launching until after fsck has completed. It could be a short loop to confirm fsck has completed and if not then sleep for some period of time.
We could do this as a startup service (/etc/rc5.d), in /etc/X11/init/initrc or in /etc/X11/Xsession. Of course any updates to the latter two files would probably mean any changes would be overwritten.
Hopefully others will chime in with their own solutions until we can get you an official fix.
RProgrammer:
I am not sure how comfortable you are with scripting but I do not see why we could not write a short workaround script that would prevent X from launching until after fsck has completed. It could be a short loop to confirm fsck has completed and if not then sleep for some period of time.
We could do this as a startup service (/etc/rc5.d), in /etc/X11/ init/initrc or in /etc/X11/Xsession. Of course any updates to the latter two files would probably mean any changes would be overwritten.
Hopefully others will chime in with their own solutions until we can get you an official fix.