Known issues with Firefox Snap?

So you’re saying you got an update for gtk-common-themes, and the theming for Firefox regressed? Or did it regress when you upgraded to 22.04 ?

1 Like

I got an update for gtk-common-themes and that when the regression happened. Even the Snap Store (Ubuntu Software) looks bad.

I haven’t touched anything regarding that. I will make sure I am not on the beta/candidate channel. This system is the family PC w/o any tinkering.
Edit: I am on the stable channel


Hello…this is new. Does this mean that Firefox snap will no longer crash when updated?

2 Likes

Should I do a new post on Snapcraft Forum regarding this? As this also extends of Chromium. I am assuming any GTK3 application.

@oSoMoN The stable channel of gtk-common-themes has been consistently out of date, at least since the last release.

I had forgot I did this, but I’ve been using the candidate or beta channel (they’ve had the same version) since Impish came out. I did this because that was when the mixed Yaru theme went away and Yaru-light was renamed Yaru, so without the updated gtk-common-themes, Chromium didn’t find the right theme when I set my system to 'Yaru'.

Since stable gtk-common-themes is still from Sep 2021, I don’t think it could include any of the new Yaru color themes from Jammy unless I don’t understand something. I’m surprised no one else noticed this actually! I only missed it because I was already on the beta channel.

2 Likes

That’s amazing, I change gtk to the candidate channel and now the color themes match.

Also where is firefox 100. I thought the point of snaps were faster updates from mozilla.

I made a post on the Snapcraft forum:

1 Like

In the candidate channel, the Mozilla release team will decide when to promote it to stable.

2 Likes

Another thing I just noticed.

The spellchecker only works in English. I installed the firefox add-on for my language (Spanish), but it doesn’t appear as a language option in the spellcheck. I never had this problem on the .deb.

Is this a known limitation?

3 Likes

How did you install it? If you right click on a textentry -> lang -> add dictionnary and you install the one for the language you want it should be listed

1 Like

That’s how I did it and the new language doesn’t appear on the menu.

1 Like

Reporting back … Jammy should be using the stable/ubuntu-22.04 channel, which is up-to-date. So if you’re like me and ever switched channels, run

snap refresh gtk-common-themes --channel=stable/ubuntu-22.04
4 Likes

Good to know. Although for the record I ran the upgrade and didn’t get put on that specific channel.

@elcste, thank you for pointing this out!
I didn’t notice that, but indeed gtk-common-themes turns to be on latest/stable/ubuntu-19.04 channel after upgrade to 22.04.

$ snap info gtk-common-themes
name: gtk-common-themes
summary: All the (common) themes
publisher: Canonical✓

tracking: latest/stable/ubuntu-19.04
refresh-date: 2021-09-23

it seems we need to figure out how to handle channel transitions on upgrade indeed, could someone report it on https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+filebug ?

1 Like
2 Likes

Sort bookmarks sorts a different folder
https://bugzilla.mozilla.org/show_bug.cgi?id=1768212

Hi! I was doing some tests since I noticed from the update to Firefox 100 the snap started to take longer to start, its look from my laptop that with each update, there is a hit in startup times both cold start and subsequent starts.

My laptop is a Thinkpad t14s with AMD Reinor and a SSD nvme.

When I was on Ubuntu Impish a run some manual test using my phone chronometer (I know is not the best way to test this, but using --trace-exec add a lot of overhead and the time reading wasn’t like in real life lots of amd gpu errors)

In impish I got:

  • Cold start: 15sec aprox (5 observations)
  • Hot start: 6sec aprox (5 observations)

When I did a fresh and clean install of Ubuntu Jammy I did the same test with my phone because a did notice a improvement in the startup time of Firefox.

In jammy a got:

  • Cold start 22.04 = 6sec aprox (5 observations)
  • Hot start 22.04 = 2sec aprox (5 observations)

I really like this improvement since reduce to half the cold start (I hope it improves even more :slight_smile: ) and 2 sec hot start feels almost instant.

But with the recent updated to Firefox 100 I noticed a regression with this times, I know that the very first time you run Firefox after an updated its need to copy some config files that take time. But I’m talking after this first import start (that took like 20sec) I did the same test with my phone:

In jammy after Firefox 100 update i got:

  • Very first start after update (import start): 20sec aprox (1 observation)
  • Cold start: 8 sec (5 observations)
  • hot start: 3sec (5 observations)

So it did get noticeably worse :frowning: then I did a snap remove firefox --purge and did a fresh install of Firefox 100 and I got back the better startups times.

In jammy Fresh install Firefox 100:

  • Cold start: 6sec (5 observations)
  • Hot start: 2sec (5 observations)

Maybe this will help attract awareness on way so many users report inconsistent startups times, I hope this help in improve this important snap.

Thanks for all the work, love this snap <3

4 Likes

In a persistent live system of 22.04 LTS Ubuntu Desktop or Ubuntu community flavour, Firefox works during the first boot, but not after reboot or shutdown+cold boot.

There is a workaround in mkusb, but I think the problem should be solved in Ubuntu.