I'm using Ubuntu 22.04, to avoid these issues I removed the snapped firefox and installed the apt-get version recommended in other sites.
It was happily running without problems until yesterday it was upgraded to 116.0.1 and firefox stopped working.
So, I decided today to move back to the default snap firefox, and here we are again, suffering with this problem.
I know is not a problem from firefox per-se, this is a problem of snap whose security model thinks that accessing /tmp folder is dangerous and didn't provide any workaround way to make it configurable :-(
And because of my last experience it seems that firefox is moving more and more to the snap version than to support the non-snap, which I find really really bad.
Question for others, is there a bug filed on snap about this flawed design about /tmp folder? I would like to add my voice there too.
Well, I'm frustrated today because of 116.0.1.
I'm using Ubuntu 22.04, to avoid these issues I removed the snapped firefox and installed the apt-get version recommended in other sites.
It was happily running without problems until yesterday it was upgraded to 116.0.1 and firefox stopped working.
So, I decided today to move back to the default snap firefox, and here we are again, suffering with this problem.
I know is not a problem from firefox per-se, this is a problem of snap whose security model thinks that accessing /tmp folder is dangerous and didn't provide any workaround way to make it configurable :-(
And because of my last experience it seems that firefox is moving more and more to the snap version than to support the non-snap, which I find really really bad.
Question for others, is there a bug filed on snap about this flawed design about /tmp folder? I would like to add my voice there too.