Conversation

@buherator duuuuude, just enable session restore 😓

1
0
0
@freddy I don't think it will help as I browse in p0rn mode. Also, I tried to look up docs, but support.mozilla.org is down for me... Why isn't there a config switch to disable forced restart[1]? I'm a grown adult, I can decide when I want to restart my browser.

[1] https://www.reddit.com/r/firefox/comments/16ug51m/is_there_any_way_to_stop_firefox_from_forcing_a/
1
0
0

@buherator I think your configuration might be borked. We do not force a restart. You should only get this error if the binary file on disk changed while browsing. In that case, Firefox is unable to create a new process due to API incompatibility. Do you use multiple Firefoxes in parallel?

1
1
0
@freddy I simply use the Debian package (so I guess a lot of users have the same experience), and your explanation clears up why this is happening, thanks!

I guess the solution is to use a FF distribution that doesn't rely on the system updater then.
1
0
1

@buherator true, using a mozilla build with our updater will ensure this doesn’t happen unexpectedly.

0
0
1
wha- was there some workflow-breaking Firefox update I don't know about? 👀
1
0
0
@me no it just seems that since Linux package managers overwrite its binaries Firefox refuses to open new tabs until it is restarted which is quite frustrating when you are in the middle of something (esp. if you are also in private mode so your tabs/sessions can't be restored).

recommendation is to use Mozilla's distribution+update mechanism to keep the browser up-to-date.
0
0
0