As a side question, why does FF snap in Jammy have two icons? One seems to be for the actual snap package, the other for some deb remainder. To remove both you would have to apt remove FF && snap remove FF.
sounds like a bug ⊠the deb is needed for upgrading from former versions but it should really just install the snap, seems there is still a .desktop file in it âŠ
Thanks for feedback. Should I file a report? Even removing FF completely and reinstalling snap only still creates two entries.
yes, you should, but i dont exactly know if ubuntu-bug firefox
will work for this to file it against the deb on launchpad, @oSoMoN should be able to tell us
Good catch! This is indeed a bug, which I just fixed.
The desktop file in the deb is intended for compatibility with existing installations where it might be favourited in the dock. But it shouldnât be visible in the activities, indeed.
Wow that was quick. My OCD says thank you.
Any plans on fixing the issue where when Firefox crashes, the theme doesnât restore, unless the app is restarted manually?
Also experienced Firefox and Thunderbird snaps âfritzingâ when open for too long. Didnât think of recording the experience.
I wonder if this issue is related?; it was noted in Lubuntu, Ubuntu-MATE originally (itâs no longer impacted) & Ubuntu Desktop using the canary ISO. You may have fixed it at the same time?? or at least you maybe able to tell me the likely package the bug should be filed on.
This is being tracked in upstream bug #1740547.
Thatâs probably a slightly different issue, where indeed the deb and the snap (both providing the browser) where installed at the same time. With the deb now a transitional package that installs the snap, this shouldnât happen any longer.
My Firefox keeps asking to be default. I set the about :config
option widget.use-xdg-desktop-portal.file-picker
to default (2).
Also, I canât open magnet links to KTorrent or Zoom with Zoom links using Firefox snap.
Just upgraded from kubuntu 21.10 to 22.04, my firefox apt was forcefully converted into a snap. From what I measured on my machine:
Firefox100 (deb):
First launch time (after system reboot) - 2.7s
Second launch time (firefox launched and then closed) - 2.7s
Firefox100 (snap):
First launch time (after system reboot) - 15s
Second launch time (firefox launched and then closed) - 4s
Iâve been spending the last couple of hours trying to get a working .deb version of firefox, as I personally donât think trading performance for security and faster updates is a deal.
I have been doing some rudimentary test, maybe this help you:
I have noticed that after an updated of the firefox snap the first startup time gets worse for some reason there is a degradation in that, what a did is a complete remove of firefox snap remove --purge firefox
and reinstalled fresh with new profile and everything. That help me reduce form a 15sec first start to a 6sec and form 6sec second start to 2sec.
I have always used the snap version of firefox.
Youâre right, I had forgotten to follow up. Thanks for the reminder. This workaround has been removed in the beta branch.
If youâre using KDE, thatâs very probably bug #1970594.
Thanks.
Did a fresh snap install with a new profile and everything, but the snap launch times are still rather high (about 15s after a computer restart, otherwise 4s, tested 3 times and without any add-ons or firefox profile modifications)
However, it probably has something to do with the (first) error message I get when I launch the firefox(snap) from terminal after a computer restart: This error (something related to libreoffice, which is installed as a .deb anyways), does not appear when I launch firefox(snap) for the second time(launch time 5s), or if I launch firefox-esr (installed as .deb, launch time 2s) before launching firefox(snap).
If there is any place better to report this, please let me know.
Thank you
Thereâs a high variance in startup time according to my anecdotal experience. This would certainly benefit from some methodical profiling. Thereâs not much missing for it to be close to flawless.
Too bad didnât help you as per @ppd there is a high variance in startup times. In this link is the only tread in the snapcraft forums that try to talk and dig in this topic of slow startup times but, it did not take traction.
In this link are the results of my test using different laptops maybe this help to get attention to this. @ppd maybe there could be the place to gather son results using methodical profiling. I have see updates affecting the startup time, even if you use something like TLP or CPU Auto-freq affects the startup time of snaps and firefox snap.