Welcome

Release Notes

What's New?

Community & Sun

Linux & Solaris

Known Issues

Troubleshooting

Solutions

Admin's guide

Printing

X-printing

Non Western Fonts

Debugging

Core/Truss Files

Debug Mode

Profile Roaming

Intro

HTTP

LDAP

Preferences

Advanced

Misc

Plugins

About: command

Intentionally left blank

 

.

What's new? (What's different from last version and why you should upgrade.)
What is different from the community version of Mozilla?
What's the difference between the Solaris and Linux versions?

Troubleshooting Guide

Feedback

Support

Mozilla software for Solaris OS
Mozilla software for Sun Java Desktop System (with Linux OS)
General

 

 

Copyright 2004 Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, California 95054 U.S.A. All rights reserved. Sun, Sun Microsystems, Java, SunOS, OpenWindows, and Solaris are trademarks, registered trademarks, or service marks of Sun Microsystems, Inc. in the U.S.A. and other countries. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. in the U.S.A. and other countries. Products bearing SPARC trademarks are based upon an architecture developed by Sun Microsystems, Inc.

What's New?

---

As always the Sun Mozilla team strives to bring you new releases with improvements to performance, stability, web site compatibility, standards support, and usability.

Non-standard Website Manager

Some webpages do not comply with the W3C standard. These webpages may or may not display correctly. Sun's Mozilla has introduced the ability to safely deal with many of the non-standard web-elements.

Accessibility

Mozilla has been designed for productive use by users with disabilities. It is completely keyboard navigable and supports assistive technologies that use the GNOME accessibility architecture, in particular the Gnopernicus screen reader and magnifier and the GNOME On-screen keyboard.

Security

Cross-platform authentication support using Kerberos (GSSAPI) and NTLM

Printing

Printing of the list of attachments in an e-mail message is now supported.

Roaming

Performance

Size and performance have improved dramatically.

Mail

One of the most requested Mozilla Mail features, an option to separate the Recipient and Sender columns in the thread pane, has been implemented

Java Desktop System Configuration Manager

Mozilla can be configured using the facilities of the Java Desktop System Configuration Manager. This tool allows for convenient configuration of Mozilla for groups of users from a central location.

Java

Easily switch between multiple JRE versions

Liveconnect

Improved support and reliability for liveconnect across domains.

Samba

Support for smb:// URLs using the gnome-vfs library (Linux only)

Want More?

For more details please visit http://wwws.sun.com/software/solaris/browser/ or http://www.mozilla.org/

---

What is the difference between the Sun release of Mozilla and the community release?

---

System Integration

Unified UI Seamless integration

Plugins - provided by default
File associations - Mozilla can directly call other programs to open various files received in email or while browsing
Menu bar - Mozilla can be launched directly from the Menu bar

Roaming

Compatibility - Compatible with Java Enterprise and standard FTP servers , supports HTTP, LDAP and FTP protocols
High availability- Access your bookmarks, preference, address book anywhere, anytime
Reliable - made some changes? Conflict resolution to avoid problems with multiple access

Non-Standard Web Site Manager

Smoother Surfing

Site Manager: Sun has added this new feature to make surfing non-standards compliant webpages easier to view. End users will be able to enable/disable these extensions on a per site basis.

Java Desktop System Configuration Manager

Smooth and secure user managment

Ease of use: Allows a system administrator to configure Mozilla and establish default preferences for an enterprise from a central location.
Consistent Configuration: The Configuration Manager allows consistent application of preferences to groups of users based on enterprise policy.

Accessibility

Visual - Supports large fonts and high contrast themes compatible with Gnome
Keyboard navigation - all Mozilla browser functions can be accessed through keyboard alone (mouse not required)
Assistive Technologies - Supports the gnome accessibility framework in order to work with assistive technologies (screen reader, screen magnifier, onscreen keyboard) that will appear in future versions of the Gnome desktop.

Printing

True Type printing - Sun Mozilla generates a postscript file which does not require extra configuration to print non-western languages

Bug FIXES!

Sun's Mozilla - Contains hundreds of bug fixes not found in the community version

---

What's the difference between the Linux and Solaris versions of Mozilla?

---

Feature	Solaris	Linux
Single Sign-On Kerberos Authentication Integrates the browser into the platform.( GSS-API authentication ) Cross-platform authentication support NTLM Interoperates with Active Directory.	YES	NO
Samba Map directly to Samba drives using: smb:// URLs	NO	YES
X-print Print using Xprt	YES	NO

---

Known Issues

---

Flash Player 6

When color depth is set to 256 colors (8 bit), text display will fail for flash 6.
If color depth is set to 16 bit or higher, this problem will not occur.
We recommend you use Flash Player 7 instead.

CDE

When color depth is set to 256 colors (8 bit), UI will not display correctly.
If color depth is set to 24 bit or higher, this problem will not occur.

Profile

If your profile is corrupted, it can cause unexpected errors in Mozilla.
If this happens, create a new profile

International Domain Names & Bookmarks

Bookmarks may not display correctly when using IDN and you may not be able to access the URL through the bookmark
This can be resolved by manually editing the bookmark

Hindi

In all dialog boxes, numerical information does not appear in Hindi

L10N

When you open the local file with multibyte characters,
mozilla shows it in location field as %xx-escaped format according to the W3C standards.

---

Solutions

---

---

X-printing (Solaris only)

---

How to set up x-printing for Mozilla.

Xprt is the Xprint print server for version 11 of the X Window system for non display devices such as printers and fax machines.

Xprint is an advanced printing system which enables X11 applications to use devices like printers, FAX or create documents in formats like PostScript, PCL or PDF. It may be used by clients such as mozilla .

How do I configure Xprint on the client side?

There is an environment variable (env vars) which controls Xprint on the client side.
The environment variable ${XPSERVERLIST} contains a list of display identifiers
(separated by white space) to tell Mozilla where it can find the X-print servers.

Example:
%export XPSERVERLIST="littlecat:80 bigdog:72"
This instructs an application to look at display 80 on the machine"littlecat" and display 72 on the machine bigdog, to look for X-print servers.

How do I setup an Xprint Server?

On Solaris Xprint Server is installed by default.

Xprt [ -ac ] [ -audit level ] [ -pn ] [ -fp fontpath ] [ -XpFile file ] [ -XpSpoolerType spoolername ] [ : display ]

: display

The X server runs on the given display. If multiple X servers are to run simultaneously on a host, each must have a unique display number. Note that the standard X server (for video displays) typically runs on display :0

Example: To start an Xprint Server on display 99:
%Xprt :99

-fp fontpath

sets the search path for fonts. This path is a comma separated list of directories which Xprt searches for font databases.

Example:

%Xprt :99 -fp \
/usr/X/lib/X11/fonts/TrueType/,\
/usr/X/lib/locale/zh/X11/fonts/TrueType/ &

For more information about how to setup an Xprint Server, please refer to http://xprint.mozdev.org/docs/Xprt.html or refer to the man page ( "man Xprt" command on Solaris )

---

How to print web pages with non-western fonts from Mozilla.

---

Pages containing non-western fonts may not always print correctly, using TrueType printing will solve this problem.

What's TrueType printing?

Mozilla uses the FreeType library to translate True Type fonts into CID type 1 fonts. It then embeds the CID Type 1 font into the postscript file.

How to set up TrueType printing?

The paths for each font set need to be in the solaris.js file located :
defaults/pref/solair.js

You can add a path to search for new True Type fonts to the solaris.js file.

Below are the default settings

pref("font.directory.truetype.1", "/usr/X/lib/locale/zh/X11/fonts/TrueType");
pref("font.directory.truetype.2", "/usr/X/lib/locale/zh.GBK/X11/fonts/TrueType");
pref("font.directory.truetype.3", "/usr/X/lib/locale/zh_CN.EUC/X11/fonts/TrueType");
pref("font.directory.truetype.4", "/usr/X/lib/locale/zh_CN.GB18030/X11/fonts/TrueType");
pref("font.directory.truetype.5", "/usr/X/lib/locale/zh_TW/X11/fonts/TrueType");
pref("font.directory.truetype.6", "/usr/X/lib/locale/zh_TW.BIG5/X11/fonts/TT");

