-1

On Boot Screen Log:

[ OK ] Sarted GNOME Display Manager. Dispatcher Service....proxy server...p link was shut down.

OS: Ubuntu 18.04.6 (last 32-bit) Linux 4.15.0-176-generic Gnome: 3.28.2

I could log in via ssh and I tried: Ubuntu fails to boot fully, stuck in log screen "ppp link was shut down" Solution b and then Solution a, but both didn't help. Then I did sudo apt purge gdm gdm3 and now I even can't login via ssh anymore. Also Alt-F2/Alt-F7 on the PC directly didn't help.

Next I tried: Ubuntu doesn't start, with a message 'Started GNOME Display Manager. Dispatcher Service... system changes.pp link was shut down' while reinstalling sudo apt install gdm3 ubuntu-desktop, but it didn't help either.

CLI only would be sufficient for me as well. How can i downgrade the desktop/gnome environment? But full functionality would be appreciated.

2 Answers2

1

If you want CLI only, I recommend you reinstall with Ubuntu Server.

Removing gdm from your install should not affect openssh-server. So I am not sure what happened there.

If you have data on your current install, and don't want to reinstall, I recommend you use the "Advanced Options" in the GRUB boot menu, and boot in Recovery Mode.

When in single-user text mode you could investigate your ssh issue, or uninstall components you no longer need. Like the ubuntu-desktop package.

A minimal OS like ubuntu-server is less likely to have issues, and also: what GPU are you using?

Bram
  • 3,699
0

It seems I accidentally updated to Ubuntu 18.04.6, however 16.04.6 is the last 32-Bit version. The 18.04.6 worked for a short time, probably until the gnome desktop manager (gdm) was updated. The other programs as ssh etc. seemed to still work.

Why i couldn't log in via ssh i still can't tell, maybe it took more time to restart due to the gdm issue and i wasn't patient enough to wait, as the gdm is started first and then the openssh-server.

I reinstalled version 16.04.6 from scratch and it works again. I had some trouble with the hdd so i can't tell if a corrupted package was also the cause of this problem. I will test the hdd soon and give update about it.