Bug 155246 - Error When Viewing Documentation with Nautilus
Error When Viewing Documentation with Nautilus
Status: CLOSED WONTFIX
Product: Fedora Legacy
Classification: Retired
Component: nautilus (Show other bugs)
rhl7.3
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Fedora Legacy Bugs
DEFER
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2005-04-18 10:54 EDT by William Makowski
Modified: 2007-04-18 13:23 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-08-13 10:22:08 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)

  None (edit)
Description William Makowski 2005-04-18 10:54:46 EDT
Description of problem:
After a recent yum update to RHL 7.3 from fedora legacy I now receive errors 
when using the standard launcher to view documentation with nautilus. The error 
reads, "The Web Page view encountered an error while starting up."

Version-Release number of selected component (if applicable):

nautilus 1.0.6-16
nautilus-mozilla 1.0.6-16
mozilla 1.4.3-0.7.1.legacy

How reproducible:
Use the standard launcher to view documentation with nautilus.  The launcher 
properties are as follows...

Name: Help
Comment: Documentation
Command: nautilus --no-default-window --no-desktop ghelp:toc
Type: Application

Actual results:
Message box pops up with "The Web Page view encountered an error while starting 
up."  No documentation displayed.

Expected results:
Documentation viewable from nautilus.

Additional info:

Using google I found that this error has been reported on different mailing 
lists.  It appears to be an incompatibility issue between versions of nautilus, 
nautilus-mozilla, mozilla.
Comment 1 Pekka Savola 2005-11-16 08:24:05 EST
This doesn't seem to be important enough to fix just on its own, so mark it DEFER.
Comment 2 Jesse Keating 2006-08-13 10:22:08 EDT
Not a security issue.

Note You need to log in before you can comment on or make changes to this bug.