File: FAQ.html

package info (click to toggle)
galeon 2.0.2-4
links: PTS
area: main
in suites: etch, etch-m68k
size: 19,212 kB
ctags: 9,891
sloc: ansic: 77,793; cpp: 15,301; sh: 8,961; xml: 5,761; makefile: 888
file content (698 lines) | stat: -rw-r--r-- 25,136 bytes
parent folder | download | duplicates (5)
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">

<!--
The text file version of the FAQ is generated with html2text
by running "html2text -nobs -rcfile FAQ.html -o FAQ FAQ.html".

http://userpage.fu-berlin.de/~mbayer/tools/

Obviously this tool is no more mantained ;)

.html2textrc:

A.attributes.internal_link = NONE
A.attributes.external_link = NONE
B.attributes = NONE
H4.attributes = NONE
H4.prefix =
H4.suffix =
H4.vspace.after = 1
OL.vspace.before = 3
OL.vspace.after = 3
OL.vspace.between = 1

-->

<html>

<head>
  <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  <title>Galeon Frequently Asked Questions</title>
</head>


<body>


<h2>Galeon Frequently Asked Questions</h2>

<p>The following questions come up often on IRC and in the mailing lists.
If you have any suggestions for this file, such as additional questions or
answers, please mail them to the galeon-devel mailing list at <a
href="mailto:galeon-devel@lists.sourceforge.net">galeon-devel@lists.sourceforge.net</a>.</p>


<h3>Index</h3>
<ol>

<li><a href="#gtkmozembed">I'm trying to compile Galeon and it needs
<tt>gtkmozembed.h</tt>.  Where is it?</a></li>

<li><a href="#crash">Galeon crashes when I go to page X.</a></li>

<li><a href="#assertion">When starting Galeon, I immediately get an
assertion error.  What does this mean?</a></li>

<li><a href="#scrollwheel">How can I get my scrollwheel mouse to work with
Galeon?</a></li>

<li><a href="#gnome">Why does Galeon depend on GNOME?  There should be a
GTK+ only version!</a></li>

<li><a href="#ld-errors">I can't compile Galeon.  I get ld errors such as
this: <tt>/usr/include/mozilla/nsCOMPtr.h:552: undefined reference to
`nsCString type_info node'</tt>.  Help!</a></li>

<li><a href="#ld-errors2">I compiled Galeon and Mozilla but I still get ld
errors.</a></li>

<li><a href="#memory">Galeon is using 80MB+ of memory!  What's going
on?</a></li>

<li><a href="#crash-startup">Galeon segfaults on startup.  What's
wrong?</a></li>

<li><a href="#crash-prefs">Galeon segfaults when opening the preferences
dialog.  What's wrong?</a></li>

<li><a href="#killed-still-running">Galeon claims that it crashed the last
time it was run, but it's currently running!  Can't I run two copies at
once?</a></li>

<li><a href="#https">Galeon hangs when I try accessing my secure
banking/intranet site.  Doesn't Galeon support https?</a></li>

<li><a href="#shortcuts">These keyboard shortcuts are all wrong!</a></li>

<li><a href="#default-browser">I want / don't want Galeon to be my default
web browser.</a></li>

<li><a href="#configure-error">How can I fix this syntax error during
configure?</a></li>

<li><a href="#gconf">When I run Galeon I get a message about gconf not
configured properly. How can I configure gconf?</a></li>

<li><a href="#gconf-lose-prefs">After the migration to gconf I occasionally
lose all/part of my prefs, they get back to defaults. Why? What can i do
about it?</a></li>

<li><a href="#help-browser">What do I need to use Galeon as my help
browser?</a></li>

<li><a href="#user-agent">How can I change the User Agent string that
Galeon uses?</a></li>

<li><a href="#load-not">Galeon is running but is not showing any
window/unable to load anything. What can i do?</a></li>

<li><a href="#nauti-oaf">I have compiled Galeon with nautilus-view support
and it doesn't work!</a></li>

<li><a href="#plugins">What's wrong with plugins in Galeon?  Can Galeon
only handle HTML?</a></li>

<li><a href="#international-characters-in-titles">Galeon doesn't display
international characters in titles correctly.</a></li>

<li><a href="#java">How do I get Java working in Galeon?</a></li>

<li><a href="#mime">I've configured MIME type X to be handled with
application Y, but it's being handled by Z instead, or multiple instances
of the helper application are being started.</a></li>

</ol>


<h3>Questions and Answers</h3>
<ol>

<li><a name="gtkmozembed">
<b>I'm trying to compile Galeon and it needs gtkmozembed.h.  Where is
it?</b></a>

<p>This header is part of Mozilla, and you need to either install the
Mozilla source or find a Mozilla-devel package containing the appropriate
headers.  This also applies for <tt>nsI*.h</tt>.  These steps are described
in detail on the <a href="http://galeon.sourceforge.net/">website</a> and
in the <tt>INSTALL</tt> file.</p>
</li>



<li><a name="crash">
<b>Galeon crashes when I go to page X.</b></a>

<p>First, try updating to a newer version.  If the problem persists, try
visiting the same page in Mozilla.  If Mozilla crashes as well, your
problem is likely a Mozilla bug.  It can be reported at <a
href="http://bugzilla.mozilla.org/">http://bugzilla.mozilla.org/</a>.  If
the crash only occurs in Galeon, please file a bug report (after checking
for duplicates) at the GNOME bugzilla site (reachable via
<b>Help-&gt;Report a bug</b>, or at <a
href="http://bugzilla.gnome.org/">http://bugzilla.gnome.org/</a>).</p>
</li>



<li><a name="assertion">
<b>When starting Galeon, I immediately get an assertion error.  What
does this mean?</b></a>

<p>The assertion usually looks like:</p>

<pre>
** CRITICAL **: file mozilla.cpp: line 64 (gboolean mozilla_load_prefs ()):
assertion `prefService != nsnull' failed.
</pre>

