On Saturday, September 21, 2013 07:34:42 PM andrea wrote:
> [FAILED] Wait for Plymouh Boot Screen to quit
>
>
>
> and in /var/log/messages
>
>
>
> there is something about
>
>
>
> Sep 21 15:24:35 localhost kdm[335]: plymouth --ping -> 0
> Sep 21 15:24:35 localhost kdm[335]: plymouth is running ...
> Sep 21 15:24:35 localhost kdm[335]: plymouth deactivate -> 0
> Sep 21 15:24:35 localhost kdm[335]: plymouth --has-active-vt -> 0
> Sep 21 15:24:35 localhost kdm[335]: plymouth should quit when server
> starts
> Sep 21 15:24:36 localhost kdm[335]: plymouth is active on VT 1, reusing
> for :0 Sep 21 15:24:36 localhost kdm[335]: X server startup timeout,
> terminating Sep 21 15:24:36 localhost kdm[335]: X server for display :0
> cannot be started, session disabled>
>
>
> any idea?
>
>
in the end something damaged in /var/log/journal
google it, it turned out that some services took too long to start.
not too sure, but renaming that folder fixed it.
What did you find "damaged" in /var/log/journal? I ask because I see this KDM
failure as well, only on one of my machines, but journalctl --verify passes
with flying colors. Also, when I issue systemctl restart display-manager
after the initial failure, KDM starts properly.
-A
--
Anthony -
http://messinet.com -
http://messinet.com/~amessina/gallery
8F89 5E72 8DF0 BCF0 10BE 9967 92DC 35DC B001 4A4E