Bug#881769: udev: Docs on upgrading to predictable network interface names don't work

Hello Karl, Karl O. Pinc [2017-11-14 16:46 -0600]: > The stretch README.Debian.gz for udev omits mention that > update-initramfs -u must be run after changing configuration files > when converting to the new "predictable network interface names". > > Attached is a patch which clarifies the

Bug#893369: systemd-udevd is killed at startup

Package: systemd Version: 238-2 Severity: critical Justification: breaks the whole system Dear Maintainer, After an update and a restart of the system, boot fails. It enters a loop, where (apparently) systemd-udevd fails to start and is retries for a certain time. After thaat, I am dropped

Bug#893369: systemd-udevd is killed at startup

Ok, I was more searching for a way to do it from inside grub itself, but this will have to do. 2018-03-18 18:55 GMT+01:00 Michael Biebl : > Am 18.03.2018 um 18:50 schrieb LEDUQUE Mickaël: > > I'll do all that, thanks. Do you know how I can set a correct keymap in > > the grub

Bug#893369: systemd-udevd is killed at startup

On Sun, 18 Mar 2018 12:14:41 +0100 =?utf-8?q?Micka=C3=ABl_Leduque?= wrote: > Package: systemd > Version: 238-2 > Severity: critical > Justification: breaks the whole system > > Dear Maintainer, > > After an update and a restart of the system, boot fails. It enters a loop, >

Bug#893369: systemd-udevd is killed at startup

Am 18.03.2018 um 18:50 schrieb LEDUQUE Mickaël: > I'll do all that, thanks. Do you know how I can set a correct keymap in > the grub "e" text editor ? I don't. But this is literally the first google hit regarding that question

Bug#893426: systemd FTBFS: syntax error close to GPGRT_ATTR_NORETURN

Package: systemd Version: 238-2 Severity: serious User: helm...@debian.org Usertags: rebootstrap systemd fails to build from source on amd64. Here is a tail of the build log. | FAILED: journal-core@sta/src_journal_journald-context.c.o | cc -Ijournal-core@sta -I. -I.. -I../

Bug#893369: systemd-udevd is killed at startup

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"). -- Package-specific info: -- System Information: Debian Release: buster/sid APT

Processed: Bug #881769 in systemd marked as pending

Processing control commands: > tag -1 pending Bug #881769 [udev] udev: Docs on upgrading to predictable network interface names don't work Added tag(s) pending. -- 881769: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881769 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#893369: systemd-udevd is killed at startup

I'll do all that, thanks. Do you know how I can set a correct keymap in the grub "e" text editor ? 2018-03-18 16:57 GMT+01:00 Michael Biebl : > On Sun, 18 Mar 2018 12:14:41 +0100 =?utf-8?q?Micka=C3=ABl_Leduque?= > wrote: > > Package: systemd > > Version:

Bug#892794: systemd-networkd fails to configure IPv6 without MTU from RA

Hi, I can confirm that our infrastructure completely broke IPv6-wise right after updating to stretch 9.4 ☺. I did not try the new build, but can confirm that everything start working again if radvd on the gateway is configured to send out an MTU. -nik signature.asc Description: PGP signature

Processed: tagging 884788

Processing commands for cont...@bugs.debian.org: > tags 884788 + wontfix Bug #884788 [systemd] systemd-ask-password echos password as stars (*) while decrypting LUKS partition Added tag(s) wontfix. > thanks Stopping processing here. Please contact me if you need assistance. -- 884788:

Bug#893369: systemd-udevd is killed at startup

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

Bug#893426: systemd FTBFS: syntax error close to GPGRT_ATTR_NORETURN

Control: reassign -1 libgpg-error-dev Control: found -1 1.28-1 Control: affects -1 + systemd Am 18.03.2018 um 19:54 schrieb Helmut Grohne: > Package: systemd > Version: 238-2 > Severity: serious > User: helm...@debian.org > Usertags: rebootstrap > > systemd fails to build from source on amd64.

Processed: Re: Bug#893426: systemd FTBFS: syntax error close to GPGRT_ATTR_NORETURN

Processing control commands: > reassign -1 libgpg-error-dev Bug #893426 [systemd] systemd FTBFS: syntax error close to GPGRT_ATTR_NORETURN Bug reassigned from package 'systemd' to 'libgpg-error-dev'. No longer marked as found in versions systemd/238-2. Ignoring request to alter fixed versions of

Bug#893369: systemd-udevd is killed at startup

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 : > Am 18.03.2018 um 20:38 schrieb Mickaël Leduque: > > Package: systemd > > Version: 238-2 > > Followup-For: Bug