To add a new font path use the same format:
pref("font.directory.truetype.<number>", "<path/ folder location>");

I.E. for Korean
pref("font.directory.truetype.7", "/usr/X/lib/locale/ko/X11/fonts/TrueType ");

NOTE: This feature requires freetype2 library support.
Make sure you have FreeType installed and the path for "libfreetype.so" is available to the system.

If Mozilla can't find the libfreetype.so add the path:
export LD_LIBRARY_PATH=<location of libfreetype.so >

---

What do I do if Mozilla hangs, freezes, crashes or exits unexpectedly?

---

If Mozilla hangs, crashes or exits unexpectedly you can take the following steps to assist us in solving the problem:

The first is to provide us with a truss output.

To obtain a truss output:

1. Exit Mozilla
2. Open a terminal window and type: truss -fo /tmp/moz_out mozilla
3. Reproduce the hang, freeze or crashes. If mozilla crashes or exits unexpectedly, go to step 6. If mozilla hangs or freezes, go to the next step.
4. Go to the window where you launched Mozilla and hit Control-C.
5. If the above command does not kill Mozilla, open a terminal window and type:
   pkill mozilla&
6. Send the truss output file through our feedback form or post the file and tell us where we can get it.

If Mozilla crashes, you also need to provide us with a core dump file.

Note: Only Sun's supported release of Mozilla can do this the community versions cannot.

The core dump file contains all the process information pertinent to debugging: contents of hardware registers, process status, and process data.

When a process crashes, the operating system writes out the core dump file to the directory from which Mozilla was launched. Sometimes the core dump file cannot be saved to disk.

There are two reasons it may not be saved:

1. The process does not have write permission to the directory from which Mozilla was launched
   
   Solution: Launch Mozilla from a directory for which you have write permission.
2. The core dump file exceeds the default permitted maximum size.
   
   Solution: Remove the file size limit using: 'ulimit -c unlimited'.

If you can save a core dump file, send it to us directly at our feedback form or let us know where we can get it. Be sure to include your complete platform information obtained using the command 'uname -a'

If you cannot send the core file, you can examine the file and send us the results instead. Solaris OS has the following tools that can be used to examine the core file:

/usr/bin/pstack ./core
/usr/bin/pmap ./core
/usr/bin/pldd ./core

Send the output in plain text format to our feedback form

 

---

Mozilla - debug option

---

While it has limitations, running Mozilla with the debug switch may be helpful to administrators in diagnosing problems. Some error/warning messages which do not show in normal mode will be displayed in two scripts: debuginfo.sh and checkpatches.sh will run if you launch mozilla with '-debug'. debuginfo.sh prints out some system info and checkpatches.sh checks if all the patches mozilla needed have been installed.

Example:

bash-2.05$ /mozilla/mozilla -debug
------- Running Mozilla 1.7 debug mode-------
USER: robin
HOSTNAME: eri0 = dart
IP ADDRESS: eri0 = 129.158.217.225
HOSTNAME: eri0 = dart
IP ADDRESS: eri0 = 129.158.217.225
ARCH: sparc
FRAME BUFFER(S): unknown
SunOS RELEASE: 5.9
KERNEL ID: Generic_112233-12
MEMORY: 256MB
SWAP: 0.0MB total, 0.0MB used, 0.0MB available
LOAD AVERAGE:19,  1 user,  :0.05, 0.01, 0.02
DNS DOMAINNAME:
ETHERNET ADDRESS: 0:3:ba:5b:97:f5
HOSTID: 835b97f5

Checking for recommended patches ...

