#986456 chromium: Could not unzip extension on armhf

Package:
chromium
Source:
chromium
Description:
web browser
Submitter:
Daniel Thompson
Date:
2021-05-08 18:27:07 UTC
Severity:
minor
#986456#5
Date:
2021-04-06 12:29:52 UTC
From:
To:
Dear Maintainer,

I am unable to install extensions using the latest chromium package for
armhf. Normally this affects me because I run chromium/armhf on a
multilib system that is predominantly arm64. However I have confirmed
that the problem also exists on a "pure" armhf userspace (although still
with an arm64 kernel) and a fully clean install.

To reproduce from a clean install (e.g. brand new home directory, no
old config files or extensions):

1. Install chromium
2. Navigate to https://chrome.google.com/webstore
3. Try to install an extension (I tested primarily with bitwarden
   but I also checked a couple of "random" ones from the suggestions
   list (Zoom, Dark Mode, Visor and saw the same results).
4. Chromium reports "An error has occured: Could not unzip extension".

This doesn't appear to be related to the recent changes to Google
Sync: I am still able to install bitwarden successfully on chromium/arm64.

In fact chromium/arm64 does offer a workaround (of sorts). On arm64 hardware.
I can install the extensions I require and then `apt install chromium:armhf`
to switch back to 32-bit chromium and the extensions continune to function!

Note that the report below is from the system I used to test with a "pure"
armhf userspace and resulted in my running with a custom kernel. On other
systems I have observed the same problem with a Debian kernel kernel
(5.10.0-5-arm64).

#986456#10
Date:
2021-05-08 18:22:10 UTC
From:
To:
control: severity -1 minor
control: forwarded -1 http://crbug.com/1060925

Daniel Thompson wrote:

Could you try a version of chromium before 67?  This may be a known
upstream bug [0].

Best wishes,
Mike

[0] http://crbug.com/1060925

#986456#17
Date:
2021-05-08 18:22:10 UTC
From:
To:
control: severity -1 minor
control: forwarded -1 http://crbug.com/1060925

Daniel Thompson wrote:

Could you try a version of chromium before 67?  This may be a known
upstream bug [0].

Best wishes,
Mike

[0] http://crbug.com/1060925