http://bugzilla.suse.com/show_bug.cgi?id=934901 http://bugzilla.suse.com/show_bug.cgi?id=934901#c3 Dr. Werner Fink changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(mrueckert@suse.co | |m) --- Comment #3 from Dr. Werner Fink --- (In reply to Marcus Rückert from comment #2)

the package, which restarts systemd-logind, is the systemd package.

The only place where a try-restart is done is in %postun %postun /sbin/ldconfig if [ $1 -ge 1 ]; then /usr/bin/systemctl daemon-reload >/dev/null 2>&1 || : /usr/bin/systemctl try-restart systemd-logind.service >/dev/null 2>&1 || : fi %if ! 0%{?bootstrap} if [ $1 -eq 0 ]; then /usr/sbin/pam-config -d --systemd || : fi %endif and had never caused problem in past with systemd-210 nor with systemd-219. Which display manager do you use? Below xdm/fvwm2/su I can do an `rpm -Uhv' with the systemd-219 packages and see how on the last run dracut gnerates the initrds. The X11 session remains and stays usable. The same for `zypper install --force *.rpm' -- You are receiving this mail because: You are on the CC list for the bug.