[SOLVED] Today's Updates no longer can get to Login Screen

[MoonRise]

Per the Subject.

Anyone else?

This is a whole new install and nothing custom at that.

[chimak111]

Start-Date: 2020-09-22  06:46:59
Commandline: /usr/bin/unattended-upgrade
Install: linux-headers-5.4.0-48-generic:amd64 (5.4.0-48.52, automatic), linux-modules-extra-5.4.0-48-generic:amd64 (5.4.0-48.52, automatic), linux-modules-5.4.0-48-generic:amd64 (5.4.0-48.52, automatic), linux-headers-5.4.0-48:amd64 (5.4.0-48.52, automatic), linux-image-5.4.0-48-generic:amd64 (5.4.0-48.52, automatic)
Upgrade: linux-headers-generic:amd64 (5.4.0.47.50, 5.4.0.48.51), linux-image-generic:amd64 (5.4.0.47.50, 5.4.0.48.51), linux-generic:amd64 (5.4.0.47.50, 5.4.0.48.51)
End-Date: 2020-09-22  06:48:15

Start-Date: 2020-09-22  06:57:39
Commandline: apt autoremove
Requested-By: chimak (1000)
Remove: linux-headers-5.4.0-42-generic:amd64 (5.4.0-42.46), linux-modules-5.4.0-42-generic:amd64 (5.4.0-42.46), linux-headers-5.4.0-42:amd64 (5.4.0-42.46), linux-image-5.4.0-42-generic:amd64 (5.4.0-42.46), linux-modules-extra-5.4.0-42-generic:amd64 (5.4.0-42.46)
End-Date: 2020-09-22  06:58:26

I haven't rebooted after the above updates. Can you boot with the previous kernel? I'll be rebooting tomorrow morning and, thanks to your post, will be wary!

[GreyGeek]

Yesterday's update installed this kernel:
5.4.0-48-generic #52-Ubuntu SMP Thu Sep 10 10:58:49 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
and it is running fine for me.

You can boot into the recovery mode and examine your log files to see what any complaints are:
https://www.maketecheasier.com/boot-...y-mode-ubuntu/

[MoonRise]

Thanks! I'll try the old kernel and let you all know.

[MoonRise]

Thanks! That was it evidently!

@GG - I will when I get a chance. Thanks!

[chimak111]

My system booted and the login screen appeared without any issue.

[MoonRise]

Same issues here but found the kernel log. Below is why it is having issues. There was an NVidia update too. Not sure how to resolve from this point. Anyone with pointers?

Sep 23 06:44:47 NBDOITS kernel: [   10.155556] NVRM: API mismatch: the client has the version 450.66, but
Sep 23 06:44:47 NBDOITS kernel: [   10.155556] NVRM: this kernel module has the version 440.100. Please
Sep 23 06:44:47 NBDOITS kernel: [   10.155556] NVRM: make sure that this kernel module and all NVIDIA driver
Sep 23 06:44:47 NBDOITS kernel: [   10.155556] NVRM: components have the same version.
Sep 23 06:44:47 NBDOITS kernel: [   10.155916] NVRM: API mismatch: the client has the version 450.66, but
Sep 23 06:44:47 NBDOITS kernel: [   10.155916] NVRM: this kernel module has the version 440.100. Please
Sep 23 06:44:47 NBDOITS kernel: [   10.155916] NVRM: make sure that this kernel module and all NVIDIA driver
Sep 23 06:44:47 NBDOITS kernel: [   10.155916] NVRM: components have the same version.
Sep 23 06:44:47 NBDOITS kernel: [   10.175274] NVRM: API mismatch: the client has the version 450.66, but
Sep 23 06:44:47 NBDOITS kernel: [   10.175274] NVRM: this kernel module has the version 440.100. Please
Sep 23 06:44:47 NBDOITS kernel: [   10.175274] NVRM: make sure that this kernel module and all NVIDIA driver
Sep 23 06:44:47 NBDOITS kernel: [   10.175274] NVRM: components have the same version.
Sep 23 06:44:49 NBDOITS kernel: [   11.942053] Lockdown: Xorg: raw io port access is restricted; see man kernel_lockdown.7
Sep 23 06:44:49 NBDOITS kernel: [   11.944449] NVRM: API mismatch: the client has the version 450.66, but
Sep 23 06:44:49 NBDOITS kernel: [   11.944449] NVRM: this kernel module has the version 440.100. Please
Sep 23 06:44:49 NBDOITS kernel: [   11.944449] NVRM: make sure that this kernel module and all NVIDIA driver
Sep 23 06:44:49 NBDOITS kernel: [   11.944449] NVRM: components have the same version.
Sep 23 06:44:49 NBDOITS kernel: [   11.945490] NVRM: API mismatch: the client has the version 450.66, but
Sep 23 06:44:49 NBDOITS kernel: [   11.945490] NVRM: this kernel module has the version 440.100. Please
Sep 23 06:44:49 NBDOITS kernel: [   11.945490] NVRM: make sure that this kernel module and all NVIDIA driver
Sep 23 06:44:49 NBDOITS kernel: [   11.945490] NVRM: components have the same version.
Sep 23 06:44:49 NBDOITS kernel: [   11.968109] NVRM: API mismatch: the client has the version 450.66, but
Sep 23 06:44:49 NBDOITS kernel: [   11.968109] NVRM: this kernel module has the version 440.100. Please
Sep 23 06:44:49 NBDOITS kernel: [   11.968109] NVRM: make sure that this kernel module and all NVIDIA driver
Sep 23 06:44:49 NBDOITS kernel: [   11.968109] NVRM: components have the same version.

