Bug#973715: fwupd-amd64-signed holding off fwupd update results in segfaulting binary
> -----Original Message-----
> From: Matteo Settenvini <msettenvini@gmail.com> On Behalf Of Matteo Settenvini
> Sent: Saturday, November 14, 2020 7:35
> To: 973715@bugs.debian.org
> Subject: Bug#973715: fwupd-amd64-signed holding off fwupd update results in
> segfaulting binary
>
> The problem suddenly become worse.
>
> Now that fwupd 1.5.1 has landed in sid, and some dependencies
> apparently changed, the fwupd-amd64-signed package holding off fwupd
> upgrade and forcing it to stay at version 1.4.6-2, is breaking the
> system:
>
> nov 14 14:29:52 rosebud kernel: fwupd[11192]: segfault at 8 ip
> 000056035dbcc548 sp 00007ffddfa64b00 error 4 in
> fwupd[56035dbaf000+20000]
> nov 14 14:29:52 rosebud kernel: Code: c7 44 24 08 00 00 00 00 66 2e 0f
> 1f 84 00 00 00 00 00 48 8b 11 8b 44 24 10 be 01 00 00 00 4c 8b 34 c2>
> nov 14 14:29:52 rosebud systemd[1]: fwupd.service: Main process exited,
> code=killed, status=11/SEGV
>
> This goes away after uninstalling the fwupd-amd64-signed package and
> installing fwupd 1.5.1, but of course on a system with SecureBoot
> enabled, this is not helping much if you have pending BIOS updates.
>
> Cheers,
> Matteo
1.5.1-1 won't migrate to testing as other issues came up with non-x86
architectures. I've uploaded a 1.5.1-2 this morning that should hopefully
sort those out.
As @Steve McIntyre mentions, it's a manual process to kick off the re-signing.
It needs to be done when 1.5.1-2 is ready to migrate. If there is another
problem that comes up (say autopkgtest fails, or some other arch still fails)
then we'll probably need to do a 1.5.1-3 and then kick it off.
Reply to: