35

I rebooted ubuntu 22.04 today and it could not find the root drive and I kept being dropped to a root shell. Correlation does not prove causality, but I find it very odd that nvme0n1p5 is mounted at both / (correct) and /var/snap/firefox/common/host-hunspell (incorrect). Not sure if this is a mount/fstab thing or a snap thing or what...

$ lsblk 
│                                     
├─nvme0n1p4 259:4    0     1G  0 part 
├─nvme0n1p5 259:5    0  29.3G  0 part /var/snap/firefox/common/host-hunspell
│                                     /
├─nvme0n1p6 259:6    0   8.2G  0 part [SWAP]

I changed fstab to use the PARTUUID instead of the UUID and it finally booted, but I would like to address this issue.

$ snap list
Name                            Version             Rev    Tracking         Publisher   Notes
bare                            1.0                 5      latest/stable    canonical✓  base
core20                          20220826            1623   latest/stable    canonical✓  base
firefox                         105.0-2             1860   latest/stable/…  mozilla✓    -
gnome-3-38-2004                 0+git.891e5bc       115    latest/stable/…  canonical✓  -
gtk-common-themes               0.1-81-g442e511     1535   latest/stable/…  canonical✓  -
hunspell-dictionaries-1-7-2004  1.7-20.04+pkg-6fd6  2      latest/stable    brlin       -
snap-store                      41.3-64-g512c0ff    599    latest/stable/…  canonical✓  -
snapd                           2.57.1              16778  latest/stable    canonical✓  snapd
snapd-desktop-integration       0.1                 14     latest/stable/…  canonical✓  -
5
  • 2
    In my Ubuntu Desktop 22.04.1 LTS lsblk sees the same extra mountpoint /var/snap/firefox/common/host-hunspell for the root partition. But the computer boots correctly using the UUID in fstab. I don't know what difference makes it boot correctly for me, but I have a SATA-SSD (not an nvme drive). My computer is a Dell Precision M4800. What's your computer (brand name and model)? I suspect that your boot problem was independent of the snap/firefox mountpoint, but I am not sure.
    – sudodus
    Commented Sep 24, 2022 at 2:57
  • I built it: Gigabyte MB/BIOS and an Intel i5-3570K. Never had windows on it (except as a VM). I bet if you uninstall the hunspell snap (and build it from source) and remove ff snap, you'll get rid of that. I think someone needs to submit a bug...
    – bvargo
    Commented Sep 24, 2022 at 3:49
  • Maybe this link can help you.
    – sudodus
    Commented Sep 24, 2022 at 5:10
  • I'm actually seeing it across 3 22.04 computers now that I've had a chance to look at it...On the computer I mentioned last night, I see the same behavior on sda6 so it isn't an nvme issue and it happened on 2 dell laptops so it's not a gigabyte issue.
    – bvargo
    Commented Sep 24, 2022 at 16:43
  • I see, thanks for these details. What is the problem with the 2 other computers: there is the extra .../snap/firefox/... mountpoint, but are there boot problems too?
    – sudodus
    Commented Sep 24, 2022 at 18:17

3 Answers 3

23

Below command removes the extra binding instantly:

snap disconnect firefox:host-hunspell

The dual binding is not harmful nor a bug, but looks un-linux to me.

3
  • 1
    Yeah, it looks quite sloppy. The computers are booting and I rarely use Firefox, but I needed to forward it via X over SSH and it failed. Log below...
    – bvargo
    Commented Jan 4, 2023 at 15:06
  • 1
    If it doesn't work, you can try umount /var/snap/firefox/common/host-hunspell. Found the solution here: https://forum.snapcraft.io/t/unlinkat-var-snap-firefox-common-host-hunspell-en-us-aff-read-only-file-system/34022/4. Commented Jun 19, 2023 at 19:12
  • you need to umout and THEN you use command above.
    – Marco
    Commented Nov 13, 2023 at 22:07
19

As indicated over at the snapcraft forum, this mount is set up to allow Firefox Snap to use the spell check dictionaries (hunspell) of the main system. A discussion about this commit is available here.

2
  • Thanks, I will look into this, how ever it seems that this snapd mount for FF components is more involved than just hunspell (gimp, libreoffice, xubuntu-docs, cups) and it seems like that is what is causing the X over SSH to fail (since they're mostly snapd mount points: pastebin.com/4cvPrVQe). I've never seen anything like this with X/SSH before and I do it quite a bit.
    – bvargo
    Commented Jan 4, 2023 at 15:09
  • If this answer resolved your current question, then please "accept" it by clicking the checkmark next to the question.
    – vanadium
    Commented Jan 5, 2023 at 11:30
1

I had a concern about the Firefox snap binding as it was showing up in the output of one of my aliases, for showing data usage and availability of mounted drives:

alias list-size='df -ahT --type=ext4 --type=vfat --type=ntfs --type=fuseblk --type=swap'

I have many LVM volumes, for which I create temporary snap partitions to preserve data integrity when I do a backup. I had found out the hard way that if the backup program inadvertently ends, one of these snap partitions could remain dangling, along with the associated snapshot functionalities. This can lead to the underlying LVM volume corrupting, and if it's part of my running system, can corrupt other volumes as well, leading to all of my Linux distros becoming nonoperational and a need to recreate LVM volumes and operating systems from backup. So I keep an eye out and am very wary of volumes suddenly appearing with "snap" in the name.

Well, I can accept your admonition that this extraneous Firefox binding is not a snapshot volume that I need to worry about. If I don't need to worry about it, I don't even need to know it's there, as with other volumes. I can take the "-a" option out of my alias and it still lists my mounted volumes, including my bindings, without showing the Firefox binding.

alias list-size='df -hT --type=ext4 --type=vfat --type=ntfs --type=fuseblk --type=swap'

I also have a function alias for lsblk which I call list-dev, which doesn't show the Firefox binding, so all is well again.

function list-dev () {
if [[ ${#} -eq 1 ]]; then
    lsblk -e7 -o NAME,FSTYPE,SIZE,LABEL,MOUNTPOINT,UUID "/dev/${1}"
else
    lsblk -e7 -o NAME,FSTYPE,SIZE,LABEL,MOUNTPOINT,UUID
fi
1
  • If you have a new question, please ask it by clicking the Ask Question button. Include a link to this question if it helps provide context. - From Review
    – David
    Commented Mar 21, 2023 at 13:35

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .