SuperMaximus Posted March 18, 2023 Posted March 18, 2023 I try to install chromium and get this: root@tinkerboard:~# sudo apt install chromium-browser Reading package lists... Done Building dependency tree... Done Reading state information... Done The following NEW packages will be installed: chromium-browser 0 upgraded, 1 newly installed, 0 to remove and 1 not upgraded. Need to get 0 B/49.2 kB of archives. After this operation, 165 kB of additional disk space will be used. Preconfiguring packages ... (Reading database ... 41567 files and directories currently installed.) Preparing to unpack .../chromium-browser_1%3a85.0.4183.83-0ubuntu2.22.04.1_armhf.deb ... => Installing the chromium snap ==> Checking connectivity with the snap store ==> Installing the chromium snap error: system does not fully support snapd: cannot mount squashfs image using "squashfs": mount: /tmp/syscheck-mountpoint-3456514169: unknown filesystem type 'squashfs'. dpkg: error processing archive /var/cache/apt/archives/chromium-browser_1%3a85.0.4183.83-0ubuntu2.22.04.1_armhf.deb (--unpack): new chromium-browser package pre-installation script subprocess returned error exit status 1 Errors were encountered while processing: /var/cache/apt/archives/chromium-browser_1%3a85.0.4183.83-0ubuntu2.22.04.1_armhf.deb E: Sub-process /usr/bin/dpkg returned an error code (1) This only happens in Armbian 23, in Armbian 22 both Ubuntu/Debian images everything worked well. Any way to solve without rebuilding image? 0 Quote
Werner Posted March 18, 2023 Posted March 18, 2023 squashfs module is present in kernel config for rockchip. Make sure it is loaded (lsmod) 0 Quote
Werner Posted March 18, 2023 Posted March 18, 2023 Providing logs with armbianmonitor -u helps with troubleshooting and significantly raises chances that issue gets addressed. 0 Quote
SuperMaximus Posted March 18, 2023 Author Posted March 18, 2023 @Werner Yes, squashfs is listed in lsmod, but it does not seem to be mounted. 0 Quote
SuperMaximus Posted March 18, 2023 Author Posted March 18, 2023 I reinstalled snapd, rebooted and the problem vanished. Don't understand why it appeared though. 0 Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.