Pop!_OS 21.10 upgrade 22.04 failure record

Problem Description:

The system always pops up a prompt box to upgrade to 22.04. In view of the previous failure of using automatic upgrade, I have ignored it. But I can't stand the trend of its daily prompts becoming more and more frequent, so try the upgrade function that comes with the system again.

Follow the prompts to download and then upgrade so far all goes well. I am just happy that the automatic update function of the system is easy to use. After restarting and entering the system, I find that the desktop does not respond, the keyboard does not respond, and the mouse can move back and forth on the dull desktop. It seems that the upgrade failed, what should I do?

Solution:

Try to press ctrl+alt+F3 to open a new command line terminal. Fortunately, there is a response. Based on the fact that the automatic update function of the system has not been used before, let’s go back without further ado.

Go to the /etc/apt directory to restore the source file to the version before the upgrade. Fortunately, the automatic upgrade will back up the previous file with a save suffix. Then execute

sudo apt-get update

sudo apt-get upgrade

Error again:

Find the corresponding log file from the error message:

warning: the compiler differs from the one used to build the kernel 

The kernel was built by: gcc (Ubuntu 11.2.0-19-ubuntu1) 11.2.0 

You are using: gcc (Ubuntu 11.2.0-7-ubuntu2) 11.2.0

CC(M) /var/lib/dkms/system76/1.0.14~xxx/build/system76.o 

gcc: error: unrecongized command-line option '-mharden-sls=all'

It seems that the gcc version does not match, but the version number is changed to the same as the kernel, and it is not easy to operate on the command line terminal. Simply delete /var/lib/dkms/system76/1.0.14~xxx and execute again

sudo apt-get upgrade

No more errors. Enter reboot to restart the computer and enter the system again, the familiar feeling is back!

If you use the system's built-in upgrade successfully, please leave a message

 

Guess you like

Origin blog.csdn.net/tianlangstudio/article/details/126353797