If SeaMonkey is not responding, make sure there
are no dialog boxes still open. Close each window on your desktop one at a
time and if you uncover a dialog window, dismiss it. If you have multiple
desktops, repeat these steps for each desktop.

This problem may affect Linux users downloading plugins. Follow these steps
to resolve the problem:

A significant number of SeaMonkey crashes are actually caused by
Java. Please make sure you are using the latest available version of Java.

The Linux binaries we distribute are now compiled with GCC 3.3 or GCC 3.4.
If you're using these binaries then you will need at least the 3.2 version of
the Java Plugin from
Sun J2SE v 1.4.2
(or the Blackdown JDK 1.4.1 compiled with GCC 3.2 or higher.) The Sun Java
Plugin is compatible with modern Linux versions like Red Hat 8 or later and
SuSE 8.1 or later (the plugin depends on a newer version of libgcc_s.so,
installing the GCC supplements for Red Hat 7.3 -GCC 3.1 Compiler Suite for
Red Hat Linux 7.3 - may allow for some older Red Hat Linux to run the plugin)
Users of older Linux versions should wait for a SeaMonkey version compiled
specifically for their Linux distro, or compile it themselves.
Other than potential plugin issues, however, SeaMonkey continues to support
very old distros.

Java J2SE releases previous to 1.3.0_01 will not work with SeaMonkey.
Problems have been reported with JRE 1.3.1 and 1.4.1. For best results JRE
1.4.2 or newer is recommended.

Running J2SE in 256 color mode may cause a flickering problem.

Sun's JRE will crash at startup if your useragent does not begin with
Mozilla/5. It might print Expected a version > 5! Version = 4
The workaround is to not forge a useragent whose version is less than 5 if you
have the Sun JRE plugin in your plugin directory. This preference would appear
in pref.js as something like: user_pref("general.useragent.override",
"Mozilla/4.0 (compatible; MSIE 5.0; Windows 98;)"); (Bug
83376)

On Linux, you must have your X server properly configured to enable
mousewheel scrolling. For XFree86, add a line to the Pointer section of your
XF86Config files such as "ZAxisMapping 4 5".
Also be sure that the Protocol line is set up correctly for your mouse.

On Windows, mousewheel scrolling does not work with all drivers. If you have
problems, try updating your driver or disabling any "helper"
programs that your mouse uses. If you have a Logitech mouse, you can either
upgrade the driver (to at least v9.60) or enable the "Microsoft Office
compatible scrolling" option in the Mouse/Buttons control panel.

SeaMonkey 1.1.4 is not compatible with older versions of Macromedia Flash for
Macintosh (anything before version 6.0 r67.) Macintosh users should upgrade to
the latest version of Flash to avoid the possibility of crashes at some Flash
sites. A free upgrade is available at the
Macromedia
Flash Player Download Center for OS X.

Many Flash on Linux problems can be fixed by upgrading to Flash 6.

On Linux, SeaMonkey crashes at pages with Flash animations if an
XIM server is used. See
International Issues as to how
to avoid the problem.

Do not share a profile between Netscape or Mozilla and SeaMonkey. Doing
this can lead to unpredictable results, some of which may include loss of
Search settings and preferences and unchecked growth of the Bookmarks file
(large enough to freeze your system). It is best to create a new profile for
each or manually copy (and change the name) an existing profile. (Bug
137164)

On Windows, some users might not be able to print on Windows 98 or Windows
ME with the default spool setting. The workaround is to go into printer
properties, choose details tab, choose spool settings, and then choose print
directly to printer. (Bug
130083)

On Linux, Full print preview functionality (toolbars, printing from print
preview, page setup, etc.) is only available with the non-standard Xprint
module. (Bug list)

In Profile Manager, if you rename a profile to a name you previously used,
all your preferences may be lost. Workaround: If you rename a profile, use a
unique name. (Bug
113203)

If problems occur during installation and your Communicator profile was not
copied and converted, you can still use your profile. Launch SeaMonkey from
the command line, adding the "-installer" option (that
is, type "seamonkey.exe -installer" on the command
line), or reinstall SeaMonkey to see the profile manager dialog again.

SeaMonkey only accepts hostnames for manual proxies. If you migrate a
Communicator 4 profile, you will need to change the settings manually.
Communicator 4 allowed URL's in manual configuration, but SeaMonkey does not.
If you migrate a profile configured this way, you will need to change the URL
to a hostname and port number. (Bug
30387)

Fedora Core 5 users using SELinux in enforcing mode will experience security
permissions problems when using the GTK1 build. Use the GTK2 build instead
(recommended), or see
this page
for more information.

No feedback is provided while restoring a certificate to a smart card, which
can take a long time since smart cards are relatively slow devices. As a
result, it may appear that the restoration is not happening. (Bug
52321)

For security reasons, SeaMonkey does not allow connections to certain ports.
To override this on a per-port basis, add a comma separated list of ports to
defaults/all.js (in your SeaMonkey installation directory). Note
that this pref only works in the all.js file in the SeaMonkey
installation directory and it affects all users of the installation. It does
not work if you add it to the prefs.js or user.js
files in your personal
profile directory.
For example, to unblock ports 1, 3, and 7, use the following line:
pref("network.security.ports.banned.override", "1,3,7");

