Bug#892360: core: do not free stack-allocated strings

Control: tags -1 patch Hi all, * Jindřich Makovička [2018-03-08 19:46 +]: > There is a fix in upstream master. > > https://github.com/systemd/systemd/pull/8391 I managed to build Debian's 238-1 with the attached patch included. I hereby confirm that those packages fix

Bug#892360: core: do not free stack-allocated strings

* Jindřich Makovička [2018-03-08 19:46 +]: > There is a fix in upstream master. > > https://github.com/systemd/systemd/pull/8391 Patched Debian sources and tried to build packages: OK: 239 FAIL: 1 SKIP: 15 TIMEOUT:0 debian/rules:281: recipe for

Bug#892360: systemd: No problem on my amd64 systems

* Diederik de Haas [2018-03-08 20:29 +0100]: > Package: systemd > Followup-For: Bug #892360 > > Wanting to let you know that I had no problem on my PC (from which I'm > reporting) and also not on my laptop. > > I did not have to specify any (systemd related) kernel

Bug#892360: systemd: Breaks also all my tested amd64 machines

* Elimar Riesebieter <riese...@lxtec.de> [2018-03-08 19:13 +0100]: [...] > ATM I am building a x86 with CONFIG_CGROUP_CPUACCT=not set. Let's > wait and see "CONFIG_CGROUP_CPUACCT is not set" gives the same error as shown in the picture of my initial bug report. The pr

Bug#892360: systemd: Breaks also all my tested amd64 machines

* Eric Valette <eric.vale...@free.fr> [2018-03-08 19:08 +0100]: > On 3/8/18 7:03 PM, Elimar Riesebieter wrote: > > * Michael Biebl <bi...@debian.org> [2018-03-08 18:54 +0100]: > > > > [...] > > > Can you check your custom kernel config, specifically if &

Bug#892360: systemd: Breaks also all my tested amd64 machines

* Michael Biebl [2018-03-08 18:54 +0100]: [...] > Can you check your custom kernel config, specifically if > CONFIG_CGROUP_CPUACCT=y I do have CONFIG_CGROUP_CPUACCT=y Well, but why does 237 works with the very same kernel? Elimar -- Numeric stability is probably not all

Bug#892360: systemd: Breaks also all my tested amd64 machines

* Michael Biebl [2018-03-08 17:09 +0100]: > Am 08.03.2018 um 17:05 schrieb Michael Biebl: > > Control: tags -1 moreinfo > > > > Am 08.03.2018 um 16:23 schrieb valette: > > [...] > Could you check if > https://github.com/systemd/systemd/issues/8387 > looks related > > I.e.

Bug#892360: systemd pid 1 freezes at startup on x86 systems

* Michael Biebl [2018-03-08 17:05 +0100]: > Control: tags -1 moreinfo > > Am 08.03.2018 um 16:23 schrieb valette: > > > Kernel: Linux 4.14.23 (SMP w/2 CPU cores; PREEMPT) > > Is this also happening with a Debian provided kernel? > I see both you and Elimar use a custom

Bug#878625: systemd: NIS users login takes longtime.

Control: reassign -1 nis Control: retitle -1 "nscd should be a Depends" * Michael Biebl <bi...@debian.org> [2017-10-16 11:27 +0200]: > Control: forwarded -1 https://github.com/systemd/systemd/issues/7074 > > Am 15.10.2017 um 10:55 schrieb Elimar Riesebieter: > &g

Bug#878625: systemd: NIS users login takes longtime.

* Elimar Riesebieter <riese...@lxtec.de> [2017-10-17 18:24 +0200]: > * Michael Biebl <bi...@debian.org> [2017-10-17 16:38 +0200]: > > > Am 15.10.2017 um 11:15 schrieb Elimar Riesebieter: > > > * Elimar Riesebieter <riese...@lxtec.de> [2017-10-15 10:55

Bug#878625: systemd: NIS users login takes longtime.

* Elimar Riesebieter <riese...@lxtec.de> [2017-10-15 10:55 +0200]: > Package: systemd > Version: 235-2 > Severity: normal > > Login as a NIS user journalctl tells: > > systemd-logind[666]: do_ypcall: clnt_call: RPC: Unable to send; errno = > Operation not permitt

Bug#843251: Job for systemd-udevd.service failed because a timeout was exceeded.

* 積丹尼 Dan Jacobson [2016-11-06 06:11 +0800]: > severity 843251 grave > thanks > Yes i386. > And you know what? > the user cannot ever boot his computer ever again, even from grub > menus' "(recovery mode)". > > ER> I can confirm this behaviour. Be care to reboot: > ER> If

Bug#756261: libpam-systemd: rdepends on libpam-systemd can't run with sysvinit as libpam-systemd depend on systemd-sysv only

Package: libpam-systemd Version: 208-6 Severity: normal Please add an alternate dependency on sysvinit-core and respective on upstart, though. Elimar -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (990, 'unstable'), (100, 'experimental') Architecture:

Bug#756097: systemd: Can't build systemd in a chroot environment

* Michael Biebl bi...@debian.org [2014-07-26 13:25 +0200]: Am 26.07.2014 10:08, schrieb Elimar Riesebieter: Package: systemd Version: 208-6 Severity: serious Justification: fails to build from source (but built successfully in the past) Using pbuilder updated today. Build stops

Bug#754984: libpam-systemd 208-6 conflicts with sysvinit-core

* Michael Biebl bi...@debian.org [2014-07-17 17:25 +0200]: Am 17.07.2014 16:20, schrieb Elimar Riesebieter: [...] I don't see the intention? You should read the changelog then. Not understanding the intentions is not a justification for reopening a bug report which has been closed by its