I am running regular Debian alone on the hard disk of my HP laptop, apparmor is now by default, but I confirm the environment is noy the cause. All things equal , everything is good wiyj kernel 4.16
another example of how the problem is: root@debian:/home/guy# systemd-analyze plot > kernel-417.svg Failed to get host information from systemd: Failed to activate service 'org.freedesktop.hostname1': timed out (service_start_timeout=25000ms) root@debian:/home/guy# systemctl --failed UNIT LOAD ACTIVE SUB DESCRIPTION ● systemd-hostnamed.service loaded failed failed Hostname Service LOAD = Reflects whether the unit definition was properly loaded. ACTIVE = The high-level unit activation state, i.e. generalization of SUB. SUB = The low-level unit activation state, values depend on unit type. 1 loaded units listed. Pass --all to see loaded but inactive units, too. To show all installed unit files use 'systemctl list-unit-files'. root@debian:/home/guy# systemctl status systemd-hostnamed.service ● systemd-hostnamed.service - Hostname Service Loaded: loaded (/lib/systemd/system/systemd-hostnamed.service; static; vendor preset: enabled) Active: failed (Result: exit-code) since Sat 2018-07-14 15:29:45 CEST; 1min 10s ago Docs: man:systemd-hostnamed.service(8) man:hostname(5) man:machine-info(5) https://www.freedesktop.org/wiki/Software/systemd/hostnamed Process: 3903 ExecStart=/lib/systemd/systemd-hostnamed (code=exited, status=226/NAMESPACE) Main PID: 3903 (code=exited, status=226/NAMESPACE) juil. 14 15:29:45 debian systemd[1]: Starting Hostname Service... juil. 14 15:29:45 debian systemd[3903]: systemd-hostnamed.service: Failed to set up mount namespacing: Bad address juil. 14 15:29:45 debian systemd[3903]: systemd-hostnamed.service: Failed at step NAMESPACE spawning /lib/systemd/systemd-hos juil. 14 15:29:45 debian systemd[1]: systemd-hostnamed.service: Main process exited, code=exited, status=226/NAMESPACE juil. 14 15:29:45 debian systemd[1]: systemd-hostnamed.service: Failed with result 'exit-code'. juil. 14 15:29:45 debian systemd[1]: Failed to start Hostname Service. root@debian:/home/guy# ________________________________ De : Michael Biebl <bi...@debian.org> Envoyé : samedi 14 juillet 2018 13:46 À : GT; 903...@bugs.debian.org Objet : Re: Bug#903691: systemd-localed.service: Failed to set up mount namespacing: Bad address control: tags -1 moreinfo unreproducible Am 13.07.2018 um 13:29 schrieb Michael Biebl: > Can you reproduce the problem with 4.16, i.e. is that a regression > introduced by 4.17? > I'm asking, because I'm running 4.14 and can't reproduce the issue. I meant 4.16 here, not 4.14. That said, I have now also installed 4.17: linux-image-4.17.0-1-amd64: Installiert: 4.17.6-1 Installationskandidat: 4.17.6-1 Versionstabelle: *** 4.17.6-1 500 I can't reproduce any problems though. Do you have SELinux, AppArmor or anything like that enabled? Does it help if you disable it? Is systemd running inside a container? Any hints how we might be able to reproduce the problem? -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?