** (mozilla-bin:10798): WARNING **: Size mismatch when converting text from input method: supplied length = 8 , result length = 6
** (mozilla-bin:10798): WARNING **: Size mismatch when converting text from input method: supplied length = 8 , result length = 6
** (mozilla-bin:10798): WARNING **: Size mismatch when converting text from input method: supplied length = 8 , result length = 6

.

---

Manually Implementing a Profile Server

---

This document assumes that you are implementing a Profile Server on a dedicated server, rather than on an existing server. We recommend using a dedicated Profile Server because it provides increased performance and minimizes interaction with other applications. This document provides instructions on how to implement Profile Server on either a Java Enterprise Web Server (version 6.1 or later) or a Java Enterprise Directory Server (versions 5.2). Since Profile Server does not rely on any proprietary features of Java Enterprise servers, other servers may work, but they have not been tested by Sun.

Which server type do I want to use?

You can store profile data on an HTTP, FTP or LDAP server. The server type you choose is largely based on your existing infrastructure and the need for administrative control over profile data. HTTP and FTP are relatively easier to setup, but do not have all of the administration features that LDAP has.

---

How do I Setup a HTTP Profile Server?

---

Enable "Remote File Manipulation" for the HTTP Profile Server.

1. Start your Administration Server and navigate to the the Administration Server page.
2. Change to the "Class Manager" view.
3. Click Content Mgmt tab.
4. Choose "Remote File Manipulation" in the left pane.
5. Check the Yes item below the label with "Activate file manipulation commands".
6. Apply the change.

Add rules for users of Profile Roaming

1. Change to the "Server Manager" view.
2. Click "Preferences" tab.
3. Choose "Restrict Access" in the left pane.
4. Edit the ACL file by adding access control rules
   Note: be sure that the user has the privilege to access their directory where roaming access files are stored.

---

How do I setup a LDAP Profile Server

---

1. Stop the Directory Server.

2. Add the Profile Server schema, shown in listing below, to your LDAP Server.
   NOTE: Java Enterprise LDAP Server includes the schema by default.

show schema

# ns-mcd-li-schema.conf
#
# Profile Server schema
#

attribute nsLIPtrURL	2.16.840.1.113730.3.1.399	ces
attribute nsLIPrefs	2.16.840.1.113730.3.1.400	ces
attribute nsLIProfileName	2.16.840.1.113730.3.1.401	cis
attribute nsLIData	2.16.840.1.113730.3.1.402	bin
attribute nsLIElementType	2.16.840.1.113730.3.1.403	cis
attribute nsLIServerType	2.16.840.1.113730.3.1.404	cis
attribute nsLIVersion	2.16.840.1.113730.3.1.405	integer
attribute nsServerPort	2.16.840.1.113730.3.1.280	cis

objectclass nsLIPtr
oid 2.16.840.1.113730.3.2.74
requires
objectclass
allows
nsLIPtrURL,
owner

objectclass nsLIProfile
oid 2.16.840.1.113730.3.2.75
requires
objectclass,
nsLIProfileName
allows
nsLIPrefs,
uid,
owner

objectclass nsLIProfileElement
oid 2.16.840.1.113730.3.2.76
requires
objectclass,
nsLIElementType
allows
owner,
nsLIData
nsLIVersion

objectclass nsLIServer
oid 2.16.840.1.113730.3.2.77
requires
objectclass,
serverhostname
allows
description,
cn,
nsServerPort,
nsLIServerType,
serverroot


3. Restart the Directory Server.
   
4. Create a root entry under which you will store the profiles. You can store all the User Profiles under a single root entry this simplifies the setup and management of Profile Roaming. The root entry that you create can contain any object class, although you would typically include the object class "orgazinationalUnit"
   
5. Set access controls for the root profiles entry, granting users both read and write access to the entry and its sub nodes. Read access lets users copy their profile data down to a local computer. In this way, you can use a single access control rule to grant authenticated access to all users, such as that shown in below.
   
   Example: (target="ldap:///ou=Roaming,o=mcom.com")(targetattr!="nsLIPrefs")(version 3.0; acl "Roaming"; allow (all) userdnattr ="owner"; )
   
