Bug#834367: systemctl daemon-reexec (as run on systemd upgrade) causes all keystrokes to go to text console in addition to X (including passwords)

Package: systemd Version: 231-2 Severity: critical Tags: security [Severity and tag due to the likely possibility of exposing user passwords this way. If this occurs with the version in jessie as well, it'll require a security update.] After running "systemctl daemon-reexec" from within an X

Bug#832713: systemd: after "systemd (231-1) unstable" update systemd-jurnald.service fails to start

On 14 août 2016 23:38, Pete Batard wrote: > Didn't fix it for me... :( Same for me, still broken. Christian ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org

Bug#832713: closed by Martin Pitt <mp...@debian.org> (Bug#832893: fixed in systemd 231-2)

Sorry, it’s not fixed in 231-2… Please see attached boot log. Rick screenlog.xz Description: Binary data ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org

Bug#832713: systemd: after "systemd (231-1) unstable" update systemd-jurnald.service fails to start

Didn't fix it for me... :( I went to an 'apt-get --reinstall install' of every single package that is listed under 'Description' above (expect -udeb and -dev), and got the 231-2 version alright, but the issue remains exactly the same, even after a full reboot. I should point out that I did

Bug#834228: systemd: /run/utmp is created with the wrong SE Linux context

Control: tags -1 moreinfo On 13 August 2016 at 09:37, Russell Coker wrote: > Package: systemd > Version: 231-1 > Severity: normal > Tags: upstream > > The file /run/utmp is created with the wrong type on SE Linux systems. The > program that creates is should either run

Processed: Re: Bug#834228: systemd: /run/utmp is created with the wrong SE Linux context

Processing control commands: > tags -1 moreinfo Bug #834228 [systemd] systemd: /run/utmp is created with the wrong SE Linux context Added tag(s) moreinfo. -- 834228: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834228 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#834164: systemd: Services are not killed after a timeout or killed immediately after ExecStop

On 13 August 2016 at 05:12, Dark Penguin wrote: >> In short, you need to make your ExecStop wait for the process to exit. >> The manpage in later versions is more explicit in this regard: >> >> Note that it is usually not sufficient to specify a >>

Bug#833487: marked as done (systemd: Replaces file in systemd-container 230-1)

Your message dated Sun, 14 Aug 2016 11:19:29 + with message-id and subject line Bug#833487: fixed in systemd 231-2 has caused the Debian Bug report #833487, regarding systemd: Replaces file in systemd-container 230-1 to be marked as done. This means that

Processing of systemd_231-2_amd64.changes

systemd_231-2_amd64.changes uploaded successfully to localhost along with the files: systemd_231-2.dsc systemd_231-2.debian.tar.xz libnss-myhostname-dbgsym_231-2_amd64.deb libnss-myhostname_231-2_amd64.deb libnss-mymachines-dbgsym_231-2_amd64.deb libnss-mymachines_231-2_amd64.deb

Processed: tagging 832713

Processing commands for cont...@bugs.debian.org: > tags 832713 + pending Bug #832713 [systemd] systemd: after "systemd (231-1) unstable" update systemd-jurnald.service fails to start Bug #832893 [systemd] Failed at step SECCOMP spawning systemd-networkd Added tag(s) pending. Added tag(s)

Bug#833849: systemd: localed fails to start if /etc/default/keyboard is missing

Hello Simon, Felipe, Felipe Sateler [2016-08-12 11:16 -0300]: > Thanks for the patch.This makes a lot of sense, especially because > ENOENT is tolerated everywhere in that file. Indeed, thanks! I added a test case for this which reproduced the failure and confirms the fix: