“Failed to start session†after interrupted upgrade to 14.04
Clash Royale CLAN TAG#URR8PPP up vote
12
down vote
favorite
While upgrading to 14.04 using sudo do-release-upgrade my network connection was interrupted and several packages failed to upgrade.
Running do-release-upgrade again reported No new releases found but apt-get listed many packages "kept back", so it seemed the system was in an intermediate state. I ran apt-get dist-upgrade which installed those packages again, then apt-get autoremove after which apt seemed happy.
However, after restarting I cannot log in at the GUI prompt. After entering my password the error "Failed to start session" appears in red. I am still able to log in from the command prompt, but I don't know what to do to solve or debug the GUI log in failure.
upgrade login-screen 14.04
asked Apr 19 '14 at 12:01
Ian Mackinnon
72411436
add a comment |Â
up vote
12
down vote
favorite
While upgrading to 14.04 using sudo do-release-upgrade my network connection was interrupted and several packages failed to upgrade.
Running do-release-upgrade again reported No new releases found but apt-get listed many packages "kept back", so it seemed the system was in an intermediate state. I ran apt-get dist-upgrade which installed those packages again, then apt-get autoremove after which apt seemed happy.
However, after restarting I cannot log in at the GUI prompt. After entering my password the error "Failed to start session" appears in red. I am still able to log in from the command prompt, but I don't know what to do to solve or debug the GUI log in failure.
upgrade login-screen 14.04
asked Apr 19 '14 at 12:01
Ian Mackinnon
72411436
3
@Elliott, tryCtrl-Alt-F1to get a shell login prompt. Then you useCtrl-Alt-F7to get back to the GUI.
– Ian Mackinnon
Apr 21 '14 at 11:01
1
This worked for me sudo apt-get install --reinstall ubuntu-session
– Aravinda
May 2 '15 at 3:14
add a comment |Â
up vote
12
down vote
favorite
up vote
12
down vote
favorite
While upgrading to 14.04 using sudo do-release-upgrade my network connection was interrupted and several packages failed to upgrade.
Running do-release-upgrade again reported No new releases found but apt-get listed many packages "kept back", so it seemed the system was in an intermediate state. I ran apt-get dist-upgrade which installed those packages again, then apt-get autoremove after which apt seemed happy.
However, after restarting I cannot log in at the GUI prompt. After entering my password the error "Failed to start session" appears in red. I am still able to log in from the command prompt, but I don't know what to do to solve or debug the GUI log in failure.
upgrade login-screen 14.04
asked Apr 19 '14 at 12:01
Ian Mackinnon
72411436
While upgrading to 14.04 using sudo do-release-upgrade my network connection was interrupted and several packages failed to upgrade.
Running do-release-upgrade again reported No new releases found but apt-get listed many packages "kept back", so it seemed the system was in an intermediate state. I ran apt-get dist-upgrade which installed those packages again, then apt-get autoremove after which apt seemed happy.
However, after restarting I cannot log in at the GUI prompt. After entering my password the error "Failed to start session" appears in red. I am still able to log in from the command prompt, but I don't know what to do to solve or debug the GUI log in failure.
upgrade login-screen 14.04
upgrade login-screen 14.04
asked Apr 19 '14 at 12:01
Ian Mackinnon
72411436
asked Apr 19 '14 at 12:01
Ian Mackinnon
72411436
asked Apr 19 '14 at 12:01
Ian Mackinnon
72411436
asked Apr 19 '14 at 12:01
Ian Mackinnon
72411436
asked Apr 19 '14 at 12:01
Ian Mackinnon
72411436
72411436
3
@Elliott, tryCtrl-Alt-F1to get a shell login prompt. Then you useCtrl-Alt-F7to get back to the GUI.
– Ian Mackinnon
Apr 21 '14 at 11:01
1
This worked for me sudo apt-get install --reinstall ubuntu-session
– Aravinda
May 2 '15 at 3:14
add a comment |Â
3
@Elliott, tryCtrl-Alt-F1to get a shell login prompt. Then you useCtrl-Alt-F7to get back to the GUI.
– Ian Mackinnon
Apr 21 '14 at 11:01
1
This worked for me sudo apt-get install --reinstall ubuntu-session
– Aravinda
May 2 '15 at 3:14
3
3
@Elliott, try
Ctrl-Alt-F1 to get a shell login prompt. Then you use Ctrl-Alt-F7 to get back to the GUI.– Ian Mackinnon
Apr 21 '14 at 11:01
@Elliott, try
Ctrl-Alt-F1 to get a shell login prompt. Then you use Ctrl-Alt-F7 to get back to the GUI.– Ian Mackinnon
Apr 21 '14 at 11:01
1
1
This worked for me sudo apt-get install --reinstall ubuntu-session
– Aravinda
May 2 '15 at 3:14
This worked for me sudo apt-get install --reinstall ubuntu-session
– Aravinda
May 2 '15 at 3:14
add a comment |Â
3 Answers
3
active
oldest
votes
up vote
15
down vote
accepted
After issuing the following command I was able to log in again:
sudo apt-get install ubuntu-desktop
I had previously removed update-notifier which caused some other packages to be removed, some of which it seems were necessary to successfully perform the distribution upgrade.
answered Apr 19 '14 at 14:46
Ian Mackinnon
72411436
1
running this command gave me a message to run 'sudo dpkg --configure -a' and this got me back on track thanks
– Aaron Williams
Oct 8 '14 at 0:09
add a comment |Â
up vote
2
down vote
For me the answer was in my /etc/lightdm/lightdm.conf - I'd been running my 12.04 LTS in ubuntu-2d mode, had to revert back to just ubuntu and that fixed the issue
answered Apr 23 '14 at 20:52
Russ Lowenthal
386137
add a comment |Â
up vote
0
down vote
Run a
sudo dpkg-reconfigure -a
to reconfigure your packages. Hopefully it will work. (At least for me it worked with several issued)
answered Apr 19 '14 at 12:35
sboda
43028
I have just tried this but the problem persists, unfortunately.
– Ian Mackinnon
Apr 19 '14 at 14:24
1
Note,-ais no longer an option fordpkg-reconfigure, at least as of Ubuntu 16.04
– CJBrew
Dec 12 '16 at 13:32
The '-a' option was removed due to too many bugs that resulted from it: bugs.launchpad.net/ubuntu/+source/debconf/+bug/1463672
– naisanza
Mar 28 '17 at 19:10
add a comment |Â
protected by Community♦ Apr 25 '14 at 18:36
Thank you for your interest in this question.
Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Would you like to answer one of these unanswered questions instead?
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
15
down vote
accepted
After issuing the following command I was able to log in again:
sudo apt-get install ubuntu-desktop
I had previously removed update-notifier which caused some other packages to be removed, some of which it seems were necessary to successfully perform the distribution upgrade.
answered Apr 19 '14 at 14:46
Ian Mackinnon
72411436
1
running this command gave me a message to run 'sudo dpkg --configure -a' and this got me back on track thanks
– Aaron Williams
Oct 8 '14 at 0:09
add a comment |Â
up vote
15
down vote
accepted
After issuing the following command I was able to log in again:
sudo apt-get install ubuntu-desktop
I had previously removed update-notifier which caused some other packages to be removed, some of which it seems were necessary to successfully perform the distribution upgrade.
answered Apr 19 '14 at 14:46
Ian Mackinnon
72411436
1
running this command gave me a message to run 'sudo dpkg --configure -a' and this got me back on track thanks
– Aaron Williams
Oct 8 '14 at 0:09
add a comment |Â
up vote
15
down vote
accepted
up vote
15
down vote
accepted
After issuing the following command I was able to log in again:
sudo apt-get install ubuntu-desktop
I had previously removed update-notifier which caused some other packages to be removed, some of which it seems were necessary to successfully perform the distribution upgrade.
answered Apr 19 '14 at 14:46
Ian Mackinnon
72411436
After issuing the following command I was able to log in again:
sudo apt-get install ubuntu-desktop
I had previously removed update-notifier which caused some other packages to be removed, some of which it seems were necessary to successfully perform the distribution upgrade.
answered Apr 19 '14 at 14:46
Ian Mackinnon
72411436
answered Apr 19 '14 at 14:46
Ian Mackinnon
72411436
answered Apr 19 '14 at 14:46
Ian Mackinnon
72411436
answered Apr 19 '14 at 14:46
Ian Mackinnon
72411436
72411436
1
running this command gave me a message to run 'sudo dpkg --configure -a' and this got me back on track thanks
– Aaron Williams
Oct 8 '14 at 0:09
add a comment |Â
1
running this command gave me a message to run 'sudo dpkg --configure -a' and this got me back on track thanks
– Aaron Williams
Oct 8 '14 at 0:09
1
1
running this command gave me a message to run 'sudo dpkg --configure -a' and this got me back on track thanks
– Aaron Williams
Oct 8 '14 at 0:09
running this command gave me a message to run 'sudo dpkg --configure -a' and this got me back on track thanks
– Aaron Williams
Oct 8 '14 at 0:09
add a comment |Â
up vote
2
down vote
For me the answer was in my /etc/lightdm/lightdm.conf - I'd been running my 12.04 LTS in ubuntu-2d mode, had to revert back to just ubuntu and that fixed the issue
answered Apr 23 '14 at 20:52
Russ Lowenthal
386137
add a comment |Â
up vote
2
down vote
For me the answer was in my /etc/lightdm/lightdm.conf - I'd been running my 12.04 LTS in ubuntu-2d mode, had to revert back to just ubuntu and that fixed the issue
answered Apr 23 '14 at 20:52
Russ Lowenthal
386137
add a comment |Â
up vote
2
down vote
up vote
2
down vote
For me the answer was in my /etc/lightdm/lightdm.conf - I'd been running my 12.04 LTS in ubuntu-2d mode, had to revert back to just ubuntu and that fixed the issue
answered Apr 23 '14 at 20:52
Russ Lowenthal
386137
For me the answer was in my /etc/lightdm/lightdm.conf - I'd been running my 12.04 LTS in ubuntu-2d mode, had to revert back to just ubuntu and that fixed the issue
answered Apr 23 '14 at 20:52
Russ Lowenthal
386137
answered Apr 23 '14 at 20:52
Russ Lowenthal
386137
answered Apr 23 '14 at 20:52
Russ Lowenthal
386137
answered Apr 23 '14 at 20:52
Russ Lowenthal
386137
386137
add a comment |Â
add a comment |Â
up vote
0
down vote
Run a
sudo dpkg-reconfigure -a
to reconfigure your packages. Hopefully it will work. (At least for me it worked with several issued)
answered Apr 19 '14 at 12:35
sboda
43028
I have just tried this but the problem persists, unfortunately.
– Ian Mackinnon
Apr 19 '14 at 14:24
1
Note,-ais no longer an option fordpkg-reconfigure, at least as of Ubuntu 16.04
– CJBrew
Dec 12 '16 at 13:32
The '-a' option was removed due to too many bugs that resulted from it: bugs.launchpad.net/ubuntu/+source/debconf/+bug/1463672
– naisanza
Mar 28 '17 at 19:10
add a comment |Â
up vote
0
down vote
Run a
sudo dpkg-reconfigure -a
to reconfigure your packages. Hopefully it will work. (At least for me it worked with several issued)
answered Apr 19 '14 at 12:35
sboda
43028
I have just tried this but the problem persists, unfortunately.
– Ian Mackinnon
Apr 19 '14 at 14:24
1
Note,-ais no longer an option fordpkg-reconfigure, at least as of Ubuntu 16.04
– CJBrew
Dec 12 '16 at 13:32
The '-a' option was removed due to too many bugs that resulted from it: bugs.launchpad.net/ubuntu/+source/debconf/+bug/1463672
– naisanza
Mar 28 '17 at 19:10
add a comment |Â
up vote
0
down vote
up vote
0
down vote
Run a
sudo dpkg-reconfigure -a
to reconfigure your packages. Hopefully it will work. (At least for me it worked with several issued)
answered Apr 19 '14 at 12:35
sboda
43028
Run a
sudo dpkg-reconfigure -a
to reconfigure your packages. Hopefully it will work. (At least for me it worked with several issued)
answered Apr 19 '14 at 12:35
sboda
43028
answered Apr 19 '14 at 12:35
sboda
43028
answered Apr 19 '14 at 12:35
sboda
43028
answered Apr 19 '14 at 12:35
sboda
43028
43028
I have just tried this but the problem persists, unfortunately.
– Ian Mackinnon
Apr 19 '14 at 14:24
1
Note,-ais no longer an option fordpkg-reconfigure, at least as of Ubuntu 16.04
– CJBrew
Dec 12 '16 at 13:32
The '-a' option was removed due to too many bugs that resulted from it: bugs.launchpad.net/ubuntu/+source/debconf/+bug/1463672
– naisanza
Mar 28 '17 at 19:10
add a comment |Â
I have just tried this but the problem persists, unfortunately.
– Ian Mackinnon
Apr 19 '14 at 14:24
1
Note,-ais no longer an option fordpkg-reconfigure, at least as of Ubuntu 16.04
– CJBrew
Dec 12 '16 at 13:32
The '-a' option was removed due to too many bugs that resulted from it: bugs.launchpad.net/ubuntu/+source/debconf/+bug/1463672
– naisanza
Mar 28 '17 at 19:10
I have just tried this but the problem persists, unfortunately.
– Ian Mackinnon
Apr 19 '14 at 14:24
I have just tried this but the problem persists, unfortunately.
– Ian Mackinnon
Apr 19 '14 at 14:24
1
1
Note,
-a is no longer an option for dpkg-reconfigure, at least as of Ubuntu 16.04– CJBrew
Dec 12 '16 at 13:32
Note,
-a is no longer an option for dpkg-reconfigure, at least as of Ubuntu 16.04– CJBrew
Dec 12 '16 at 13:32
The '-a' option was removed due to too many bugs that resulted from it: bugs.launchpad.net/ubuntu/+source/debconf/+bug/1463672
– naisanza
Mar 28 '17 at 19:10
The '-a' option was removed due to too many bugs that resulted from it: bugs.launchpad.net/ubuntu/+source/debconf/+bug/1463672
– naisanza
Mar 28 '17 at 19:10
add a comment |Â
protected by Community♦ Apr 25 '14 at 18:36
Thank you for your interest in this question.
Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Would you like to answer one of these unanswered questions instead?
3
@Elliott, try
Ctrl-Alt-F1to get a shell login prompt. Then you useCtrl-Alt-F7to get back to the GUI.– Ian Mackinnon
Apr 21 '14 at 11:01
1
This worked for me sudo apt-get install --reinstall ubuntu-session
– Aravinda
May 2 '15 at 3:14