Marcelo Duarte Reporter
	Description • 10 years ago

User Agent: Mozilla/5.0 (Windows NT 5.1; rv:35.0) Gecko/20100101 Firefox/35.0
Build ID: 20141111004002

Steps to reproduce:

When opening PDF document after changing the form to open PDF for Adobe Reader, it does not list the application or opening the PDF in Firefox Aurora Developer, the error occurs after upgrading the day 11/10/2014, formerly open normally.


Actual results:


Open the PDF in Firefox only, using the same plugin to open using Adobe Reader in Firefox Aurora Developer, presents no problems.


Expected results:

Open PDF in an external PDF reader program.

	Panos Astithas (he/him) [:past] (please ni?)
	Comment 1 • 10 years ago

Developer Edition is using a separate profile by default. My guess is that the plugin is not installed in this profile. Try running the Adobe Reader installer again.

	Marcelo Duarte Reporter
	Comment 2 • 10 years ago

Yes, actually the "problem" is in profile if I choose the default profile it opens the application, more open without choosing the profile believe he use the dev-edition-default, and not the choice of opening the file outside what is the solution? Delete the profile dev-edition-default?

	Panos Astithas (he/him) [:past] (please ni?)
	Comment 3 • 10 years ago

Developer Edition is really meant to be using its own profile. Did you verify that about:addons doesn't list the Adobe Reader add-on in the dev-edition-default profile?

Using Sync to copy your data from your main profile do your Developer Edition profile should copy all your existing add-ons (make sure you tick the appropriate checkbox). That's the recommended approach, but I think running the Adobe Reader installer again will also install the plugin there.

	Gingerbread Man
	Comment 4 • 9 years ago

(In reply to Panos Astithas [:past] from comment #1)
> Developer Edition is using a separate profile by default. My guess is that
> the plugin is not installed in this profile. Try running the Adobe Reader
> installer again.

Plug-ins are system-wide. They're not profile-specific, unlike extensions.

	Ciprian Muresan [:cmuresan], Ecosystem QA
	Comment 5 • 9 years ago

Since the reporter didn't provide the requested information and I was unable to reproduce this on the latest release(43.0.3) and the latest Nightly(46.0a1), I will mark this issue as RESOLVED INCOMPLETE. If you still encounter this problem, please feel free to reopen this bug, or file a new one.