![](https://seccdn.libravatar.org/avatar/3bc64bb793cf22fd052ba5a860075f2e.jpg?s=120&d=mm&r=g)
Hi *, yesterday I updated one of my LEAP 15.2 machines. The machine rebootet into maintenance mode afterwards, but I wasn't able to do anything, because the keyboard also wasn't functional. There were error messages on the console regarding systemd-journald and systemd-udevd, which both failed to start. I was not able to recover from this situation, except by recovering the machine from the latest backup. Afterwards everything was back to normal - the machine came up as usual. I then retried the update and saw, that systemd-journald and systemd-udevd even refused to restart during this update. So I have a running machine now without those services, but I suppose, it won't reboot any more as before. Both services gave errors like this: Main PID: 18098 (code=exited, status=228/SECCOMP) Is that only my machine that shows those errors? I didn't read anywhere here in the lists about a problem like that. The internet, though, lists a few occasions, where problems like that happened. Any idea, what to do besides recovering again and don't update for a while? TIA. Bye. Michael. -- Michael Hirmke -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org