Bug#902336: systemd: sddm login screen does not appear until after more than a minute

[Martin Steigerwald]

Dear Michael.

Thank you for your replies.

Michael Biebl - 25.06.18, 10:26:
> Am 25.06.2018 um 10:14 schrieb Martin Steigerwald:
> > severity 902336 important
> > thanks
> > 
> > Martin Steigerwald - 25.06.18, 09:18:
> >> Package: systemd
> >> Version: 239-1
> >> Severity: normal
> > 
> > […]
> > 
> >> % systemctl --state=failed
> >> 
> >>   UNIT           LOAD   ACTIVE SUB    DESCRIPTION
> >> 
> >> ● chrony.service loaded failed failed chrony, an NTP client/server
> >> ● upower.service loaded failed failed Daemon for power management
> >> […]
> > 
> > Regarding upower I see:
> > 
> > Jun 25 10:01:08 merkaba upowerd[6031]: /usr/lib/upower/upowerd:
> > error while
> > loading shared libraries: libffi.so.6: cannot enable executable 
stack as shared object requires:
> [..]
> 
> > As I need back a working system, I removed any and all privilege
> > limitations
> > from upower service, so that only:
> Do you have SELinux, AppArmor, a GRSecurity enabled kernel or
> something like this enabled?
> 
> The results from booting with a Debian provided kernel would be useful
> as well.
> 
> Your problem might be seccomp related.

None of this:

% egrep "SELINUX|APPARMOR" /boot/config-4.17.0-tp520-btrfstrim+ 
# CONFIG_SECURITY_APPARMOR is not set

No GRSecurity either.

No difference in SECCOMP options between Debian and my kernel as
far as I can tell:

% egrep "SECCOMP" /boot/config-4.17.0-tp520-btrfstrim+
CONFIG_HAVE_ARCH_SECCOMP_FILTER=y
CONFIG_SECCOMP_FILTER=y
CONFIG_SECCOMP=y

% egrep "SECCOMP" /boot/config-4.16.0-2-amd64         
CONFIG_HAVE_ARCH_SECCOMP_FILTER=y
CONFIG_SECCOMP_FILTER=y
CONFIG_SECCOMP=y

May schedule a 4.16 and then a 4.17 debian kernel reboot after paid
work. I did not have any issues as I still had self-compiled 4.16 kernel
installed. But that might be co-incidence as I run unstable and may
have updated whatever else at a similar time.

Thanks,
-- 
Martin