The cmd line switches -new-tab and -new-window don't work anymore if
the browser was initially started with the cmd line switch -no-remote.

Trying to open a new tab in a running browser then results in a
message box saying 'Iceweasel is already running, but is not
responding. To open a new window, you must first close the existing
iceweasel process, or restart your system'.

This behaviour was introduced some time ago and I think there was a
similar issue some time (years?) ago.

To reproduce

1. start a new browser process:

$ iceweasel -no-remote http://<insert your url here> &

2. try to open a new tab in the running browser:

$ iceweasel -new-tab http://<insert your url here> &

Dang.

Regards
hmw

I'm curious to know when it worked, because I don't remember it ever
working.

Mike

Hello,

Mike Hommey wrote:
[...]
we utilizing this feature (in conjunction with -P resp. -ProfileManager)
on desktop machines running stable. It works at least with iceweasel
3.5.16-11. I'm not sure, but I think a test machine upgraded to
testing early this year worked as expected. But again, I can't
remember exactly.

Regards
hmw

src:iceweasel has been superseded by src:firefox-esr in version
45.0esr-1 in March 2016. Transitional packages to ease upgrades were
provided in the wheezy, jessie, stretch and buster releases. The
transitional packages have been removed finally before the bullseye
release in August 2021.
After regular security support for buster ended in August 2022 and LTS
support ended in June 2024, I'm closing the remaining bug reports now.

Andreas