6. Depending on what server you're using, you might also be able to set this ACL using a separate administrative tool.
   
7. Under the profiles root, create a profile for each user by creating a nsLIProfile entry. Below shows an example of an LDIF that you can use to create a profile entry for a user called pete.
   

   Example:
   dn: nsLIProfileName=pete,ou=Roaming,o=myCompany
   changetype: add
   objectclass: top
   objectclass: nsLIProfile
   nsLIProfileName: pete
   owner: uid=pete,ou=People,o=myCompany

8. Create user entries that Browser will authenticate users against. You can create new entries for users, as in listing below, or you can replicate user entries from the corporate directory to the Profile server (recommended).
   

   Example:
   dn: uid=pete,ou=People,o=myCompany
   changetype: add
   objectclass: top
   objectclass: inetOrgPerson
   cn: pete
   userpassword: myPassword

---

Profile Roaming Preferences

---

Profile Server includes a set of new Browser preferences that you can use to control many aspects of the feature. For example, you can set or lock preferences to enable the feature, set the location of the Profile server or corporate directory, define what files users are permitted to transfer to and from the server, and so on.

Profile Roaming preferences can be set in two places:

1. On the Profile server, using Profile Server Control 
2. In Browser's Preferences window (set by the user)

The browser stores all Profile Server preferences in special file: "prefs.js" in the active user profile, along with other user preferences that are served through Profile Server.

The following table gives a full list of Profile Server preferences you can set. Note that if you are setting preferences on the server using Profile Server Control, you do not need to work with preferences directly. Instead, you can use the graphical user interface of the Profile Server Console.

Preference Setting	What file the preference lets you allow or disallow to transfer.
roaming.files.abook.mab	Address book
roaming.files.history.mab	Collected address book
roaming.files.bookmarks.html	Bookmarks
roaming.files.cookies.txt	Cookies
roaming.files.cookperm.txt	Cookie permissions
roaming.files.history.dat	Browser history
roaming.files.mimeTypes.rdf	Help Application Setting
roaming.files.panels.rdf	Sidebar panel list
roaming.files.localstore.rdf	Windows setting
roaming.files.liprefs.js	User preference
roaming.files.mailViews.dat	Mail view setting
roaming.files.training.dat	Junk mail filter
roaming.files.filter	Mail filters
	Note: You can also use the graphical user interface of the Profile Server Console.

Note: Some files have a tendency to become large such as address book, browser history.
If the transfer of this file adversely affects network performance, consider setting this preference to false on server side.

---

Advanced Features

---

Profile Server also supports the following features:

1. Replication - For greater performance and data integrity, Profile Roaming is compatible with replicated LDAP servers. Simply point the Browser client to a replicated server; writing to the master server is handled automatically. (You can used the DNS round-robin technique to distribute load across replicated servers)
   
2. Server Side Preferences - When reading a LDAP profile entry for Profile Roaming, The browser can also pull down preferences set by an administrator in the nsLIPrefs attribute

---

Plugins

---

Plugin installation instructions

Download plugins, and install in Mozilla's plugin directory

Mozilla's plugin directory

1) The default plugins directory is in <Mozilla installation directory>/plugins
2) The default user plugins directory is in $HOME/.mozilla/plugins
3) The user defined plugin directory could be set by an environment variable "env: MOZ_PLUGIN_PATH"
For example "export MOZ_PLUGIN_PATH=~/download/plugins"

Java

Real Player

Macromedia Flash

Adobe Acrobat Reader

---

How do I use the "about:" command?

---

Mozilla contains many hidden commands. The following are some of the available commands in Mozilla 1.7

about:	Displays the about Mozilla page containing copyright and version information
about:about	Complete "about:" commands list
about:buildconfig	Build platform, Build tools, & Configure arguments information
about:cache	Memory cache device, Disk cache device
about:config	Detailed configuration information
about:plugins	Detailed plugin information

 

---