<p>If this happens, it usually means there is a problem or incompatibility
with your Mozilla installation.  Try manually exporting/setting your
<tt>MOZILLA_FIVE_HOME</tt> environment variable and then executing
<tt>galeon-bin</tt>.  This is known to work sometimes, but it's also known
to not work for some users (Debian installations in particular).</p>

<p>Another time when this has been known to happen is when the Mozilla has
been updated/changed with old lingering user files that (for some reason)
are causing problems.  Removing Mozilla user files (<tt>rm -rf
~/.mozilla"</tt>) and/or removing Galeon's Mozilla profile files (<tt>rm
-rf ~/.galeon/mozilla/galeon</tt>) may fix this problem.  Be sure to back
up any important files in these directories (such as Mozilla bookmarks,
preferences, etc.) if necessary.</p>
</li>



<li><a name="scrollwheel">
<b>How can I get my scrollwheel mouse to work with Galeon?</b></a>

<p>Galeon supports scrollwheel mice natively.  If your other applications
work fine with the wheel and Galeon does not, it could be because other
programs (such as Imwheel) are interfering.  However, even with Imwheel the
wheel can still be used if the wheel is pushed down while scrolled (I'm not
sure why, and this may only be true for Logitech mice).</p>

<p>If your wheel doesn't work at all for any applications, you probably
need to configure your X server.  For XFree86, this can be done by adding
the line <tt>ZAxisMapping 4 5</tt> to the <tt>Pointer</tt> (mouse) section
of <tt>XF86Config</tt>.</p>

<p>If you still want to use imwheel for the wheelmouse support in other
applications, you can place the following two lines in your
<tt>~/.imwheelrc</tt> file and restart imwheel to tell it not to interfere
with Galeon:</p>

<pre>
"^Galeon"
@Exclude
</pre>
</li>



<li><a name="gnome">
<b>Why does Galeon depend on GNOME?  There should be a GTK+ only
version!</b></a>

<p>First of all, from the very start Galeon has always intended to be a
GNOME web browser.  If you don't use GNOME, then Galeon probably isn't a
very good choice for the time being.</p>

<p>So why lock Galeon into the GNOME environment?  There are many
advantages to using the existing GNOME libraries.  Contrary to what some
think, depending on existing libraries to do typical tasks in modern
desktop applications is <b>not</b> bloat.  In fact, it's the exact opposite
of bloat.  The bottom line is that implementing our own toolbar, our own
configuration mechanism, our own session management, and our own dialogs
would be counter-productive.</p>

<p>Galeon relies on many standard GNOME libraries (GTK+, libgnome,
libglade, libxml, etc.).  Given these requirements, how much would we gain
by removing the GNOME dependency?  This is not only illogical, but
conflicts with some of Galeon's other goals of integrating nicely with the
GNOME desktop.</p>

