Integrity and config errors Ubuntu
from Another_username@lemmy.world to linux@lemmy.ml on 04 Dec 2023 13:23
https://lemmy.world/post/9128645

Hello everyone…I’m getting these integrity and confit errors during startup. Nothing seems broken. Does anyone know a fix or should i just ignore? Thanks!

#linux

cbarrick@lemmy.world on 04 Dec 2023 13:49 next collapse

X.509 certs are commonly used in TLS/HTTPS.

Why is one needed in your boot process?

Is your drive encrypted?

Another_username@lemmy.world on 04 Dec 2023 14:04 next collapse

I have no idea why it’s needed. I’m a noob so maybe I fucked it up somehow haha

My device isn’t encrypted.

Another_username@lemmy.world on 04 Dec 2023 14:38 next collapse

I was trying to install a docker container at one point. Could this be it?

cbarrick@lemmy.world on 04 Dec 2023 18:56 collapse

Did you try to set up that container to serve HTTPS?

It sounds like you have some service configured to serve HTTPS, and it’s having trouble starting because the cert is broken.

Only that particular service will be broken. The rest of the system is fine.

Check systemctl status --failed for more info.

Edit: I’m only talking about the X.509 error. The AMD error is probably related to your hardware.

Another_username@lemmy.world on 05 Dec 2023 19:37 collapse

I was setting up the containers to fix a problem when using wine, but found a different solution. I checked the system status. 0 units failed and x.509 isn’t mentioned

lemann@lemmy.one on 04 Dec 2023 15:06 next collapse

X.509 certs are commonly used in TLS/HTTPS.

Why is one needed in your boot process?

Don’t know why but I found this funny

merthyr1831@lemmy.world on 12 Dec 2023 08:56 collapse

Secure boot uses them

darcmage@lemm.ee on 04 Dec 2023 14:15 next collapse

Did a search for ubuntu “integrity: problem loading x.509 certificate” and the first result indicates out of date bios certificates needed for secure boot on older laptops. Disabling secure boot seems to be the suggested fix.

med@sh.itjust.works on 04 Dec 2023 14:19 next collapse

You might check your BIOS clock time too, if the certs are ‘expired’, it might be the future, or more likely, the past. Certs have validity timers that specify start and end.

It’s more likely that your BIOS is just old, and you’ll have to keep secure boot disabled from now on.

Another_username@lemmy.world on 04 Dec 2023 14:26 collapse

I did try disabling secure boot and the errors are still there…just double checked it. My machine is new so I wouldn’t thing âge is the problem.

clb92@feddit.dk on 04 Dec 2023 16:10 collapse

Did you check that the date and time is set correctly in the BIOS?

Another_username@lemmy.world on 04 Dec 2023 16:16 collapse

I checked it with timedatect1, and that is correct

voidMainVoid@lemmy.world on 04 Dec 2023 14:30 next collapse

As a rule of thumb, if my computer is working without any problems, I’ll just ignore warnings and errors that show up during boot or shutdown.

atzanteol@sh.itjust.works on 04 Dec 2023 14:47 next collapse

Kernel boot logs aren’t well disciplined to be careful about what is an error or not. Sometimes it’s just checking for the existence of hardware and reports the error it gets if it doesn’t exist.

If things are working I wouldn’t worry.

Quereller@lemmy.one on 04 Dec 2023 15:50 next collapse

The amd_gpio line is a bug to ignore, the message has the wrong priority and should only be written to the log file.

Another_username@lemmy.world on 04 Dec 2023 15:55 collapse

ok thanks…I’ll stop trying to fix it :)

isVeryLoud@lemmy.ca on 04 Dec 2023 20:20 next collapse

Mmmm, confit errors 😋🍽️

MrAlternateTape@lemm.ee on 04 Dec 2023 21:15 next collapse

As far as I know, other distributions just don’t show these errors, but Ubuntu choose to show them.

Most of them are just due too a BIOS implementation that is not entirely up to standards, from what I understand. It seems some manufacturers have chosen to make their system easier to use with Windows instead of strictly enforcing standards.

I just ignore the errors. As long as everything works properly, I feel fine with that.

merthyr1831@lemmy.world on 12 Dec 2023 08:55 collapse

yup. and it’s usually on laptops that run less standard bios setups that aren’t easily flashed anyway

merthyr1831@lemmy.world on 12 Dec 2023 08:54 collapse

It’s a thing with certain laptops, where their secure boot certs are outdated or something. Not really anything you can do to fix, but it doesnt mean anything in practice - I never had issues with it after running linux across multiple distros about a year on my Acer nitro 5.

only thing you might have issues with is using secure boot in certain distros but if you don’t have problems then no need to worry

Another_username@lemmy.world on 12 Dec 2023 09:07 collapse

Thanks for your reply! That goes for both the errors?

merthyr1831@lemmy.world on 15 Dec 2023 08:26 collapse

the gpio one could also just be the BIOS being whacky. I think I have the same one show up on my Acer laptop and I’ve never had an issue.

Another_username@lemmy.world on 15 Dec 2023 09:06 collapse

The gpio one was fixed with the last update :)