when the screen locks while upgrading ubuntu, login is not possible anymore

Bug #319332 reported by coCoKNIght
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Software Updater
Invalid
Undecided
Unassigned
update-manager (Ubuntu)
New
Undecided
Unassigned

Bug Description

While upgrading to jaunty at some point during the actual instalation process I was unable to unlock the screen (My machine locks the screen after 5 minutes). My password would just not be accepted anymore.

Changed in update-manager:
status: New → Invalid
Revision history for this message
Tim Casey (tjcasey) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better.

We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test a current, supported, Ubuntu version.

If you test it, and it is still an issue, we would appreciate if you could upload updated logs by running apport-collect <bug #>, and the log files from /var/log/dist-upgrade/ (if any).

Changed in update-manager (Ubuntu):
status: New → Incomplete
tags: added: intrepid2jaunty
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for update-manager (Ubuntu) because there has been no activity for 60 days.]

Changed in update-manager (Ubuntu):
status: Incomplete → Expired
Revision history for this message
James Lewis (james-fsck) wrote :

This just happened to me while upgrading from 17.04 to 17.10..... It may be hard to replicate, but if the screen locks at the wrong moment, after the system has started updating packages it leaves it in a state where it cannot be unlocked.

I was left with a locked system, and an incomplete upgrade which I am still attempting to repair manually.

Changed in update-manager (Ubuntu):
status: Expired → New
Revision history for this message
James Lewis (james-fsck) wrote :

See attached image... this did not recover to a working state, and I was forced to kill the X session / dpkg components after waiting 12 hours... and attempt manual repair of the system.

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.