568103 - 'Open Containing Folder' button does not work but throws exception

Status: RESOLVED INCOMPLETE

(Firefox :: General, defect)

Description

[Deepak Kumar Vasudevan]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.3) Gecko/20100401 Firefox/3.6.3
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.3) Gecko/20100401 Firefox/3.6.3

The 'Open Containing Folder' button in about:support does not work but throws an exception as follows:

Error: uncaught exception: [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsILocalFile.reveal]"  nsresult: "0x80004005 (NS_ERROR_FAILURE)"  location: "JS frame :: about:support :: openProfileDirectory :: line 351"  data: no]

Reproducible: Always

Steps to Reproduce:
1. Type about:support
2. Navigate to 'Application Basics' section
3. Locate 'Profile Directory' head and click 'Open Containing Folder' button
Actual Results:  
Logs the following error in Errorconsole:



Error: uncaught exception: [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsILocalFile.reveal]"  nsresult: "0x80004005 (NS_ERROR_FAILURE)"  location: "JS frame :: about:support :: openProfileDirectory :: line 351"  data: no]

Expected Results:  
A windows explorer should open with the path of the profile folder auto-navigated.

Comment 1

[Tyler Downer [He/Him]]

Reporter, are you still seeing this issue with Firefox 3.6.13 or later in safe mode? If not, please close. These links can help you in your testing.
http://support.mozilla.com/kb/Safe+Mode
http://support.mozilla.com/kb/Managing+profiles

You can also try to reproduce in Firefox 4 Beta 8 or later, there are many improvements in the new version, http://www.mozilla.com/en-US/firefox/all-beta.html

Comment 2

[Martijn Wargers (dead)]

I guess this can happen if fexplorer.exe is not there where it should be expected, or something like that.

Comment 3

[Tyler Downer [He/Him]]

No reply, INCOMPLETE. Please retest with Firefox 3.6.13 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.