You are currently viewing a snapshot of www.mozilla.org taken on April 21, 2008. Most of this content is highly out of date (some pages haven't been updated since the project began in 1998) and exists for historical purposes only. If there are any pages on this archive site that you think should be added back to www.mozilla.org, please file a bug.
Use Bugzilla to report bugs. Avoid submitting a duplicate bug report by checking to see if your problem is already listed here or one of our most frequently reported bugs. The bug reporting guidelines explain how to write a useful bug report that results in your problem being fixed.
If Mozilla is locked up but doesn't seem to have crashed, 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:
The Linux binaries distributed by mozilla.org are now compiled with GCC 3.2. If you're using these binaries then you will need 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.) 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 either install the egcs 1.1.2 build of Mozilla and the JRE 1.4.1 or wait for a Mozilla version compiled specifically for their Linux distro.
Java J2SE releases previous to 1.3.0_01 will not work with Mozilla. Problems have been reported with JRE 1.3.1. For best results JRE 1.4.1 is recommended. Mozilla has been tested with all 1.3.0_* versions of the JRE, and JRE 1.3.1, and beta versions of JDK 1.4.
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:
"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.
On Windows, old drivers of Synaptics touchpad may not have scrolling enabled for Mozilla. You can get a new driver at http://www.synaptics.com/support/downloads.cfm .
On Macintosh, 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.
Plugins installed for Communicator 4.x may not be available for Mozilla. Workaround: install these plugins in the Mozilla Plugins folder.
On Windows the Adobe SVG plugin crashes. Workaround: Don't copy it (NPSVG3.dll NPSVG3.zip) into your plugins folder. If you want to view SVGs, there are Mozilla builds with native SVG support. (Bug 133567)
On Windows NT and 95 only, Microsoft Media Player file embedded in web pages may not work. (Bug 66015)
On Linux, there may be problems with ESD Audio and Flash. (Bug 85772)
Many Flash on Linux problems can be fixed by upgrading to Flash 6.
On Linux, Mozilla crashes at pages with Flash animations if an XIM server is used. See International Issues as to how to avoid the problem.
On Mac OS X, Microsoft Media Player files embedded in web pages will not work. (Bug 119045)
Do not share a profile between Netscape and Mozilla nightly builds. 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 Print Preview, plugins are not shown. (Bug 134002)
The default Unix/Linux binary comes with an alternate print module called Xprint which
features CUPS, LPRng,
MathML, TrueType fonts and
PostScript/PDF/PCL output support.
For more information see http://xprint.mozdev.org for a thorough and very detailed guide and Mozilla.org's Xprint project pages.
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 Mozilla
from the command line, adding the "
-installer" option (that is,
mozilla.exe -installer" on the command line), or reinstall
Mozilla to see the profile manager dialog again.
Mozilla 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 Mozilla 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)
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, Mozilla 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 Mozilla installation directory). Note that this pref
only works in the
all.js file in the Mozilla installation
directory and it affects all users of the installation. It does not work if
you add it to the
user.js files in your
personal profile directory. For example, to unblock
ports 1, 3, and 7, use the following line:
For security reasons, Mozilla does not allow web content to link to local
files. An error like:Security Error: Content at url may not load or
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 all files on your system and
that your system can access then you may add the following line to user.js in
your personal profile directory.
user_pref("security.checkloaduri", false); (Bug 84128)
On Windows, some software firewalls may block Mozilla from properly accessing the Internet. If Mozilla is not working properly, check that your firewall settings allows Mozilla to connect to the net. If your receive a warning from ZoneAlaram that Mozilla attempts to set itself up as a local server, it is due to Mozilla communicating with Personal Security Manager (PSM) which is required to access secure Web and mail servers, and you should allow Mozilla access.
If a username or password is embedded into a URI in the form of http://username:email@example.com. Mozilla will not warn the user of this when the user follows the link. URI's with long usernames in the form of http://firstname.lastname@example.org could deceive users into thinking they were going to mozilla.org when they were really going to fraudsite.com. (Bug 122445)
Pages that appear to be rendered incorrectly may be due to standards compliance issues. See the Netscape DevEdge and Mozilla Evangelism sites for more details.
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.
If the user is downloading a file in the background and the user exits from the File menu, the download will abort without warning. Workaround: Only exit after downloads finish. (Bug 28385)
On Macintosh, the horizontal scrollbar in the View Source window might be missing. Resize the window to see the scrollbar. (Bug 56488)
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)
Moving or copying a labeled message will not retain label in destination when filing across accounts:
In the Mail/News Account Settings: Server Settings dialog box, any changes you make to local directory settings won't take effect until you exit and restart Mozilla (Bug 2654)
On Linux you may encounter problems if you install Mozilla in a root user environment then run as another user. Problems include saving to Sent folder, Drafts, Templates or general authentication problems. (Bug 49397)
The Mail & Newsgroups Account Settings dialog box does not display correctly at lower monitor resolutions such as 800 by 600 or 640 by 480. If possible, increase your monitor's display resolution above 800 by 600. (Bug 82122)
Mozilla does not integrate with AOL Mail and Netscape WebMail, as Netscape 6/7 do. If you share your Netscape 6/7 profile with Mozilla, 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:
MIME Type: application/rtf Description: Rich Text Document Extension: rtfand then select OK to close the dialogs.
Mozilla does not import Communicator 4.x addressbooks. (Bug 35509)
To import Outlook address books, you must have the default mail client set to "Microsoft Outlook" in Microsoft Internet Explorer. (Bug 90206)
You must exit and restart Mozilla to see the effect of a change to the option: "show All IMAP mail folders" or "show only subscribed IMAP mail folders." To access this option: click 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.
LDAP directories with ldif extensions may appear after migration from Communicator 4.x. (Bug 94645)
Mozilla 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 browser. 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 Mozilla, 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. Mozilla 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., "email@example.com". 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.
Edit|PasteAs function is not functioning. (Bugs 73286, 41547)
You can not print HTML Source. (Bug 82239)
Some shortcut keys do not function properly. (Bug list
Hourglass does not show when application is busy. (Bug 83300)
Some element icons do not render in Show All Tags mode. (Bug 88036)
List editing can cause nested lists to outdent to next level list. (Bug 98547)
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".