Looks like commenting out SystemCallArchitectures=native
fixes the issue. 2018-03-18 22:27 GMT+01:00 LEDUQUE Mickaël <mledu...@gmail.com>: > I disabled them all and got a normal startup. > Now I'll try to find the one (or more) that causes the problem. > Thanks. > > 2018-03-18 21:48 GMT+01:00 Michael Biebl <bi...@debian.org>: > >> Am 18.03.2018 um 20:38 schrieb Mickaël Leduque: >> > Package: systemd >> > Version: 238-2 >> > Followup-For: Bug #893369 >> > >> > It didn't work so I just added the options in /etc/default/grub. >> > Here are the journal and the systemctl list-jobs output (which is just >> "no jobs"). >> > >> >> Ok, thanks. >> Once you are dropped into the rescue shell, can you try running >> systemd-udevd manually, via >> /lib/systemd/systemd-udevd >> >> If that works, you can try disabling the security features in >> /lib/systemd/system/systemd-udevd.service >> by commenting out the lines >> >> MemoryDenyWriteExecute=yes >> RestrictRealtime=yes >> RestrictAddressFamilies=AF_UNIX AF_NETLINK AF_INET AF_INET6 >> SystemCallArchitectures=native >> LockPersonality=yes >> >> one by one and test if that makes a difference. >> >> >> -- >> Why is it that all of the instruments seeking intelligent life in the >> universe are pointed away from Earth? >> >> >
_______________________________________________ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
