failed to start login service

I have a simple system set up in virtualbox, mostly to browse and torrent. Rarely have major problems. Recently I realized that cron was not working when flexget was not activated as expected. A check of journalctl threw up repeated instances of the following:

I use autologin to console (and then to X via bash_profile) and there is no glitch except that I find that getting to desktop takes a little longer these days. Thought it is due to psd. I have no idea when this happened as things have been OK.

Any advice? I suspect that cron's failure is due to this issue though honestly I have no basis to think so. Systemctl shows cronie.service loaded and running. System is up to date.

Re: failed to start login service

With all the changes over the past year, I have been wanting to set up a fresh installation to remove any old issues that might not have been properly dealt with over time. This current issue, and the fact that the move to consolidate everything to /usr/bin has happened, tilted the balance.

New installation, login is OK, no repeated messages from systemd-logind, cronie is working.

Why the problems, I have no idea. But the new installation is working well.

Re: failed to start login service

Closing this thread.It never gained any traction. It is an old thread. The assertion in the previous thread is incorrect. And, I believe, the OP dealt with it with a re-install. Not much point in continuing.

Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael FaradaySometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing----How to Ask Questions the Smart Way