Bug#859189: systemd-logind: Unix group changes ignored by gdm/lightdm until logind is restarted

2017-03-31 Thread Nathan Dorfman
Control: retitle -1 systemd-logind: Unix group changes ignored by gdm/lightdm until logind is restarted On Fri, Mar 31, 2017 at 12:40:55PM +0200, Michael Biebl wrote: > When you log out, do you still have an open logind session for that user > (you can check that as root from the console via

Bug#802211: systemd: rescue.service fails if root password is not set, needs sulogin --force

2017-03-30 Thread Nathan Dorfman
On Fri, Mar 31, 2017 at 12:51:08AM +0200, Michael Biebl wrote: > Maybe I'm overly paranoid here, but maybe that helps to better > understand my concerns. No, your concerns sound reasonable to me, and I agree that demanding a username from group sudo, along with its password sounds like it could

Bug#802211: systemd: rescue.service fails if root password is not set, needs sulogin --force

2017-03-30 Thread Nathan Dorfman
Hi, this is still an issue with the default stretch install, if the option to not set a root password is taken at installation. It is quite severe IMO, especially considering how likely it is to be discovered only when the rescue shell is actually needed. If this really can't be fixed before

Bug#837893: systemd: Logging from gnome session is passed on to all syslog facilities

2017-03-25 Thread Nathan Dorfman
I think these messages are being (erroneously) passed specifically to the KERN facility, not all facilities as the summary states. For one thing, the superfluous messages don't appear in the user.log file, as they do in kern.log, despite the fact that rsyslogd is configured to route all

Bug#858211: (no subject)

2017-03-21 Thread Nathan Dorfman
Just to confirm, things seem OK with the following in system.conf: DefaultTimeoutStartSec=3s DefaultTimeoutStopSec=15s Everything including graphical desktop login comes up and down with no issues. I think it'd be slightly better to keep the longer timeout, but allow the console operator to

Bug#858211: systemd: uninterruptible wait if swap is missing, even in rescue boot

2017-03-20 Thread Nathan Dorfman
On Sun, Mar 19, 2017 at 09:53:58PM +0100, Michael Biebl wrote: > Since systemd starts everything in parallel, which service should > ctrl+c apply to? In this situation, systemd gives the distinct impression that all other jobs have started, and it is now waiting for just one. A countdown timer is

Bug#858162: /bin/systemctl: systemctl rescue hangs system cold if desktop session is active

2017-03-19 Thread Nathan Dorfman
On Mon, Mar 20, 2017 at 01:38:49AM +0100, Michael Biebl wrote: > Am 20.03.2017 um 01:36 schrieb Michael Biebl: > > The relevant bits are in the journal log > >> Mar 19 20:09:08 stretch systemd[1]: Stopped Login Service. > > > Some of those in between > > Mar 19 20:09:08 stretch dbus[451]: