On Thu, Oct 18, 2018 at 3:29 PM Cecil Westerhof wrote:
> I found out that in reality no reboot had taken place. For one reason or
> another that did not work. Doing:
> systemctl reboot
> systemctl poweroff
> init 0
> halt
>
> All did not work. Those gave messages like:
>
On Do, 18.10.18 15:14, Cecil Westerhof (cldwester...@gmail.com) wrote:
> I found out that in reality no reboot had taken place. For one reason or
> another that did not work. Doing:
> systemctl reboot
> systemctl poweroff
> init 0
> halt
>
> All did not work. Those gave messages
Op wo 17 okt. 2018 om 20:06 schreef Cecil Westerhof :
> Since this morning I have a strange problem, when I execute:
> systemctl status cups
>
> I get:
> Failed to get properties: Failed to activate service
> 'org.freedesktop.systemd1': timed out
>
> This is with every service, not just
On Mi, 17.10.18 20:06, Cecil Westerhof (cldwester...@gmail.com) wrote:
> Since this morning I have a strange problem, when I execute:
> systemctl status cups
>
> I get:
> Failed to get properties: Failed to activate service
> 'org.freedesktop.systemd1': timed out
>
> This is with every
Since this morning I have a strange problem, when I execute:
systemctl status cups
I get:
Failed to get properties: Failed to activate service
'org.freedesktop.systemd1': timed out
This is with every service, not just cups.
I tried 'everything', even rebooting the system.
What could be
