Ubuntu
meta-kde package

"cannot unlock the session" during upgrade to Kubuntu 15.04

Bug #1448171 reported by Leon Maurer
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
meta-kde (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

I've tried upgrading two of my computers from Kubuntu 14.10 to 15.04. In both cases, I started the upgrade, left since it takes a long time to download, and when I came back I was unable to unlock the screen. I'd enter my password as usual and be told "cannot unlock the session because the authentication system failed to work". I tried switching to a terminal and killing the screen locker, but then I'd just return to a black screen. I don't want to restart the computers with the install partly completed (I don't know where it left off), but I don't see any other options...

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

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

Changed in meta-kde (Ubuntu):
status: New → Confirmed
Revision history for this message
alex (1alex) wrote :

The same happened to me and then I used top to verify if the update appeared to have completed and then rebooted.... it appears to have completed successfully but it took alot longer then usual to reboot which is probably normal for the first time... update-apt-xapo and baloo_file processses were running and using lots of CPU and the HDD

Revision history for this message
Leon Maurer (leon-n-maurer) wrote :

I managed to get everything working by rebooting then finishing the install from the command line (just had to tell dpkg to finish installing everything). Still, that shouldn't have been necessary...

Revision history for this message
alex (1alex) wrote :

definitely shouldn't happen but what command did you use to complete the install? "sudo do-release-upgrade -d" told me no new release was found, but "sudo apt-get autoremove" removed about 515mb of installed packages...

Revision history for this message
Leon Maurer (leon-n-maurer) wrote :

I think it was "sudo dpkg --configure -a". All the packages were downloaded, and the installation had started, so that command picked up where the updater had left off.

Jan W (ubuntu-kiekerjan)
tags: added: 17.04
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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