Bug#435052: iceape-browser: fails to launch from icedove if not already running

Mike Hommey mh at glandium.org
Sun Jul 29 06:20:59 UTC 2007


On Sun, Jul 29, 2007 at 01:07:21AM +0200, Alexander Sack <asac at debian.org> wrote:
> On Sun, Jul 29, 2007 at 12:50:26AM +0200, Tom wrote:
> > Package: iceape-browser
> > Version: 1.0.10~pre070720-0etch1
> > Severity: important
> > 
> > when launching iceape from icedove setting network.protocol-handler.app.http
> > to /usr/bin/iceape, iceape does not start. If iceape was already running,
> > the selected url is loaded as expected.
> > 
> > The reason seems to be that iceape inherits the environment from icedove, and
> > icedove sets MOZILLA_FIVE_HOME (in /usr/lib/icedove/run-mozilla.sh, called
> > from /usr/bin/icedove). Iceape does not set MOZILLA_FIVE_HOME to a proper
> > value and fails to start. If I unset MOZILLA_FIVE_HOME in /usr/bin/iceape,
> > then iceape starts up like expected. It seems that this is debian-specific,
> > as the original seamonkey launch-script does set MOZILLA_FIVE_HOME. In fact,
> > run-mozilla.sh is equal in seamonkey, firefox and thunderbird, and the original
> > way of setting MOZILLA_FIVE_HOME seem to be correct.
> > Is there a reason for handling this differently in iceape, icedove and iceweasel?
> 
> 
> Mike, do you use a custom script for iceape? or is mozilla.in used for
> that?

Same custom script as iceweasel. MOZILLA_FIVE_HOME has not been required
for a while. It would actually be better if icedove didn't set it.

Mike




More information about the pkg-mozilla-maintainers mailing list