Bug 365051

Summary: Error message regarding Downloads folder when opening preferences
Product: [Fedora] Fedora Reporter: lexual <lex.lists>
Component: epiphanyAssignee: Gecko Maintainer <gecko-bugs-nobody>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 7CC: mcepl
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-04-10 09:51:12 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description lexual 2007-11-03 09:04:18 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en; rv: Gecko/20071019 Fedora/ Epiphany/2.18 Firefox/

Description of problem:

You are shown an error message stating:

The folder contents could not be displayed
error accessing 'file:///home/lexhider/Desktop/Downloads': File not found

epiphany should be fixed so that this unnecessary error message is no longer seen by an user who enter the preference dialog.

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

How reproducible:

Steps to Reproduce:
1.Enter preferences

Actual Results:

Expected Results:

Additional info:

Comment 1 Matěj Cepl 2008-02-28 16:03:25 UTC
Is this still relevant with the latest upgrade to your distro?

Comment 2 Matěj Cepl 2008-04-10 09:51:12 UTC
Since there are insufficient details provided in this report for us to
investigate the issue further, and we have not received feedback to the
information we have requested above, we will assume the problem was not
reproducible, or has been fixed in one of the updates we have released for the
reporter's distribution.

Users who have experienced this problem are encouraged to upgrade to the latest
update of their distribution, and if this issue turns out to still be
reproducible in the latest update, please reopen this bug with additional