Terminal syntax for Firefox fails after update [Solved]

[Jakob77]

The errors only appear after an update.

If it only happens after an update you could change your script into a two steps (commands) to test.

Have your script open one window and then a short sleep before the command to open the other two windows.

Thank you.
I don't like it but I guess you are on the right track.
It seems the Firefox syntax is not reliable and it is better to let Linux handle it.
One of the computers was suddenly hit conical by the problem and that gave me a chance to do some testing.
This syntax for Terminal seems to be more reliable:

Code: Select all

firefox 'https://mxlinux.org/' & firefox 'https://mxlinux.org/wiki/system/iso-download-mirrors/#checksumsignatures' & firefox 'https://endoflife.date/mxlinux'

EDIT:

I go with this one and see what happens:

Code: Select all

firefox --new-window 'https://mxlinux.org/' & firefox --new-window 'https://mxlinux.org/wiki/system/iso-download-mirrors/#checksumsignatures' & firefox --new-window 'https://endoflife.date/mxlinux'

[Jakob77]

There has been one more happening that I can't explain.
As towwire suggested I therefore now also add some sec. sleep before opening the last two windows:

Code: Select all

(sleep 3s && firefox --new-window 'https://mxlinux.org/') & (sleep 2,5s && firefox --new-window 'https://mxlinux.org/wiki/system/iso-download-mirrors/#checksumsignatures') & (sleep 0s && firefox --new-window 'https://endoflife.date/mxlinux')

I will go with that and see what changes but I don't like to name it a solution.
I think it still ought to be completely straight forward to make a reliable syntax for opening some new windows in Firefox.

[j2mcgreg]

@Jakob77 wrote:

I think it still ought to be completely straight forward to make a reliable syntax for opening some new windows in Firefox.

It's a trap we all fall into when we assume that human logic = Linux logic.

[DukeComposed]

I think it still ought to be completely straight forward to make a reliable syntax for opening some new windows in Firefox.

This is what home page settings do. One sets the home page in Settings and then, when starting Firefox, one can immediately go to that page on startup. There's even a neat feature that lets you specify multiple URLs as multiple home pages by using "|" to combine them in a single string.

[Jakob77]

Thank you but if I use this Terminal command:

Code: Select all

firefox --help

Then I can still read this line:

--new-window <url> Open <url> in a new window.

Adding more options has never been a problem before, and this syntax for Terminal has worked perfectly for many years:

Code: Select all

firefox --new-window 'https://mxlinux.org/' --new-window 'https://mxlinux.org/wiki/system/iso-download-mirrors/#checksumsignatures' --new-window 'https://endoflife.date/mxlinux'

There has to be something wrong..?

Has anybody replicated the phenomenon.?

[CharlesV]

that line works perfectly here.

[Eadwine Rose]

Same here.. works fine.

[Jakob77]

Did you try to use it for opening Firefox the first time after updates.?

My happy life with Firefox based on limited expectations is being put on a test.
Except for the security settings I aim not to save and keep any important data inside Firefox.
After a fresh install I restore nothing to Firefox. The little configuration needed is done manually and hopefully I can avoid add-ons.
Not even my favorites are saved in Firefox. I have them in icons and scripts, and I backup the panel safely with the MX-Tool for it.
As long as the Firefox Terminal syntax works with my icons it just takes me where I want to go.
And with those limitations used for years Firefox has been a fantastic browser that can 'drill' almost any page. :-)

However, now when the Terminal syntax is not reliable anymore the happy days are over. Opening more than one window was taking it too far.
If you use a configuration that is only used by a limited group of people there will always be a risk that some update will overlook it and eliminate the option later on. And nobody else can see or understand it is a problem so it will likely not be fixed for a very long time.
I recon it can never be completely avoided but I think it is sad when it happens, and with the Terminal syntax we are in my opinion on ground that ought to be completely solid and stable after any update.

[Eadwine Rose]

Firefox has been updated for me on the 3rd of April, so yes.

[Jakob77]

If you want to replicate the error you may have to run the Terminal command as the very first thing after updating.
I am not sure it is every time or if the update has to include Firefox software to make it happen.
Slower pages might make it more significant.