gdm3 won't start by default after upgrade to 18.10 from 18.04

up vote
1
down vote

favorite

When I configure gdm as my default display manager (dpkg-reconfigure gdm3) and then reboot, I get a black screen with a blinking cursor. From there, I cannot do anything since the ttys does not work (ctrl+alt+F1 to F7). I could not figure out why.

In order to resolve this issue, I boot into safe mode, reconfigure lightdm and then reboot.

I observed that gdm could not start for some reason (hence the black screen).

$ systemctl status gdm.service 

● gdm.service - GNOME Display Manager

   Loaded: loaded (/lib/systemd/system/gdm.service; static; vendor preset: enabled)

   Active: inactive (dead)



Nov 04 16:46:05 rigel systemd[1]: gdm.service: Unit cannot be reloaded because it is inactive.

When I manually start gdm systemctl status gdm.service I am able to logout and log back in using gdm. After reboot, the black screen occurs again with the blinking cursor.

Any ideas? Thanks.

GNOME Shell 3.30.1

Ubuntu 18.10 cosmic

Kernel: x86_64 Linux 4.18.0-10-generic

NVIDIA driver 410.73 (GeForce GTX 970)

edited Nov 5 at 8:35

asked Nov 4 at 15:18

jimouris

145

How old is this computer? Laptop or desktop? Video card? Does it boot if you set nomodeset in the kernel boot line in GRUB?
– heynnema
Nov 4 at 23:45

@heynnema Thanks for the suggestion. The computer is a desktop (not old, about 3 years). My video card is Nvidia GeForce GTX 970. I tried the nomodeset flag in GRUB but I got the same error.
– jimouris
Nov 5 at 12:29

You could try reinstalling gdm3. Maybe the update didn't complete. sudo apt-get update and sudo apt-get install --reinstall gdm3. Then sudo dpkg-reconfigure gdm3 and reboot.
– heynnema
Nov 5 at 13:05

I have also tried that, did not work.
– jimouris
Nov 5 at 14:12

Update: Disabling Wayland and reinstalling ubuntu-session fixed the issue, as @adrinux suggested.
– jimouris
Nov 28 at 11:31

add a comment |

up vote
1
down vote

favorite

In order to resolve this issue, I boot into safe mode, reconfigure lightdm and then reboot.

I observed that gdm could not start for some reason (hence the black screen).

$ systemctl status gdm.service 

● gdm.service - GNOME Display Manager

   Loaded: loaded (/lib/systemd/system/gdm.service; static; vendor preset: enabled)

   Active: inactive (dead)



Nov 04 16:46:05 rigel systemd[1]: gdm.service: Unit cannot be reloaded because it is inactive.

When I manually start gdm systemctl status gdm.service I am able to logout and log back in using gdm. After reboot, the black screen occurs again with the blinking cursor.

Any ideas? Thanks.

GNOME Shell 3.30.1

Ubuntu 18.10 cosmic

Kernel: x86_64 Linux 4.18.0-10-generic

NVIDIA driver 410.73 (GeForce GTX 970)

edited Nov 5 at 8:35

asked Nov 4 at 15:18

jimouris

145

How old is this computer? Laptop or desktop? Video card? Does it boot if you set nomodeset in the kernel boot line in GRUB?
– heynnema
Nov 4 at 23:45

@heynnema Thanks for the suggestion. The computer is a desktop (not old, about 3 years). My video card is Nvidia GeForce GTX 970. I tried the nomodeset flag in GRUB but I got the same error.
– jimouris
Nov 5 at 12:29

You could try reinstalling gdm3. Maybe the update didn't complete. sudo apt-get update and sudo apt-get install --reinstall gdm3. Then sudo dpkg-reconfigure gdm3 and reboot.
– heynnema
Nov 5 at 13:05

I have also tried that, did not work.
– jimouris
Nov 5 at 14:12

Update: Disabling Wayland and reinstalling ubuntu-session fixed the issue, as @adrinux suggested.
– jimouris
Nov 28 at 11:31

add a comment |

up vote
1
down vote

favorite

In order to resolve this issue, I boot into safe mode, reconfigure lightdm and then reboot.

I observed that gdm could not start for some reason (hence the black screen).

$ systemctl status gdm.service 

● gdm.service - GNOME Display Manager

   Loaded: loaded (/lib/systemd/system/gdm.service; static; vendor preset: enabled)

   Active: inactive (dead)



Nov 04 16:46:05 rigel systemd[1]: gdm.service: Unit cannot be reloaded because it is inactive.

When I manually start gdm systemctl status gdm.service I am able to logout and log back in using gdm. After reboot, the black screen occurs again with the blinking cursor.

Any ideas? Thanks.

GNOME Shell 3.30.1

Ubuntu 18.10 cosmic

Kernel: x86_64 Linux 4.18.0-10-generic

NVIDIA driver 410.73 (GeForce GTX 970)

edited Nov 5 at 8:35

asked Nov 4 at 15:18

jimouris

145

In order to resolve this issue, I boot into safe mode, reconfigure lightdm and then reboot.

I observed that gdm could not start for some reason (hence the black screen).

$ systemctl status gdm.service 

● gdm.service - GNOME Display Manager

   Loaded: loaded (/lib/systemd/system/gdm.service; static; vendor preset: enabled)

   Active: inactive (dead)



Nov 04 16:46:05 rigel systemd[1]: gdm.service: Unit cannot be reloaded because it is inactive.

When I manually start gdm systemctl status gdm.service I am able to logout and log back in using gdm. After reboot, the black screen occurs again with the blinking cursor.

Any ideas? Thanks.

GNOME Shell 3.30.1

Ubuntu 18.10 cosmic

Kernel: x86_64 Linux 4.18.0-10-generic

NVIDIA driver 410.73 (GeForce GTX 970)

boot login lightdm gdm 18.10

edited Nov 5 at 8:35

asked Nov 4 at 15:18

jimouris

145

edited Nov 5 at 8:35

asked Nov 4 at 15:18

jimouris

145

edited Nov 5 at 8:35

asked Nov 4 at 15:18

jimouris

145

asked Nov 4 at 15:18

jimouris

145

asked Nov 4 at 15:18

jimouris

145

How old is this computer? Laptop or desktop? Video card? Does it boot if you set nomodeset in the kernel boot line in GRUB?
– heynnema
Nov 4 at 23:45

@heynnema Thanks for the suggestion. The computer is a desktop (not old, about 3 years). My video card is Nvidia GeForce GTX 970. I tried the nomodeset flag in GRUB but I got the same error.
– jimouris
Nov 5 at 12:29

You could try reinstalling gdm3. Maybe the update didn't complete. sudo apt-get update and sudo apt-get install --reinstall gdm3. Then sudo dpkg-reconfigure gdm3 and reboot.
– heynnema
Nov 5 at 13:05

I have also tried that, did not work.
– jimouris
Nov 5 at 14:12

Update: Disabling Wayland and reinstalling ubuntu-session fixed the issue, as @adrinux suggested.
– jimouris
Nov 28 at 11:31

add a comment |

How old is this computer? Laptop or desktop? Video card? Does it boot if you set nomodeset in the kernel boot line in GRUB?
– heynnema
Nov 4 at 23:45

@heynnema Thanks for the suggestion. The computer is a desktop (not old, about 3 years). My video card is Nvidia GeForce GTX 970. I tried the nomodeset flag in GRUB but I got the same error.
– jimouris
Nov 5 at 12:29

You could try reinstalling gdm3. Maybe the update didn't complete. sudo apt-get update and sudo apt-get install --reinstall gdm3. Then sudo dpkg-reconfigure gdm3 and reboot.
– heynnema
Nov 5 at 13:05

I have also tried that, did not work.
– jimouris
Nov 5 at 14:12

Update: Disabling Wayland and reinstalling ubuntu-session fixed the issue, as @adrinux suggested.
– jimouris
Nov 28 at 11:31

How old is this computer? Laptop or desktop? Video card? Does it boot if you set nomodeset in the kernel boot line in GRUB?
– heynnema
Nov 4 at 23:45

@heynnema Thanks for the suggestion. The computer is a desktop (not old, about 3 years). My video card is Nvidia GeForce GTX 970. I tried the nomodeset flag in GRUB but I got the same error.
– jimouris
Nov 5 at 12:29

You could try reinstalling gdm3. Maybe the update didn't complete. sudo apt-get update and sudo apt-get install --reinstall gdm3. Then sudo dpkg-reconfigure gdm3 and reboot.
– heynnema
Nov 5 at 13:05

I have also tried that, did not work.
– jimouris
Nov 5 at 14:12

Update: Disabling Wayland and reinstalling ubuntu-session fixed the issue, as @adrinux suggested.
– jimouris
Nov 28 at 11:31

add a comment |

3 Answers
3

active

oldest

votes

up vote
1
down vote

accepted

I had the same problem on both my Ubuntu 18.04 boxes after upgrade to 18.10. Both are configured with nvidia grahpics and to use the vanilla gnome session Ubuntu provides (not the Unity-ish version they munged together). Much faffing with nvidia drivers had no effect.

I did two other things - not sure which brought it back. From this answer
Edit /etc/gdm3/custom.conf as a sudo and uncomment the line to force Xorg over Wayland

WaylandEnable=false

I also installed ubuntu-session:

sudo apt install ubuntu-session

But not sure whether that is really required so I suggest you try editing /etc/gdm3/custom.conf and rebooting first.

hth

edited 2 days ago

jimouris

145

answered Nov 27 at 10:37

adrinux

263

New contributor

Thanks!! I have tried to disable Wayland WaylandEnable=false (I saw it in the same answer as you), but it had not worked. However, reinstalling ubuntu-session fixed the problem.
– jimouris
Nov 28 at 11:21

Out if interest did you revert that change to WaylandEnable=false before reinstalling ubuntu-session?
– adrinux
2 days ago

Yes, I first disabled Wayland and then reinstalled ubuntu-session.
– jimouris
2 days ago

add a comment |

up vote
0
down vote

NVIDIA driver 410.73 may be causing the computer to boot to a black screen. Uninstall it, remove the PPA that it was installed from, run sudo apt update, and run sudo reboot. Then open the terminal and type:

sudo apt update  

sudo apt upgrade  

sudo ubuntu-drivers autoinstall   

sudo reboot

The autoinstall command of ubuntu-drivers installs drivers that are appropriate for automatic installation including their dependencies.

edited Nov 6 at 7:16

answered Nov 5 at 15:17

karel

55.3k11122140

Thanks for the suggestion but it did not work too; I got the exactly same error. It does not seem to be related with the drivers.
– jimouris
Nov 9 at 10:22

gdm3 gives the black screen with nvidia-410 or 390. You may get help by preventing Wayland, but I do not. By installing lightdm, maybe you solved. However, the config of graphics setup is very fragile and requires a number of kernel parameters to make sure the screen will turn on when you resume from suspend. (devtalk.nvidia.com/default/topic/1044633/linux/…) and (devtalk.nvidia.com/default/topic/1044730/linux/…)
– pauljohn32
21 hours ago

@pauljohn32 It's true that the graphics setup is very fragile. It's so fragile that it can cross the line into mixed hardware/software issues, e.g. a big graphics card being driven by a small power supply can result in various types of instability, including boot issues. The Nvidia graphics cards are named according to their graphics engines (e.g. GT 710 and GTX 1050) and different built-in graphics engines plays a role in this too.
– karel
21 hours ago

add a comment |

up vote
0
down vote

In my case, I needed to switch from the display manger gdm3 to sddm and everything then worked. Before this switch I also reinstalled and reconfigured gmd3 first - but no joy. I then switched to sddm and everything worked properly.
I hope this helps others.

answered 2 days ago

JoelParke

1014

New contributor

Yes, the problem is only with gdm, not lightdm or ssdm. Disabling Wayland and reinstalling ubuntu-session fixed the problem.
– jimouris
2 days ago

1

Please don't add "thank you" as an answer. Instead, vote up the answers that you find helpful. - From Review
– Fabby
2 days ago

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',
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');
});

Post as a guest

Name

Required, but never shown

StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1089970%2fgdm3-wont-start-by-default-after-upgrade-to-18-10-from-18-04%23new-answer', 'question_page');
}
);

Post as a guest

Name

Required, but never shown

3 Answers
3

active

oldest

votes

3 Answers
3

active

oldest

votes

up vote
1
down vote

accepted

I did two other things - not sure which brought it back. From this answer
Edit /etc/gdm3/custom.conf as a sudo and uncomment the line to force Xorg over Wayland

WaylandEnable=false

I also installed ubuntu-session:

sudo apt install ubuntu-session

But not sure whether that is really required so I suggest you try editing /etc/gdm3/custom.conf and rebooting first.

hth

edited 2 days ago

jimouris

145

answered Nov 27 at 10:37

adrinux

263

New contributor

Thanks!! I have tried to disable Wayland WaylandEnable=false (I saw it in the same answer as you), but it had not worked. However, reinstalling ubuntu-session fixed the problem.
– jimouris
Nov 28 at 11:21

Out if interest did you revert that change to WaylandEnable=false before reinstalling ubuntu-session?
– adrinux
2 days ago

Yes, I first disabled Wayland and then reinstalled ubuntu-session.
– jimouris
2 days ago

add a comment |

up vote
1
down vote

accepted

I did two other things - not sure which brought it back. From this answer
Edit /etc/gdm3/custom.conf as a sudo and uncomment the line to force Xorg over Wayland

WaylandEnable=false

I also installed ubuntu-session:

sudo apt install ubuntu-session

But not sure whether that is really required so I suggest you try editing /etc/gdm3/custom.conf and rebooting first.

hth

edited 2 days ago

jimouris

145

answered Nov 27 at 10:37

adrinux

263

New contributor

Thanks!! I have tried to disable Wayland WaylandEnable=false (I saw it in the same answer as you), but it had not worked. However, reinstalling ubuntu-session fixed the problem.
– jimouris
Nov 28 at 11:21

Out if interest did you revert that change to WaylandEnable=false before reinstalling ubuntu-session?
– adrinux
2 days ago

Yes, I first disabled Wayland and then reinstalled ubuntu-session.
– jimouris
2 days ago

add a comment |

up vote
1
down vote

accepted

I did two other things - not sure which brought it back. From this answer
Edit /etc/gdm3/custom.conf as a sudo and uncomment the line to force Xorg over Wayland

WaylandEnable=false

I also installed ubuntu-session:

sudo apt install ubuntu-session

But not sure whether that is really required so I suggest you try editing /etc/gdm3/custom.conf and rebooting first.

hth

edited 2 days ago

jimouris

145

answered Nov 27 at 10:37

adrinux

263

New contributor

I did two other things - not sure which brought it back. From this answer
Edit /etc/gdm3/custom.conf as a sudo and uncomment the line to force Xorg over Wayland

WaylandEnable=false

I also installed ubuntu-session:

sudo apt install ubuntu-session

But not sure whether that is really required so I suggest you try editing /etc/gdm3/custom.conf and rebooting first.

hth

edited 2 days ago

jimouris

145

answered Nov 27 at 10:37

adrinux

263

New contributor

edited 2 days ago

jimouris

145

edited 2 days ago

jimouris

145

edited 2 days ago

jimouris

145

answered Nov 27 at 10:37

adrinux

263

New contributor

answered Nov 27 at 10:37

adrinux

263

answered Nov 27 at 10:37

adrinux

263

New contributor

adrinux is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

Thanks!! I have tried to disable Wayland WaylandEnable=false (I saw it in the same answer as you), but it had not worked. However, reinstalling ubuntu-session fixed the problem.
– jimouris
Nov 28 at 11:21

Out if interest did you revert that change to WaylandEnable=false before reinstalling ubuntu-session?
– adrinux
2 days ago

Yes, I first disabled Wayland and then reinstalled ubuntu-session.
– jimouris
2 days ago

add a comment |

Thanks!! I have tried to disable Wayland WaylandEnable=false (I saw it in the same answer as you), but it had not worked. However, reinstalling ubuntu-session fixed the problem.
– jimouris
Nov 28 at 11:21

Out if interest did you revert that change to WaylandEnable=false before reinstalling ubuntu-session?
– adrinux
2 days ago

Yes, I first disabled Wayland and then reinstalled ubuntu-session.
– jimouris
2 days ago

Thanks!! I have tried to disable Wayland WaylandEnable=false (I saw it in the same answer as you), but it had not worked. However, reinstalling ubuntu-session fixed the problem.
– jimouris
Nov 28 at 11:21

Out if interest did you revert that change to WaylandEnable=false before reinstalling ubuntu-session?
– adrinux
2 days ago

Yes, I first disabled Wayland and then reinstalled ubuntu-session.
– jimouris
2 days ago

add a comment |

up vote
0
down vote

sudo apt update  

sudo apt upgrade  

sudo ubuntu-drivers autoinstall   

sudo reboot

The autoinstall command of ubuntu-drivers installs drivers that are appropriate for automatic installation including their dependencies.

edited Nov 6 at 7:16

answered Nov 5 at 15:17

karel

55.3k11122140

Thanks for the suggestion but it did not work too; I got the exactly same error. It does not seem to be related with the drivers.
– jimouris
Nov 9 at 10:22

gdm3 gives the black screen with nvidia-410 or 390. You may get help by preventing Wayland, but I do not. By installing lightdm, maybe you solved. However, the config of graphics setup is very fragile and requires a number of kernel parameters to make sure the screen will turn on when you resume from suspend. (devtalk.nvidia.com/default/topic/1044633/linux/…) and (devtalk.nvidia.com/default/topic/1044730/linux/…)
– pauljohn32
21 hours ago

@pauljohn32 It's true that the graphics setup is very fragile. It's so fragile that it can cross the line into mixed hardware/software issues, e.g. a big graphics card being driven by a small power supply can result in various types of instability, including boot issues. The Nvidia graphics cards are named according to their graphics engines (e.g. GT 710 and GTX 1050) and different built-in graphics engines plays a role in this too.
– karel
21 hours ago

add a comment |

up vote
0
down vote

sudo apt update  

sudo apt upgrade  

sudo ubuntu-drivers autoinstall   

sudo reboot

The autoinstall command of ubuntu-drivers installs drivers that are appropriate for automatic installation including their dependencies.

edited Nov 6 at 7:16

answered Nov 5 at 15:17

karel

55.3k11122140

Thanks for the suggestion but it did not work too; I got the exactly same error. It does not seem to be related with the drivers.
– jimouris
Nov 9 at 10:22

gdm3 gives the black screen with nvidia-410 or 390. You may get help by preventing Wayland, but I do not. By installing lightdm, maybe you solved. However, the config of graphics setup is very fragile and requires a number of kernel parameters to make sure the screen will turn on when you resume from suspend. (devtalk.nvidia.com/default/topic/1044633/linux/…) and (devtalk.nvidia.com/default/topic/1044730/linux/…)
– pauljohn32
21 hours ago

@pauljohn32 It's true that the graphics setup is very fragile. It's so fragile that it can cross the line into mixed hardware/software issues, e.g. a big graphics card being driven by a small power supply can result in various types of instability, including boot issues. The Nvidia graphics cards are named according to their graphics engines (e.g. GT 710 and GTX 1050) and different built-in graphics engines plays a role in this too.
– karel
21 hours ago

add a comment |

up vote
0
down vote

sudo apt update  

sudo apt upgrade  

sudo ubuntu-drivers autoinstall   

sudo reboot

The autoinstall command of ubuntu-drivers installs drivers that are appropriate for automatic installation including their dependencies.

edited Nov 6 at 7:16

answered Nov 5 at 15:17

karel

55.3k11122140

sudo apt update  

sudo apt upgrade  

sudo ubuntu-drivers autoinstall   

sudo reboot

The autoinstall command of ubuntu-drivers installs drivers that are appropriate for automatic installation including their dependencies.

edited Nov 6 at 7:16

answered Nov 5 at 15:17

karel

55.3k11122140

edited Nov 6 at 7:16

answered Nov 5 at 15:17

karel

55.3k11122140

answered Nov 5 at 15:17

karel

55.3k11122140

answered Nov 5 at 15:17

karel

55.3k11122140

Thanks for the suggestion but it did not work too; I got the exactly same error. It does not seem to be related with the drivers.
– jimouris
Nov 9 at 10:22

gdm3 gives the black screen with nvidia-410 or 390. You may get help by preventing Wayland, but I do not. By installing lightdm, maybe you solved. However, the config of graphics setup is very fragile and requires a number of kernel parameters to make sure the screen will turn on when you resume from suspend. (devtalk.nvidia.com/default/topic/1044633/linux/…) and (devtalk.nvidia.com/default/topic/1044730/linux/…)
– pauljohn32
21 hours ago

@pauljohn32 It's true that the graphics setup is very fragile. It's so fragile that it can cross the line into mixed hardware/software issues, e.g. a big graphics card being driven by a small power supply can result in various types of instability, including boot issues. The Nvidia graphics cards are named according to their graphics engines (e.g. GT 710 and GTX 1050) and different built-in graphics engines plays a role in this too.
– karel
21 hours ago

