Error after sudo apt update && sudo apt full-upgrade

[victorxavier]

Hello guys!

I am having a problem with Debian since I executed this command: sudo apt update && sudo apt full-upgrade. I was trying to update my new laptop from debian 12 to 13. Even with these errors I ignored and continue to upgrade and when I reboot it is having a kernel problem that I believe to be in the previous error. I am typing this message in the recovery mode and I don't know if anything else to do, like downgrade or solving this problem. I will be very grateful to all answers from this problem.

 

[Oldhabbits]

For me, best thing you can do is temporary remove linux-headers-amd64, and while you at it, also remove linux-headers-6.1.0-38-amd64. They seem to hold back any other kernel-related upgrade; after all things are done, you can install these headers back for the running 6.12.41 kernel.
Good luck !

 

[CaffeineAddict]

Have you tried installing linux-headers-6.12.41+deb13-amd64 manually prior upgrade?

 

[Brickwizard]

Sounds like something didn't install properly last time you ran update
try first running

'sudo dpkg --configure -a

then sudo apt update && apt upgrade -y

or re-boot and at grub select advanced options and roll back to the Kernel before the problem one, boot then run the updates again

 

[Condobloke]

I will second @Brickwizard's advice above...

sudo dpkg --configure -a

Want some more info to read ?

Fix ”sub-process /usr/bin/dpkg returned an error code (1)"

The ”sub-process /usr/bin/dpkg returned an error code (1)" error points to a problem with the dpkg package manager. Find out how to fix it.

phoenixnap.com

[Solved] “sub process usr bin dpkg returned an error code 1″

If you are encountering “sub process usr bin dpkg returned an error code 1” while installing software on Ubuntu Linux, here is how you can fix it.

itsfoss.com

 

[osprey]

Hello guys!

View attachment 27445

I am having a problem with Debian since I executed this command: sudo apt update && sudo apt full-upgrade. I was trying to update my new laptop from debian 12 to 13. Even with these errors I ignored and continue to upgrade and when I reboot it is having a kernel problem that I believe to be in the previous error. I am typing this message in the recovery mode and I don't know if anything else to do, like downgrade or solving this problem. I will be very grateful to all answers from this problem.

This problem can arise because of a missed step in updating and upgrading that can avoid this issue. The wise steps are to: apt update and then apt upgrade before you run apt full-upgrade.

The reason is to get the system in a more optimal state, that is, the most upgraded state, before running the full-upgrade ... one step at a time.

Another aspect worth considering is to run the commands separately so that the output on screen can be inspected and any issues attended to. For example, after running apt upgrade alone, the screen shows what will be done, and if anything looks suspicious or improbable, then the user can make adjustments by holding off some packages that look like they could be troublesome. Granted, there's some experience needed for this sort of assessment.

Another thing is to install the package: apt-listbugs, which will show existing bugs on the screen after running apt upgrade, which will then also give the user the opportunity to proceed or make adjustments to deal with the situation, for example, by holding off the packages with the bugs.

To attack this particular problem in post #1, one can try running, as root: dpkg --configure -a, but if that fails, another tack is to select an earlier kernel that works on a reboot and delete all the packages that are troublesome, and start the whole updating and upgrading process again with more discernment such as the approach outlined above.

 

[wizardfromoz]

Helpers - has anyone the experience with the new deb822 format that uses a modernize-sources whereby /etc/apt/sources.list is replaced with a file

debian.sources

?? If not, it might be considered for the OP.

I'll hang back until I see how this is progressing

Avagudweegend

Wizard

BTW initially I am not overly impressed with the new method, I prefer files named sources.list, but I may change my mind. It's happened before (well, maybe a 1,000 years ago)

 

[Brickwizard]

no I have had a look but at the moment i see no real advantage [looks more complicated to me] pleased to see this paragraph in the docs

the traditional format and is supported by all current APT versions.It has the advantage of being relatively compact for single-sources andrelatively easy for humans to parse.

 

[osprey]

Helpers - has anyone the experience with the new deb822 format that uses a modernize-sources whereby /etc/apt/sources.list is replaced with a file

debian.sources

?? If not, it might be considered for the OP.

I'll hang back until I see how this is progressing

Avagudweegend

Wizard

BTW initially I am not overly impressed with the new method, I prefer files named sources.list, but I may change my mind. It's happened before (well, maybe a 1,000 years ago)

Four machines here have modernized sources running debian stable, testing, sid and siduction. The new format is more detailed and clearer with prefixed titles for each line of configuration. Compare:

deb http://ftp.au.debian.org/debian/ trixie main contrib non-free non-free-firmware

with:

# Modernized from /etc/apt/sources.list
Types: deb
URIs: http://ftp.au.debian.org/debian/
Suites: trixie
Components: main  contrib non-free non-free-firmware
Signed-By: /usr/share/keyrings/debian-archive-keyring.gpg

When one runs: apt modernize-sources to create the new configuration, it backs up the old sources.lists so the user loses nothing and theoretically can revert if they wish. In operation however, now for some weeks, it's flawless. Does that help?

 

[victorxavier]

Have you tried installing linux-headers-6.12.41+deb13-amd64 manually prior upgrade?

I didnt try it

 

[victorxavier]

Sounds like something didn't install properly last time you ran update
try first running

'sudo dpkg --configure -a

then sudo apt update && apt upgrade -y

or re-boot and at grub select advanced options and roll back to the Kernel before the problem one, boot then run the updates again

Thank you for the suggestion, but my headers are breaking this operation

 

[Brickwizard]

the only other thing i can think of at the moment is in order listed...

sudo apt update && apt --fix-missing
sudo apt fix--broken install
sudo apt upgrade

 

[Mike-BTU]

the only other thing i can think of at the moment is in order listed...

sudo apt update && apt --fix-missing
sudo apt fix--broken install
sudo apt upgrade

Did this work right?