I have "Open links from other apps in": "a new tab in the most recent window", which works correctly with the original firefox script, but mozilla-launcher always forces new window. Also, please DO make mozilla-launcher a USE option for mozilla-* builds! (I know there is a separate bug entry for this, but it's been ignored for months). There is absolutely no reason mozilla-launcher is a must. I like Gentoo for the freedom it gives for usage profiles, and this is one of very few places when I'm FORCED to tweak it beyond the native gentoo tools' capabilities. Reproducible: Always Steps to Reproduce:
We introduced mozilla-launcher because the mozilla.org launch script had a number of shortcomings. The first and foremost was that the user could not launch Mozilla / Firefox / Thunderbird twice (or spawn a new window/tab/whatever) with it. If this has changed we really don't have a reason to use mozilla-launcher at all anymore. Please advise on whether you're able to do the following with the mozilla.org launch script: gentoo$ firefox [ ... ] <-- firefox launches gentoo$ firefox If it spawns the profile manager the issue still exists. If it opens a new window/tab in the original firefox process, it's been resolved.
With firefox, yes, this has been fixed some time ago (can't say for sure exactly when, though). firefox-1.0 is certainly ok. As to thunderbird, I don't really understand why two instances of mailer should be run in parallel... BTW, when unmerging mozilla-launcher, it doesn't restore links to original scripts.
please do block mozilla-launcher with firefox >= 1.0! I was searching for this *bug* now for over two hours until I found this thread. firefox gets started a second time without opening the profile manager. btw if you unmerge mozilla-launcher you have to do: ln -sf /usr/lib/MozillaFirefox/firefox /usr/bin/firefox
mozilla-launcher fixes a number of other issues present in the default mozilla.org scripts. I'm not going to add a USE var for this because it would mean supporting the mozilla.org scripts, so then I'd have to patch them, and eventually they would become mozilla-launcher. This problem is fixed in mozilla-launcher-1.28. If you don't have MOZILLA_NEWTYPE set in your environment, then the new default is to let the program preferences take effect.
