-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, Finally pushed one of my desktop machines to 13.2 and things didn't go quite as I had hoped for :( The behavior I am observing is consistent with behavior I have seen in the past when there was trouble with NIS, i.e. everything login, starting of a terminal session, the appearance of the login screen takes forever. Could use some help trying to sort this out. systemd provides the following information: # systemctl restart systemd-logind.service Job for systemd-logind.service failed. See "systemctl status systemd-logind.service" and "journalctl -xn" for details. # journalctl -xn - -- Logs begin at Sat 2015-03-07 19:07:33 EST, end at Sun 2015-03-08 06:53:21 EDT. -- Mar 08 06:52:30 lion systemd-logind[7781]: Failed to fully start up daemon: Connection timed out Mar 08 06:52:30 lion dbus[876]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out Mar 08 06:52:30 lion systemd[1]: Cannot add dependency job for unit cups.socket, ignoring: Unit cups.socket failed to load: No such file or directory. Mar 08 06:52:56 lion dbus[876]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out Mar 08 06:52:56 lion systemd-logind[7787]: Failed to fully start up daemon: Connection timed out Mar 08 06:52:56 lion systemd[1]: Failed to start Login Service. - -- Subject: Unit systemd-logind.service has failed - -- Defined-By: systemd - -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel - -- - -- Unit systemd-logind.service has failed. - -- - -- The result is failed. Mar 08 06:53:21 lion systemd-logind[7789]: Failed to enable subscription: Connection timed out Mar 08 06:53:21 lion systemd-logind[7789]: Failed to fully start up daemon: Connection timed out Mar 08 06:53:21 lion dbus[876]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out Mar 08 06:53:21 lion systemd[1]: Cannot add dependency job for unit cups.socket, ignoring: Unit cups.socket failed to load: No such file or directory. ypwhich returns the name of the nis server thus I think it is not an nis issue, but the behavior certainly is the same. - From the output, obviously cups has issues, but I do not understand why that would delays w.r.t. login or starting applications. Help is much appreciated. Thanks, Robert - -- Robert Schweikert MAY THE SOURCE BE WITH YOU Public Cloud Architect LINUX rjschwei@suse.com IRC: robjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQEcBAEBAgAGBQJU/C0WAAoJEE4FgL32d2UkUtoH/2EaDkQuRRJtNCYdbkzzMmdh dWnfxE40bgczPeCE2spaEUWv+UBx+K0mNxkH2UjeQf7DytYIvtCzmk9+VGD1bMsv sZPJXGHZ6KT8OxBz6+3I8o7SQ3pYmZ6g30Zhe2osy88SxBSywfVh7tDA1KXc8apj bx9BAR36Q8wgAXOuGjdAsA/CQhWjfA2Jys4tnxEfXoc6b28Ef9cyzLwv7QpKwqxw ianU9DexLigE9kcdcOIvcDTEBUGyhUFb27SoSVbdNPGVVdUgSnky4dwjxkYa9mkg 2KmrRq7aEucgS4h8XJFN9ZyCKOX7dlx21US3LKViZF/jS/4BUD1wekJrNy64cdU= =kv2U -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org