[claydoh]

you need to rebuild the kernel module for your specific kernel, that is what the mismatch is indicating.

Try reinstalling nvidia-driver-450, I cannot find or recall if there is a simpler method to have the system just build/rebuild the modules for all the kernels you have, which us what is supposed to happen. Until it doesn't of course.

[MoonRise]

Thanks all! I'll try the NVidia reinstall and see what it does.

[MoonRise]

That didn't fix it though I did the reinstall of all Nvidia 450 components through Synaptic. Maybe some other way?

[Aguilito]

I have the same problem. This is a relatively fresh install from distro and I had been running for a week or so without a cold start.

Today this morning, boot completes without starting the graphical login.

To login I have to do a console login and then startx manually. That works.

Something appears to have gone wrong with the startup scripts.

Update:

I did an "apt update" and then installed all found upgrades and the problem is gone.

There is a lot of rough edges with this kubuntu 20.04...unexpected and not very welcome.

[MoonRise]

Sees a little different from my issue, of which I've yet to resolve. Mine revolves around the Nvidia driver used in the kernel I was updated to. Unfortunately the Kernel and the Nvidia driver were updated at the same time and I guess that didn't play nice. Luckily I can get to login via another kernel that I left on here.

To all here, I tried

[FONT=monospace][COLOR=#000000]ls /var/lib/initramfs-tools | sudo xargs -n1 /usr/lib/dkms/dkms_autoinstaller start[/COLOR]
[/FONT]

Still does not boot but at least it fails out to a konsole like area instead of the PC's BIOS splash.

Still looking. If I get it fixed I'll report back here.

[jglen490]

I have the same problem. This is a relatively fresh install from distro and I had been running for a week or so without a cold start.

Today this morning, boot completes without starting the graphical login.

To login I have to do a console login and then startx manually. That works.

Something appears to have gone wrong with the startup scripts.

Update:

I did an "apt update" and then installed all found upgrades and the problem is gone.

There is a lot of rough edges with this kubuntu 20.04...unexpected and not very welcome.

I don't know if you started from 20.04 or from 20.04.1, but I think it may make a difference. I was on 18.04.5, and did a clean install to 20.04. It worked, but there were issues, so I went back to 18.04.5. When 20.04.1 was released, I clean installed that one - much better. Basically, one small issue with the Realtek wifi adapter, and a larger one with HPLIP - in my my neither is specifically Kubuntu's fault. The Realtek issue is resolved, it just took a wile for the maintainer to catch up to 20.04. The HPLIP on has been sort of resolved via CUPS "driverless". Not 100%, but certainly 75% of the HPLIP GUI and 95%+ on the print and scan functionality.

The point of my ramble is that with a new LTS, the xx.xx.1 release is far better, smoother, organized, correct, and satisfying than the original.

[Aguilito]

The point of my ramble is that with a new LTS, the xx.xx.1 release is far better, smoother, organized, correct, and satisfying than the original.

You could be right. However, I started with .1 on my workstation and my laptop was .0. As I mentioned it got resolved on the workstation.

Then I noted laptop was behind. It had been playing up whereby everytime I have to start up I had to go via recovery and then resume boot. Otherwise I got a hanging screen.

After updates I now get past the hanging screen but graphical startup doesn't happen.

So, I think it is time to re-install with .1 on the laptop but I am seriously beginning to regret being a alpha tester for kubuntu 20.04.x ..

[MoonRise]

So, after many recent kernel updates and one NVidia update I still had the issue.

Made the time to look into the issue further.

Noted I had extra files in /etc/grub.d. Couldn't tell why but there were instructions there on how to recover from the backup files Whatever it was that created those. DON'T do what it states. Broke being able to run update-grub.

So, what was it that did all this mess. Grub Customizer. I removed that but of course I had already damaged GRUB so since I was able to still boot with the old Grub CFG file that was still viable I did the following and everything is back normal.

The steps I used are as follows:

1. I confirmed that I had an internet connection with sudo apt-get update # ***
2. I purged grub-pc and grub-common with sudo apt-get purge grub-pc grub-common
3. I read the warning about removing the bootloader, hit TAB to highlight "" and pressed ENTER.
4. I issued the command apt-get install grub-common grub-pc and when prompted I hit TAB to highlight "" and pressed ENTER
5. When presented with the device option, I used the UP/DN keys to select the correct drive (sdX) NOT a partition.
   I made sure the installation drive [] /dev/sdX had an asterisk next to it ( in my case: [] /dev/sda ). If it doesn't, highlight it and press the SPACE bar to select it. Then I hit TAB to highlight "" and pressed ENTER
   I tested that the installation was complete and working by issuing the command sudo update-grub and everything worked error free as expected.