Bug#893369: systemd-udevd is killed at startup

Looks like commenting out SystemCallArchitectures=native fixes the issue. 2018-03-18 22:27 GMT+01:00 LEDUQUE Mickaël : > 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

Bug#893054: systemd: System failed to boot after upgrade/install systemd from systemd:i386

Am 15.03.2018 um 23:31 schrieb Jeff Ketchum: > I upgraded systemd, and after a failure to boot, realized it was on > systemd:i386. > I went into a recovery environment and removed systemd:i386 and > installed systemd. > After that It failed to boot at a different location. > I was able to get it

Bug#893369: systemd-udevd is killed at startup

Am 18.03.2018 um 22:41 schrieb LEDUQUE Mickaël: > No I don't think I have one > dpkg -l udev only shows udev and64 what about systemd? i386 or amd64 -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description:

Processed: bug 883690 is forwarded to https://github.com/systemd/systemd/issues/8483

Processing commands for cont...@bugs.debian.org: > forwarded 883690 https://github.com/systemd/systemd/issues/8483 Bug #883690 [systemd] systemd Caught , "Freezing execution", __libc_fatal("*** %n in writable segment detected ***\n") after execute asprintf(, "U\002%c%s%n"... in

Processed: Re: Processed: Re: Bug#893426: systemd FTBFS: syntax error close to GPGRT_ATTR_NORETURN

Processing control commands: > reassign -1 systemd Bug #893426 [libgpg-error-dev] systemd FTBFS: syntax error close to GPGRT_ATTR_NORETURN Bug reassigned from package 'libgpg-error-dev' to 'systemd'. No longer marked as found in versions libgpg-error/1.28-1. Ignoring request to alter fixed

Bug#893369: systemd-udevd is killed at startup

No I don't think I have one dpkg -l udev only shows udev and64 2018-03-18 22:39 GMT+01:00 Michael Biebl : > Am 18.03.2018 um 22:33 schrieb LEDUQUE Mickaël: > > Looks like commenting out > > > > SystemCallArchitectures=native > > > > fixes the issue. > > Does that mean you have

Bug#893369: systemd-udevd is killed at startup

Am 18.03.2018 um 22:33 schrieb LEDUQUE Mickaël: > Looks like commenting out > > SystemCallArchitectures=native > > fixes  the issue. Does that mean you have a udev:i386 installed on a amd64 system? If so, that would basically be a duplicate of #869719 -- Why is it that all of the

Processed: severity of 893369 is important

Processing commands for cont...@bugs.debian.org: > severity 893369 important Bug #893369 [systemd] systemd-udevd is killed at startup Severity set to 'important' from 'critical' > thanks Stopping processing here. Please contact me if you need assistance. -- 893369:

Processed: Re: Processed: Re: Processed: Re: Bug#893426: systemd FTBFS: syntax error close to GPGRT_ATTR_NORETURN

Processing control commands: > tags -1 fixed-upstream patch Bug #893426 [systemd] systemd FTBFS: syntax error close to GPGRT_ATTR_NORETURN Added tag(s) fixed-upstream and patch. > forwarded -1 https://github.com/systemd/systemd/pull/8456 Bug #893426 [systemd] systemd FTBFS: syntax error close to

Processed: Bug #893282 in systemd marked as pending

Processing control commands: > tag -1 pending Bug #893282 [systemd] systemd: SuccessAction=reboot in wrong stanza in /lib/systemd/system/system-update-cleanup.service Added tag(s) pending. -- 893282: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893282 Debian Bug Tracking System Contact

Processed: Bug #893426 in systemd marked as pending

Processing control commands: > tag -1 pending Bug #893426 [systemd] systemd FTBFS: syntax error close to GPGRT_ATTR_NORETURN Added tag(s) pending. -- 893426: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893426 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#893426: Processed: Re: Processed: Re: Bug#893426: systemd FTBFS: syntax error close to GPGRT_ATTR_NORETURN

Control: tags -1 fixed-upstream patch Control: forwarded -1 https://github.com/systemd/systemd/pull/8456 Fixed upstream by https://github.com/systemd/systemd/commit/848e863acc51ecfb0f3955c498874588201d9130 -- Why is it that all of the instruments seeking intelligent life in the universe are

Bug#883569: libpam-systemd: Prefer systemd-sysv over systemd-shim

On Thu, 8 Mar 2018 12:47:22 +0100 Martin Pitt wrote: > Hello Michael, > > Michael Biebl [2018-03-08 12:16 +0100]: > > Am 08.03.2018 um 09:22 schrieb Martin Pitt: > > There is one case: someone installs a minimal system without > > libpam-systemd, then switches to sysvinit-core,