--new-window, --new-instance, --new-tab don't work
Categories
(Core :: Widget: Gtk, defect, P3)
Tracking
()
People
(Reporter: bill, Unassigned)
References
(Blocks 1 open bug)
Details
User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/104.0.0.0 Safari/537.36
Steps to reproduce:
A cronjob kicks off a script that contains a firefox call. This worked just fine prior to the snap version on Ububtu 22.04.1LTS
DISPLAY=${display} firefox --new-window ${HOME}/MESSAGE.html
Now, the first instance works and all subsequent instances fail when the first is still up. Failure says:
Firefox is already running, but is not responding. To use Firefox, you must first close the existing Firefox process, restart your device, or use a different profile.
Tried changing from --new-window to --new-instance, --new-tab, --private-window and they all error out.
Mozilla/5.0 (X11; Linux x86_64; rv:103.0) Gecko/20100101 Firefox/103.0
Actual results:
First instance works as expected and all other instances error out.
Expected results:
Several Firefox instances should pop up.
Comment 1•3 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::Widget: Gtk' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
Comment 2•2 years ago
|
||
What about DISPLAY=... snap run firefox --new-window [...]
? Though you might then hit bug 1800350
Comment 3•2 years ago
|
||
Redirect a needinfo that is pending on an inactive user to the triage owner.
:stransky, since the bug has recent activity, could you have a look please?
For more information, please visit BugBot documentation.
Updated•2 years ago
|
Comment 4•7 months ago
|
||
This is working, the original report was mentionning opening a file from CLI which is bug 1800350
Description
•