Mozilla Monitor Plus will automatically remove your info from Data Broker sites.
  • Mozilla has launched a paid subscription service called Mozilla Monitor Plus, which monitors and removes personal information from over 190 sites where brokers sell data.
  • The service is priced at $8.99 per month and is an extension of the free dark web monitoring service Mozilla Monitor (previously Firefox Monitor).
  • Basic Monitor members receive a free scan and one-time removal sweep, while Plus members get continual monthly data broker scans and removal attempts.

Archive link: https://archive.ph/YdY3R

  • agent_flounder@lemmy.worldEnglish
    7·
    9 months ago

    super cool not disgusting abomination of a bug that’s not a bug. Remap my fucking root directory?

    I am not convinced that’s what’s going on. It looks more like some weird thing snap does to make hunspell available to snap Firefox.

    Have you seen this behavior on your own Ubuntu install? In other words, can you reproduce the described scenario?

    • foggy@lemmy.worldEnglish
      110·
      9 months ago

      Yes. I literally have a cron job to unmount and rename my root directory to / that runs every 12 hours.

      • Derp@lemmy.mlEnglish
        41·
        9 months ago

        And how does that work? How do you unmount the root directory of a live system and invoke a script?

        • foggy@lemmy.worldEnglish
          24·
          9 months ago
          
sudo umount /var/snap/Firefox/common/host-hunspell 2>/dev/null

Sudo snap disconnect Firefox:host-hunspell 2>/dev/null

          Like that?

          It’s not unmounting my root directory it’s unmounting what Firefox mounted on my root directory.

          • murderisbad@lemm.eeEnglish
            31·
            9 months ago

            You are misinterpreting the information here. Neither Firefox nor Ubuntu are doing anything to your root directory. The behavior described and what you are undoing is that your storage device is being made available at two locations: both at / and at the hunspell path.

            • foggy@lemmy.worldEnglish
              13·
              9 months ago

              lsblk outputs that my NVMe0n1p1 is mounted at /var/snap/Firefox/common/host-hunspell.

              This drive and partition is where my root is.

              • patatahooligan@lemmy.worldEnglish
                4·
                9 months ago

                lsblk is just lacking a lot of information and creating a false impression of what is happening. I did a bind mount to try it out.

                sudo mount -o ro --bind /var/log /mnt

                This mounts /var/log to /mnt without making any other changes. My root partition is still mounted at / and fully functional. However, all that lsblk shows under MOUNTPOINTS is /mnt. There is no indication that it’s just /var/log that is mounted and not the entire root partition. There is also no mention at all of /. findmnt shows this correctly. Omitting all irrelevant info, I get:

                TARGET                                                SOURCE                 [...]
/                                                     /dev/dm-0              [...]
[...]
└─/mnt                                                /dev/dm-0[/var/log]    [...]

                Here you can see that the same device is used for both mountpoints and that it’s just /var/log that is mounted at /mnt.

                Snap is probably doing something similar. It is mounting a specific directory into the directory of the firefox snap. It is not using your entire root partition and it’s not doing something that would break the / mountpoint. This by itself should cause no issues at all. You can see in the issue you linked as well that the fix to their boot issue was something completely irrelevant.

      • agent_flounder@lemmy.worldEnglish
        31·
        9 months ago

        That makes no sense. The bug listed shows the same device mounted to / and that spelling for in /var or whatever. And your system wouldn’t operate if / didn’t exist. I’m almost curious enough to go set up a VM to try to see what’s happening.

        • foggy@lemmy.worldEnglish
          32·
          9 months ago

          My working solution is literally running a Cron .sh which is

          sudo umount /var/snap/Firefox/common/host-hunspell 2>/dev/null

Sudo snap disconnect Firefox:host-hunspell 2>/dev/null

          If Firefox updates via snap, it will change back to bullshit. Is the case in every 22.04 VM I have on my machine as well. This script effectively gives me “/” back, and unfucks the rest of my machine.

          It is a reason for me looking to leave Ubuntu after 12 years dedicated. Just because it makes no sense doesn’t mean it isn’t happening.