gdm3 display manager hangs after booting with Ubuntu 18.10
2
I want to use gdm3 but unfortunately, it does not work. After booting it just completely hangs.
boot process stopped after Started GNOME Display Manager
It just does not do anything. Installing lightdm and activating it via sudo dpkg-reconfigure lightdm does work but then again that's not what I want.
I tried several things already:
- Reinstalling NVIDIA drivers
- Changing my run level to
multi-user.target
- Using
update-rc.d -f gdm3 remove && update-rc.d gdm3 defaultsto reconfigure gdm3 - Installing the packages that I need
sudo apt-get install ubuntu-gnome-desktop gnome-shell gnome - Reinstalling gdm3
Does anyone know how I can get gdm3 to work?
nvidia gnome 18.10 gdm timeout
asked Jan 4 at 22:33
NiklasNiklas
2121516
add a comment |
2
I want to use gdm3 but unfortunately, it does not work. After booting it just completely hangs.
boot process stopped after Started GNOME Display Manager
It just does not do anything. Installing lightdm and activating it via sudo dpkg-reconfigure lightdm does work but then again that's not what I want.
I tried several things already:
- Reinstalling NVIDIA drivers
- Changing my run level to
multi-user.target
- Using
update-rc.d -f gdm3 remove && update-rc.d gdm3 defaultsto reconfigure gdm3 - Installing the packages that I need
sudo apt-get install ubuntu-gnome-desktop gnome-shell gnome - Reinstalling gdm3
Does anyone know how I can get gdm3 to work?
nvidia gnome 18.10 gdm timeout
asked Jan 4 at 22:33
NiklasNiklas
2121516
2
How old is this computer? Exactly WHERE does it hang? Do you see the splash screen? At the GRUB menu, edit the kernel line that says "quiet splash" and add "nomodeset" and see if that allows it to boot. If it does, I'll give you a permanent fix. Report back to @heynnema
– heynnema
Jan 5 at 2:49
@heynnema When I'm booting I'm seeing the GNU GRUB version 2.02 screen. I went to advanced options -> Ubuntu with Linux 4.18.0-10-generic and addednomodesetso it's nowlinux /boot/vmlinuz-4.18.0-10-generic root=UUID=62de2584-320c-49c3-85f4-057c6c967281 ro quiet splash nomodeset $vt_handoff. I pressedF10. Got to the Splash Screen showing Ubuntu 18.10 and from the same log messages appeared as above and this is the point where it hangs. This computer is quite old. ~2012 NVIDIA 660TI with Intel i7 3770k
– Niklas
Jan 5 at 12:33
Please see my answer for something quick to try. If it doesn't work, we may try to uninstall the Nvidia drivers, and see what happens. Report back to @heynnema
– heynnema
Jan 5 at 23:16
How did you "Changing my run level to multi-user.target"?
– heynnema
Jan 7 at 22:58
sudo systemctl isolate multi-user.target && sudo systemctl enable multi-user.target && sudo systemctl set-default multi-user.target
– Niklas
Jan 9 at 18:27
add a comment |
2
2
2
I want to use gdm3 but unfortunately, it does not work. After booting it just completely hangs.
boot process stopped after Started GNOME Display Manager
It just does not do anything. Installing lightdm and activating it via sudo dpkg-reconfigure lightdm does work but then again that's not what I want.
I tried several things already:
- Reinstalling NVIDIA drivers
- Changing my run level to
multi-user.target
- Using
update-rc.d -f gdm3 remove && update-rc.d gdm3 defaultsto reconfigure gdm3 - Installing the packages that I need
sudo apt-get install ubuntu-gnome-desktop gnome-shell gnome - Reinstalling gdm3
Does anyone know how I can get gdm3 to work?
nvidia gnome 18.10 gdm timeout
asked Jan 4 at 22:33
NiklasNiklas
2121516
I want to use gdm3 but unfortunately, it does not work. After booting it just completely hangs.
boot process stopped after Started GNOME Display Manager
It just does not do anything. Installing lightdm and activating it via sudo dpkg-reconfigure lightdm does work but then again that's not what I want.
I tried several things already:
- Reinstalling NVIDIA drivers
- Changing my run level to
multi-user.target
- Using
update-rc.d -f gdm3 remove && update-rc.d gdm3 defaultsto reconfigure gdm3 - Installing the packages that I need
sudo apt-get install ubuntu-gnome-desktop gnome-shell gnome - Reinstalling gdm3
Does anyone know how I can get gdm3 to work?
nvidia gnome 18.10 gdm timeout
nvidia gnome 18.10 gdm timeout
asked Jan 4 at 22:33
NiklasNiklas
2121516
asked Jan 4 at 22:33
NiklasNiklas
2121516
edited Jan 5 at 12:23
Niklas
asked Jan 4 at 22:33
NiklasNiklas
2121516
asked Jan 4 at 22:33
NiklasNiklas
2121516
asked Jan 4 at 22:33
NiklasNiklas
2121516
2121516
2
How old is this computer? Exactly WHERE does it hang? Do you see the splash screen? At the GRUB menu, edit the kernel line that says "quiet splash" and add "nomodeset" and see if that allows it to boot. If it does, I'll give you a permanent fix. Report back to @heynnema
– heynnema
Jan 5 at 2:49
@heynnema When I'm booting I'm seeing the GNU GRUB version 2.02 screen. I went to advanced options -> Ubuntu with Linux 4.18.0-10-generic and addednomodesetso it's nowlinux /boot/vmlinuz-4.18.0-10-generic root=UUID=62de2584-320c-49c3-85f4-057c6c967281 ro quiet splash nomodeset $vt_handoff. I pressedF10. Got to the Splash Screen showing Ubuntu 18.10 and from the same log messages appeared as above and this is the point where it hangs. This computer is quite old. ~2012 NVIDIA 660TI with Intel i7 3770k
– Niklas
Jan 5 at 12:33
Please see my answer for something quick to try. If it doesn't work, we may try to uninstall the Nvidia drivers, and see what happens. Report back to @heynnema
– heynnema
Jan 5 at 23:16
How did you "Changing my run level to multi-user.target"?
– heynnema
Jan 7 at 22:58
sudo systemctl isolate multi-user.target && sudo systemctl enable multi-user.target && sudo systemctl set-default multi-user.target
– Niklas
Jan 9 at 18:27
add a comment |
2
How old is this computer? Exactly WHERE does it hang? Do you see the splash screen? At the GRUB menu, edit the kernel line that says "quiet splash" and add "nomodeset" and see if that allows it to boot. If it does, I'll give you a permanent fix. Report back to @heynnema
– heynnema
Jan 5 at 2:49
@heynnema When I'm booting I'm seeing the GNU GRUB version 2.02 screen. I went to advanced options -> Ubuntu with Linux 4.18.0-10-generic and addednomodesetso it's nowlinux /boot/vmlinuz-4.18.0-10-generic root=UUID=62de2584-320c-49c3-85f4-057c6c967281 ro quiet splash nomodeset $vt_handoff. I pressedF10. Got to the Splash Screen showing Ubuntu 18.10 and from the same log messages appeared as above and this is the point where it hangs. This computer is quite old. ~2012 NVIDIA 660TI with Intel i7 3770k
– Niklas
Jan 5 at 12:33
Please see my answer for something quick to try. If it doesn't work, we may try to uninstall the Nvidia drivers, and see what happens. Report back to @heynnema
– heynnema
Jan 5 at 23:16
How did you "Changing my run level to multi-user.target"?
– heynnema
Jan 7 at 22:58
sudo systemctl isolate multi-user.target && sudo systemctl enable multi-user.target && sudo systemctl set-default multi-user.target
– Niklas
Jan 9 at 18:27
2
2
How old is this computer? Exactly WHERE does it hang? Do you see the splash screen? At the GRUB menu, edit the kernel line that says "quiet splash" and add "nomodeset" and see if that allows it to boot. If it does, I'll give you a permanent fix. Report back to @heynnema
– heynnema
Jan 5 at 2:49
How old is this computer? Exactly WHERE does it hang? Do you see the splash screen? At the GRUB menu, edit the kernel line that says "quiet splash" and add "nomodeset" and see if that allows it to boot. If it does, I'll give you a permanent fix. Report back to @heynnema
– heynnema
Jan 5 at 2:49
@heynnema When I'm booting I'm seeing the GNU GRUB version 2.02 screen. I went to advanced options -> Ubuntu with Linux 4.18.0-10-generic and added
nomodeset so it's now linux /boot/vmlinuz-4.18.0-10-generic root=UUID=62de2584-320c-49c3-85f4-057c6c967281 ro quiet splash nomodeset $vt_handoff. I pressed F10. Got to the Splash Screen showing Ubuntu 18.10 and from the same log messages appeared as above and this is the point where it hangs. This computer is quite old. ~2012 NVIDIA 660TI with Intel i7 3770k– Niklas
Jan 5 at 12:33
@heynnema When I'm booting I'm seeing the GNU GRUB version 2.02 screen. I went to advanced options -> Ubuntu with Linux 4.18.0-10-generic and added
nomodeset so it's now linux /boot/vmlinuz-4.18.0-10-generic root=UUID=62de2584-320c-49c3-85f4-057c6c967281 ro quiet splash nomodeset $vt_handoff. I pressed F10. Got to the Splash Screen showing Ubuntu 18.10 and from the same log messages appeared as above and this is the point where it hangs. This computer is quite old. ~2012 NVIDIA 660TI with Intel i7 3770k– Niklas
Jan 5 at 12:33
Please see my answer for something quick to try. If it doesn't work, we may try to uninstall the Nvidia drivers, and see what happens. Report back to @heynnema
– heynnema
Jan 5 at 23:16
Please see my answer for something quick to try. If it doesn't work, we may try to uninstall the Nvidia drivers, and see what happens. Report back to @heynnema
– heynnema
Jan 5 at 23:16
How did you "Changing my run level to multi-user.target"?
– heynnema
Jan 7 at 22:58
How did you "Changing my run level to multi-user.target"?
– heynnema
Jan 7 at 22:58
sudo systemctl isolate multi-user.target && sudo systemctl enable multi-user.target && sudo systemctl set-default multi-user.target– Niklas
Jan 9 at 18:27
sudo systemctl isolate multi-user.target && sudo systemctl enable multi-user.target && sudo systemctl set-default multi-user.target– Niklas
Jan 9 at 18:27
add a comment |
1 Answer
1
active
oldest
votes
0
Not sure if this is going to fix your problem, but it's quick, so it's worth a try...
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 Jan 5 at 23:15
heynnemaheynnema
18.2k22054
Went into Grub. Selected Ubuntu with Linux 4.18.0-10-generic (recovery mode). From there I got to the point where I'm seeingStarted Update UTMP about System Runlevel Changesand from there I'm stuck again. It does not go further.
– Niklas
Jan 7 at 22:40
@Niklas Is this what's happening AFTER the mod in my answer? Do you have both Intel and Nvidia GPU's on your system? If so, go to the BIOS and temporarily select the Intel GPU and see if you get farther. If you do, the Nvidia driver is suspect. What version is it?
– heynnema
Jan 7 at 22:57
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
});
}
});
draft saved
draft discarded
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%2f1107042%2fgdm3-display-manager-hangs-after-booting-with-ubuntu-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
0
Not sure if this is going to fix your problem, but it's quick, so it's worth a try...
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 Jan 5 at 23:15
heynnemaheynnema
18.2k22054
Went into Grub. Selected Ubuntu with Linux 4.18.0-10-generic (recovery mode). From there I got to the point where I'm seeingStarted Update UTMP about System Runlevel Changesand from there I'm stuck again. It does not go further.
– Niklas
Jan 7 at 22:40
@Niklas Is this what's happening AFTER the mod in my answer? Do you have both Intel and Nvidia GPU's on your system? If so, go to the BIOS and temporarily select the Intel GPU and see if you get farther. If you do, the Nvidia driver is suspect. What version is it?
– heynnema
Jan 7 at 22:57
add a comment |
0
Not sure if this is going to fix your problem, but it's quick, so it's worth a try...
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 Jan 5 at 23:15
heynnemaheynnema
18.2k22054
Went into Grub. Selected Ubuntu with Linux 4.18.0-10-generic (recovery mode). From there I got to the point where I'm seeingStarted Update UTMP about System Runlevel Changesand from there I'm stuck again. It does not go further.
– Niklas
Jan 7 at 22:40
@Niklas Is this what's happening AFTER the mod in my answer? Do you have both Intel and Nvidia GPU's on your system? If so, go to the BIOS and temporarily select the Intel GPU and see if you get farther. If you do, the Nvidia driver is suspect. What version is it?
– heynnema
Jan 7 at 22:57
add a comment |
0
0
0
Not sure if this is going to fix your problem, but it's quick, so it's worth a try...
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 Jan 5 at 23:15
heynnemaheynnema
18.2k22054
Not sure if this is going to fix your problem, but it's quick, so it's worth a try...
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 Jan 5 at 23:15
heynnemaheynnema
18.2k22054
answered Jan 5 at 23:15
heynnemaheynnema
18.2k22054
answered Jan 5 at 23:15
heynnemaheynnema
18.2k22054
answered Jan 5 at 23:15
heynnemaheynnema
18.2k22054
18.2k22054
Went into Grub. Selected Ubuntu with Linux 4.18.0-10-generic (recovery mode). From there I got to the point where I'm seeingStarted Update UTMP about System Runlevel Changesand from there I'm stuck again. It does not go further.
– Niklas
Jan 7 at 22:40
@Niklas Is this what's happening AFTER the mod in my answer? Do you have both Intel and Nvidia GPU's on your system? If so, go to the BIOS and temporarily select the Intel GPU and see if you get farther. If you do, the Nvidia driver is suspect. What version is it?
– heynnema
Jan 7 at 22:57
add a comment |
Went into Grub. Selected Ubuntu with Linux 4.18.0-10-generic (recovery mode). From there I got to the point where I'm seeingStarted Update UTMP about System Runlevel Changesand from there I'm stuck again. It does not go further.
– Niklas
Jan 7 at 22:40
@Niklas Is this what's happening AFTER the mod in my answer? Do you have both Intel and Nvidia GPU's on your system? If so, go to the BIOS and temporarily select the Intel GPU and see if you get farther. If you do, the Nvidia driver is suspect. What version is it?
– heynnema
Jan 7 at 22:57
Went into Grub. Selected Ubuntu with Linux 4.18.0-10-generic (recovery mode). From there I got to the point where I'm seeing
Started Update UTMP about System Runlevel Changes and from there I'm stuck again. It does not go further.– Niklas
Jan 7 at 22:40
Went into Grub. Selected Ubuntu with Linux 4.18.0-10-generic (recovery mode). From there I got to the point where I'm seeing
Started Update UTMP about System Runlevel Changes and from there I'm stuck again. It does not go further.– Niklas
Jan 7 at 22:40
@Niklas Is this what's happening AFTER the mod in my answer? Do you have both Intel and Nvidia GPU's on your system? If so, go to the BIOS and temporarily select the Intel GPU and see if you get farther. If you do, the Nvidia driver is suspect. What version is it?
– heynnema
Jan 7 at 22:57
@Niklas Is this what's happening AFTER the mod in my answer? Do you have both Intel and Nvidia GPU's on your system? If so, go to the BIOS and temporarily select the Intel GPU and see if you get farther. If you do, the Nvidia driver is suspect. What version is it?
– heynnema
Jan 7 at 22:57
add a comment |
draft saved
draft discarded
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.
draft saved
draft discarded
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%2f1107042%2fgdm3-display-manager-hangs-after-booting-with-ubuntu-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
2
How old is this computer? Exactly WHERE does it hang? Do you see the splash screen? At the GRUB menu, edit the kernel line that says "quiet splash" and add "nomodeset" and see if that allows it to boot. If it does, I'll give you a permanent fix. Report back to @heynnema
– heynnema
Jan 5 at 2:49
@heynnema When I'm booting I'm seeing the GNU GRUB version 2.02 screen. I went to advanced options -> Ubuntu with Linux 4.18.0-10-generic and added
nomodesetso it's nowlinux /boot/vmlinuz-4.18.0-10-generic root=UUID=62de2584-320c-49c3-85f4-057c6c967281 ro quiet splash nomodeset $vt_handoff. I pressedF10. Got to the Splash Screen showing Ubuntu 18.10 and from the same log messages appeared as above and this is the point where it hangs. This computer is quite old. ~2012 NVIDIA 660TI with Intel i7 3770k– Niklas
Jan 5 at 12:33
Please see my answer for something quick to try. If it doesn't work, we may try to uninstall the Nvidia drivers, and see what happens. Report back to @heynnema
– heynnema
Jan 5 at 23:16
How did you "Changing my run level to multi-user.target"?
– heynnema
Jan 7 at 22:58
sudo systemctl isolate multi-user.target && sudo systemctl enable multi-user.target && sudo systemctl set-default multi-user.target– Niklas
Jan 9 at 18:27