After upgrade, cannot login
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ubuntu-release-upgrader (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
Upon upgrading to Ubuntu 15.04, I am not able to login.
It takes me to the login screen. When I login, the screen goes black, and then for no reason I'm on the login screen again. No invalid password, nothing.
1. My ubuntu version= 15.04
2. I do not know what package is causing this.
3. What I expected to happen: After typing in my login credetials, I would be taken to my desktop.
4. What actually happened: After typing in my credentials, I was returned to the login screen with no error messsages whatsoever.
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: ubuntu-
ProcVersionSign
Uname: Linux 3.16.0-34-generic i686
ApportVersion: 2.17.2-0ubuntu1.1
Architecture: i386
CrashDB: ubuntu
Date: Wed Jul 1 09:08:30 2015
InstallationDate: Installed on 2015-04-04 (87 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release i386 (20141022.1)
PackageArchitec
ProcEnviron:
TERM=linux
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: ubuntu-
Symptom: dist-upgrade
UpgradeStatus: Upgraded to vivid on 2015-07-01 (0 days ago)
There were a ton of errors contacting the us.archive. ubuntu. com mirror during your upgrade.
2015-06-30 21:20:09,283 ERROR IOError in cache.commit(): 'Failed to fetch http:// us.archive. ubuntu. com/ubuntu/ pool/main/ b/base- files/base- files_7. 2ubuntu9_ i386.deb Could not resolve 'us.archive. ubuntu. com' us.archive. ubuntu. com/ubuntu/ pool/main/ b/bash/ bash_4. 3-11ubuntu2_ i386.deb Could not resolve 'us.archive. ubuntu. com' us.archive. ubuntu. com/ubuntu/ pool/main/ s/systemd/ libsystemd0_ 219-7ubuntu6_ i386.deb Could not resolve 'us.archive. ubuntu. com' us.archive. ubuntu. com/ubuntu/ pool/main/ libc/libcap2/ libcap2_ 2.24-6_ i386.deb Could not resolve 'us.archive. ubuntu. com'
Failed to fetch http://
Failed to fetch http://
Failed to fetch http://
I would try logging in via a different desktop session and try running update-manager.