Re: Query about Iceape, Iceweasel
On 10/09/2007 11:56 PM, Bret Busby wrote:
Who is responsible for Iceape and Iceweasel?
apt-cache show iceweasel | grep Maintainer
I am running Debian 4.0, which came with these two applications rather
than the Mozilla applications, and the two applications appear to be
quite buggy and unstable.
Iceweasel works for me.
To go to the Mozilla web site to try to install the equivalent
applications (I don't remember what they are named - I think that one is
seamonkey (?) ), they are not available as .deb packages for Debian, and
trying to install them otherwise, is too problematic.
It's not so bad. You untar a tarball, read a README and execute an
installer script.
Problems with
that, reported t5o Mozialla, have apparently been ignored - maybe
Moziila doesn't like Debian users and so ignores us, hoping we will just
disappear.
From where did you get this idea?
Both Iceape and Iceweasel, open up "untitled windows" when trying to
open web pages at all kinds of locations, and, trying to close one of
these "untitled windows" when it is initially displayed, crashes the
application, including all of the browser windows that it has open; a
procedure has to be used, of some time later, finding the duplicate copy
of the "untitled window" that the application has opened, and, closing
that, will cause the "untitled window" to close. So, when these
"untitled windows start opening, all that can be done, is minimising the
"untitled window" and its duplicate (they open in pairs), and, again
clicking on the link to get the destination that was sought when the
application decided to goawry.
I first suggest that you purge and reinstall Iceweasel.
If that doesn't solve the problem, come back in here with more specifics
of your hardware and software.
Also, the two applications appear to be designed to use up all of the
RAM, regardless of how much RAM is available and how many browser
windows and tabs ar open, leading to crashes in the application, the
windows manager, and, sometimes, the operating system.
Mozilla applications are legendary memory hogs, but I don't see this.
Firefox and Thunderbird typically use 150 to 300 MB of memory on my
system, but I have 512 MB of RAM, so the system rarely needs to use swap
even when both programs are used at the same time.
My experience has been that, when Firefox reaches 300 MB, it rarely goes
beyond that; however, that is with Flash and Java disabled.
If you do decide to have the courage to install Seamonkey on Etch, you
need to install libstdc++5 first.
Reply to: