Bug#864341: systemd-sysctl: failed to apply sysctl config at bootup

Hi, any news? We are being hit by this bug, which is a bit annoying. Are upstream systemd developers aware of this issue? best regards ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.o

Processed: block 873661 with 871514

Processing commands for cont...@bugs.debian.org: > block 873661 with 871514 Bug #873661 [src:systemd] Switch back to default GCC 873661 was not blocked by any bugs. 873661 was not blocking any bugs. Added blocking bug(s) of 873661: 871538, 871514, 872987, and 872438 > thanks Stopping processing he

Bug#873661: Switch back to default GCC

Source: systemd Version: 234-2.3 Severity: normal Due to bug in GCC-7 on mips64el, which caused test-suite failures, systemd was switched to GCC-6 to work around that issue. Once #871514 is fixed, we should drop export CC = gcc-6 export CXX = g++-6 from debian/rules again. -- Package-specific i

Processed: Re: Bug#806256: libpam-systemd: log out from a TTY and your X input devices get lost!

Processing control commands: > found -1 systemd/234-2.3 Bug #806256 [libpam-systemd] libpam-systemd: log out from a TTY and your X input devices get lost! Bug #867745 [libpam-systemd] libpam-systemd: log out from a TTY and your X input devices get lost! Marked as found in versions systemd/234-2.

Bug#806256: libpam-systemd: log out from a TTY and your X input devices get lost!

Control: found -1 systemd/234-2.3 On Sat, 31 Dec 2016 16:10:13 +0100 Francesco Poli wrote: [...] > On Fri, 30 Dec 2016 19:37:48 +0100 Michael Biebl wrote: > > > On Sat, 13 Feb 2016 22:02:02 +0100 Francesco Poli > > wrote: > [...] > > > Hello again, > > > have you found a way to reproduce the b

Processed: Debian bug: #873638

Processing commands for cont...@bugs.debian.org: > retitle 873638 Don't use systemd-timesyncd if ntpd or other time syncing > program is running Bug #873638 [systemd] Don't use systemd-timesyncd if ntpd or other time syncing program Changed Bug title to 'Don't use systemd-timesyncd if ntpd or o

Bug#873628: systemd: Apparent regression on #825394, logind.conf accepts upstream default of KillUserProcesses=yes

Control: tags -1 confirmed pending On Tue, Aug 29, 2017 at 1:32 PM, Frisco Rose, Ph.D. wrote: > Package: systemd > Version: 234-2.3 > Severity: normal > > Dear Maintainer, > > According to > bugs.debian.org/cgi-bin/bugreport.cgi?bug=825394 > > Either compile systemd with --without-kill-user-pr

Processed: Re: Bug#873628: systemd: Apparent regression on #825394, logind.conf accepts upstream default of KillUserProcesses=yes

Processing control commands: > tags -1 confirmed pending Bug #873628 [systemd] systemd: Apparent regression on #825394, logind.conf accepts upstream default of KillUserProcesses=yes Added tag(s) pending and confirmed. -- 873628: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873628 Debian Bu

Bug#873613: systemd gets confused at shutdown time

Control: tags -1 moreinfo On Tue, Aug 29, 2017 at 10:35 AM, Harald Dunkel wrote: > Package: systemd > Version: 232-25+deb9u1 > > At shutdown time systemd just shows a message saying > > watchdog: watchdog0: watchdog did not stop! > > for 5 minutes :-(. > > If I boot without quiet, then sy

Processed: Re: Bug#873613: systemd gets confused at shutdown time

Processing control commands: > tags -1 moreinfo Bug #873613 [systemd] systemd gets confused at shutdown time Added tag(s) moreinfo. -- 873613: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873613 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#873613: systemd gets confused at shutdown time

Package: systemd Version: 232-25+deb9u1 At shutdown time systemd just shows a message saying watchdog: watchdog0: watchdog did not stop! for 5 minutes :-(. If I boot without quiet, then systemd reveals that it gets confused by service dependencies, nfs mount points and probably some v