“Failed to start session” after upgrade to 18.04
After upgrading to 18.04 from 16.04 I get a login screen which looks complete but typing in my password gives the error failed to start session.
I can use Ctrl+Alt+F1 to access tty where logging in is successful but starting almost immediately terminates.
I have read similar solutions about installing ubuntu-session but attempting these gives unable to correct problems, you have held broken packages with the dependencies on gnome-shell and gnome-session-bin listed as unmet dependencies.
boot 18.04 desktop-environments
asked Sep 28 '18 at 7:52
k.child90k.child90
12
add a comment |
After upgrading to 18.04 from 16.04 I get a login screen which looks complete but typing in my password gives the error failed to start session.
I can use Ctrl+Alt+F1 to access tty where logging in is successful but starting almost immediately terminates.
I have read similar solutions about installing ubuntu-session but attempting these gives unable to correct problems, you have held broken packages with the dependencies on gnome-shell and gnome-session-bin listed as unmet dependencies.
boot 18.04 desktop-environments
asked Sep 28 '18 at 7:52
k.child90k.child90
12
What happens if you try to runsudo apt-get install -fin tty?
– m_krsic
Oct 1 '18 at 15:02
add a comment |
After upgrading to 18.04 from 16.04 I get a login screen which looks complete but typing in my password gives the error failed to start session.
I can use Ctrl+Alt+F1 to access tty where logging in is successful but starting almost immediately terminates.
I have read similar solutions about installing ubuntu-session but attempting these gives unable to correct problems, you have held broken packages with the dependencies on gnome-shell and gnome-session-bin listed as unmet dependencies.
boot 18.04 desktop-environments
asked Sep 28 '18 at 7:52
k.child90k.child90
12
After upgrading to 18.04 from 16.04 I get a login screen which looks complete but typing in my password gives the error failed to start session.
I can use Ctrl+Alt+F1 to access tty where logging in is successful but starting almost immediately terminates.
I have read similar solutions about installing ubuntu-session but attempting these gives unable to correct problems, you have held broken packages with the dependencies on gnome-shell and gnome-session-bin listed as unmet dependencies.
boot 18.04 desktop-environments
boot 18.04 desktop-environments
asked Sep 28 '18 at 7:52
k.child90k.child90
12
asked Sep 28 '18 at 7:52
k.child90k.child90
12
edited Oct 2 '18 at 9:00
k.child90
asked Sep 28 '18 at 7:52
k.child90k.child90
12
asked Sep 28 '18 at 7:52
k.child90k.child90
12
asked Sep 28 '18 at 7:52
k.child90k.child90
12
12
What happens if you try to runsudo apt-get install -fin tty?
– m_krsic
Oct 1 '18 at 15:02
add a comment |
What happens if you try to runsudo apt-get install -fin tty?
– m_krsic
Oct 1 '18 at 15:02
What happens if you try to run
sudo apt-get install -f in tty?– m_krsic
Oct 1 '18 at 15:02
What happens if you try to run
sudo apt-get install -f in tty?– m_krsic
Oct 1 '18 at 15:02
add a comment |
2 Answers
2
active
oldest
votes
I took this along to a laptop clinic who solved the issue. The login screen, importantly, looked identical to the 16.04 Unity login screen which betrayed the problem in transferring to 18.04 (which has a very different looking login screen).
In TTY attempting to install certain packages gave unmet dependencies, and following the chain down gave the ligbm1 package at the base. This is the dependency for a lot of unity and xserver packages (attempting startx also failed). Uninstalling ligbm1 and then installing it again allowed installing ubuntu-desktop without error.
answered Oct 2 '18 at 9:00
k.child90k.child90
12
add a comment |
What helped me:
- to use sudo dpkg --remove [package-name] to remove problematic packages found via sudo dpkg --configure -a (source: https://stackoverflow.com/a/35969176/557223). Some packages couldn't be removed as they were dependencies of another packages.
- to run sudo apt-get install -f (it started to working again, yay)
- to rename org.freedesktop.systemd1.service file as mentioned in https://askubuntu.com/a/838673
- To run sudo apt-get update and dist-upgrade and autoremove, and do-release-upgrade
Kudos to https://ubuntuforums.org/showthread.php?t=2398895&page=2 dragans2's post!
answered Jan 4 at 11:08
mmalmeidammalmeida
3302314
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1079141%2ffailed-to-start-session-after-upgrade-to-18-04%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
I took this along to a laptop clinic who solved the issue. The login screen, importantly, looked identical to the 16.04 Unity login screen which betrayed the problem in transferring to 18.04 (which has a very different looking login screen).
In TTY attempting to install certain packages gave unmet dependencies, and following the chain down gave the ligbm1 package at the base. This is the dependency for a lot of unity and xserver packages (attempting startx also failed). Uninstalling ligbm1 and then installing it again allowed installing ubuntu-desktop without error.
answered Oct 2 '18 at 9:00
k.child90k.child90
12
add a comment |
I took this along to a laptop clinic who solved the issue. The login screen, importantly, looked identical to the 16.04 Unity login screen which betrayed the problem in transferring to 18.04 (which has a very different looking login screen).
In TTY attempting to install certain packages gave unmet dependencies, and following the chain down gave the ligbm1 package at the base. This is the dependency for a lot of unity and xserver packages (attempting startx also failed). Uninstalling ligbm1 and then installing it again allowed installing ubuntu-desktop without error.
answered Oct 2 '18 at 9:00
k.child90k.child90
12
add a comment |
I took this along to a laptop clinic who solved the issue. The login screen, importantly, looked identical to the 16.04 Unity login screen which betrayed the problem in transferring to 18.04 (which has a very different looking login screen).
In TTY attempting to install certain packages gave unmet dependencies, and following the chain down gave the ligbm1 package at the base. This is the dependency for a lot of unity and xserver packages (attempting startx also failed). Uninstalling ligbm1 and then installing it again allowed installing ubuntu-desktop without error.
answered Oct 2 '18 at 9:00
k.child90k.child90
12
I took this along to a laptop clinic who solved the issue. The login screen, importantly, looked identical to the 16.04 Unity login screen which betrayed the problem in transferring to 18.04 (which has a very different looking login screen).
In TTY attempting to install certain packages gave unmet dependencies, and following the chain down gave the ligbm1 package at the base. This is the dependency for a lot of unity and xserver packages (attempting startx also failed). Uninstalling ligbm1 and then installing it again allowed installing ubuntu-desktop without error.
answered Oct 2 '18 at 9:00
k.child90k.child90
12
answered Oct 2 '18 at 9:00
k.child90k.child90
12
answered Oct 2 '18 at 9:00
k.child90k.child90
12
answered Oct 2 '18 at 9:00
k.child90k.child90
12
12
add a comment |
add a comment |
What helped me:
- to use sudo dpkg --remove [package-name] to remove problematic packages found via sudo dpkg --configure -a (source: https://stackoverflow.com/a/35969176/557223). Some packages couldn't be removed as they were dependencies of another packages.
- to run sudo apt-get install -f (it started to working again, yay)
- to rename org.freedesktop.systemd1.service file as mentioned in https://askubuntu.com/a/838673
- To run sudo apt-get update and dist-upgrade and autoremove, and do-release-upgrade
Kudos to https://ubuntuforums.org/showthread.php?t=2398895&page=2 dragans2's post!
answered Jan 4 at 11:08
mmalmeidammalmeida
3302314
add a comment |
What helped me:
- to use sudo dpkg --remove [package-name] to remove problematic packages found via sudo dpkg --configure -a (source: https://stackoverflow.com/a/35969176/557223). Some packages couldn't be removed as they were dependencies of another packages.
- to run sudo apt-get install -f (it started to working again, yay)
- to rename org.freedesktop.systemd1.service file as mentioned in https://askubuntu.com/a/838673
- To run sudo apt-get update and dist-upgrade and autoremove, and do-release-upgrade
Kudos to https://ubuntuforums.org/showthread.php?t=2398895&page=2 dragans2's post!
answered Jan 4 at 11:08
mmalmeidammalmeida
3302314
add a comment |
What helped me:
- to use sudo dpkg --remove [package-name] to remove problematic packages found via sudo dpkg --configure -a (source: https://stackoverflow.com/a/35969176/557223). Some packages couldn't be removed as they were dependencies of another packages.
- to run sudo apt-get install -f (it started to working again, yay)
- to rename org.freedesktop.systemd1.service file as mentioned in https://askubuntu.com/a/838673
- To run sudo apt-get update and dist-upgrade and autoremove, and do-release-upgrade
Kudos to https://ubuntuforums.org/showthread.php?t=2398895&page=2 dragans2's post!
answered Jan 4 at 11:08
mmalmeidammalmeida
3302314
What helped me:
- to use sudo dpkg --remove [package-name] to remove problematic packages found via sudo dpkg --configure -a (source: https://stackoverflow.com/a/35969176/557223). Some packages couldn't be removed as they were dependencies of another packages.
- to run sudo apt-get install -f (it started to working again, yay)
- to rename org.freedesktop.systemd1.service file as mentioned in https://askubuntu.com/a/838673
- To run sudo apt-get update and dist-upgrade and autoremove, and do-release-upgrade
Kudos to https://ubuntuforums.org/showthread.php?t=2398895&page=2 dragans2's post!
answered Jan 4 at 11:08
mmalmeidammalmeida
3302314
answered Jan 4 at 11:08
mmalmeidammalmeida
3302314
answered Jan 4 at 11:08
mmalmeidammalmeida
3302314
answered Jan 4 at 11:08
mmalmeidammalmeida
3302314
3302314
add a comment |
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1079141%2ffailed-to-start-session-after-upgrade-to-18-04%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
What happens if you try to run
sudo apt-get install -fin tty?– m_krsic
Oct 1 '18 at 15:02