On Tue, 4 May 2021 23:47:30 +0100
Steve McIntyre wrote:
>
> Wow, OK. That *is* surprising! Oh well, thanks for the information
> anyway. It seems that *something* has caused your system to install
> shim-signed, but I've no clue what! :-)
>
I have been trying to recapture my memory and I think
Hi Steve,
On Tue, 4 May 2021 20:26:33 +0100
Steve McIntyre wrote:
> I'll ask you the same question I asked Jörgen earlier - did you
> deliberately install shim-signed on a non-EFI system, or was it pulled
> in automatically somehow? I'm struggling to see a way to get here
> automatically.
>
I r
On Wed, May 05, 2021 at 12:53:53AM +0200, Michael Rasmussen wrote:
>On Tue, 4 May 2021 23:47:30 +0100
>Steve McIntyre wrote:
>
>>
>> Wow, OK. That *is* surprising! Oh well, thanks for the information
>> anyway. It seems that *something* has caused your system to install
>> shim-signed, but I've n
On Tue, May 04, 2021 at 10:00:05PM +0200, Michael Rasmussen wrote:
>Hi Steve,
>
>On Tue, 4 May 2021 20:26:33 +0100
>Steve McIntyre wrote:
>
>> I'll ask you the same question I asked Jörgen earlier - did you
>> deliberately install shim-signed on a non-EFI system, or was it pulled
>> in automatical
After the latest upgrade which failed you are not able to uninstall the
package either.
In my opinion this should race the severity to grave.
sudo dpkg -r --force-all shim-signed:amd64
(Reading database ... 613031 files and directories currently installed.)
Removing shim-signed:amd64 (1.34+15.4-2
Hi Michael,
On Tue, May 04, 2021 at 06:06:13PM +0200, Michael Rasmussen wrote:
>After the latest upgrade which failed you are not able to uninstall the
>package either.
>
>In my opinion this should race the severity to grave.
>
>sudo dpkg -r --force-all shim-signed:amd64
>(Reading database ... 613
6 matches
Mail list logo
