Stuck at Started Gnome Display Manager 18.10
I just recently installed ubuntu 18.10. After successful installation when I reboot my system then Ubuntu didn't boot, its stuck by showing started gnome display manager. In this condition what should I do? my keyboard is also not working. what is the problem? how can I get a complete Ubuntu desktop ready without any errors? or any other installation process please help me out.
boot
asked Dec 16 '18 at 8:07
Shyam Mahanta
6
add a comment |
I just recently installed ubuntu 18.10. After successful installation when I reboot my system then Ubuntu didn't boot, its stuck by showing started gnome display manager. In this condition what should I do? my keyboard is also not working. what is the problem? how can I get a complete Ubuntu desktop ready without any errors? or any other installation process please help me out.
boot
asked Dec 16 '18 at 8:07
Shyam Mahanta
6
1
Possible duplicate of Ubuntu 18.10 Cosmic not starting GNOME session on bootup
– karel
Dec 16 '18 at 9:01
@karel switching DM's may not be the best solution. Please see my answer.
– heynnema
Dec 16 '18 at 17:02
In Ubuntu 18.10 the wayland session is installed, but it is not used by default.
– karel
Dec 16 '18 at 17:43
@karel actually it is used, and many users with older GPU's can't get past the Ubuntu boot logo with the 5 rotating dots (or gdm3 not starting). Disabling wayland in this way solves that problem and allows the machine to fully boot properly.
– heynnema
Dec 16 '18 at 17:53
add a comment |
I just recently installed ubuntu 18.10. After successful installation when I reboot my system then Ubuntu didn't boot, its stuck by showing started gnome display manager. In this condition what should I do? my keyboard is also not working. what is the problem? how can I get a complete Ubuntu desktop ready without any errors? or any other installation process please help me out.
boot
asked Dec 16 '18 at 8:07
Shyam Mahanta
6
I just recently installed ubuntu 18.10. After successful installation when I reboot my system then Ubuntu didn't boot, its stuck by showing started gnome display manager. In this condition what should I do? my keyboard is also not working. what is the problem? how can I get a complete Ubuntu desktop ready without any errors? or any other installation process please help me out.
boot
boot
asked Dec 16 '18 at 8:07
Shyam Mahanta
6
asked Dec 16 '18 at 8:07
Shyam Mahanta
6
asked Dec 16 '18 at 8:07
Shyam Mahanta
6
asked Dec 16 '18 at 8:07
Shyam Mahanta
6
asked Dec 16 '18 at 8:07
Shyam Mahanta
6
6
1
Possible duplicate of Ubuntu 18.10 Cosmic not starting GNOME session on bootup
– karel
Dec 16 '18 at 9:01
@karel switching DM's may not be the best solution. Please see my answer.
– heynnema
Dec 16 '18 at 17:02
In Ubuntu 18.10 the wayland session is installed, but it is not used by default.
– karel
Dec 16 '18 at 17:43
@karel actually it is used, and many users with older GPU's can't get past the Ubuntu boot logo with the 5 rotating dots (or gdm3 not starting). Disabling wayland in this way solves that problem and allows the machine to fully boot properly.
– heynnema
Dec 16 '18 at 17:53
add a comment |
1
Possible duplicate of Ubuntu 18.10 Cosmic not starting GNOME session on bootup
– karel
Dec 16 '18 at 9:01
@karel switching DM's may not be the best solution. Please see my answer.
– heynnema
Dec 16 '18 at 17:02
In Ubuntu 18.10 the wayland session is installed, but it is not used by default.
– karel
Dec 16 '18 at 17:43
@karel actually it is used, and many users with older GPU's can't get past the Ubuntu boot logo with the 5 rotating dots (or gdm3 not starting). Disabling wayland in this way solves that problem and allows the machine to fully boot properly.
– heynnema
Dec 16 '18 at 17:53
1
1
Possible duplicate of Ubuntu 18.10 Cosmic not starting GNOME session on bootup
– karel
Dec 16 '18 at 9:01
Possible duplicate of Ubuntu 18.10 Cosmic not starting GNOME session on bootup
– karel
Dec 16 '18 at 9:01
@karel switching DM's may not be the best solution. Please see my answer.
– heynnema
Dec 16 '18 at 17:02
@karel switching DM's may not be the best solution. Please see my answer.
– heynnema
Dec 16 '18 at 17:02
In Ubuntu 18.10 the wayland session is installed, but it is not used by default.
– karel
Dec 16 '18 at 17:43
In Ubuntu 18.10 the wayland session is installed, but it is not used by default.
– karel
Dec 16 '18 at 17:43
@karel actually it is used, and many users with older GPU's can't get past the Ubuntu boot logo with the 5 rotating dots (or gdm3 not starting). Disabling wayland in this way solves that problem and allows the machine to fully boot properly.
– heynnema
Dec 16 '18 at 17:53
@karel actually it is used, and many users with older GPU's can't get past the Ubuntu boot logo with the 5 rotating dots (or gdm3 not starting). Disabling wayland in this way solves that problem and allows the machine to fully boot properly.
– heynnema
Dec 16 '18 at 17:53
add a comment |
1 Answer
1
active
oldest
votes
You may have a problem with an older computer, with an older GPU. Try this...
- boot to recovery mode
- choose root access
type:
sudo mount -o remount,rw / # to remount the disk r/w
sudo pico /etc/gdm3/custom.conf # edit this file
change:
#WaylandEnable=false
to:
WaylandEnable=false
Then reboot.
answered Dec 16 '18 at 17:01
heynnema
18.1k22054
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%2f1102256%2fstuck-at-started-gnome-display-manager-18-10%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
You may have a problem with an older computer, with an older GPU. Try this...
- boot to recovery mode
- choose root access
type:
sudo mount -o remount,rw / # to remount the disk r/w
sudo pico /etc/gdm3/custom.conf # edit this file
change:
#WaylandEnable=false
to:
WaylandEnable=false
Then reboot.
answered Dec 16 '18 at 17:01
heynnema
18.1k22054
add a comment |
You may have a problem with an older computer, with an older GPU. Try this...
- boot to recovery mode
- choose root access
type:
sudo mount -o remount,rw / # to remount the disk r/w
sudo pico /etc/gdm3/custom.conf # edit this file
change:
#WaylandEnable=false
to:
WaylandEnable=false
Then reboot.
answered Dec 16 '18 at 17:01
heynnema
18.1k22054
add a comment |
You may have a problem with an older computer, with an older GPU. Try this...
- boot to recovery mode
- choose root access
type:
sudo mount -o remount,rw / # to remount the disk r/w
sudo pico /etc/gdm3/custom.conf # edit this file
change:
#WaylandEnable=false
to:
WaylandEnable=false
Then reboot.
answered Dec 16 '18 at 17:01
heynnema
18.1k22054
You may have a problem with an older computer, with an older GPU. Try this...
- boot to recovery mode
- choose root access
type:
sudo mount -o remount,rw / # to remount the disk r/w
sudo pico /etc/gdm3/custom.conf # edit this file
change:
#WaylandEnable=false
to:
WaylandEnable=false
Then reboot.
answered Dec 16 '18 at 17:01
heynnema
18.1k22054
answered Dec 16 '18 at 17:01
heynnema
18.1k22054
answered Dec 16 '18 at 17:01
heynnema
18.1k22054
answered Dec 16 '18 at 17:01
heynnema
18.1k22054
18.1k22054
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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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%2f1102256%2fstuck-at-started-gnome-display-manager-18-10%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
1
Possible duplicate of Ubuntu 18.10 Cosmic not starting GNOME session on bootup
– karel
Dec 16 '18 at 9:01
@karel switching DM's may not be the best solution. Please see my answer.
– heynnema
Dec 16 '18 at 17:02
In Ubuntu 18.10 the wayland session is installed, but it is not used by default.
– karel
Dec 16 '18 at 17:43
@karel actually it is used, and many users with older GPU's can't get past the Ubuntu boot logo with the 5 rotating dots (or gdm3 not starting). Disabling wayland in this way solves that problem and allows the machine to fully boot properly.
– heynnema
Dec 16 '18 at 17:53