Can't login to system, system is booting up error

Bug #1591622 reported by QkiZ
136
This bug affects 25 people
Affects Status Importance Assigned to Milestone
console-setup (Ubuntu)
Fix Released
High
Mathieu Trudel-Lapierre
Xenial
Fix Released
High
Mathieu Trudel-Lapierre
Yakkety
Fix Released
High
Mathieu Trudel-Lapierre

Bug Description

[Impact]
Regression in console-setup 1.108ubuntu15.1 in xenial-proposed which introduced a dependency loop caused logins to fail in around 10% of boots.

[Test case]
1) reboot
2) attempt to login

In the failure case, the system will display an error message:
"System is booting up. See pam_nologin(8)."

[Regression Potential]
This is intended to fix a regression already found in xenial-proposed due to dependencies in the systemd units. Other ordering issues may arise, such that it is possible for another process to otherwise fail to load because of the invalid dependencies between systemd jobs. Care is to be taken in testing the proposed fix, and involves many reboot tests.

---

On login screen (LightDM) I cant login to system because system error is displayed: System is booting up. See pam_nologin(8). This message is appearing randomly, sometimes when I boot system I can login and sometimes not. It starts to show after last console-setup-linux, console-setup and keyboard-configuration to version 1.108ubuntu15.1.
Photo with error in attachment.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: lightdm 1.18.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-23.41-lowlatency 4.4.10
Uname: Linux 4.4.0-23-lowlatency x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Sun Jun 12 08:50:29 2016
InstallationDate: Installed on 2015-02-13 (484 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
LightdmConfig:
 [Seat:*]
 allow-guest = false
SourcePackage: lightdm
UpgradeStatus: Upgraded to xenial on 2016-04-25 (47 days ago)
mtime.conffile..etc.init.lightdm.conf: 2015-06-08T20:05:20

Revision history for this message
QkiZ (qkiz) wrote :
Revision history for this message
glasairman (wlk461) wrote :

Me too for the last three days since 10.6.2016.

resolved by rebooting, after 1-2 tries its starts OK

Revision history for this message
QkiZ (qkiz) wrote :

I'd downgrade console-setup-linux, console-setup and keyboard-configuration to 1.108ubuntu15 and everything back to normal.

Revision history for this message
QkiZ (qkiz) wrote :

* I downgraded ...

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

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

Changed in lightdm (Ubuntu):
status: New → Confirmed
Revision history for this message
Chris Taklis (aka Kailor) (ctaklis) wrote :

@QkiZ (qkiz) how do you downgrade? because it affected me too today!

Revision history for this message
QkiZ (qkiz) wrote :

Downgrade:
sudo apt-get install console-setup-linux=1.108ubuntu15 console-setup=1.108ubuntu15 keyboard-configuration=1.108ubuntu15

Block updates for packages:
sudo apt-mark hold console-setup-linux console-setup keyboard-configuration

Revision history for this message
Gerard Louw (gerardlouw) wrote :

Also just got greeted by this message. QkiZ's fix seems to work for me as well (for the last few reboots), but given the sporadic nature of the bug I can't be sure.

Revision history for this message
QkiZ (qkiz) wrote :

It must be tested for next week, I think.

affects: lightdm (Ubuntu) → console-setup (Ubuntu)
Changed in console-setup (Ubuntu):
assignee: nobody → Mathieu Trudel-Lapierre (cyphermox)
importance: Undecided → High
Revision history for this message
QkiZ (qkiz) wrote :

I have another bug related to console-setup package but now I'm testing it. I will make another bug report for this package.

Revision history for this message
QkiZ (qkiz) wrote :
tags: added: regression-update
Revision history for this message
Mathieu Trudel-Lapierre (cyphermox) wrote :

This is a regression in proposed, not updates.

tags: added: regression-proposed
removed: regression-update
Revision history for this message
QkiZ (qkiz) wrote :

Which package have regression? And in which version?

Changed in console-setup (Ubuntu):
status: Confirmed → In Progress
description: updated
Changed in console-setup (Ubuntu Xenial):
status: New → Fix Released
status: Fix Released → In Progress
Changed in console-setup (Ubuntu Yakkety):
status: In Progress → Fix Released
Changed in console-setup (Ubuntu Xenial):
importance: Undecided → High
assignee: nobody → Mathieu Trudel-Lapierre (cyphermox)
Revision history for this message
Martin Pitt (pitti) wrote : Please test proposed package

Hello QkiZ, or anyone else affected,

Accepted console-setup into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/console-setup/1.108ubuntu15.2 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Changed in console-setup (Ubuntu Xenial):
status: In Progress → Fix Committed
tags: added: verification-needed
Revision history for this message
gregory pecqueur (anode7) wrote :

Hi,

This package fixes the bug for me

console-setup : 1.108ubuntu15.2

Thank you!

Revision history for this message
QkiZ (qkiz) wrote :

I have enabled proposed repo already. For two reboots I haven't problems. But this require more reboots to confirm. I will use system for few next days and add post if problem is resolved.

Revision history for this message
Marina Hildebrand (marina071170) wrote :

looks good so far. Had this bug on 3 of my machines and it seems Ok now.
But as QkiZ already says, this will need some more testing

Revision history for this message
QkiZ (qkiz) wrote :

I think that 1.108ubuntu15.2 version resolve problem.

tags: added: verification-done
removed: verification-needed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package console-setup - 1.108ubuntu15.2

---------------
console-setup (1.108ubuntu15.2) xenial; urgency=medium

  * Reorganize and correct console-setup, keyboard-setup and setvtrgb along the
    lines of the logic in 16.04: (LP: #1591622, #1593156)
    - debian/console-setup-linux.setvtrgb.service: don't require being run
      before system-getty.slice.
    - debian/keyboard-configuration.links: both console-setup and
      keyboard-setup systemd units should be installed to sysinit.target rather
      than multi-user.
    - debian/keyboard-configuration.keyboard-setup.service: move loadkeys call
      at local-fs-pre.target and in this more suitable location.
    - debian/keyboard-configuration.console-setup.service: move to running
      after the screen, keyboard, and filesystems are ready and set up all of
      what may still need to be done to configure the virtual consoles
      appropriately: set a final keymap, font, etc.

console-setup (1.108ubuntu15.1) xenial; urgency=medium

  * debian/console-setup-linux.setvtrgb.service: port the upstart job for
    applying our preferred color settings to a systemd unit so it gets run.
    This will fix debconf prompts on console being extra ugly. (LP: #1576893)
  * debian/console-setup-linux.links: enable our setvtrgb service in sysinit.
  * debian/keyboard-configuration.links: fix link source for console-setup
    service. (LP: #1572697)
  * debian/control: add dh-systemd to Build-Depends.
  * debian/keyboard-configuration.keyboard-setup.service: also enable
    keyboard-setup as a systemd service so we can have proper keymaps enabled
    in VTs. (LP: #1579267)
  * debian/keyboard-configuration.links: enable keyboard-setup service.

 -- Mathieu Trudel-Lapierre <email address hidden> Thu, 16 Jun 2016 14:41:19 +0300

Changed in console-setup (Ubuntu Xenial):
status: Fix Committed → Fix Released
Revision history for this message
Adam Conrad (adconrad) wrote : Update Released

The verification of the Stable Release Update for console-setup has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

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

Duplicates of this bug

Other bug subscribers

Remote bug watches

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