(11-02-2022, 02:01 PM)trinidad link Wrote: Well the two upgrades I finished both required running updates twice. The first update attempt failed in both cases (one in qemu on Debian, one on a quad core CPU bare metal) but after waiting a few minutes both second attempts at updates were successful. The upgrade routine then ran smoothly and quickly for both. Curious about the cause, maybe linked to kernel fwupd? I did not reboot between the two attempts at updates and both machines had ample RAM and disk space. I was using the default US repo.
TC
It seems the error happened to many. It happened to me too, but I forgot if I rebooted. I guess that being in the CLI, I just reissued "sudo apt upgrade" and it worked.
The error came from "lite-patch" and I guess it was an internal dpkg - System signalling error.
Thinking and reading about "kernel fwupd", makes me belive that fwupd is vulnerable to CPU tick delays, which often occure when storage media is involved. I got this kind of errors when working on some programs written in RapidQ and Gambas.
The Repo:
I switched to a Romanian mirror, so it's debatable if there was a wget error.
Best regards!
"It's easy to die for an idea. It's way harder TO LIVE for your idea!"
Current Machine:
Dell Precision T1700, 16 GB RAM, SSD Kingston A400, 480 GB.
Laptop:
ASUS X200MA , Intel® Celeron® N2830, 2 GB RAM, SSD Kingston A400, 480 GB.
Current Machine:
Dell Precision T1700, 16 GB RAM, SSD Kingston A400, 480 GB.
Laptop:
ASUS X200MA , Intel® Celeron® N2830, 2 GB RAM, SSD Kingston A400, 480 GB.