<p>However, if you absolutely don't want to use GNOME, there is now a
project known as <a href="http://www.muhri.net/skipstone/">SkipStone</a>
which implements a GTK+-only web browser.</p>
</li>



<li><a name="ld-errors">
<b>I can't compile Galeon.  I get ld errors such as this
(/usr/include/mozilla/nsCOMPtr.h:552: undefined reference to `nsCString
type_info node'). Help!</b></a>

<p>This is due to the fact that you're trying to compile Galeon and Mozilla
with a different compiler version.  Download the right Mozilla package for
your distribution (take a look at <a
href="http://galeon.sourceforge.net/download.html">http://galeon.sourceforge.net/download.html</a>).</p>
</li>



<li><a name="ld-errors2">
<b>I compiled Galeon and Mozilla but I still get ld errors.</b></a>

<p>Note that both applications must be compiled not only with the same
version of compiler, but also with the same compiler flags.  For example,
with gcc Mozilla by default adds <tt>-fno-rtti</tt> and
<tt>-fno-exceptions</tt> or <tt>-fno-handle-exceptions</tt> (depends on gcc
version).  Galeon now adds <tt>-fno-rtti</tt>, which should be normally be
sufficient. This can be disabled with the <tt>--enable-cpp-rtti</tt> flag
to ./autogen.sh.</p>

<p>If you need further flag changes, you have two chances to get things
in sync:</p>

<ol>
<li>
Compile Mozilla with this .mozconfig script: (You must place it in your home directory) 

<pre>
# sh
# Build configuration script
#
# See http://www.mozilla.org/build/unix.html for build instructions.
#

# Options for 'configure' (same as command-line options).
ac_add_options --disable-tests
ac_add_options --disable-debug
ac_add_options --enable-strip-libs
ac_add_options --enable-crypto
ac_add_options --enable-optimize
</pre>
</li>

<li>
<p>Configure Mozilla with standard configure script and compile it.  Before
configuring Galeon set the proper <tt>CXXFLAGS</tt>. For example, with
latest version of gcc:</p>

<pre>
CXXFLAGS='-fno-exceptions'
export CXXFLAGS
</pre>

<p>For more see <a
href="http://lxr.mozilla.org/seamonkey/source/configure.in">configure.in</a>
in the Mozilla source.  You can save some space by disabling RTTI.</p>
</li>
</ol>
</li>



<li><a name="memory">
<b>Galeon is using 80MB+ of memory!  What's going on?</b></a>

<p>On Linux systems, threads are essentially visible as separate processes to
many user-space applications.  This means that process X, using 10MB of
memory with 5 threads sharing that same 10MB will appear to consume 50MB
(though it is not).  Only count one process, not all of them (this is true
for many other applications besides Galeon).</p>
</li>



<li><a name="crash-startup">
<b>Galeon segfaults on startup.  What's wrong?</b></a>

<p>Make sure the <tt>MOZILLA_FIVE_HOME</tt> environment variable points to
the directory where the Mozilla executables are installed.  If Mozilla is
compiled from source, try <tt>[mozilla_build_dir]/dist/bin</tt>.</p>
</li>



<li><a name="crash-prefs">
<b>Galeon segfaults when opening the preferences dialog.  What's
wrong?</b></a>

Run Galeon from an xterm and check if you get this message:

<pre>
GnomeUI-ERROR **: file gnome-icon-item.c: line 304 (get_default_font):
assertion failed: (default_font != NULL)
</pre>

If so you need to properly set your language environment.  Example:

<pre>
export LANG=de_DE
</pre>
</li>



<li><a name="killed-still-running">
<b>Galeon claims that it crashed the last time it was run, but it's
currently running! Can't I run two copies at once?</b></a>

<p>This problem has been observed with out of date versions of Oaf (including
0.6.1). Upgrade to 0.6.5 (availble from Ximian).</p>

<p>This can also be caused by the GNOME_Galeon_Automation.oaf file not being
installed in a place that oaf can look for it.</p>

<p>If you've compiled Galeon from a source tarball, chances are it's
installed it in <tt>/usr/local/share/oaf/GNOME_Galeon_Automation.oaf</tt>.
However, oaf isn't searching this directory, so when you start another
copy, oaf tells Galeon that it isn't running and it doesn't know to
attach.</p>

<p>To fix this, make a symlink called
<tt>/usr/share/oaf/GNOME_Galeon_Automation.oaf</tt> which links to
<tt>/usr/local/share/oaf/GNOME_Galeon_Automation.oaf</tt>, or alternatively
add <tt>export OAF_INFO_PATH=/usr/local/share/oaf</tt> (for sh scripts) or
<tt>setenv OAF_INFO_PATH /usr/local/share/oaf</tt> (for csh scripts) to
your shell startup.  If the <tt>GNOME_Galeon_Automation.oaf</tt> file is
being installed into a different directory, you will have to use that
instead.  When you start Galeon twice, it should attach and open a new
window/tab in the existing process.  You may need to restart your X session
and/or gconfd (<tt>gconftool --shutdown</tt>) and oafd (<tt>killall
oafd</tt>) for the changes to take effect.</p>

<p>Another possibility is that the value of the <tt>DISPLAY</tt>
environment variable differs in the two locations from which Galeon is
being started.  Frequently, <tt>DISPLAY</tt> will be set to <tt>:0</tt> in
the window manager, but to <tt>:0.0</tt> in terminals.  One way to work
around this is to set the variable to <tt>:0.0</tt> in your X startup
script (usually <tt>~/.xsession</tt> or <tt>~/.xinitrc</tt>), by adding the
line <tt>export DISPLAY=:0.0</tt> (for sh scripts) or <tt>setenv DISPLAY
:0.0</tt> (for csh scripts).</p>
</li>



<li><a name="https">
<b>Galeon hangs when I try accessing my secure banking/intranet site?
Doesn't Galeon support https?</b></a>

Yes, Galeon does support https (as long as you have the Mozilla PSM module
configured / installed).   Just make sure you installed mozilla-psm
properly.
</li>



<li><a name="shortcuts">
<b>These keyboard shortcuts are all wrong!</b></a>

<p>If you want to rebind a shortcut, Galeon supports the standard GTK+ way
of changing shortcuts: simply hover over the menu option with the mouse
pointer and press the keyboard shortcut you want to rebind it to.<p>
</li>



<li><a name="default-browser">
<b>I want / don't want Galeon to be my default web browser.</b></a>

When Galeon is first used, it asks you if you want to make it the default
web browser in GNOME. This setting is stored in the GNOME Control Center
under <b>Document Handlers / URL Handlers</b>. To stop Galeon from being
the default web browser, delete the association with HTTP, HTTPS and
whichever other protocols you set it up for. To make Galeon the default
Web Browser, add a binding from these protocols to <tt>galeon "%s"</tt>.
</li>



<li><a name="configure-error">
<b>How can I fix this syntax error during configure?</b></a>

<pre>
    ./configure: line 538: syntax error near unexpected token `AM_INIT_AUTOMAKE(galeon,'
</pre>

Make sure you have xml-i18n-tools installed and try again.
</li>



<li><a name="gconf">
<b>When I run Galeon I get a message about GConf not being configured
properly. How can I configure GConf?</b></a>

<p>First and foremost, be sure you have a new GConf (1.0.7 is the latest at
this writing) rather than an old one. In particular, 1.0.4 is too old and
causes problems.</p>

<p>If you do <tt>ps jaxwww | grep gconf</tt> and see two <tt>gconfd-1</tt>
processes, that's what's wrong; just kill them both and restart Galeon.
This problem has not been reported with GConf 1.0.7, only older
versions.</p>

<p>If you have trouble with 1.0.7, most likely it's because your home
directory is NFS-mounted and either your operating system doesn't support
locks in NFS directories or you have stuck locks due to a hard system
crash. Try <tt>rm -r ~/.gconf*/*lock</tt> if you are <b>sure</b> you have
no gconfd processes (for your login name) running on any machine using your
NFS home directory. If you nuke the lock when gconfd is running and bad
stuff happens, it's your own fault. ;-)</p>

<p>If you want to use GConf while logged in from two different machines,
sharing the same home directory, you must enable TCP/IP for ORBit by adding
the line <tt>ORBIIOPIPv4=1</tt> to <tt>/etc/orbitrc</tt> and restart
gconfd. You will need to do this on <b>both</b> machines; one machine will
contact the gconfd running on the other.  This setup is poorly tested but
should work.</p>

<p>It's possible schema installation failed when you installed Galeon, so
you can try reinstalling them as follows:</p>

<pre>
GCONF_CONFIG_SOURCE=`gconftool-1 --get-default-source`  \
gconftool-1 --makefile-install-rule /etc/gconf/schemas/galeon.schemas
</pre>

<p>Be sure your GConf config file is set up correctly by editing the
<tt>path</tt> file in the directory <tt>$sysconfdir/gconf/1</tt>.  A basic
configuration for the default backend would look like:</p>

<pre>
xml:readonly:/etc/gconf/gconf.xml.mandatory
include "$(HOME)/.gconf.path"
xml:readwrite:$(HOME)/.gconf
xml:readonly:/etc/gconf/gconf.xml.defaults
</pre>

<p>You can also take a look at <tt>$sysconfdir/gconf/1/path.example</tt>
and in most cases you can simply move it to
<tt>$sysconfdir/gconf/1/path</tt>.  Be sure that the path file can be read
by all users.</p>

<p>Ensure you have a <tt>$sysconfdir/gconf/gconf.xml.defaults</tt> dir set
up with the right permissions. In most cases you can run <tt>chmod -R 755
$sysconfdir/gconf/gconf.xml.defaults</tt>.</p>

<p><b>WARNING:</b> The GConf deamon makes heavy use of a cache so when
changing your setup you will probably need to restart it.</p>

<p>Be sure you have no applications depending on gconf running and then
run:</p>

<pre>
gconftool --shutdown
</pre>

<p>GConf will then restart when it is required.</p>

<p>If none of the above works, enable user syslogging and see if gconf is
logging any error messages. On Linux, to do this try adding this line to
<tt>/etc/syslog.conf</tt>:</p>

<pre>
user.*   /var/log/user
</pre>

<p>then run <tt>service syslog restart</tt>, reproduce your gconf problem, and
look in <tt>/var/log/user</tt> for messages. If gconf is failing to get a
lock then the issue is probably the NFS thing mentioned earlier.  Otherwise
maybe there are other informative error messages.</p>

<p>If you still can't figure it out, try mailing <a
href="mailto:gconf-list@gnome.org">gconf-list@gnome.org</a>, describing
what happened when you tried all of the above and what version of gconf you
have, what exact error messages you get, etc.</p>
</li>



<li><a name="gconf-lose-prefs">
<b>After the migration to gconf i occasionally lose all/part of my
prefs, they get back to defaults. Why? What can i do about it?</b></a>

<p>We still don't know why.  Any insight on this will be highly appreciated.
We believe its a gconf glitch.</p>

<p>When the Galeon with apparently messed-up prefs starts, and you are sure
you did set all your prefs right the previous session, go to a terminal
window and run <tt>killall gconfd-1</tt>.  After restarting Galeon, your
prefs should be back to normal.
</li>



<li><a name="help-browser">
<b>What do I need to use Galeon as my help browser?</b></a>

<p>Galeon uses external conversion programs to render all info and man
content as HTML. Thus, these programs have to present if info and man pages
are to be viewed. We use <tt>gnome-man2html2</tt> and
<tt>gnome-info2html2</tt> which are part of the Nautilus package. So, if
you don't have Nautilus installed, you won't have these programs. We know
that there will be plenty of people who haven't got Nautilus installed, so
we're going to put together a separate package for the conversion programs,
hopefully pretty soon. :-)</p>

<p>The new style of SGML help documents (gnome-help:, so far only supported
by nautilus itself) require gnome-db2html2 from Nautilus.</p>

<p>The normal GNOME help documents, which are regular HTML files (and
accessed through the ghelp: protocol), do not require an external
converter.</p>

<p>The toc: pages (toc:, toc:man, toc:info, toc:ghelp, toc:gnome-help) also
don't require anything special.</p>
</li>



<li><a name="user-agent">
<b>How can I change the User Agent string that Galeon uses?</b></a>

<p>This feature is already implemented. It is not in the UI because there
was a Mozilla bug that made Galeon crash at startup with some
strings.</p>

<p>You can set the user agent from the command line using GConf:</p>
<ol>
<li><p>To get the current user agent:</p>
<pre>gconftool -g /apps/galeon/Advanced/Network/user_agent</pre></li>
 
<li><p>To set the user agent to <tt>XXX</tt>:</p>
 <pre>gconftool -s /apps/galeon/Advanced/Network/user_agent --type=string "XXX"</pre></li>

<li><p>To restore the default user agent:</p>
<pre>gconftool -s /apps/galeon/Advanced/Network/user_agent --type=string default</pre></li>
</ol>
</li>



<li><a name="load-not">
<b>Galeon is running but is not showing any window/unable to load
anything. What can i do?</b></a>

<p>Galeon needs to run once as the user that owns the Mozilla distribution
directory, because Mozilla wants to write some files there.</p>
</li>



<li><a name="nauti-oaf">
<b>I have compiled Galeon with nautilus-view support and it doesn't
work!</b></a>

<p>Make sure that the file <tt>GNOME_Galeon_NautilusView.oaf</tt> is
correctly installed (it shuld be in <tt>/usr/share/oaf</tt> in most setups)
and restart oaf.  Also, you'll have to setup Nautilus to use Galeon to
render HTML, once Galeon has been installed (to do so, you have to select
the <b>View as other...</b> option in the Nautilus view selection
optionmenu).
</li>



<li><a name="plugins">
<b>What's wrong with plugins in Galeon?  Can Galeon only handle
HTML?</b></a>

<p>See the plugins section of the User Manual (plugins.html).
</li>



<li><a name="international-characters-in-titles">
<b>Galeon doesn't display international characters in titles
correctly.</b></a>

<p>The common cause for this is an incorrectly set <tt>LC_CTYPE</tt>
environment variable. You can see this by typing the command
<tt>locale</tt> in a terminal window.</p>

<p>The <tt>LC_CTYPE</tt> variable controls what character set applications
should use for their output. If <tt>LC_CTYPE</tt> is unset or set to
&quot;C&quot;, this essentially means that applications are expected to use
ASCII for their output. The problem is that ASCII doesn't include any
international characters, and hence international characters won't get
displayed correctly, if at all.</p>

<p>You can easily correct this by making sure the <tt>LC_CTYPE</tt>
variable is set to your locale, like <tt>LC_CTYPE=de_DE</tt> if you are in
Germany. This will make sure that applications can correctly display your
native characters. Please note that it will not change the language of the
applications, it only changes the character set used.</p>
</li>



<li><a name="java">
<b>How do I get Java working in Galeon?</b></a>

<p>To use Java in Galeon, you'll need to install a plugin for Mozilla.</p>

<p>You can download the Linux x86 version of Sun's Java Runtime Environment
(JRE) from <a
href="http://java.sun.com/j2se/1.3/jre/download-linux.html">http://java.sun.com/j2se/1.3/jre/download-linux.html</a>.
Once you've installed it, you'll need to create a symbolic link in your
Mozilla plugin directory to the plugin file.  The plugin file is at
<tt>[JRE directory]/plugin/i386/libjavaplugin_oji.so.</tt></p>

<p>If you prefer, you can instead install Sun's Java SDK, or the SDK
offerred at <a
href="http://www.blackdown.org/">http://www.blackdown.org/</a>.  If you're
on a different platform, you may need to use a different vendor's Java
environment.  As long as they provide a Mozilla-compatible plugin, though,
things should still work.</p>

<p>Once you've installed the plugin, it should be visible on the
<tt>about:plugins</tt> page, and if you have the <b>Allow Java</b>
preference enabled, Galeon should be able to run Java applets.</p>
</li>



<li><a name="mime">
<b>I've configured MIME type X to be handled with application Y, but it's
being handled by Z instead, or multiple instances of the helper application
are being started.</b></a>

<p>A likely cause for this is an errant Mozilla preference.  Exit Galeon
and open <tt>~/.galeon/mozilla/galeon/prefs.js</tt> in your favorite text
editor, and look for a line that tells Mozilla how to handle the
problematic MIME type.  If you find such a line, delete it and save the
file.  After doing this, the MIME type should be handled correctly in
Galeon.</p>

<p>It is also possible that the MIME type has been registered by the
Plugger plugin.  Plugger is a wrapper plugin that passes unsupported files
from the browser to external programs.  To check which files are being
handled by Plugger, examine the <tt>/etc/pluggerrc</tt> file.  You can
either edit the file so that Plugger will use different programs, or delete
the offending lines altogether so that Galeon will handle the file types
instead.  For file types that are often embedded in documents (like WAV
sound files or MIDI music files), it may make more sense to use Plugger, as
Galeon is unable to launch helper applications for inline content.  <!--
FIXME: Is this correct? :)  -Dan -->  Please see the Plugger documentation
for more information.</p>
</li>

</ol>

</body>
</html>