Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 430988 - Firefox asks to be the default browser
Firefox asks to be the default browser
Product: Fedora
Classification: Fedora
Component: firefox (Show other bugs)
All Linux
low Severity low
: ---
: ---
Assigned To: Gecko Maintainer
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2008-01-30 17:48 EST by Julian Sikorski
Modified: 2008-02-08 10:29 EST (History)
0 users

See Also:
Fixed In Version: 3.0-0.beta2.16.nightly20080206.fc9
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-02-08 10:29:36 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Julian Sikorski 2008-01-30 17:48:45 EST
Description of problem:
Although Firefox is set as default browser in System -> Preferences -> Personal
-> Preferred Applications, it asks to be the default browser every time it is
run. What is the issue, is that it sets the following value:
/usr/lib64/firefox-3.0b3pre/firefox "%s"
which causes the plugins to be not detected

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

How reproducible:

Steps to Reproduce:
1. Install the said version of firefox
2. Run it using htmlview
3. Answer yes to the question about making firefox the default
Actual results:
A non-working command is set

Expected results:
A working command is set, or even better, firefox respects the gnome settings

Additional info:
This can be related to a recent xulrunner or nss update, since I remember
everything was working fine a while ago. I am running Fedora 8 if that matters,
only firefox and required deps are from rawhide.
Comment 1 Christopher Aillon 2008-01-31 14:54:42 EST
I just committed something which ought to fix this next time we do a build (in
the next few days).

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