add a comment |

Thanks for the suggestion but it did not work too; I got the exactly same error. It does not seem to be related with the drivers.
– jimouris
Nov 9 at 10:22

gdm3 gives the black screen with nvidia-410 or 390. You may get help by preventing Wayland, but I do not. By installing lightdm, maybe you solved. However, the config of graphics setup is very fragile and requires a number of kernel parameters to make sure the screen will turn on when you resume from suspend. (devtalk.nvidia.com/default/topic/1044633/linux/…) and (devtalk.nvidia.com/default/topic/1044730/linux/…)
– pauljohn32
21 hours ago

@pauljohn32 It's true that the graphics setup is very fragile. It's so fragile that it can cross the line into mixed hardware/software issues, e.g. a big graphics card being driven by a small power supply can result in various types of instability, including boot issues. The Nvidia graphics cards are named according to their graphics engines (e.g. GT 710 and GTX 1050) and different built-in graphics engines plays a role in this too.
– karel
21 hours ago

Thanks for the suggestion but it did not work too; I got the exactly same error. It does not seem to be related with the drivers.
– jimouris
Nov 9 at 10:22

gdm3 gives the black screen with nvidia-410 or 390. You may get help by preventing Wayland, but I do not. By installing lightdm, maybe you solved. However, the config of graphics setup is very fragile and requires a number of kernel parameters to make sure the screen will turn on when you resume from suspend. (devtalk.nvidia.com/default/topic/1044633/linux/…) and (devtalk.nvidia.com/default/topic/1044730/linux/…)
– pauljohn32
21 hours ago

@pauljohn32 It's true that the graphics setup is very fragile. It's so fragile that it can cross the line into mixed hardware/software issues, e.g. a big graphics card being driven by a small power supply can result in various types of instability, including boot issues. The Nvidia graphics cards are named according to their graphics engines (e.g. GT 710 and GTX 1050) and different built-in graphics engines plays a role in this too.
– karel
21 hours ago

add a comment |

up vote
0
down vote

answered 2 days ago

JoelParke

1014

New contributor

Yes, the problem is only with gdm, not lightdm or ssdm. Disabling Wayland and reinstalling ubuntu-session fixed the problem.
– jimouris
2 days ago

1

Please don't add "thank you" as an answer. Instead, vote up the answers that you find helpful. - From Review
– Fabby
2 days ago

add a comment |

up vote
0
down vote

answered 2 days ago

JoelParke

1014

New contributor

Yes, the problem is only with gdm, not lightdm or ssdm. Disabling Wayland and reinstalling ubuntu-session fixed the problem.
– jimouris
2 days ago

1

Please don't add "thank you" as an answer. Instead, vote up the answers that you find helpful. - From Review
– Fabby
2 days ago

add a comment |

up vote
0
down vote

answered 2 days ago

JoelParke

1014

New contributor

answered 2 days ago

JoelParke

1014

New contributor

answered 2 days ago

JoelParke

1014

New contributor

answered 2 days ago

JoelParke

1014

answered 2 days ago

JoelParke

1014

New contributor

JoelParke is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

Yes, the problem is only with gdm, not lightdm or ssdm. Disabling Wayland and reinstalling ubuntu-session fixed the problem.
– jimouris
2 days ago

1

Please don't add "thank you" as an answer. Instead, vote up the answers that you find helpful. - From Review
– Fabby
2 days ago

add a comment |

Yes, the problem is only with gdm, not lightdm or ssdm. Disabling Wayland and reinstalling ubuntu-session fixed the problem.
– jimouris
2 days ago

1

Please don't add "thank you" as an answer. Instead, vote up the answers that you find helpful. - From Review
– Fabby
2 days ago

Yes, the problem is only with gdm, not lightdm or ssdm. Disabling Wayland and reinstalling ubuntu-session fixed the problem.
– jimouris
2 days ago

Please don't add "thank you" as an answer. Instead, vote up the answers that you find helpful. - From Review
– Fabby
2 days ago

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.

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.

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Name

Required, but never shown

Name

Required, but never shown

This page is only for reference, If you need detailed information, please check here

搜尋此網誌

Cfxtrjtrk