Control: close -1
On Sun, 19 Mar 2017 19:37:10 -0600 Nathan Dorfman
wrote:
> On Mon, Mar 20, 2017 at 01:38:49AM +0100, Michael Biebl wrote:
> > Am 20.03.2017 um 01:36 schrieb Michael Biebl:
> > > The relevant bits are in the journal log
> > >> Mar 19 20:09:08 stretch systemd[1]: Stopped Login
On Mon, Mar 20, 2017 at 01:38:49AM +0100, Michael Biebl wrote:
> Am 20.03.2017 um 01:36 schrieb Michael Biebl:
> > The relevant bits are in the journal log
> >> Mar 19 20:09:08 stretch systemd[1]: Stopped Login Service.
>
>
> Some of those in between
> > Mar 19 20:09:08 stretch dbus[451]:
Am 20.03.2017 um 01:36 schrieb Michael Biebl:
> The relevant bits are in the journal log
>> Mar 19 20:09:08 stretch systemd[1]: Stopped Login Service.
Some of those in between
> Mar 19 20:09:08 stretch dbus[451]: [system] Activation via systemd failed for
> unit
Am 20.03.2017 um 01:21 schrieb Nathan Dorfman:
> Yes, in both cases!
Ok, good to know. This means we are on the right track.
As if the Xorg errors aren't relevant. Could it be
> the plymouth
> error? The plymouth package wasn't installed by default; was it supposed
> to be?
Nope the plymouth
Am 19.03.2017 um 23:53 schrieb Michael Biebl:
> Am 19.03.2017 um 22:03 schrieb Michael Biebl:
>
>> If you can access the system via SSH, please attach the output of of
>> systemctl list-jobs
>> systemctl status
>> journalctl -alb
>
> My guess is, that this is related to logind. In stretch,
Am 19.03.2017 um 22:03 schrieb Michael Biebl:
> If you can access the system via SSH, please attach the output of of
> systemctl list-jobs
> systemctl status
> journalctl -alb
My guess is, that this is related to logind. In stretch, wayland and
root-less Xorg require logind to set up the
Am 19.03.2017 um 07:50 schrieb Nathan Dorfman:
> Package: systemd
> Version: 232-19
> Severity: normal
> File: /bin/systemctl
>
> Dear Maintainer,
>
> The 'systemctl rescue' and 'init 1' commands completely hang the system if
> run while a graphical login is active, whether from a xterm or a
7 matches
Mail list logo
