lost login after update 8.10 to 9.04a2

Bug #315887 reported by Peter T Hayward
4
Affects Status Importance Assigned to Milestone
Ubuntu
Invalid
Undecided
Unassigned

Bug Description

System: Ubuntu 8.10 running on Sony Vaio VGN-fs115B with 512M RAM, Intel i915 video and Intel 2200 NIC.
This is a disposable system for testing Jaunty.

I updated my 8.10 distribution to 9.04 alpha2 using the recommended command dist-upgrade -d
The upgrade completed, but vim-runtime was broken. I fixed that using the option in synaptic.
All looked OK and I rebooted.
The login screen came up as before - but no sound. I had sound with 8.10.
Put in login name and password.
The screen went blank then broke up into fuzzy vertical pattern. The logon screen reappeared.
I cannot now logon.
The session options allow a failsafe terminal, and that let me logon, using the credentials that I was using at normal logon screen (but not using any other credentials).
In the X terminal window I could run only as user, attempts to 'sudo su' failed.
My home directory was present and had normal permissions.
Since one bug had been reported (309541) for the user-setup package failing to create new encrypted user I checked for ecryptfs module (though I am updating and keeping my existing user this might be relevant).
No ecryptfs module loaded and not present in this kernel's modules.
It was present in modules for 8.10.
I have tried using an earlier kernel to boot from but his has the same problem (it is on the same partition).
No other ideas at present - my testing of 9.04 is suspended until I get a log on working.

Revision history for this message
Adil Arif (adisari06) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, according to this report, you are not using the most recent version of your Ubuntu release. Are you are still having this issue. Thanks in advance.

Changed in ubuntu:
status: New → Incomplete
Revision history for this message
Pedro Villavicencio (pedro) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.

Changed in ubuntu:
status: Incomplete → Invalid
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.