Excerpts from Gavin Graham's message of 2012-12-19 02:25:34 UTC:
> @Pieter
>
> I agree, it is not a fix (well, a permanent and proper one anyway) but
> it does suggest that it's a race condition and that it is in the Binary
> itself and not the /etc/init/lightdm script as some of the other
> potential "fixes" have tried to remedy.
>
Actually thats not really the case.
The most likely case is that there's something, hardware wise, missing
that X needs, that isn't encoded in the events that trigger lightdm
to start.
We'll need full X logs to determine that for sure, but thats what I
suspect. Its possible that udev events are being emitted for devices
that aren't 100% ready, or that there are more events that need to be
blocked on.
Excerpts from Gavin Graham's message of 2012-12-19 02:25:34 UTC:
> @Pieter
>
> I agree, it is not a fix (well, a permanent and proper one anyway) but
> it does suggest that it's a race condition and that it is in the Binary
> itself and not the /etc/init/lightdm script as some of the other
> potential "fixes" have tried to remedy.
>
Actually thats not really the case.
The most likely case is that there's something, hardware wise, missing
that X needs, that isn't encoded in the events that trigger lightdm
to start.
We'll need full X logs to determine that for sure, but thats what I
suspect. Its possible that udev events are being emitted for devices
that aren't 100% ready, or that there are more events that need to be
blocked on.