org.freedesktop.login1.service references non-existant systemd-logind-launcher, gdm will not start

Bug #1302331 reported by Mercury
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
systemd (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

debian/patches/debian-changes alters systemd-204/src/login/org.freedesktop.login1.service to exec /lib/systemd/systemd-logind-launch, instead of /bin/false.

systemd-logind-launch is in debian/, and the override_dh_install rule in debian/rules does an install.

Sadly, systemd-logind-launch is not listed in systemd-services.install, so it does not actually get built into the package.

The result is a Ubuntu Gnome 14.04 installation which will sit on the booting screen indefinitely, with gdm refusing to start.

This was not happening in 204-5ubuntu13, and is happening in 204-5ubuntu16.

Manually copiing systemd-logind-launch from the source package to /lib/systemd results in a booting system once more.

(Well, you could alawys switch VTs and login that way, but that is not all that useful for most people.)

The correct fix appears to simply be adding lib/system/systemd-logind-launch to debian/systemd/services.install in the source package.

Zephaniah E. Loss-Cutler-Hull.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: systemd-services 204-5ubuntu16 [modified: usr/share/dbus-1/system-services/org.freedesktop.login1.service]
Uname: Linux 3.14.0-f1-dirty x86_64
ApportVersion: 2.14-0ubuntu1
Architecture: amd64
CurrentDesktop: GNOME
Date: Thu Apr 3 23:52:24 2014
InstallationDate: Installed on 2014-03-16 (19 days ago)
InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140226)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/zsh
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Mercury (warp-spam-launchpad) wrote :
Revision history for this message
Mercury (warp-spam-launchpad) wrote :

With 204-5ubuntu17 the package is still not shipping systemd-logind-launch, which is still referred to by /usr/share/dbus-1/system-services/org.freedesktop.login1.service.

I'll have to retest to see if my system will boot properly without it, but even if so, that would be a change in impact, but not of the bug itself.

Revision history for this message
أحمد المحمودي (Ahmed El-Mahmoudy) (aelmahmoudy) wrote :

I just tested the fix reported by Mercury and it worked. Thanks !

Revision history for this message
Launchpad Janitor (janitor) wrote :

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

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

Other bug subscribers

Remote bug watches

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