Ubuntu
systemd package

Don't run logind in a default raring installation

Bug #1167642 reported by Harald Höller
20
This bug affects 2 people
Affects Status Importance Assigned to Milestone
systemd (Ubuntu)
Fix Released
Medium
Martin Pitt
Ubuntu ubuntu-13.04

Bug Description

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 outpu?:

[ 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.

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: login 1:4.1.5.1-1ubuntu3
ProcVersionSignature: Ubuntu 3.8.0-16.26-generic 3.8.5
Uname: Linux 3.8.0-16-generic x86_64
ApportVersion: 2.9.2-0ubuntu5
Architecture: amd64
Date: Wed Apr 10 17:22:43 2013
InstallationDate: Installed on 2013-04-07 (3 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130402.1)
MarkForUpload: True
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: shadow
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Harald Höller (harald-hoeller) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in shadow (Ubuntu):
status: New → Confirmed
Harald Höller (harald-hoeller)
affects: shadow (Ubuntu) → systemd (Ubuntu)
Revision history for this message
Martin Pitt (pitti) wrote :

For raring we shouldn't run logind in the first place. I think it's best to not install the D-BUS *.service file for raring, and only let logind be started through the upstart job that we ship in libpam-systemd (i. e. when you actually want to use logind instead of ConsoleKit). Putting on my list for raring final, thanks for the report!

Changed in systemd (Ubuntu):
assignee: nobody → Martin Pitt (pitti)
importance: Undecided → Medium
milestone: none → ubuntu-13.04
status: Confirmed → In Progress
summary: - 13.04 login: lagging after password entry for several seconds
+ Don't run logind in a default raring installation
Revision history for this message
Martin Pitt (pitti) wrote :

BTW, the delay seems unrelated to that logind error message; that should be quite harmless. Without libpam-systemd installed, lightdm does not use logind.

Revision history for this message
Martin Pitt (pitti) wrote :

Fix uploaded, needs release team review.

Changed in systemd (Ubuntu):
status: In Progress → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package systemd - 198-0ubuntu10

---------------
systemd (198-0ubuntu10) raring; urgency=low

  * debian/systemd-services.install: Don't install the D-BUS activation file
    for logind. Without libpam-systemd's upstart job (which sets up the
    cgroups) it does not work anyway, and with the upstart job it is already
    running anyway. We'll put that back in raring+1 to respawn after crashes,
    but for raring we do not want to run logind by default. (LP: #1167642)
 -- Martin Pitt <email address hidden> Fri, 12 Apr 2013 06:44:27 +0200

Changed in systemd (Ubuntu):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.