For security reasons, SeaMonkey does not allow web content to link to local
files. An error like: Security Error: Content at url may not load or link to
file:///something will appear in the javascript console. If you need to follow
links to local paths it is recommended that you drag the link to the location
bar and then drop it on the webpage. If you really don't like the security
check and are willing to risk a site having access to all files on your system
and that your system can access then you may add the site's name to a policy
(say one called "policyname") as described in the
CAPS documentation
and set the "capability.policy.policyname.checkloaduri.enabled"
preference to "allAccess".

On Windows, some software firewalls may block SeaMonkey from properly
accessing the Internet. If SeaMonkey is not working properly, check that your
firewall settings allows SeaMonkey to connect to the net. If your receive a
warning from ZoneAlarm that SeaMonkey attempts to set itself up as a local
server, it is due to SeaMonkey communicating with Personal Security Manager
(PSM) which is required to access secure Web and mail servers, and you should
allow SeaMonkey access.

Using Windows 98 with some ATI graphics adapters will result in occasional
corruption of inline images as rendered on web pages. This is an ATI graphics
driver bug. (Bug
104992)

While enabling HTTP pipelining may significantly improve page load times, it
can prevent some websites from loading correctly. If you experience problems
loading a website, please verify that HTTP pipelining is disabled and try
again (see Preferences->Advanced->HTTP Networking). HTTP pipelining is
disabled by default.

The Forward, Reply, Reply All, and Reply to Folder buttons may not work. This
happens if you have some form of popup blocking enabled. A telltale sign of
this is a small explosion icon in the statusbar. An easy way to fix this is to
select Tools->Popup Manager->Allow Popups From This Site. (Bug
102476)

Attempting to compose, forward, or reply to a message may result in a
non-functional compose window. To work around it, open a new compose window,
close the new window, and then close non-functional one. If you try again, it
will work. (Bug
307672 )

Moving or copying a labeled message will not retain label in destination
when filing across accounts:

IMAP to any other account (including Local Folders): Message labels are
lost.

SeaMonkey does not integrate with AOL Mail and Netscape WebMail, as Netscape
6/7 do. If you share your Netscape 6/7 profile with SeaMonkey, you may be able
to see headers for messages in the account's Inbox if you have previously
checked one of these accounts in Netscape 6/7, but you will be unable to
interact with the messages. To access your AOL Mail, WebMail, or Netscape
Instant Messenger, you need to use Netscape 6/7.

Attaching RTF files to emails may result in them being sent such that most
readers will not be able to read them. If you plan to send RTF attachments,
you should go to Edit->Preferences->Navigator->Helper Applications,
select "New Type", and enter:

You must exit and restart SeaMonkey to see the effect of a change to the
option "show only subscribed IMAP mail folders". To access this
option: choose the Advanced button in the Server section of the Account
Settings dialog box. (Bug
38943)

The Subscribe dialog box may not work with news servers that require
authentication. If you open a password-protected newsgroup you may be prompted
more than once for the user name and password combination.

SeaMonkey may temporarily hang during LDAP autocomplete if network
connectivity is broken. Specifically, if the LDAP server in question is
unreachable (network connectivity problems, including taking a laptop outside
a firewall), the entire app will hang when attempting to contact that server.
The app will begin responding again after about 10 seconds (the length of the
TCP timeout). (Bug
79509)

Moving/Copying a downloaded message (while offline) will result in not being
able to read the message at the new folder while you are offline. Workaround:
Go online to read it, then re-download the message to have it accessible when
you are offline. (Bug
78809)

When starting SeaMonkey, if you only have one profile, both of the Offline
preferences for startup mode ("Ask me if I want online or offline
mode", or "Use my previous online/offline state") do not work.
SeaMonkey will always start in online mode. To go offline, from the File menu,
choose Work Offline. (Bug
82487)

When Publishing in Composer, if the Publishing URL, file name, username, or
password contain any special characters (such as "@") that need to
be escaped, then Composer creates a duplicate site entry each time you publish
the document. To work around this bug, choose the original site name from the
Site Name list in the Publish dialog box before publishing the document again.
For example, some ISP users have usernames that are also their email
addresses, e.g., "janedoe@ispname.net". After publishing to this
site, the next time you use the Publish dialog, the username from the document
URL will appear as "janedoe%40ispname.net" (the "@" was
escaped during publishing). Since Composer can't find this entry, it creates a
duplicate site name. (Bug
141819)

You may not be able to simultaneously edit a document using both Composer and
another editor. (Bug
27820)

Certain pages (such as ones that set frames) can't be edited. However, you
are still able to choose the Edit Page option in the File menu for such pages.
An editor window opens, but you are unable to edit the page.

Once you've floated all the views out of the main window, no drop targets
remain to bring them back. If you have "Save Default Layout On Exit" checked,
and you exit, you will appear to be stuck like this. (Bug
151785)

As a workaround, show the Interactive Session from the Show->View/Hide
menu, and type "/restore-layout factory".