systemd-logind failed to enable subscription: launch helper exited with unknown return code 1

Bug #1527843 reported by LAZA
30
This bug affects 3 people
Affects Status Importance Assigned to Milestone
systemd (Ubuntu)
Invalid
Undecided
Unassigned
Wily
Expired
Undecided
Unassigned

Bug Description

Started my machine succesfully at night and the next morning the screen is blank/black and no GUI available.
Switching to TTY1 i got after the login these messages:

[31989] systemd-logind[4272]: Failed to enable subscription: Launch helper exited with unknown return code 1
[31989] systemd-logind[4272]: Failed to fully start up daemon: Input/output error

The much bigger problem is:
PC does *not* start with normal boot options, i have to choose manually the upstart option in GRUB2.
#1527806

It is a fresh installed Xubuntu 15.10, all packages installed via Synaptic or CLI.

Xubuntu 15.10

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

This does not apply to 16.04 any more, the launch helper got eliminated completely. That said, 15.10 under upstart still ought to work. Please attach /var/log/syslog.

> PC does *not* start with normal boot options,

See bug 1527806 how to fix that.

Changed in systemd (Ubuntu):
status: New → Invalid
Changed in systemd (Ubuntu Wily):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for systemd (Ubuntu Wily) because there has been no activity for 60 days.]

Changed in systemd (Ubuntu Wily):
status: Incomplete → Expired
Revision history for this message
biondi fernando (biondi-fernando) wrote :

I recently upgraded from Ubuntu 14.04 LTS to 16.04 LTS and was using it normally for one week , until I had to suddenly power off the machine due to a black out and gives me two errors while attempting to boot normally a) systemd -logind: Failed to enable subscription :Launh helper exited with unknown return code 1 b) Failed to fully start up deamon Input/Output error .Only boots on recovery mode .Please HELP

Revision history for this message
biondi fernando (biondi-fernando) wrote :
Download full text (288.7 KiB)

 attaching my /var/log/syslog : May 3 03:47:16 hp-laptop rsyslogd: [origin software="rsyslogd" swVersion="8.16.0" x-pid="1153" x-info="http://www.rsyslog.com"] rsyslogd was HUPed
May 3 03:47:46 hp-laptop anacron[1148]: Job `cron.daily' terminated
May 3 03:47:46 hp-laptop anacron[1148]: Normal exit (1 job run)
May 3 03:51:49 hp-laptop kernel: [ 690.994586] perf interrupt took too long (5004 > 5000), lowering kernel.perf_event_max_sample_rate to 25000
May 3 03:55:32 hp-laptop systemd[1]: Starting Cleanup of Temporary Directories...
May 3 03:55:32 hp-laptop systemd-tmpfiles[3025]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring.
May 3 03:55:32 hp-laptop systemd[1]: Started Cleanup of Temporary Directories.
May 3 04:04:22 hp-laptop systemd[1]: Stopping Manage, Install and Generate Color Profiles...
May 3 04:04:22 hp-laptop systemd[1]: Stopping ACPI event daemon...
May 3 04:04:22 hp-laptop systemd[1]: Stopping Daemon for generating UUIDs...
May 3 04:04:22 hp-laptop systemd[1]: Closed Load/Save RF Kill Switch Status /dev/rfkill Watch.
May 3 04:04:22 hp-laptop systemd[1]: Stopping Disk Manager...
May 3 04:04:22 hp-laptop systemd[1]: Stopping RealtimeKit Scheduling Policy Service...
May 3 04:04:22 hp-laptop systemd[1]: Starting Unattended Upgrades Shutdown...
May 3 04:04:23 hp-laptop systemd[1]: Stopping Daemon for power management...
May 3 04:04:23 hp-laptop systemd[1]: Stopping User Manager for UID 1000...
May 3 04:04:23 hp-laptop systemd[1]: Stopping Save/Restore Sound Card State...
May 3 04:04:23 hp-laptop kernel: [ 1444.558411] mtrr: no MTRR for d0000000,770000 found
May 3 04:04:24 hp-laptop rsyslogd: [origin software="rsyslogd" swVersion="8.16.0" x-pid="1153" x-info="http://www.rsyslog.com"] exiting on signal 15.
May 3 04:10:23 hp-laptop rsyslogd: [origin software="rsyslogd" swVersion="8.16.0" x-pid="593" x-info="http://www.rsyslog.com"] start
May 3 04:10:23 hp-laptop kernel: [ 0.000000] microcode: CPU0 microcode updated early to revision 0x95, date = 2010-10-02
May 3 04:10:23 hp-laptop kernel: [ 0.000000] Initializing cgroup subsys cpuset
May 3 04:10:23 hp-laptop kernel: [ 0.000000] Initializing cgroup subsys cpu
May 3 04:10:23 hp-laptop kernel: [ 0.000000] Initializing cgroup subsys cpuacct
May 3 04:10:23 hp-laptop kernel: [ 0.000000] Linux version 4.4.0-21-generic (buildd@lgw01-21) (gcc version 5.3.1 20160413 (Ubuntu 5.3.1-14ubuntu2) ) #37-Ubuntu SMP Mon Apr 18 18:33:37 UTC 2016 (Ubuntu 4.4.0-21.37-generic 4.4.6)
May 3 04:10:23 hp-laptop kernel: [ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic root=UUID=1711b353-f958-4cba-8691-5f8eba70dfe1 ro quiet splash init=/sbin/upstart
May 3 04:10:23 hp-laptop kernel: [ 0.000000] KERNEL supported cpus:
May 3 04:10:23 hp-laptop kernel: [ 0.000000] Intel GenuineIntel
May 3 04:10:23 hp-laptop kernel: [ 0.000000] AMD AuthenticAMD
May 3 04:10:23 hp-laptop kernel: [ 0.000000] Centaur CentaurHauls
May 3 04:10:23 hp-laptop kernel: [ 0.000000] x86/fpu: Legacy x87 FPU detected.
May 3 04:10:23 hp-laptop kernel: [ 0.000000] x86/fpu: Using 'lazy' FPU context switches.
May 3 04:10:23 hp-laptop...

Revision history for this message
Eric Bruce (ericb7799) wrote :

Found your post after I had the exact same problem after installing some packages, in my case looks like caused by blueman2.0.4-1ubuntu2

You may have a different cause but symptoms looks about the same. I just got my system back up by running the following from the cmd line once you log in to the CLI:

sudo start lightdm

Revision history for this message
Sergey Kruglov (spiderman82) wrote :

I deleted Bluеman, but the system will not boot normally. At boot time, offers to enter into emergency mod! When loading upstart mode, the system boots in console mode tty1.

my syslog

Revision history for this message
Larry Griffin (l-g-griffin) wrote :

( knocked my laptop off the table and I have the same problem is there any work around??

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

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