I installed the phoenix-0.3 ebuild and it works fine but when I start mozilla i get a new phoenix window instead. I want to be able to use both.
The problem is with mozilla-xremote-client, which checks for existing mozilla instances before starting mozilla. See the folowing phoenix bug for more info: http://bugzilla.mozilla.org/show_bug.cgi?id=170609 A workaround is to run /usr/lib/mozilla/mozilla-bin directly, which will bypass the script at /usr/bin/mozilla which uses mozilla-xremote-client.
hi! there's no way at the moment to find out the name of the instance (mozilla or phoenix) this is the place where the args to mozilla-x-remote-client r parsed: http://lxr.mozilla.org/seamonkey/source/xpfe/components/xremote/src/XRemoteService.cpp#93 afaik there r 2 options: 1) remove the ping() stuff from /usr/bin/mozilla 2) patch mozilla-sources /me votes for 1 greetings, LordVan
So you are going to inconvenience the 95% mozilla users for sake of the 5% that also have phoenix installed ? You must remember .. if you take that ping stuff out, it will open new instances of mozilla for each time you 'click' on a link (or whatever)... I for one will vote against this. Anyhow, who use two browsers in normal circumstances ?
So you are going to inconvenience the 95% mozilla users for sake of the 5% that also have phoenix installed ? You must remember .. if you take that ping stuff out, it will open new instances of mozilla for each time you 'click' on a link (or whatever)... I for one will vote against this. Anyhow, who use two browsers in normal circumstances at the same time?
that's a good point.... what about an addtional check if a mozilla process is running? shouldn't be too difficult afaik... greetings, LordVan
Seems like it works with phoenix-0.4. I tested it a minute ago with: $ phoenix & $ mozilla I got a phoenix window and a mozilla window - that's how it should be, right? Plus it works the other way around, too. Is it okay to close this bug? -phoen][x-
No traffic, seems fixed.
*** Bug 20057 has been marked as a duplicate of this bug. ***
Seems this is an issue again. Could you try with mozilla-1.3 ?
tried with mozilla-1.3-r1 (20030427), as well as mozilla-1.2.1-r5, and phoenix-bin-0.5 : phoenix & mozilla i get two phoenix windows.
I've looked at this in detail. The problem is simply that xremote will communicate with any window on the display that provides the appropriate X properties. The properties are identical between firefox and mozilla. There are two possible ways to solve this problem: 1. Patch firefox, along with its version of xremote, to use firefox-specific properties instead of the generic mozilla variables. This may be the best long-term solution and would not be terribly difficult to do. 2. Use a hack in the launcher script to expose only the good windows to xremote's search. For right now I've implemented #2 in net-www/mozilla-launcher. It uses xprop and LOGNAME to fool xremote into contacted only the right windows. It's certainly a hack, but anything other than #1 will necessarily be a hack. If it doesn't work out, then we'll have to investigate #1 further. net-www/mozilla-launcher will first be used by net-www/mozilla-1.7_beta-r1 when I finish committing that.
Fixed in mozilla-1.7_beta-r1 and mozilla-firefox-0.8-r2, both ~arch masked at the moment. I will consider backporting to older ebuilds if these are not marked stable for 2004.1
thanks, the problem seems to be solved by these masked versions of firefox and mozilla.
