i got the +b1 version of systemd this afternoon and its fixed
On Wed, Feb 2, 2022 at 10:15 AM John Paul Adrian Glaubitz <
glaub...@physik.fu-berlin.de> wrote:
> Hello!
>
> On 2/2/22 18:55, H wrote:
> > Thank you Adrian!
>
> Try upgrading your machines, it should be fixed now.
>
> Adrian
>
> --
>
Hello!
On 2/2/22 18:55, H wrote:
> Thank you Adrian!
Try upgrading your machines, it should be fixed now.
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaub...@debian.org
`. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
`-GPG: 62FF 8A75 84E0 2956
Thank you Adrian!
On Wed, Feb 2, 2022 at 1:00 AM John Paul Adrian Glaubitz <
glaub...@physik.fu-berlin.de> wrote:
> Hello!
>
> On 2/2/22 00:11, H wrote:
> > FWIW, A little bit information that might be helpful:
> >
> > I started journald manually via /lib/systemd/systemd-journald, no error
> mess
Hello!
On 2/2/22 00:11, H wrote:
> FWIW, A little bit information that might be helpful:
>
> I started journald manually via /lib/systemd/systemd-journald, no error
> message
> to stdout and stderr, nor journalctl output. Actually journalctl still does
> not
> work (empty for all services).
>
>
Hello!
On 2/1/22 23:59, Cameron MacPherson wrote:
> on my system i get
> systemd[1]: Caught , core dump failed (child 210, code=killed,
> status=6/ABRT)
>
> prior to rebooting there were messages about journald not starting. i will
> see if
> i can go back to an older version of systemd.
That
5 matches
Mail list logo
