• bsergay
    link
    fedilink
    arrow-up
    1
    ·
    edit-2
    4 months ago

    lol, the full answer I had written somehow was ripped to pieces. I’ll therefore keep it brief.

    • Thank you for the reply!
    • Apologies for making you wait so long for an answer! Thank you for your patience!
    • Thank you for correcting me when I had wrongfully suggested that it’s found in about:support while it’s found (as seen below) in about:profiles instead. I know it’s found in Firefox, I (just) messed up the exact spot. Therefore, thank you for countering misinformation!

    • You’ve mentioned stuff that require to be addressed and corrected, but I’ll leave it at this. You should read documentation and don’t take people’s words anyways.
    • DarkThoughts@fedia.io
      link
      fedilink
      arrow-up
      1
      ·
      4 months ago

      Thank you for correcting me when I had wrongfully suggested that it’s found in about:support while it’s found (as seen below) in about:profiles instead. I know it’s found in Firefox, I (just) messed up the exact spot. Therefore, thank you for countering misinformation!

      It was not found in either page, as I already explained. Maybe they’ve fixed it by now but at the time of my comment the page led to the mentioned empty standard folder path you’d expect on a regular installation.

      • bsergay
        link
        fedilink
        arrow-up
        1
        ·
        4 months ago

        Maybe they’ve fixed it by now but at the time of my comment the page led to the mentioned empty standard folder path you’d expect on a regular installation.

        Alright, so through the flathub remote-info --log flathub org.mozilla.firefox command, we can view which commit was active at that moment.

        Command yields:

        Firefox - Fast, Private & Safe Web Browser
        
        ID: org.mozilla.firefox
        Ref: app/org.mozilla.firefox/x86_64/stable
        Arch: x86_64
        Branch: stable
        Version: 129.0
        License: MPL-2.0
        Collection: org.flathub.Stable
        Download: 98.6 MB
        Installed: 259.6 MB
        Runtime: org.freedesktop.Platform/x86_64/23.08
        Sdk: org.freedesktop.Sdk/x86_64/23.08
        
        Commit: 57fc35d29f0ee4915ebd903e2b9ce5497972c175cf0a6950153ec91d6f1b3e33
        Parent: 6a16f6a509340ad3bb833c9d9aa794ed78910aa43803a7420438b880aa0a6ce0
        Subject: Export org.mozilla.firefox
        Date: 2024-08-06 12:45:05 +0000
        History: 
        
        Commit: 6a16f6a509340ad3bb833c9d9aa794ed78910aa43803a7420438b880aa0a6ce0
        Subject: Export org.mozilla.firefox
        Date: 2024-07-26 13:29:41 +0000
        
        Commit: 5b92a5aa533a8f68fe1d73f3910392018c4d4bb9f4370ee0577384e101999ce8
        Subject: Export org.mozilla.firefox
        Date: 2024-07-23 14:34:25 +0000
        

        So, at the time of your comment, commit 6a16f6a509340ad3bb833c9d9aa794ed78910aa43803a7420438b880aa0a6ce0 was active and deployed on your system. Let’s find out what downgrading to this commit yields.

        Downgrading through sudo flatpak update --commit=6a16f6a509340ad3bb833c9d9aa794ed78910aa43803a7420438b880aa0a6ce0 org.mozilla.firefox, after which the about:profiles page is opened on this downgraded Firefox yields:

        The beautiful part is that, as Flatpak is containerized anyways, anyone can downgrade to the earlier commit and it yields the exact same result. So, please feel free to verify this for yourself.

        So, as a result, if the logic and the appliance is sound, then this showcases that your claim is either still true and portrays an anomaly -which I would deem as highly unlikely- or it’s simply false and you were just mistaken.

        Finally, if I’ve messed up at any of the steps, then please feel free to correct me.

        • DarkThoughts@fedia.io
          link
          fedilink
          arrow-up
          1
          ·
          4 months ago

          My guy, I don’t need to verify anything. I know what I saw. I literally clicked the open directory button too which just would lead me to the standard profile directory too. There’s 100% no mistaking it, as I have done this process countless of times over the past couple decades. Maybe it is the same weird way that the audio applet in the sys tray did not work at first and didn’t show any devices or apps, and how the audio system settings didn’t default properly for some games to the correct audio device - until they did some days later. If they had something like virtualbox in the repos I would’ve maybe installed the image I have on my usb stick again in a VM, but I’m not gonna through the process of wiping my installation again just to prove a point to some random rude asshole.

          • bsergay
            link
            fedilink
            arrow-up
            1
            ·
            4 months ago

            Aight, so you didn’t like my methodology. That’s fine; I’ve got no qualms with putting in the work. So, if you allow me, I would like to propose the following:

            • Option 1. Somehow grant me access to the exact image you used. This could be done in multiple ways:
              • Either, just send me the link from which you downloaded it yourself.
              • Or, send it over to me through whichever file sharing/hosting solution you enjoy.
            • Option 2. Getting VirtualBox to work on Bazzite is most likely a huge pain in the ass. Therefore, if it’s fine with you, I could help you install virt-manager (if you even need any help with that). Furthermore, FWIW, it’s worth noting that (GNOME) Boxes should work as well. It’s relatively simple, though. Thankfully, at least installing it is as easy as flatpak install org.gnome.Boxes*.