When I login to my Ubuntu 13.04 beta2 (std Unity) session, after I enter the password, there is a deferral of some seconds which is not there on my 12.04. LTS partition.
Can this be related to the dmesg output:
[ 37.101723] systemd-logind[2350]: New seat seat0.
[ 37.101785] systemd-logind[2350]: Failed to save seat data for seat0: No such file or directory
and if so, what does it mean? I tried to google that lines but could not find any helpful references.
Using aptitude gave me the following information:
aptitude search systemd
p libpam-systemd - system and service manager - PAM module
p libpam-systemd:i386 - system and service manager - PAM module
p libsystemd-daemon-dev - systemd utility library - development files
p libsystemd-daemon-dev:i386 - systemd utility library - development files
i libsystemd-daemon0 - systemd utility library
p libsystemd-daemon0:i386 - systemd utility library
p libsystemd-id128-0 - systemd 128 bit ID utility library
p libsystemd-id128-0:i386 - systemd 128 bit ID utility library
p libsystemd-id128-dev - systemd 128 bit ID utility library - development
p libsystemd-id128-dev:i386 - systemd 128 bit ID utility library - development
p libsystemd-journal-dev - systemd journal utility library - development files
p libsystemd-journal0 - systemd journal utility library
p libsystemd-journal0:i386 - systemd journal utility library
p libsystemd-login-dev - systemd login utility library - development file
p libsystemd-login-dev:i386 - systemd login utility library - development file
p libsystemd-login0 - systemd login utility library
p libsystemd-login0:i386 - systemd login utility library
p live-config-systemd - Live System Configuration Scripts (systemd backend)
p python-systemd - python bindings for the systemd journal
p python-systemd:i386 - python bindings for the systemd journal
i systemd-services - systemd runtime services
p systemd-services:i386 - systemd runtime services
i systemd-shim - shim for systemd
p systemd-shim:i386 - shim for systemd